customer-onboarding-coach

by charlie-morrison

Install this Skill

curl -fsSL -o customer-onboarding-coach.zip https://skill.seembox.com/api/v1/skills/customer-onboarding-coach/download && unzip customer-onboarding-coach.zip

Download customer-onboarding-coach.zip

SKILL.md About

---
name: customer-onboarding-coach
description: Coach a B2B SaaS / PLG company on building or fixing customer onboarding — defining the activation event (the leading indicator of long-term retention), measuring time-to-value (T2V) honestly, designing the onboarding sequence by customer segment (self-serve / mid-touch / high-touch white-glove), the structural moves (in-app product tours that don't feel like product tours, sample data / templates, integration accelerators, success-criteria contracts at kickoff), the operational moves (welcome calls, onboarding milestones, the 30-60-90 day plan, the executive sponsor mapping, the "go-live" definition), instrumenting onboarding (event-based progress tracking, drop-off detection, intervention triggers), recovering stuck implementations, and the handoff from onboarding to ongoing CSM. Use when founder says "customers aren't activating", "onboarding broken", "low feature adoption", "long time to value", "stuck implementations", "T2V too long", "white-glove vs self-serve", "kickoff call", "go-live", "60-day churn". Triggers on phrases like "customer onboarding", "activation event", "time to value", "T2V", "implementation", "kickoff call", "white glove onboarding", "self-serve activation", "onboarding playbook", "60-day cliff", "onboarding flow", "user activation".
---

# customer-onboarding-coach

Coach a B2B SaaS / PLG company through customer onboarding — the period from contract signature (or first signup) to the customer experiencing the core value of the product. Onboarding is the highest-leverage operational lever in the customer lifecycle: a customer who reaches activation in week 1 retains 3-5x better at month 12 than one who takes 30+ days. The 30-60-90 day cliff is the most common churn pattern in B2B SaaS, and it is overwhelmingly an onboarding failure, not a product failure.

This coach walks the company through diagnosis, segmentation of onboarding tracks, design of the activation event, and operational instrumentation. It treats onboarding as a manufacturable process, not a series of ad-hoc support tickets.

## When to engage

Trigger when the founder / VPCS / VP Product says:
- Symptom statements: "customers aren't activating", "low feature adoption", "30-60-90 day churn", "implementation stuck"
- Time-to-value pain: "onboarding takes 6+ weeks", "T2V too long", "customers go dark after kickoff"
- Self-serve vs high-touch confusion: "should we white-glove every customer", "PLG isn't activating", "implementation team can't keep up"
- Specific structures: "kickoff call", "go-live", "onboarding playbook", "30-60-90 day plan"
- Handoff issues: "onboarding to CSM transition is broken", "renewal happens before customer is fully live"
- Specific metrics: "activation event", "TTV", "feature adoption rate", "onboarding NPS"

Do not engage for: pure UX / first-run-experience design (different — UX-driven), customer support / ticket triage (different), or legal / contract onboarding (DPA, MSA — different skill).

## Diagnostic sweep

1. **What is the activation event?** What single customer behavior most strongly predicts 12-month retention? Common examples:
   - Slack: 2,000 messages sent in a workspace
   - Notion: 3 pages created collaboratively
   - Linear: 5 issues created and assigned
   - Stripe: first $X transacted
   - Datadog: first dashboard with monitors set
   - Figma: first design opened by a second teammate
   If the company can't name their activation event, that's diagnostic finding #1.

2. **Time-to-Value (T2V) baseline.**
   - Median T2V from signup to activation event
   - 25th / 50th / 75th / 90th percentile
   - Distribution by customer segment (SMB / mid-market / enterprise)
   - Trend over last 12 months: improving / flat / degrading?

3. **Activation rate by cohort.**
   - % of new customers who reach activation event within 30 days
   - 30-day vs 90-day vs ever-activated rates
   - Cohort comparison (have improvements moved the rate?)

4. **Onboarding modes today.**
   - Self-serve (no human touch)
   - Tech-touch (automated emails, in-app tours, plus support tickets)
   - Mid-touch (welcome call + scheduled check-ins)
   - High-touch (dedicated implementation manager, kickoff, multi-week project)

5. **Retention correlation.**
   - 90-day retention split by activated vs not-activated cohort
   - Renewal rates split by feature adoption depth
   - Top churn reasons in customer-facing exit interviews

6. **Operational state.**
   - Onboarding playbook documentation: yes/no
   - In-product tours / checklists: yes/no
   - Onboarding metrics dashboard: yes/no
   - Dedicated onboarding team: yes / no
   - Handoff to CSM defined: yes / no

## The activation event — define it before designing onboarding

Most onboarding failures start with not knowing the activation event. Without it, you optimize for vanity (first login, account creation) instead of leading-indicator behaviors.

### How to find the activation event
- Pull a cohort of customers who renewed at year 1 vs churned in year 1
- For each, look at first-30-day behaviors (events, feature usage, integration completions)
- Find the single behavior with the highest predictive power (typically AUC 0.75+ on retention model)
- Validate: customers who DID it retain 3-5x better than customers who DIDN'T

### Common activation events by product type
- **Collaboration products**: 2nd user invited and active
- **CRUD productivity**: N items created and used
- **Data products**: first integration connected and data flowing
- **API platforms**: first production API call from customer's environment
- **Analytics**: first dashboard saved and shared
- **Marketplace**: first transaction completed

### Activation event criteria
- Observable in product data (you can measure it)
- Reachable in week 1 (not "10,000 messages") — but not so trivial that everyone hits it (not "first login")
- Causally meaningful (customer experiences value when reaching it)
- Stable over time (doesn't depend on a feature that may be deprecated)

## Time-to-Value (T2V) — measure it honestly

T2V = time from signup (or contract signature) to activation event. Measure this as the primary onboarding metric.

### Baselines
- Self-serve PLG products: target T2V <1 day, healthy <7 days
- Mid-touch SaaS: target T2V <14 days, healthy <30 days
- Enterprise SaaS: target T2V <60 days, healthy <90 days, problematic >120 days

### Why "T2V is 6 weeks" is often a lie
- Companies often measure T2V as "time to go-live" (project completion) instead of "time to value"
- Customer might be live and not getting value
- The honest measure is when the customer-side outcome happens, not when the implementation team finishes

### Reduce T2V — top moves
- **Pre-built templates**: customer starts from a working template, not blank state
- **Sample data / sandbox**: customer can experiment without their own data first
- **Integration accelerators**: pre-built integration to common tools, not from-scratch SDK work
- **In-app tour**: contextual hints during the activation flow
- **Quickstart kickoff**: 30-min live walkthrough for mid-touch / high-touch customers
- **Done-for-you setup**: implementation team builds initial config; customer reviews

## Segmentation — different onboarding tracks for different customers

A unified onboarding track is almost always wrong. Typical 3-track model:

### Self-serve / PLG track
- Target: <$10K ACV, individual-decision buyers, collaborative-product fit
- Onboarding: in-product tour, sample data, in-app help, async email sequences
- Time investment: 0-2 hours of human time per customer
- T2V target: <7 days
- Activation rate target: 25-50% within 30 days
- Key elements: well-designed first-run experience, automated nudges at drop-off points, low-friction integration setup

### Mid-touch track
- Target: $10-50K ACV, multi-stakeholder decisions, mid-market
- Onboarding: kickoff call, 30/60/90 day plan, scheduled check-ins, in-product tours
- Time investment: 5-15 hours of CSM/implementation time per customer
- T2V target: <30 days
- Key elements: kickoff call within 5 days of signup, milestones documented and tracked, scheduled outcome reviews

### High-touch / white-glove track
- Target: $50K+ ACV, enterprise, complex implementations
- Onboarding: dedicated implementation manager, multi-stakeholder kickoff, weeks of integration support, executive sponsor engagement
- Time investment: 40-200+ hours of cross-functional time per customer
- T2V target: <90 days
- Key elements: project-managed implementation, named stakeholder mapping, change-management support, executive escalation paths

### When to graduate customers between tracks
- Self-serve customer growing into mid-market scale → upgrade to mid-touch
- Mid-touch customer hitting expansion threshold → upgrade to high-touch
- Don't strand customers mid-track when their needs change

## Designing the high-touch onboarding (40-200 hour implementations)

### Pre-kickoff (T-2 to T-0)
- Welcome email with kickoff agenda, prep checklist
- Stakeholder mapping: identify executive sponsor, project lead, technical owner, end-user champion
- Pre-kickoff data request (technical environment, integration requirements, success criteria draft)

### Kickoff call (T-0)
- 60-90 minute call with full stakeholder team
- Agree on success criteria (what does "go-live" mean?)
- Agree on milestones (T+30, T+60, T+90)
- Document decision rights (who can sign off on what)
- Set up shared workspace (Slack channel, Notion, project tool)

### Weekly cadence (T+1 to T+90)
- Weekly status meetings (30 min, fixed slot)
- Async daily updates from implementation lead
- Risk log + RAID (risks, assumptions, issues, decisions)
- Milestones tracked against agreed plan

### 30-60-90 day plan structure
- **30 days**: integration complete, sample data flowing, first power user trained
- **60 days**: 5+ users onboarded, first business outcome demonstrated, customer-side champion empowered
- **90 days**: full production usage, executive sponsor briefed on outcomes, expansion conversation starts

### Go-live definition
- Has to be specific and customer-validated
- "5 users actively using product, 1 production workflow live, 1 outcome demonstrated"
- NOT "implementation team finished"

### Handoff to CSM
- Pre-handoff briefing: implementation lead documents customer state, open issues, success criteria progress, executive sponsor relationship
- Joint handoff call: implementation lead + CSM + customer
- 30-day overlap: implementation lead available for technical questions during transition

## Designing the mid-touch onboarding

### Standard sequence
- Day 0 (signup): welcome email + calendar link for 30-min kickoff call
- Day 0-5: kickoff call scheduled and held; success criteria documented
- Day 5-10: customer completes setup with in-product tour; first integration live
- Day 14: check-in call to review progress; troubleshoot blockers
- Day 30: milestone review; activation event status
- Day 60: feature adoption review; expansion conversation if appropriate
- Day 90: handoff to long-term CSM

### Kickoff call structure (mid-touch)
- 30 minutes
- Goal: align on outcomes + map first 30 days
- Agenda:
  - 5 min: introductions, current state
  - 10 min: customer's specific use case + success criteria
  - 10 min: configuration walkthrough + integration plan
  - 5 min: 30-60-90 day milestones + check-in cadence

### Common mid-touch failures
- Kickoff call scheduled too late (>10 days after signup) — momentum lost
- Generic kickoff (not customer-specific) — doesn't map success criteria
- No documented milestones — no trigger for intervention
- CSM not engaged until renewal — discovers stuck implementation 30 days before contract renewal

## Designing self-serve / PLG onboarding

### First-run experience
- Eliminate barriers: minimum required fields, no email confirmation if possible, social login preferred
- Skip the corporate dashboard — customer should see the product immediately
- Sample data / template: customer can interact with a working example before importing their own
- Progressive disclosure: don't show all features at once; reveal them as customer needs them
- Empty state design: every empty state has a clear next action

### In-app product tours (without being annoying)
- Don't use modal-overlay tours that block the product
- Use contextual hints (small tooltips that appear when relevant)
- Trigger on action: when user is about to need a feature, show the hint
- Skip-able and dismissible
- Re-discoverable via help menu

### Automated email sequences
- Welcome email (immediate)
- Day 1 email: "have you tried X?"
- Day 3 email: "common stuck point Y has solution Z"
- Day 7 email: "if you've done A, B, C, you might be ready for D"
- Day 14 email: re-engagement if user hasn't activated
- Day 21 email: feedback ask + offer of help

### Drop-off detection + intervention
- Identify common drop-off points (typically: account setup → first action, first action → integration, integration → invite team)
- Trigger automated nudges at drop-off
- Trigger human outreach (CSM email or chat) at high-value customer drop-offs

## Instrumenting onboarding

### Required event tracking
- Signup / account creation
- First login
- First [activation event] action
- Integration connected
- Team member invited
- Sample data interacted with
- Help articles viewed
- Support tickets opened

### Onboarding dashboard metrics
- T2V (median, P25, P50, P75, P90)
- Activation rate by cohort
- Drop-off funnel (signup → first action → integration → invite → activation)
- Time spent in onboarding per customer
- Onboarding NPS / CSAT
- Implementation cost per customer (high-touch only)

### Intervention triggers
- Customer hasn't logged in within 7 days of signup → automated email + CSM ping
- Customer logged in but hasn't completed integration in 14 days → CSM outreach
- Customer hit drop-off point in funnel → automated content + CSM follow-up
- High-touch customer's milestone slipping → escalation to project lead
- Any customer at 60 days without activation → executive review

### Onboarding scorecard / health-check
- Customer-side: "are you experiencing the value you signed up for?" (qualitative)
- Product-side: activation event hit, feature adoption depth, usage frequency
- Stakeholder-side: executive sponsor engagement, champion strength, change-management buy-in

## Recovering stuck implementations

### Diagnose the stuck cause
- Stakeholder issue: champion left, executive sponsor disengaged, vendor change at customer
- Technical issue: integration broken, environment problem, data quality
- Process issue: customer-side workflow doesn't fit product, change-management resistance
- Resource issue: customer doesn't have time / budget to complete

### Intervention by cause
- Stakeholder: re-anchor with executive sponsor; identify new champion; map new stakeholders
- Technical: implementation team takes over the technical work, even if customer was supposed to do it
- Process: revise success criteria; phase the implementation (smaller scope first); identify minimum viable activation
- Resource: phase / pause / restart with explicit timeline; consider scope reduction

### When to escalate
- Two consecutive missed milestones → CSM escalation
- 60 days in implementation with <30% activation → engineering or product involvement
- 90 days in with no activation → executive escalation, possible refund / restart

### When to fire the customer
- Unwilling to complete required customer-side actions (e.g., data prep, integration access)
- Champion left and no replacement after multiple attempts
- Customer team's process is fundamentally incompatible with product
- After 6+ months of continued investment with no activation
- Politely offer refund + amicable separation; rare but right call sometimes

## Handoff to ongoing CSM

### Pre-handoff
- Implementation lead documents: customer state, open issues, executive sponsor relationship, success criteria progress, expansion opportunities, risk factors
- Schedule joint call: implementation + CSM + customer

### Handoff meeting
- 30 minutes
- Implementation lead summarizes: what's live, what's open, success metrics
- CSM introduces: their role, cadence, key questions
- Customer confirms: comfort with transition, escalation path

### Post-handoff overlap
- 30 days: implementation lead remains available for technical questions
- CSM owns customer relationship from day of handoff
- Document handoff in CRM (Salesforce, HubSpot) and customer-success platform

## Common anti-patterns

- Treating every customer the same way (one-track onboarding for SMB and enterprise)
- Measuring T2V as "go-live" instead of "value-realized"
- Not defining the activation event
- Activation event so easy it doesn't predict retention (e.g., "first login")
- Activation event so hard it's unreachable in onboarding period
- No instrumentation; relying on CSM gut feel
- High-touch onboarding without project management discipline (no milestones, no risk log)
- Self-serve onboarding without drop-off detection
- Premature handoff to CSM (before activation hit)
- Onboarding team's compensation tied to "time-to-go-live" instead of "T2V" or activation rate
- No 30-60-90 day plan documented and shared with customer
- Kickoff call without success criteria documented in writing

## Output to founder / VPCS

After diagnostic, produce:

1. **Activation event definition** (or analysis to identify it from data)
2. **T2V baseline** + target by segment
3. **Onboarding tracks** (self-serve / mid-touch / high-touch with eligibility thresholds)
4. **Track-by-track playbook** (steps, milestones, time investment per customer)
5. **Instrumentation plan** (events to track, dashboard metrics, intervention triggers)
6. **Drop-off detection + recovery** (specific intervention plays)
7. **Handoff to CSM definition** (pre-handoff, meeting, overlap)
8. **Stuck-implementation recovery framework** (diagnose, intervene, escalate, exit)
9. **30-60-90 day implementation roadmap** (for the org to build / fix the onboarding system)
10. **Metric dashboard mockup** (the 5-7 numbers leadership reviews weekly)

Onboarding is the most underbuilt operational system in most B2B SaaS. The customers who activate in week 1 become champions; the customers who don't activate in 60 days become churn statistics. Building this system is one of the highest-leverage investments a SaaS leader can make. This coach walks the company through that build, segment by segment, metric by metric.

_meta.json Metadata

{
  "ownerId": "kn7d5eszdfwftk153ymhdm4qhs83qsqy",
  "publishedAt": 1778114790318,
  "slug": "customer-onboarding-coach",
  "version": "1.0.0"
}