Customer Onboarding Sequences
Time-to-first-value targets, activation milestones

Designs customer onboarding sequences: time-to-first-value targets, activation milestones, guided setup, and onboarding emails. Use when the user is building onboarding for new customers, reducing time to value, or fixing activation…
---
name: onboarding-sequences
description: >-
Designs customer onboarding sequences: time-to-first-value targets, activation
milestones, guided setup, and onboarding emails. Use when the user is building
onboarding for new customers, reducing time to value, or fixing activation
drop-off. Triggers on: "onboarding sequence", "customer onboarding", "time to
value", "activation flow", "new customer setup".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
version: "1.0.0"
author: LeadMagic
category: lifecycle
tags: [lifecycle, onboarding, activation, time-to-value, customer-success]
frameworks:
- "Lincoln Murphy — Desired Outcome"
- "Wes Bush — Product-Led Onboarding"Overview
Activation (stage 3). Canonical definitions → references/gtm-lifecycle-stages.md. Deep dive (TTA benchmarks, audit, anti-patterns) → references/activation-playbook.md. Metrics & monitoring → references/lifecycle-metrics-by-stage.md, the gtm-metrics skill (lifecycle-monitoring-dashboard.md).
Manual install (npx, ZIP)
npx skills add LeadMagic/gtm-skills --skill onboarding-sequences -g -a claude-codenpx degit LeadMagic/gtm-skills/skills/lifecycle/onboarding-sequences#main ~/.claude/skills/onboarding-sequencesConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md6.7 KB
Read SKILL.md here
Show the full text142 lines
Customer Onboarding Sequences
Overview
Onboarding is the highest-risk period in the customer lifecycle. 40-60% of churn happens in the first 90 days. A structured onboarding sequence that drives customers to their first value moment within 7 days reduces churn by 30-50%. This skill covers design and execution.
Authoritative Foundations
- Lincoln Murphy — Desired Outcome — Onboarding succeeds when the customer reaches their required outcome in the right way; design milestones backward from that outcome.
- Wes Bush — Product-Led Onboarding — Remove steps that don't move users toward the first value moment, and measure time to first value.
- Samuel Hulick — UserOnboard — Frame onboarding around the user becoming more capable, not around touring features.
When to Use
- "Build onboarding sequence"
- "Customer onboarding"
- "Reduce time to first value"
- "New customer setup"
- "Activation flow"
Lifecycle Stage
Activation (stage 3). Canonical definitions → references/gtm-lifecycle-stages.md.
Deep dive (TTA benchmarks, audit, anti-patterns) → references/activation-playbook.md.
Metrics & monitoring → references/lifecycle-metrics-by-stage.md, the gtm-metrics skill (lifecycle-monitoring-dashboard.md).
Core Principle
Customers don't churn because your product is bad — they churn because they never experienced the value. Your onboarding has one job: get them to the "aha moment" as fast as possible.
Step-by-Step Process
Phase 1: Define the Aha Moment
Identify what "value realized" looks like for your product:
- Data product (LeadMagic, Clearbit): First successful enrichment or verification
- CRM: First deal moved through a pipeline stage
- Analytics: First dashboard built
- Sequencing (Outreach, Smartlead): First sequence sent
- General SaaS: Activation event that correlates with retention (find it in your data)
Measure: users who hit [Aha Moment] within 7 days have 80%+ 90-day retention. Users who don't have <30% 90-day retention. Goal: 80%+ of new customers hit Aha Moment in week 1.
Phase 2: Onboarding Journey Map
- Day 0 (Pre-launch): Welcome email. What to expect. How to prepare. "Bring your [data/team/credentials] — here's what you'll need."
- Day 1 (Launch): Account created. Guided first action. "Do this one thing right now and you'll see value in 5 minutes."
- Day 3 (First value): Follow-up email. "Did you try [first action]? Here's what to do next."
- Day 7 (Deepen): Second value moment. "Now that you've [first action], here's how to [advanced use case]."
- Day 14 (Habit): Usage check-in. "You've used [product] X times. Teams like yours typically see [result] by now."
- Day 30 (Expansion): "Ready for the next level? Here are 3 features power users love."
Phase 3: Multi-Channel Onboarding
- In-app: Guided tours, tooltips, checklists, progress bars. Don't show everything — show the 3 steps to the aha moment.
- Email: Triggered based on in-app behavior. If they completed step 1, email about step 2. If they haven't logged in for 3 days, re-engagement email.
- SMS/Slack (for high-touch): "Quick question about your setup — need help?"
- CSM call (enterprise): 30-minute kickoff call in week 1. Screen share the setup. Answer questions.
Phase 4: Onboarding Content
- Quickstart guide: 1-page PDF. The 3 things to do in your first session. Screenshots. 5 minutes to read.
- Setup video: 3-5 minute walkthrough. Show, don't tell.
- Template library: Pre-built configurations, templates, examples. "Start from this template and you'll be live in 10 minutes."
- FAQ: "Common setup questions" — answer the 10 things every new user asks. Link from onboarding emails.
Phase 5: Measurement & Optimization
- Activation rate: % of new customers who hit Aha Moment within 7 days
- Time to first value: Median days from signup to Aha Moment
- Onboarding completion: % who complete the full onboarding sequence
- Onboarding churn: % who churn during onboarding (first 30 days)
- A/B test: Onboarding email sequences, in-app flows, CSM touch points
- Kill: Onboarding steps that don't correlate with retention
Output Format
Onboarding sequence design with: aha moment definition, journey map, multi-channel plan, content inventory, and optimization framework.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
- Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
- Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
Execution Artifacts
references/framework-notes.md— Named frameworks and reference tablestemplates/output-template.md— Deliverable shell for agent outputscripts/check-output.py— Lightweight deliverable validator Canonical lifecycle:references/gtm-lifecycle-stages.md— Stage index (Activation row)references/activation-playbook.md— First value event, TTA, audit checklistreferences/lifecycle-metrics-by-stage.md— Activation metrics + thresholds- the
gtm-metricsskill (lifecycle-monitoring-dashboard.md) — Weekly activation panel references/lifecycle-skill-index.md— Lifecycle cluster router
Related Skills
- cs-playbooks, churn-prevention, lifecycle-drips, customer-marketing, expansion-selling
| 1 | |
| 2 | name onboarding-sequences |
| 3 | description >- |
| 4 | Designs customer onboarding sequences: time-to-first-value targets, activation |
| 5 | milestones, guided setup, and onboarding emails. Use when the user is building |
| 6 | onboarding for new customers, reducing time to value, or fixing activation |
| 7 | drop-off. Triggers on: "onboarding sequence", "customer onboarding", "time to |
| 8 | value", "activation flow", "new customer setup". |
| 9 | license MIT |
| 10 | compatibility Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed |
| 11 | metadata |
| 12 | version "1.0.0" |
| 13 | author LeadMagic |
| 14 | category lifecycle |
| 15 | tags [lifecycle, onboarding, activation, time-to-value, customer-success] |
| 16 | frameworks |
| 17 | - "Lincoln Murphy — Desired Outcome" |
| 18 | - "Wes Bush — Product-Led Onboarding" |
| 19 | - "Samuel Hulick — UserOnboard" |
| 20 | |
| 21 | |
| 22 | # Customer Onboarding Sequences |
| 23 | |
| 24 | ## Overview |
| 25 | Onboarding is the highest-risk period in the customer lifecycle. 40-60% of |
| 26 | churn happens in the first 90 days. A structured onboarding sequence that |
| 27 | drives customers to their first value moment within 7 days reduces churn |
| 28 | by 30-50%. This skill covers design and execution. |
| 29 | |
| 30 | ## Authoritative Foundations |
| 31 | **Lincoln Murphy — Desired Outcome** — Onboarding succeeds when the customer reaches their required outcome in the right way; design milestones backward from that outcome. |
| 32 | **Wes Bush — Product-Led Onboarding** — Remove steps that don't move users toward the first value moment, and measure time to first value. |
| 33 | **Samuel Hulick — UserOnboard** — Frame onboarding around the user becoming more capable, not around touring features. |
| 34 | |
| 35 | ## When to Use |
| 36 | "Build onboarding sequence" |
| 37 | "Customer onboarding" |
| 38 | "Reduce time to first value" |
| 39 | "New customer setup" |
| 40 | "Activation flow" |
| 41 | |
| 42 | ## Lifecycle Stage |
| 43 | |
| 44 | **Activation** (stage 3). Canonical definitions → `references/gtm-lifecycle-stages.md`. |
| 45 | Deep dive (TTA benchmarks, audit, anti-patterns) → `references/activation-playbook.md`. |
| 46 | Metrics & monitoring → `references/lifecycle-metrics-by-stage.md`, the `gtm-metrics` skill (lifecycle-monitoring-dashboard.md). |
| 47 | |
| 48 | ## Core Principle |
| 49 | > Customers don't churn because your product is bad — they churn because they |
| 50 | > never experienced the value. Your onboarding has one job: get them to the |
| 51 | > "aha moment" as fast as possible. |
| 52 | |
| 53 | ## Step-by-Step Process |
| 54 | |
| 55 | ### Phase 1: Define the Aha Moment |
| 56 | Identify what "value realized" looks like for your product: |
| 57 | **Data product (LeadMagic, Clearbit):** First successful enrichment or verification |
| 58 | **CRM:** First deal moved through a pipeline stage |
| 59 | **Analytics:** First dashboard built |
| 60 | **Sequencing (Outreach, Smartlead):** First sequence sent |
| 61 | **General SaaS:** Activation event that correlates with retention (find it in your data) |
| 62 | |
| 63 | Measure: users who hit [Aha Moment] within 7 days have 80%+ 90-day retention. |
| 64 | Users who don't have <30% 90-day retention. Goal: 80%+ of new customers hit |
| 65 | Aha Moment in week 1. |
| 66 | |
| 67 | ### Phase 2: Onboarding Journey Map |
| 68 | **Day 0 (Pre-launch):** Welcome email. What to expect. How to prepare. |
| 69 | "Bring your [data/team/credentials] — here's what you'll need." |
| 70 | **Day 1 (Launch):** Account created. Guided first action. "Do this one thing |
| 71 | right now and you'll see value in 5 minutes." |
| 72 | **Day 3 (First value):** Follow-up email. "Did you try [first action]? |
| 73 | Here's what to do next." |
| 74 | **Day 7 (Deepen):** Second value moment. "Now that you've [first action], |
| 75 | here's how to [advanced use case]." |
| 76 | **Day 14 (Habit):** Usage check-in. "You've used [product] X times. |
| 77 | Teams like yours typically see [result] by now." |
| 78 | **Day 30 (Expansion):** "Ready for the next level? Here are 3 features |
| 79 | power users love." |
| 80 | |
| 81 | ### Phase 3: Multi-Channel Onboarding |
| 82 | **In-app:** Guided tours, tooltips, checklists, progress bars. Don't show |
| 83 | everything — show the 3 steps to the aha moment. |
| 84 | **Email:** Triggered based on in-app behavior. If they completed step 1, |
| 85 | email about step 2. If they haven't logged in for 3 days, re-engagement email. |
| 86 | **SMS/Slack (for high-touch):** "Quick question about your setup — need help?" |
| 87 | **CSM call (enterprise):** 30-minute kickoff call in week 1. Screen share |
| 88 | the setup. Answer questions. |
| 89 | |
| 90 | ### Phase 4: Onboarding Content |
| 91 | **Quickstart guide:** 1-page PDF. The 3 things to do in your first session. |
| 92 | Screenshots. 5 minutes to read. |
| 93 | **Setup video:** 3-5 minute walkthrough. Show, don't tell. |
| 94 | **Template library:** Pre-built configurations, templates, examples. |
| 95 | "Start from this template and you'll be live in 10 minutes." |
| 96 | **FAQ:** "Common setup questions" — answer the 10 things every new user |
| 97 | asks. Link from onboarding emails. |
| 98 | |
| 99 | ### Phase 5: Measurement & Optimization |
| 100 | **Activation rate:** % of new customers who hit Aha Moment within 7 days |
| 101 | **Time to first value:** Median days from signup to Aha Moment |
| 102 | **Onboarding completion:** % who complete the full onboarding sequence |
| 103 | **Onboarding churn:** % who churn during onboarding (first 30 days) |
| 104 | **A/B test:** Onboarding email sequences, in-app flows, CSM touch points |
| 105 | **Kill:** Onboarding steps that don't correlate with retention |
| 106 | |
| 107 | ## Output Format |
| 108 | Onboarding sequence design with: aha moment definition, journey map, multi-channel |
| 109 | plan, content inventory, and optimization framework. |
| 110 | |
| 111 | |
| 112 | |
| 113 | ## Quality Check |
| 114 | |
| 115 | Before delivering, verify: |
| 116 | [ ] All required sections are complete |
| 117 | [ ] Output matches the user's stated need |
| 118 | [ ] Named frameworks are cited for key recommendations |
| 119 | [ ] No vague claims — every recommendation has a specific action |
| 120 | [ ] Deliverable is ready for operational use, not just conceptual |
| 121 | |
| 122 | ## Common Pitfalls |
| 123 | |
| 124 | **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables. |
| 125 | **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner. |
| 126 | **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority. |
| 127 | |
| 128 | ## Execution Artifacts |
| 129 | |
| 130 | `references/framework-notes.md` — Named frameworks and reference tables |
| 131 | `templates/output-template.md` — Deliverable shell for agent output |
| 132 | `scripts/check-output.py` — Lightweight deliverable validator |
| 133 | **Canonical lifecycle:** |
| 134 | `references/gtm-lifecycle-stages.md` — Stage index (Activation row) |
| 135 | `references/activation-playbook.md` — First value event, TTA, audit checklist |
| 136 | `references/lifecycle-metrics-by-stage.md` — Activation metrics + thresholds |
| 137 | the `gtm-metrics` skill (lifecycle-monitoring-dashboard.md) — Weekly activation panel |
| 138 | `references/lifecycle-skill-index.md` — Lifecycle cluster router |
| 139 | |
| 140 | ## Related Skills |
| 141 | cs-playbooks, churn-prevention, lifecycle-drips, customer-marketing, expansion-selling |
| 142 |
Details
- License
- MIT
- Stars on the repo
- ★ 62
- Checked
- Source
- LeadMagic/gtm-skills ↗
- Creator
- LeadMagic · 129 listings
Similar skills
See all →
SkillOnboarding CRO
SkillUser Onboarding CRO
SkillOnboarding CRO
AgentSuccess Account Manager
SkillTechnology Adoption Segments
SkillSuccess Plan BuilderMore from LeadMagic
SkillStrategic Account Marketing
SkillCluster Account Marketing
SkillProgrammatic Account Targeting
SkillAccount Strategy Designer
SkillTarget Account Selector