Optimize user onboarding flows and activation rates
Optimizes post-signup onboarding and activation by finding the aha moment, designing the flow, and measuring drop-off.
Why it matters
Help product teams design and improve post-signup onboarding experiences that guide users to their 'aha moment' quickly, increase activation rates, and establish habits that drive long-term retention.
Outcomes
What it gets done
Audit existing onboarding flows to identify drop-off points and friction
Define activation metrics and identify the key actions that correlate with retention
Design step-by-step onboarding flows with checklists, empty states, and progress indicators
Create coordinated email sequences triggered by user behavior during onboarding
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-onboarding | bash Overview
Onboarding CRO
This skill optimizes post-signup onboarding by defining the product's activation (aha moment), designing the immediate post-signup flow and checklist, coordinating email and in-app touches, handling stalled users, and measuring activation rate and funnel drop-off. Use it for onboarding flow, activation rate, first-run experience, empty states, or time-to-value work. Defer to signup, emails, paywalls, or ab-testing skills for adjacent funnel stages.
What it does
Helps optimize post-signup onboarding, user activation, first-run experience, and time-to-value, working from four core principles: time-to-value is everything (remove every step between signup and core value), one goal per session, do-don't-show (interactive beats tutorial), and progress creates motivation. It starts by defining activation - finding the "aha moment" action that correlates most strongly with retention, with examples by product type (project management: create a project and add a team member; analytics: install tracking and see a first report; design tool: create and export/share a design; marketplace: complete a first transaction) - then tracks activation rate, time to activation, steps to activation, and activation by cohort or source. For the immediate post-signup window it weighs three approaches (product-first for simple B2C/mobile products, guided setup for products needing personalization, value-first for products with demo data) against their overwhelm/friction/authenticity risks, always requiring a clear single next action, no dead ends, and progress indication for multi-step flows. An onboarding checklist pattern is recommended for multi-step setups or self-serve B2B products: 3-7 items ordered by value with quick wins first, a progress bar, a completion celebration, and a dismiss option so users aren't trapped. Empty states are treated as onboarding opportunities rather than dead ends - explaining what the area is for, showing what it looks like populated, and giving a clear primary action, optionally pre-populated with example data - and tooltips/guided tours are capped at 3-5 steps, dismissable, and not repeated for returning users. Multi-channel coordination uses trigger-based emails (immediate welcome, incomplete-onboarding reminders at 24h/72h, an activation-achieved celebration with next step, and feature-discovery emails at days 3/7/14) that reinforce in-app actions rather than duplicate them. Stalled users - defined by inactivity days or incomplete setup - get a three-tier re-engagement response: an email sequence addressing likely blockers, in-app "pick up where you left off" recovery, and personal outreach for high-value accounts. Measurement tracks activation rate, time to activation, onboarding completion rate, and day 1/7/30 retention, with funnel analysis identifying the biggest step-to-step drop-off to focus on. Recommendations are delivered as either an audit (finding, impact, recommendation, priority per issue) or a full flow design (activation goal, step-by-step flow, checklist items, empty-state copy, email triggers, and a metrics plan), and it checks for existing product-marketing context before asking questions the team has already answered.
When to use - and when NOT to
Use it when someone wants to optimize onboarding flow, activation rate, first-run experience, empty states, an onboarding checklist, or time-to-value. For adjacent stages, defer to sibling skills: signup for the flow before onboarding, emails for the onboarding email series specifically, paywalls for converting to paid during or after onboarding, and ab-testing for testing onboarding changes.
Inputs and outputs
Input is the product type, its defined activation event, and the current post-signup flow including where users drop off. Output is either an onboarding audit (per-issue finding, impact, recommendation, priority) or a full onboarding flow design with activation goal, step-by-step flow, checklist items, empty-state copy, email triggers, and a measurement plan.
Integrations
Reads existing product-marketing context files before asking questions, and hands off to the signup, emails, paywalls, and ab-testing skills for adjacent parts of the funnel.
Who it's for
Product and growth teams who want users to reach their activation moment faster and stay retained, with a structured process for defining activation, designing the flow around it, and measuring where users actually drop off.
Source README
Onboarding CRO
When to Use
Use this skill when you need when the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new...
You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
- Product Context - What type of product? B2B or B2C? Core value proposition?
- Activation Definition - What's the "aha moment"? What action indicates a user "gets it"?
- Current State - What happens after signup? Where do users drop off?
Core Principles
1. Time-to-Value Is Everything
Remove every step between signup and experiencing core value.
2. One Goal Per Session
Focus first session on one successful outcome. Save advanced features for later.
3. Do, Don't Show
Interactive > Tutorial. Doing the thing > Learning about the thing.
4. Progress Creates Motivation
Show advancement. Celebrate completions. Make the path visible.
Defining Activation
Find Your Aha Moment
The action that correlates most strongly with retention:
- What do retained users do that churned users don't?
- What's the earliest indicator of future engagement?
Examples by product type:
- Project management: Create first project + add team member
- Analytics: Install tracking + see first report
- Design tool: Create first design + export/share
- Marketplace: Complete first transaction
Activation Metrics
- % of signups who reach activation
- Time to activation
- Steps to activation
- Activation by cohort/source
Onboarding Flow Design
Immediate Post-Signup (First 30 Seconds)
| Approach | Best For | Risk |
|---|---|---|
| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |
| Guided setup | Products needing personalization | Adds friction before value |
| Value-first | Products with demo data | May not feel "real" |
Whatever you choose:
- Clear single next action
- No dead ends
- Progress indication if multi-step
Onboarding Checklist Pattern
When to use:
- Multiple setup steps required
- Product has several features to discover
- Self-serve B2B products
Best practices:
- 3-7 items (not overwhelming)
- Order by value (most impactful first)
- Start with quick wins
- Progress bar/completion %
- Celebration on completion
- Dismiss option (don't trap users)
Empty States
Empty states are onboarding opportunities, not dead ends.
Good empty state:
- Explains what this area is for
- Shows what it looks like with data
- Clear primary action to add first item
- Optional: Pre-populate with example data
Tooltips and Guided Tours
When to use: Complex UI, features that aren't self-evident, power features users might miss
Best practices:
- Max 3-5 steps per tour
- Dismissable at any time
- Don't repeat for returning users
Multi-Channel Onboarding
Email + In-App Coordination
Trigger-based emails:
- Welcome email (immediate)
- Incomplete onboarding (24h, 72h)
- Activation achieved (celebration + next step)
- Feature discovery (days 3, 7, 14)
Email should:
- Reinforce in-app actions, not duplicate them
- Drive back to product with specific CTA
- Be personalized based on actions taken
Handling Stalled Users
Detection
Define "stalled" criteria (X days inactive, incomplete setup)
Re-engagement Tactics
- Email sequence - Reminder of value, address blockers, offer help
- In-app recovery - Welcome back, pick up where left off
- Human touch - For high-value accounts, personal outreach
Measurement
Key Metrics
| Metric | Description |
|---|---|
| Activation rate | % reaching activation event |
| Time to activation | How long to first value |
| Onboarding completion | % completing setup |
| Day 1/7/30 retention | Return rate by timeframe |
Funnel Analysis
Track drop-off at each step:
Signup → Step 1 → Step 2 → Activation → Retention
100% 80% 60% 40% 25%
Identify biggest drops and focus there.
Output Format
Onboarding Audit
For each issue: Finding → Impact → Recommendation → Priority
Onboarding Flow Design
- Activation goal
- Step-by-step flow
- Checklist items (if applicable)
- Empty state copy
- Email sequence triggers
- Metrics plan
Common Patterns by Product Type
| Product Type | Key Steps |
|---|---|
| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |
| Marketplace | Complete profile → Browse → First transaction → Repeat loop |
| Mobile App | Permissions → Quick win → Push setup → Habit loop |
| Content Platform | Follow/customize → Consume → Create → Engage |
Experiment Ideas
When recommending experiments, consider tests for:
- Flow simplification (step count, ordering)
- Progress and motivation mechanics
- Personalization by role or goal
- Support and help availability
For comprehensive experiment ideas: See references/experiments.md
Task-Specific Questions
- What action most correlates with retention?
- What happens immediately after signup?
- Where do users currently drop off?
- What's your activation rate target?
- Do you have cohort analysis on successful vs. churned users?
Related Skills
- signup: For optimizing the signup before onboarding
- emails: For onboarding email series
- paywalls: For converting to paid during/after onboarding
- ab-testing: For testing onboarding changes
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.