Time to Value: the leading indicator that decides whether the customer renews
If onboarding takes 11 months and the contract is 12, the renewal is already lost. Time to Value is the most underrated CS leading indicator — and the only one with a concrete timeframe rule (30 or 90 days, depending on touch model).
If your onboarding takes 11 months and the contract is 12, the renewal is already lost — no matter how well the product performs in the 30 days that remain. That's the central thesis of Time to Value (TTV), articulated by Lincoln Murphy et al. in Customer Success (Mehta, Steinman, Murphy, 2016): there is a direct correlation between onboarding length and renewal probability.
And yet, TTV is probably the most underrated metric in CS teams. Most measure retention (a lag indicator) and NPS (a noisy signal) — and ignore the only metric that predicts renewal behavior months before it happens.
This article synthesizes what five authors and frameworks say about TTV, in the order they matter in practice.
Why TTV is make-or-break
Two value curves illustrate the stakes (Mehta et al., ch. 11):
- Delayed-value scenario: the customer enters the product, sees no result, slides into the trough of disillusionment, and by the time value finally arrives, the internal sponsor has already disengaged or changed roles.
- Improved-value scenario: the team delivers a small early win — a Phase 1 value — and the curve flattens out. The sponsor stays engaged, and there's time to calibrate before the contract expires.
The operational rule: deliver a visible win early and track the longer arc in parallel. The early win buys customer patience for the rest of the journey.
Time to First Value ≠ Time to Ultimate Value
The most common confusion is treating TTV as one thing. It's two:
| Metric | What it measures |
|---|---|
| Time to First Value | The first demonstrable milestone — often a small proof point delivered to the immediate sponsor. |
| Time to Ultimate Value | The full business outcome the customer signed up for — often months or quarters out. |
Programs that only track ultimate value miss the leading indicator. Programs that only track first value declare victory too early and wake up to churn. Track both, with different weights.
The ladder nobody teaches: Day Zero → Aha → First Value
The biggest source of operational confusion in onboarding is treating "activation," "aha moment," and "first value" as synonyms. Chiang (2019), citing practices at Intercom and Facebook, separates them surgically:
Day Zero → Aha Moment → First Value
(I'm enabled) (I get it now) (I got something)
| Concept | Question it answers | Failure if missed |
|---|---|---|
| Day Zero | "Has the customer completed the enabling work?" | They never reach any value at all |
| Aha moment | "Has the customer recognized the value pattern?" | They get mechanical value but don't internalize it |
| First Value | "Has the customer measurably won something?" | They lose the renewal narrative |
The operational consequence matters: if you can't yet measure First Value directly (because you're still negotiating the definition, or because the signal only shows up at six months), measure Day Zero. Day Zero is the best proxy for First Value that exists.
Intercom's Day Zero is things like: invited 5 teammates, integrated with system X, configured custom data Y. Facebook's Aha is the famous "7 friends in 10 days." Every product has its own. You need yours.
The 30/90 rule (Damin)
Of all the sources in the literature, Hiram Damin (Customer Success: O Sucesso das Empresas Focadas em Clientes, 2019) is the only one who commits to concrete numbers:
| Touch model | Time to First Value |
|---|---|
| Tech Touch / Low Touch | ≤ 30 days |
| Mid Touch / High Touch / complex contracts | ~ 90 days |
These are upper bounds, not averages. Faster is always better. Use the 30/90 rule as a planning heuristic when sizing onboarding capacity per segment.
Damin's analogy is the car: to drive, you need to "activate" — open the door, get in, close it, turn the key, accelerate. AC and Bluetooth come later. Activation = First Value delivered = the minimum needed to use the product. Not the full feature set.
His warning is the same one every author raises:
Pay close attention not to put the success of the product or service ahead of what is success for the companies you serve.
First Value is the customer's win, not a milestone the vendor invented.
The golden script: how to capture First Value pre-sale
The most valuable operational contribution comes from Winning by Design's CSM/AM book (WBD, 2018). It's a three-question script meant to be used during the sales cycle — not after.
1. "If you had only one number that you're allowed to show your boss to prove that we've been successful, what would it be?"
2. "What processes or behaviors do you feel need to change to achieve that number?"
3. "Which aspect of our [product or service] do you expect to be most influential in creating that change?"
The sequence peels the onion — outcome → behavior change → product mechanism. The output goes onto the Joint Impact Plan (or Customer Success Plan, depending on your stack) as a First Value milestone with a target date.
The mutual-commitment close:
"Great — so if either of us doesn't follow this plan, then we risk not achieving that value in this time frame. Make sense?"
Why pre-sale? Sponsors disengage the moment the deal is signed (Mehta et al., ch. 11). If the success metric wasn't named while attention was high, you'll chase the customer for six months trying to extract it — and probably won't.
The six accelerators of First Value (Weber)
Donna Weber (Onboarding Matters, 2021) turned TTV from metric into program. Her six accelerators are prescriptive:
- Success Plans — per-customer document naming expectation, target outcome, and how the vendor will help.
- Quick Wins — deliver visible value instantly, even if small. Days, not months.
- In-app Guidance — tooltips, onboarding flows, contextual prompts. Scales onboarding without burning CSM time.
- Learning Pathways — self-serve training at the customer's pace. Supports low-touch and tech-touch.
- Phased Deployments — chunk the rollout into discrete phases, each with increasing functionality and value.
- Customer Maturity Model — crawl → walk → run with case histories at each level. As the customer advances, show them the next rung.
The phasing rule (Nello Franco, quoted in Weber 2021):
Even if your solution can provide an order of magnitude return on investment, don't try to get there all at once. Provide quick wins by phasing your deployment.
When does onboarding end?
This is where the authors diverge — and where most teams play in the dark. The four frameworks side by side:
| Source | When onboarding ends |
|---|---|
| Mehta et al. 2016 | TTV is hit |
| Weber 2021 | (not explicit; it's the deliverable of the "Adopt" stage) |
| McCulloch 2021 | Value One is delivered |
| WBD 2018 | First Value is hit (explicit line) |
| Damin 2019 | Primeiro Valor delivered + customer activated |
Practical recommendation: draw a line. Onboarding has an end — when First Value has been delivered. Without that line, onboarding never ends, adoption never begins, and the customer sits in a limbo where nobody owns them.
The Huddle case: First Value as a contract clause
In 2011, Huddle introduced an unprecedented adoption guarantee: within 90 days, 100% of the customer's initial users would be trained and active — or full refund.
Outcome (MarketWired, 2012): nearly 90% of enterprise customers said the tool was easy to use; adoption rates were exceptional. SharePoint at the time ran 32% in three months.
Lincoln Murphy's analysis: Huddle likely looked at the data and realized that if a customer fully engages within 90 days, they're likely to stay for the estimated lifetime of 3 to 5 years. Day-Zero-by-90-days correlated with multi-year retention.
This is the best-documented case for tying an onboarding milestone to a commercial commitment. We're not recommending you copy it — we're recommending you sit with what it reveals: TTV is a strong enough leading indicator that a company can bet revenue on it.
The 4 most common TTV mistakes
- Defining First Value internally and surprising the customer with it. The definition has to be co-created with the sponsor pre-sale and written into the success plan.
- Gold-plating First Value. Fast and visible beats elegant and late. The customer prefers a small win today over a big win in six months.
- Defining First Value as a product milestone, not a customer-business outcome. "Customer configured X modules" is not First Value — it's Day Zero. First Value is "customer reduced response time by 18%."
- Not measuring Day Zero. When First Value is hard to instrument, Day Zero is the cleanest proxy. Teams that measure only renewals get blindsided; teams that measure Day Zero see the problem 60 days earlier.
What to do this week
If you want to start operationalizing TTV for real, three moves solve 80%:
- For every customer signed in the last 90 days, write down the First Value they signed up for. If you can't, the problem is sales-to-CS handoff, not onboarding.
- Define your Day Zero. What are the 3–5 tasks that, once complete, let the customer begin extracting value? Instrument them in-product.
- Compute the average time from signature to First Value for customers who renewed vs. churned in the last 12 months. If the gap is material — and it almost always is — you have the chart that justifies investing in onboarding to any board.
TTV is not a vanity metric. It's the only one that reliably predicts, months in advance, whether the customer will extend the contract. Teams that treat TTV as Pillar 2's #1 priority (see The 7 Pillars of Customer Success) reduce churn before they even know next renewal's number.
Synthesis of: Mehta, Steinman & Murphy (2016), Customer Success; Weber (2021), Onboarding Matters; McCulloch (2021), The Seven Pillars of Customer Success; Winning by Design (2018), The SaaS Sales Method for Customer Success & Account Managers; Damin (2019), Customer Success: O Sucesso das Empresas Focadas em Clientes; Chiang (2019), The Startup's Guide to Customer Success.
