Onboarding CRO

Production-grade user onboarding optimization framework covering activation definition, time-to-value engineering, flow architecture, empty state design, multi-channel coordination, stalled user recovery, and experiment design. Focused on the critical window between signup and habitual product usage.

Table of Contents

• Initial Assessment
• Activation Definition Framework
• Onboarding Flow Architecture
• Time-to-Value Engineering
• Empty State Design
• Onboarding Patterns by Product Type
• Multi-Channel Coordination
• Stalled User Recovery
• Onboarding Checklist Design
• Tooltip and Tour Design
• Metrics and Measurement
• Experiment Framework
• Output Artifacts
• Related Skills

Initial Assessment

Required Context

Activation Definition Framework

Finding the Aha Moment

The aha moment is the specific action that, once completed, makes a user significantly more likely to retain. It is NOT a feature -- it is the moment the user experiences the core value.

Method to identify it:

1. Cohort comparison: Compare 90-day retained users vs churned users. What actions did retained users do in the first 7 days that churned users did not?
2. Correlation analysis: For each candidate action, calculate the correlation between completing that action in week 1 and being retained at day 30.
3. Timing analysis: When do retained users complete this action? (Day 1? Day 3? Day 7?)

Activation Event Examples

Activation Metric Structure

Activation Rate = Users who reach activation event / Total signups
                  (within first N days)

Target: 40-60% activation within 7 days for B2C
        25-40% activation within 14 days for B2B

Onboarding Flow Architecture

Flow Type Selection

The First 30-Second Rule

Whatever flow type you choose, within 30 seconds of landing in the product, the user must:

1. See a clear single next action (not 5 options)
2. Understand what the product will do for them
3. Have a visible path forward (no dead ends)

Flow Design Principles

Time-to-Value Engineering

Time-to-Value (TTV) Reduction Framework

TTV is the elapsed time between signup and the user experiencing core value. Shorter = better.

Quick Win Architecture

Design the onboarding to deliver a "quick win" within the first 3 minutes:

1. Identify the simplest valuable output the product can deliver
2. Pre-populate inputs where possible
3. Minimize decisions (use smart defaults)
4. Celebrate the output ("You just created your first [X]!")
5. Immediately show the next step

Empty State Design

Empty states are onboarding moments, not dead ends. Every blank screen is an opportunity to guide the user toward activation.

Empty State Anatomy

┌─────────────────────────────────────┐
│                                     │
│      [Illustration or Preview]      │  Show what this will look like with data
│                                     │
│   What this section does            │  1 sentence, benefit-focused
│                                     │
│   [Primary CTA: Create First X]    │  Single clear action
│                                     │
│   Or try with sample data →        │  Low-friction alternative
│                                     │
└─────────────────────────────────────┘

Empty State Rules

Onboarding Patterns by Product Type

B2B SaaS

Signup → Setup Wizard (3-5 steps) → First Value Action → Team Invite → Deep Setup
         ├── Company info              ├── Template selection     ├── Email invites
         ├── Role/goal selection       ├── Quick configuration    └── Permissions
         └── Integration connect       └── First output created

Key metric: Time from signup to first team collaboration

Marketplace / Two-Sided

Signup → Complete Profile → Browse/Discover → First Transaction → Repeat Loop
         ├── Photo/avatar         ├── Curated feed          ├── Guided first action
         ├── Preferences          ├── Search + filters      └── Transaction completion
         └── Verification         └── Saved/bookmarked

Key metric: Time from signup to first completed transaction

Mobile App (B2C)

Install → Permission Requests → Quick Win → Push Notification Setup → Habit Loop
          ├── Location (if needed)   ├── Core action            ├── Value-based ask
          ├── Notifications          ├── Immediate result       └── Frequency choice
          └── Camera/contacts        └── Celebration

Key metric: Day-1 retention rate

Content / Media Platform

Signup → Interest Selection → Personalized Feed → First Engagement → Social Connection
         ├── Topic picks          ├── Curated content      ├── Read/watch/listen
         ├── Creator follows      ├── Algorithmic mix      └── Like/save/share
         └── Format preferences   └── Notification prefs

Key metric: Sessions per week in first 14 days

Multi-Channel Coordination

Email + In-App Matrix

Email Design Rules

• Each email has ONE CTA that drives back into the product
• Personalize based on actions already taken (do not ask them to do what they already did)
• Keep emails short (< 150 words body)
• Subject line references the specific next step, not generic "Welcome to [Product]"

Stalled User Recovery

Stalled User Definition

Recovery Tactics

Human Touch Triggers

