Time to Value Is Killing Onboarding

Time to value is a vanity metric for onboarding. It sounds right: compress the timeline to first measurable value, show activation in 30 days, declare success by day 60. Every onboarding playbook in SaaS is built on this premise. The problem: it stops predicting customer success by month four and creates false confidence that the customer is actually set up to retain, expand, and operate independently.

Optimising for speed to initial value produces a system that prioritises shallow activation over deep capability building. The renewal team inherits the consequences.

Why It Collapses at Scale

At enterprise scale, customers aren't a homogeneous cohort moving through the same onboarding funnel. One customer needs the product to scale immediately. Another is a small department inside a much larger company, piloting a capability they may roll out gradually across multiple business units. A third is replacing an incumbent with a migration that requires a long period of parallel running before cutover.

Time to value means something completely different in each of these scenarios. The metric either becomes too abstract to guide execution, or it gets measured by lowering the bar until every customer hits it. A user account created counts as value. A dashboard viewed counts as value. An API authentication counts as value. These are activations, not outcomes. They're the equipment, not the work.

By month four, activation becomes noise. Customers have either integrated the product into their operational rhythm or they haven't. They've either discovered that what they bought solves the problem they expected, or they're managing drift. The onboarding team is no longer the lever. But the onboarding metrics are silent on this transition. Health scores are silent on it. Renewal forecasts are built on a foundation of silence.

A customer can look perfectly onboarded by every time-to-value metric and discover at renewal that they can't sustain the value proposition without ongoing professional services. Another customer can look slow on activation benchmarks but by month six be operating independently, expanding use cases, and building internal expertise. The metric doesn't distinguish between these trajectories because it was never designed to.

The Incentive Trap

Onboarding teams measured on time to value optimise for exactly one thing: reaching "value delivered" as fast as possible within a defined window, usually 60-90 days. After that window closes, accountability transfers. If the customer churns at month five because they can't sustain their use case, that's categorised as a CSM failure. If the customer discovers six months in that they're using the product wrong and can't expand without rebuilding their data model, that's a sales issue. The onboarding team shipped its metrics and moved to the next cohort.

This fragmentation creates three predictable failures.

First: onboarding gets optimised for pace, not depth. Discovery gets compressed because discovery is slow. Customer learning gets organised around demos and happy-path workflows instead of thorough investigation of integration risks, data challenges, and organisational adoption barriers. The team measures for speed-to-completion. Edge cases get deferred to "post-onboarding."

Second: playbooks get built for the easy customers. The repeatable programme works well for customers whose use case maps cleanly to product capabilities, whose data is well-structured, and whose internal alignment is strong. Those customers were going to succeed anyway. The programme should be optimising for the ones where onboarding creates differentiation: complex migrations, non-standard data, teams with organisational friction around change. Instead, those customers get the same fixed-duration playbook and hit the deadline in a brittle, incomplete state.

Third: renewal conversations become remediation conversations. Instead of arriving at month twelve with a story about successful, expanding outcomes, the CSM is walking into a conversation where the customer has discovered problems that should have been surfaced at week three. The renewal team burns months of capacity fixing what onboarding rushed past. This is particularly visible in large deals where implementation is complex. Onboarding declares successful activation. Renewals inherit a customer who never reached stable operations.

What Sustained Value Looks Like

Value isn't a binary event on day 45. It's a trajectory with gates.

For a customer deploying a complex platform, the trajectory looks like this: initial value, then confident internal capability, then independent execution of the primary use case, then readiness to expand into secondary use cases, and finally the ability to onboard new users and use cases without re-engaging the vendor.

Each gate matters. Reaching date targets means nothing if gates fail. A customer who looks activated on schedule but hasn't reached confident internal capability is a future escalation. A customer who reaches independent execution is an expansion candidate. The distinction is binary and it has direct revenue implications.

You see this pattern repeatedly in complex onboardings. The team hits the activation target. Dashboards are live, data is loaded, metrics say success. Months later, the first expansion use case exposes that the core configuration was incomplete. The original onboarding team didn't have visibility into the edge cases because discovery was compressed. The CSM inherits the explanation job when expansion stalls.

The customer looked onboarded. They weren't ready for the next phase. The onboarding metric said green. The revenue trajectory said stalled.

Measuring What Actually Predicts Retention

Onboarding should be measured on gate achievement by cohort. What percentage of customers reach confident independent execution by the natural milestone date for their segment. What percentage reach expansion capability by month six. What percentage reach month twelve without returning to onboarding for rework or requiring CSM escalation for foundational fixes.

These metrics extend beyond the traditional onboarding function's boundaries. They require the onboarding team to care not just about whether customers are activated, but whether they're activated correctly: with the right foundation, genuine capability, and sustainable outcomes. That makes measurement harder. It also makes it honest.

The Operational Change

Measuring sustained value instead of time to value changes how onboarding operates.

Discovery gets more rigorous. Instead of a structured intake call, discovery becomes an investigation of technical readiness, organisational alignment, data challenges, and realistic timelines. Friction gets identified at week one instead of discovered at month four.

Playbooks stop being prescriptive sequences and start being decision trees. What's the actual integration risk. What's the readiness of this customer's team. What should happen first. The path changes by customer context, not just by product line.

The onboarding team gets held accountable for outcomes at months three, six, and nine, not just completions at day 60. This requires visibility into what happens after handoff. It requires the team to own the trajectory, not just the starting line.

This is harder to manage, measure, and report. It's also the only model that produces sustainable outcomes at scale. Time to value makes onboarding look efficient while hiding the capability gap that renewal teams inherit. Sustained value is a leading indicator that actually predicts expansion, retention, and reference-ability. One gets measured in days. The other gets measured in the customers who are still successful twelve months after they signed.