Editing Onboard

Part of [[The Playbook]] — phase 1 of 5: '''Onboard''' → [[Adopt]] → [[Risk]] → [[Renew]] → [[Grow]].

==Treat it as a deploy, not a checklist==

Most onboarding programs are a task checklist: accounts created, training scheduled, kickoff call held. None of that is a deploy — a deploy has defined success criteria set before you start, a staged rollout instead of flipping everything on at once, and a rollback or rescue plan if it doesn't go live cleanly. Onboarding should work the same way: a stated time-to-first-value target, a phased rollout across teams or use cases rather than a big-bang launch, and a named rescue path if the customer isn't live on schedule.

==The stakes are concrete==

Customers who reach first value within 14 days retain at 80%+ a year later; customers who miss the 30-day mark retain at only 35–50%. Onboarding speed is close to the single biggest lever a CS org has over year-one churn — which is exactly why it's phase one, not a formality before the "real" work starts.

==Set a real time-to-first-value target==

There's no honest single universal number — benchmarks split sharply by segment (roughly 7 days for SMB, 12 for enterprise, sub-2-days for fast self-serve categories) — but the target should be a specific "aha" milestone, not "onboarding complete." Measure days from contract signature to that milestone, not to some internal completion checkbox.

==Where this feeds==

A customer who hits their onboarding target moves cleanly into [[Adopt]]. One who doesn't is the first entry in the [[Risk|Post-Onboarding Adoption Lag Play]].

==Sources==

* [https://userpilot.com/blog/time-to-value-benchmark-report-2024/ Userpilot — 2024 Time-to-Value Benchmark Report] — TTV medians and the 14-/30-day retention cliff

[[Category:Customer Success Manager]]
[[Category:Technical Account Manager]]