Time to Value in SaaS: How to Define and Measure It

Most customer success teams say they want customers to reach value faster, but few can say how many days it currently takes. Without a number, "faster" is a feeling. This guide shows how to define time to value (TTV), pick a start event and a value milestone, calculate it, and use it to find stuck accounts early.

What time to value means (and what it does not)

Time to value is the time from the start of the customer relationship to the moment an account reaches a defined value milestone. Metabase's metric definition is explicit that without a stated milestone the metric is not well defined. Intellum describes the same idea as the time between signup and the customer's first meaningful outcome.

Two related terms are easy to mix up:

• Time to first value (TTFV): the time to the first measurable outcome. ClientSuccess contrasts it with TTV, which it uses for reaching a repeatable, sustained level of value.
• Onboarding completion time: how long your internal checklist takes. This is your progress, not the customer's. A customer can finish every onboarding step and still get no value.

Pick one term and one definition for your company, and write it down.

Step 1: Choose one start event

The clock needs a single, consistent starting point. Contract signature, kickoff call and first login can be days or weeks apart. Metabase suggests contract start for sales-led accounts and signup for self-serve accounts, and says to apply the choice consistently. ClientSuccess lists kickoff, contract start or implementation start as workable options.

There is no universal right answer, and sources disagree. What matters is that you choose once. If you start at contract signature, your TTV includes any delay between the deal closing and the kickoff. That is often the delay you most want to see, so for sales-led B2B, contract start is a practical default.

Step 2: Define the value milestone

The milestone should be something the customer would recognize as progress, not something you did for them. Compare:

Metabase offers a useful test: a good milestone correlates with retention. If reaching it does not predict renewal, it is an activity marker rather than a value marker. You can check this later by comparing renewal outcomes for accounts that reached the milestone and those that did not.

Intellum adds a caution: because the business defines value rather than the customer, TTV can become a vanity metric if it is the only thing you track. Confirm the milestone with a few customers by asking what result they hoped to see in the first 90 days.

Also write down a version number. Metabase notes that changing the milestone changes the metric, so annotate any change on your chart.

Step 3: Calculate it

The formula Metabase uses is:

Time to value = median(milestone date - start date)
                across accounts that reached the milestone

Some practical rules:

1. Use the median, not the mean. A few stalled accounts will distort an average. Metabase also suggests reporting the 90th percentile (p90) to show the slow tail.
2. Report the reached-milestone rate next to the duration. If only 60% of a cohort has reached the milestone, the median of that 60% flatters you. Track "reached within 30 days" as a percentage as well.
3. Segment. Metabase recommends separating self-serve and enterprise accounts because their start events and typical ranges differ, so a blended number shifts whenever the customer mix changes.
4. Group by start month. Compare cohorts, not one running average.

Worked example (illustrative)

For example, imagine a company that signed six mid-market accounts in March. The days from contract start to the first shared report were 12, 18, 21, 25, 40 and "not yet reached."

• Reached milestone: 5 of 6 (83%)
• Median TTV of the five that reached it: 21 days
• Reached within 30 days: 4 of 6 (67%)
• The sixth account is the one to act on today.

These numbers are invented to show the arithmetic, not a benchmark.

Step 4: Be careful with benchmarks

Published TTV benchmarks vary widely because companies define start and value differently. Intellum, citing Userpilot's 2025 benchmark, reports a median of about 1 day, 12 hours and 23 minutes. That figure comes from product signups, where value is reached inside the app, and it will not fit a sales-led product with an implementation project.

Your best benchmark is your own baseline. ClientSuccess recommends measuring your own starting point, segment by segment, and reducing it month over month. Use external numbers only to sanity-check your order of magnitude.

Step 5: Capture the data with minimal effort

You do not need a data warehouse to start. ClientSuccess suggests five fields per account as a minimum: segment, target first-value milestone, start date, first-value date, and blockers or status. Product event tracking can come later.

A simple tracker looks like this:

Client:               ____________
Segment:              SMB / Mid-market / Enterprise
Start date:           ____________  (contract start)
Target milestone:     ____________  (v1)
Target date:          start + ___ days
Milestone reached on: ____________
Days to value:        reached - start
Blocker / status:     ____________
Owner:                ____________

If you keep this in a spreadsheet, add a column for "days since start" so stalled accounts stand out. If your CRM supports custom fields and formulas, you can calculate it automatically. In XPI CRM, for example, you can add custom date fields for the milestone and use a formula field for the day count. A playbook can start automatically when a client is created, so the milestone and target date are set on day one. See the spreadsheets comparison if you are deciding when a sheet stops being enough.

Step 6: Use it to intervene

TTV is only useful if it triggers action before the account goes quiet. Set a target for each segment based on your baseline, then check progress against it.

Weekly TTV check

• List accounts started in the last 120 days that have not reached the milestone
• Flag any account past 50% of its target window with no progress
• For each flagged account, name the blocker: customer resources, technical, unclear goal, or wrong users involved
• Assign one next action and one owner, with a date
• Escalate accounts past 100% of target to the account executive or an executive sponsor
• Note common blockers and fix the cause in your onboarding plan

The common blockers matter more than any single account. If three accounts stall at the integration step, fix the integration guide, not the three accounts. For the plan that surrounds this, see our customer onboarding plan template.

Connect TTV to health and renewals

A late milestone is an early risk signal. An account still short of the milestone at day 60 deserves a different conversation from one that hit it at day 14. Feed the result into your customer health score, or at minimum put it in the churn risk review. Later, test the relationship: compare renewal rates for accounts that reached the milestone inside your target window against those that did not. That is how you confirm the milestone is worth tracking, as Metabase suggests.

Common mistakes

• Moving the milestone to make the trend look better. Version changes instead.
• Averaging everything. Use the median, p90 and the reached rate.
• Mixing segments. A blended number hides what is happening in each.
• Measuring your tasks. If the milestone is "kickoff held," you are measuring your calendar.
• Tracking without acting. A number nobody reviews weekly will not change.

Try it in XPI CRM

XPI CRM gives you clients, custom fields, playbooks and tasks in one place, so a TTV tracker and its follow-up actions can live next to your health scores and renewals. You can also connect an AI assistant to review stalled accounts (setup guide), and the help center covers custom fields and playbooks. Start free — every feature included, no credit card.