# Women Between Professional Identities — product-line translation

Use this reference after a women-transition Sales Safari has identified a credible segment and Margarita asks how to arrange existing Cosmos Luminosity products.

## Core distinction

Do not present Magic Cloud, AudioBoosts, LumoSide, Portal, Gateways, cacao, bodywork and personal work as equal products on one shelf. Separate:

1. **Customer progression** — recognition → free result → first paid decision → implementation → continuity → premium → live/loyalty.
2. **Tool family** — symbolic, audio/state, knowledge infrastructure, community, embodied and human-guided tools.
3. **Gateways category** — bounded entries with a concrete result; individual modalities can be specific Gateways.

Each level must produce a standalone result. A woman must not have to buy the next level for the previous one to be useful.

## Recommended ladder

### 0. Recognition content

Job: identify the transition without imposing a new identity.

Primary CTA: **Map where you are now.** Do not send cold traffic directly to a membership, premium offer or embodied modality.

### 1. Free orientation

**Transition Check-in → Between Identities Map → optional Magic Cloud.**

The map should show:

- what became too small;
- what the old role has been carrying besides income;
- what remains hers (`Preserve 3`);
- current phase and capacity;
- one useful distinction;
- one reversible test;
- one conversation;
- one evidence question;
- review date.

Show the result before mandatory email capture.

Magic Cloud follows a named question. Its role is an optional symbolic perspective, not prediction, diagnosis, financial reasoning or the decision itself.

### 2. First paid offer

**Gateway: Between Identities** — one transition decision for the next 30–90 days.

Manual MVP:

- check-in/pre-work;
- 90-minute guided session;
- written Transition Architecture within 48 hours;
- 14-day evidence-building period;
- short review.

Core outputs:

- Preserve / Release / Redesign;
- role-function decomposition;
- 2–4 scenarios with reversibility scores;
- life test, market test, body/state observation and key conversation;
- success, stop-loss and review criteria;
- first-week calendar;
- identity narrative draft;
- specialist referrals where appropriate.

Validate through real payment/deposit and manual delivery before creating a self-guided course. Never infer price acceptance from income, title, likes or praise.

### 3. Second paid level

**Between Identities Evidence Cycle** — a four-week implementation container after Gateway.

Job: turn a map into lived evidence. Use one active experiment, weekly check-in, evidence log, phase-specific AudioBoost and final decision review.

AudioBoosts are support objects tied to an action and review question, not an unstructured low-ticket library. Examples: Permission to Pause, After the Title, Keep What Is Yours, Visibility Before Certainty, Return to the Experiment.

### 4. Continuity

**LumoSide** — ongoing private implementation environment after a map, Gateway or screening.

Core loop:

- weekly capacity/state check;
- one active experiment;
- evidence log;
- Preserve monitor;
- body / people / contribution / money rhythm;
- decision journal;
- monthly Transition Review.

Do not sell LumoSide first as a generic women’s space or content membership. Before a concrete transition job, it risks looking like another community/library.

### 5. Infrastructure

**Portal** initially connects maps, Magic Cloud history, AudioBoosts, experiment queues, evidence logs, routes and review dates. It is infrastructure inside paid products/LumoSide before it is a standalone subscription.

Only test a separate self-guided Portal tier after repeated independent use appears.

### 6. Premium

**Private Transition Architecture** for complex, private, high-stakes cases involving founder/leader identity, business, household, money, geography, care and implementation.

Premium is justified by complexity, privacy, human judgment and implementation support—not by more inspiration or a senior title alone.

Possible branches:

- Founder/Leader Separation;
- Portfolio Future Design;
- bespoke Private Transition Architecture.

### 7. Embodied/live/loyalty

- Existing 33-point light-touch practice becomes a clearly named **Body Gateway**, not the definition of the whole Gateways category.
- Cosmos Cacao belongs to ritual, salons, groups, cycle openings/closures and live loyalty experiences; it is not the first answer to a career-identity decision.
- Spazio Dimensioni art may be an optional premium/live artifact, never mandatory proof of outcome.

## Minimum launch set

Activate only:

1. free Check-in + Between Identities Map + optional Magic Cloud;
2. three manually delivered paid Gateway places;
3. one four-week Evidence Cycle offered first to Gateway participants;
4. qualified premium route.

Meanwhile:

- create AudioBoosts from observed implementation blocks;
- let Portal connect the route;
- derive LumoSide loops from repeated Evidence Cycle behaviour;
- keep Body Gateway available locally;
- test cacao in small live formats.

Avoid launching multiple paid Gateways, a broad audio library, a large self-guided course and a full membership simultaneously.

## Evidence discipline

Label separately:

- repeated audience evidence;
- product-design hypothesis;
- price hypothesis;
- validated payment/completion/retention evidence.

Public research can establish language, transitions, objections and adjacent purchases. It cannot establish demand for Gateway, LumoSide or premium without payment behaviour.

## Naming and architecture pitfall

If `Gateways` currently names one touch modality, distinguish:

- **Cosmos Luminosity Gateways** — product family;
- **Body Gateway: [specific outcome]** — embodied modality;
- **Gateway: Between Identities** — first paid decision product.

This prevents one modality from occupying the category name and makes the ecosystem legible.