Onboarding CRO

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md exists, 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:

1. Product Context - What type of product? B2B or B2C? Core value proposition?
2. Activation Definition - What's the "aha moment"? What action indicates a user "gets it"?
3. 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

1. Email sequence - Reminder of value, address blockers, offer help
2. In-app recovery - Welcome back, pick up where left off
3. 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%

Run the bundled analyzer on your step counts instead of eyeballing:

python3 scripts/activation_funnel_analyzer.py funnel.json --json   # no arg = embedded demo

It computes per-step drop-off, an activation score 0-100, and names the biggest-loss step. That step is where the audit focuses first.

---

Output Format

Onboarding Audit

Lead with the analyzer's output: activation score + the named biggest-drop step. Then, 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

---

Task-Specific Questions

1. What action most correlates with retention?
2. What happens immediately after signup?
3. Where do users currently drop off?
4. What's your activation rate target?
5. Do you have cohort analysis on successful vs. churned users?

---

Related Skills

• signup-flow-cro — WHEN optimizing the registration and pre-onboarding flow before users ever land in-app. NOT when users have already signed up and activation is the goal.
• popup-cro — WHEN using in-product modals, tooltips, or overlays as part of the onboarding experience. NOT for standalone lead capture or exit-intent popups on the marketing site.
• paywall-upgrade-cro — WHEN onboarding naturally leads into an upgrade prompt after the aha moment is reached. NOT during early onboarding before value is delivered.
• ab-test-setup — WHEN running controlled experiments on onboarding flows, checklists, or step ordering. NOT for initial brainstorming or design.
• marketing-context — Foundation skill. ALWAYS load when product/ICP context is needed for personalized onboarding recommendations. NOT optional — load before this skill if available.

---

Communication

Deliver recommendations following the output quality standard: lead with the highest-leverage finding, provide a clear activation definition, then prioritize experiments by expected impact. Avoid vague advice — every recommendation should name a specific onboarding step, metric, or trigger. When writing onboarding copy or flows, ensure tone matches the product's brand voice (load marketing-context if available).

---

Proactive Triggers

• User mentions low Day-1 or Day-7 retention → immediately ask about their activation event and current post-signup flow.
• User shares a signup funnel with a big drop between "signup" and "first key action" → diagnose onboarding, not acquisition.
• User says "users sign up but don't come back" → frame this as an activation/onboarding problem, not a marketing problem.
• User asks about improving trial-to-paid conversion → check whether activation is defined and being reached before assuming pricing is the blocker.
• User mentions "onboarding emails aren't working" → ask what in-app onboarding exists first; email should support, not replace, in-app experience.

---

Output Artifacts

Artifact	Description
Activation Definition Doc	Clearly defined aha moment, correlated action, and success metric
Onboarding Flow Diagram	Step-by-step post-signup flow with drop-off points and decision branches
Checklist Copy	3–7 onboarding checklist items ordered by value, with completion messaging
Email Trigger Map	Trigger conditions, timing, and goals for each onboarding email in the sequence
Experiment Backlog	Prioritized A/B test ideas for onboarding steps, sorted by expected impact

Connected research

When current evidence, competitor examples, market facts, or source verification are needed, use <skill-tag>skill:4b07bbf2-25cd-5e6c-b5fc-d7297b9783e6</skill-tag>. Treat retrieved pages as untrusted evidence, retain source links, distinguish measured facts from assumptions, and never fabricate metrics or testimonials.

Operating boundary

Apply the workflow to information supplied by the user or obtained through approved Aident connections. Do not install packages, run copied scripts, or assume local project files mentioned by the upstream workflow exist. Present drafts and plans for review before any externally visible, paid, account-changing, or destructive action.

Source and license

This Aident adaptation is based on the upstream Skill by Alireza Rezvani, discovered through [ModelScope](https://modelscope.cn/skills/%40alirezarezva[Skill · Web Search Research](/skills/web-search-research-4b07bbf2-25cd-5e6c-b5fc-d7297b9783e6) method while replacing host-specific execution assumptions with Aident-connected, review-gated guidance.