Metrics, retention and the organization · Answered by Golden Section from more than 400 B2B software companies observed
Build it backward from the value the customer was sold. Onboarding is finished when that value is realized and the customer can say so, not when the software is switched on. That means five parts with one named owner: a written handoff from sales that preserves what was promised, account and invoicing setup, a staged implementation with client sign-offs, training limited to the minimum features that deliver the promise, and an adoption metric that ends the high-touch period. Time to value should be as short as that minimum feature set allows, and it is measured on your own cohorts rather than against a universal number. Start by writing the adoption metric for your largest segment, then map every step between signature and that metric.
Onboarding ends at an adoption metric the customer recognizes, not at go-live. Every step before it needs an owner, a trigger and a proof of completion, and the process improves only when you measure each cohort's time to that metric.
| Metric | Value | What it means | Source |
|---|---|---|---|
| Feedback window for onboarding interviews | customers onboarded in the prior 45 to 60 days | recency window for asking customers where the process could improveolder cohorts remember too little to be useful | Golden Section playbookOnboarding Process |
| Iteration pace | at least one average onboarding cycle between changes | minimum wait before judging a process changeunless the fix is urgent, results need a full cycle to show | Golden Section playbookOnboarding Process |
| Implementation phases | 5, each gated by client sign-off | planning and requirements, design and configuration, user acceptance testing, deployment, close-outscope documents are signed before configuration begins | Golden Section playbookImplementation Project Lifecycle |
A customer forms a lasting view of your company in the first weeks after signature. The sale described a destination, and onboarding either delivers it or reveals the gap. When there is no process, each implementation depends on who happens to run it, requirements stay fuzzy, and the customer is trained on everything instead of the three things that matter to them. The result is a customer who is live but not adopted, which is the account that churns at first renewal.
The structure is deliberately plain. The onboarding play owns the handoff, the checklist and the adoption metric. The implementation lifecycle gates each phase on client sign-off so scope cannot drift silently. Implementation hours tracking tells you what onboarding actually costs, which matters because vertical software carries services cost that belongs in gross margin. Measure each cohort's time to the adoption metric and you have a number you can improve rather than a feeling about how onboarding is going.
A company selling scheduling software to dental groups goes live with most customers in five weeks, yet a third of them file support tickets asking how to do things covered in training. The team rewrites onboarding around one adoption metric, 200 appointments booked through the system, and cuts training to the four features that get there. Go-live stays near five weeks, but the median time to the adoption metric falls from eleven weeks to seven across the next two cohorts, and support tickets from new accounts drop. All figures are illustrative.
Products that customers configure themselves can replace much of this with in-product guidance, though they still need an adoption metric. Enterprise implementations with custom development need the full five-phase lifecycle and a contract that prices overages, or onboarding becomes unpaid consulting.
From the Golden Section mistakes list, each paired with the play that prevents it.
Unstructured implementations make every customer's first experience depend on who happened to run it.
Requirements accepted fuzzy at signature surface as scope fights halfway through onboarding.
A scope nobody with authority approved cannot be delivered or demonstrated.
Onboarding is where the customer pays the cost of changing behavior, and a process that ignores that cost stalls adoption.
In the order we would run them. Each is on its own page, most with a free Excel template.
Defines the handoff, the checklist, segment training guides and the adoption metric that ends onboarding.
Runs implementation in five phases with client sign-off at each gate, so scope cannot drift.
Tracks implementation hours by customer so you can price onboarding, bill overages and show its true cost.
Sets the process for retraining and super-users after onboarding, so training does not become an unpaid expense.
Picks up the account at the adoption metric and keeps it moving toward full adoption and expansion.
Customer plays Onboarding is the first of four account management stages, and the customer plays connect it to adoption, renewal and retention.
As quickly as the minimum feature set that delivers the value sold allows, and no single number fits every vertical. Measure time from signature to your adoption metric for each monthly cohort, then work it down. A useful definition of done reads like the last ten customers went live inside a stated number of days, set from your own history.
Implementation is the technical project: requirements, configuration, data conversion, testing and deployment. Onboarding is the wider process around it, including the sales handoff, invoicing, training and the adoption metric. A customer can be implemented and still not onboarded.
One named role, ideally a specialist who handles setup, training and support orientation, then hands the account to account management once the adoption metric is met. Shared ownership between sales and support is how steps fall between people.
Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-09-23. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.