Your Onboarding Has a Setup Completion Rate. Does It Have a Time-to-Value Rate?

Implementation completion tells you the checklist ended. Time to value tells you whether the customer reached a useful outcome—and how long the gap lasted.

An onboarding dashboard can look healthy while a new customer is still waiting for the product to do the job they bought it for. The setup checklist is complete; the data source is connected; training is done. But has the customer reached a result they would recognize as useful?

That is a different question from whether onboarding finished. Keep the completion metric—it helps you see where implementation stalls—but pair it with a measure of first value. Strictly speaking, time to value is a duration, not a rate. The companion rate is the share of eligible customers who reach a defined value milestone within a defined window.

Setup is a milestone. Value is an outcome.

Setup events are usually easy to count: an account was configured, an integration connected, a user invited. Those events show that work happened. They do not necessarily show that the work solved a customer problem.

For a support platform, connecting an inbox may be a setup event; resolving a customer case through the intended workflow may be a first-value milestone. For another product, first value might be a paid invoice, a report shared with a team, or a workflow completed successfully. The right event depends on the job the customer hired the product to do.

A useful test is: Would the customer say something changed for the better when this event happened? A login, page view, or tutorial click is usually a weak substitute. Amplitude’s activation-event guidance makes the same distinction: choose an event that describes the value received, not merely the screen or button used to get there.

First value is not the same as full adoption or proven return on investment. Treat it as the earliest meaningful outcome, then track later milestones—repeat use, broader team adoption, or measurable business impact—separately. That keeps an early activation signal useful without asking it to prove more than it can.

Define the clock before you measure it

For each onboarding path, write down two timestamps:

• Start: the consistent event that begins the clock, such as workspace creation for a self-serve product or a customer kickoff for a sales-assisted implementation.
• First value: the first time the agreed customer outcome is achieved.

Then calculate time to value = first-value timestamp − start timestamp. The Amplitude overview of time to value describes the same basic ingredients: a start point, a value event, and elapsed time between them.

Do not quietly change the start event from one cohort to another. If self-serve and enterprise customers have genuinely different journeys, define and label each clock, and compare like with like. Otherwise a change in your timestamp convention can look like an improvement or a slowdown that never happened in the customer experience.

Also decide whether the unit is a user or an account. If one person can get value alone, a user-level measure may fit. If the promised outcome requires a team, an account-level milestone is more honest than counting an administrator’s setup action. Pendo’s onboarding measurement guide explicitly distinguishes measuring success by visitors or accounts and supports defining success events for particular segments.

Segment by the path to value

A single blended number can hide the customers who are stuck. Start with segments whose expected outcome or implementation path is meaningfully different: use case, self-serve versus assisted onboarding, customer size, or a required integration. Do not split the data into so many tiny groups that every movement looks important.

The milestone can differ by customer job, but label those definitions clearly. If one segment’s first value is a completed report and another’s is an automated workflow, compare each group with its own baseline rather than presenting the durations as if they measured an identical event.

For customers who do share a milestone, look beyond the average. A median shows the typical time for customers who reached value; a higher percentile shows how long the slower part of that group took. Keep accounts that have not yet reached the milestone visible, too. If you calculate time only for customers who succeeded and hide everyone else, a small fast group can make onboarding appear healthier than it is.

Put time and attainment on the same dashboard

A practical first-value view can sit beside your setup-completion chart. Track:

1. Setup completion: the share that finished the agreed implementation steps.
2. First-value attainment: the share that reached the milestone within a stated window.
3. Time to first value: the median and a slower-tail percentile among accounts that reached it.
4. Not yet at value: eligible accounts still waiting, shown by segment and cohort age.

Choose a window that fits the product’s actual buying and implementation cycle; there is no single deadline that makes sense for every SaaS product. Compare cohorts at the same age, and keep the number of accounts in view so a small sample does not masquerade as a trend. If some cohorts have not had enough time to mature, label them rather than treating their incomplete journeys as final outcomes.

If completion is high but first-value attainment is low, the checklist may be measuring internal readiness rather than customer progress. If both are low, find the earliest stalled step. And if a customer completes setup but cannot reach the outcome, trace the handoffs and decisions around that workflow; Rothenhall’s guide to diagnosing the first broken revenue-workflow handoff offers a useful way to distinguish unclear operating rules from missing implementation.

The number is a prompt to investigate

Once the milestone is instrumented, check whether customers who reach it also return to use the product or advance to the next outcome. That can help you decide whether the event is a useful early signal. It does not, on its own, prove that reaching the event caused later retention; Amplitude’s activation guidance makes that correlation-versus-causation caveat explicit.

The point is not to replace onboarding completion with one supposedly perfect metric. Completion tells you whether the planned setup work got done. Time to value and first-value attainment tell you whether—and how quickly—the customer began to get something useful from it. Keep both views, then use the gap between them to find where the customer journey needs attention.