Onboarding CRO
Optimize the user onboarding experience for "$ARGUMENTS". Design flows that get users to the "aha moment" faster and increase activation rates.
Prerequisites
Read .metapowers/marketing/$ARGUMENTS/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "$ARGUMENTS". Run
/marketing:customer-research $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/marketing/$ARGUMENTS/skip-log.md.
Process
Read context:
- Read
.metapowers/marketing/$ARGUMENTS/00-strategy.mdfor audience context - Read
.metapowers/marketing/$ARGUMENTS/03-convert.mdif it exists (for signup flow context)
- Read
Define the "aha moment":
- What action or outcome makes users understand the product's value?
- How quickly can a new user reach it?
- What's the current time-to-value?
Map the onboarding flow:
- Current onboarding steps (if URL or flow provided)
- Where do users drop off? (identify the biggest leak)
- Which steps are essential vs. optional?
- Progressive disclosure: what can be deferred?
Design improvements:
- Welcome experience: personalized based on use case or persona
- Checklist or wizard: guided steps to activation
- Empty states: helpful, not empty
- Tooltips, tours, or contextual help
- Onboarding emails: complement in-app experience
- Success celebrations: reinforce progress
Write the artifact to
.metapowers/marketing/$ARGUMENTS/04-engage.mdunder an## Onboarding CROsection:- Aha Moment Definition — the activation event
- Current Flow Assessment — steps and drop-off points
- Recommended Flow — optimized onboarding design
- In-App + Email Coordination — how both channels work together
- Activation Metrics — what to track
Output
Onboarding CRO strategy written to .metapowers/marketing/$ARGUMENTS/04-engage.md. Present a summary highlighting:
- Defined aha moment
- Biggest onboarding friction point
- Top 3 improvements to implement