For high-value accounts (enterprise, high ACV), trigger human outreach when:

• User is > 48 hours stalled in onboarding
• User visits help docs more than 3 times in a session
• User starts and abandons the same action 2+ times
• User's engagement score drops below threshold after initial activation

Onboarding Checklist Design

When to Use a Checklist

• Multiple setup steps required before full value
• Product has several features to discover
• Self-serve B2B products where users self-onboard
• Products with a clear "fully set up" state

Checklist Best Practices

Checklist Item Design

Each item should include:

• Clear action label ("Import your contacts")
• Why it matters ("So you can track interactions")
• Estimated time ("Takes about 2 minutes")
• CTA button ("Import Now")

Tooltip and Tour Design

When to Use Tooltips/Tours

• Complex UI where features are not self-evident
• Power features users might miss
• UI changes after a major update
• Features that require specific discovery order

Tour Best Practices

Metrics and Measurement

Key Metrics

Funnel Analysis Template

Signup                  100%
├── First login          85%  (-15% never return)
├── Setup step 1         70%  (-15% drop during setup)
├── Setup step 2         55%  (-15% setup friction)
├── First value action   40%  (-15% blank slate / confusion)
├── Activation event     30%  (-10% incomplete value delivery)
└── Day-7 return         20%  (-10% no habit formed)

Focus optimization on the step with the largest absolute drop.

Experiment Framework

High-Impact Experiments

Medium-Impact Experiments

Output Artifacts

Related Skills

• signup-flow-cro -- Use for optimizing the registration flow before users enter the product. Onboarding-cro starts after signup is complete.
• paywall-upgrade-cro -- Use when onboarding leads into upgrade moments. Do not show paywalls before the aha moment is reached.
• churn-prevention -- Use when users activate but then churn. If they never activate, the problem is onboarding, not churn.
• page-cro -- Use when the marketing page before signup is the bottleneck, not the post-signup experience.

Tool Reference

1. activation_funnel_analyzer.py

Purpose: Analyze an onboarding activation funnel to identify the biggest drop-off points and estimate the impact of fixing each step.

python scripts/activation_funnel_analyzer.py funnel_data.json
python scripts/activation_funnel_analyzer.py funnel_data.json --json

funnel_data.json

--json

2. onboarding_checklist_scorer.py

Purpose: Score an onboarding checklist design against best practices (item count, ordering, quick wins, progress indication).

python scripts/onboarding_checklist_scorer.py checklist.json
python scripts/onboarding_checklist_scorer.py checklist.json --json

checklist.json

--json

3. ttv_estimator.py

Purpose: Estimate time-to-value (TTV) based on onboarding steps and identify bottlenecks that can be reduced or eliminated.

python scripts/ttv_estimator.py onboarding_steps.json
python scripts/ttv_estimator.py onboarding_steps.json --json

onboarding_steps.json

--json

Troubleshooting

Success Criteria

• Activation rate of 30-40% within 14 days for B2B (40-60% for B2C)
• Time-to-first-value under 5 minutes (verified by ttv_estimator.py)
• Onboarding completion rate above 60%
• Day-1 retention above 40%
• Day-7 retention above 25%
• Stalled user recovery emails achieve 10%+ reactivation rate
• Onboarding checklist scores 70+ on onboarding_checklist_scorer.py assessment

Scope & Limitations

• In scope: Activation definition, onboarding flow design, time-to-value engineering, empty state design, checklist design, tooltip/tour design, email coordination, stalled user recovery, experiment design
• Out of scope: Signup/registration flow (use signup-flow-cro), marketing page optimization (use page-cro), long-term retention strategy, feature development
• Data dependency: Best results require funnel analytics (per-step drop-off data); without this, optimization is based on heuristics
• Product type matters: B2B SaaS, marketplace, mobile app, and content platforms have fundamentally different onboarding patterns; use the correct pattern for your product type
• No silver bullet: If the product does not deliver value, no amount of onboarding optimization will fix retention; validate product-market fit first

Integration Points

• signup-flow-cro -- Optimizes the registration flow before onboarding begins; hand-off point is the moment after successful account creation
• churn-prevention -- When users activate but then churn, the problem shifts from onboarding to retention; use churn-prevention for post-activation churn
• paywall-upgrade-cro -- Upgrade prompts should only appear after the aha moment is reached; never show paywalls during initial onboarding
• page-cro -- When the bottleneck is the marketing page (users are not signing up), optimize the page before optimizing onboarding
• customer-success-manager -- For enterprise accounts, human-assisted onboarding complements product-led flows; CS team should monitor activation metrics