← All skills
onboarding-cro
Use when optimizing post-signup onboarding, user activation, first-run experience, or time-to-value, especially if users sign up but don't activate or return.
About this skill
Use when optimizing post-signup onboarding, user activation, first-run experience, or time-to-value, especially if users sign up but don't activate or return.
SKILL.md
onboarding-cro.SKILL.mdPlace it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.
--- name: onboarding-cro description: Use when optimizing post-signup onboarding, user activation, first-run experience, or time-to-value, especially if users sign up but don't activate or return. category: Marketing version: 1.0.0 tools: [] --- # Onboarding CRO Help users reach their "aha moment" as fast as possible and establish habits that lead to long-term retention. Check the Knowledge Base for existing product-marketing context first, and use it instead of re-asking questions already answered there. Before recommending anything, understand: product context (B2B or B2C, core value prop), the activation definition (what action indicates a user "gets it"), and current state (what happens after signup, where 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 the first session on one successful outcome; save advanced features for later. 3. **Do, don't show** — interactive beats tutorial; doing the thing beats learning about the thing. 4. **Progress creates motivation** — show advancement, celebrate completions, make the path visible. ## Defining Activation Find the action that correlates most strongly with retention: what do retained users do that churned users don't, and what's the earliest indicator of future engagement? Examples by product type: project management → create first project + add a team member; analytics → install tracking + see first report; design tool → create first design + export/share; marketplace → complete first transaction. Track: % of signups reaching activation, time to activation, steps to activation, and activation rate by cohort/source. ## Onboarding Flow Design **First 30 seconds after signup:** product-first (best for simple/B2C/mobile products, risk = blank-slate overwhelm), guided setup (best when personalization is needed, risk = friction before value), or value-first with demo data (risk = may not feel "real"). Whichever approach, always have a clear single next action, no dead ends, and progress indication for multi-step flows. **Onboarding checklist pattern** — use for multi-step setup or self-serve B2B: 3–7 items, ordered by value with quick wins first, a visible progress bar/completion %, celebration on completion, and a dismiss option that doesn't trap the user. **Empty states** are onboarding opportunities, not dead ends: explain what the area is for, show what it looks like with data, give a clear primary action to add the first item, and consider pre-populating with example data. **Tooltips and guided tours** — use for complex UI or non-obvious power features: cap at 3–5 steps, make them dismissable anytime, and don't repeat them for returning users. ## Multi-Channel Onboarding Trigger-based email cadence: welcome (immediate), incomplete-onboarding nudges (24h, 72h), activation celebration + next step, feature discovery (days 3, 7, 14). Email should reinforce in-app actions rather than duplicate them, drive back to the product with a specific CTA, and personalize based on actions already taken. ## Handling Stalled Users Define "stalled" explicitly (e.g. X days inactive, incomplete setup). Re-engage via an email sequence reminding of value and addressing blockers, in-app "welcome back, pick up where you left off" prompts, and for high-value accounts, human outreach. ## Measurement Key metrics: activation rate, time to activation, onboarding completion %, and Day 1/7/30 retention. Track drop-off at every funnel step — a typical shape looks like Signup 100% → Step 1 80% → Step 2 60% → Activation 40% → Retention 25%. Compute an activation score (0–100) from the step-by-step drop-off data and name the single biggest-loss step — that's where the audit should focus first, rather than eyeballing the funnel. ## Output Format **Onboarding audit:** lead with the activation score and the named biggest-drop step, then for each issue give Finding → Impact → Recommendation → Priority. **Onboarding flow design:** activation goal, step-by-step flow, checklist items if applicable, empty-state copy, email-sequence triggers, and a metrics plan. ## Common Patterns by Product Type 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 Consider tests for: flow simplification (step count, ordering), progress/motivation mechanics, personalization by role or goal, and support/help availability. ## Communication Lead with the highest-leverage finding, give a clear activation definition, then prioritize experiments by expected impact. Every recommendation should name a specific step, metric, or trigger — avoid vague advice. Match onboarding copy tone to the product's brand voice. ## Proactive Triggers - Low Day-1/Day-7 retention mentioned → immediately ask about the activation event and current post-signup flow. - A signup funnel shows a big drop between signup and first key action → diagnose onboarding, not acquisition. - "Users sign up but don't come back" → frame as an activation/onboarding problem, not a marketing problem. - Trial-to-paid conversion concerns → check whether activation is defined and being reached before assuming pricing is the blocker. - "Onboarding emails aren't working" → ask what in-app onboarding exists first; email should support it, not replace it. ## Coordinate With @mention a signup-flow specialist for pre-onboarding registration friction (not post-signup activation), a popup/modal specialist for in-product overlays used during onboarding, a paywall specialist once onboarding naturally leads into an upgrade prompt, and an experimentation specialist to run controlled tests on onboarding flows once there's a clear hypothesis.
Install
Syntic App
- 1Create a dedicated folder for this skill in your local skills library.
- 2Place SKILL.md into that folder.
- 3Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1Save SKILL.md in your local Syntic Code skills directory.
- 2Keep related files in the same skill folder.
- 3Run in a safe environment and validate outputs.