Ask three people on a post-sales team how long it takes a customer to get value and you'll often get three different answers. One counts from contract signature, one from kickoff and one from the first login. One means the first report, another means full rollout. All of them are "time to value," and none of them can be compared.
Before you can improve time to value (TTV), you need a measurement everyone trusts. This guide covers how to define the start and end of TTV, which statistics to report, how to set a fixed-day activation target such as day 14, how to cut the numbers by cohort and segment and how to put it all on one report. If you already measure TTV and want to shorten it, see how to reduce time to value after the sale.
Why TTV Is Harder to Measure Than It Looks
TTV sounds like a simple duration: the time between two dates. In practice, both dates are judgment calls, and the data for each usually lives in a different system. The start date sits in the CRM, the end date in product analytics and the context in between in call notes and project plans.
Three problems show up again and again:
- Inconsistent definitions. If the start and end events change from quarter to quarter, the trend line means nothing.
- Manual logging. When CSMs mark milestones by hand, the data is late, incomplete and different for each rep.
- Accounts that never finish. An average that ignores accounts still in onboarding looks better than reality, because the slowest accounts aren't counted yet.
Fixing these is less about tooling than about writing a few decisions down and sticking to them.
Step 1: Pick One Start Event
The start event is when the clock begins. There are a few reasonable choices, and each answers a slightly different question.
Contract signature or closed-won date
This is the customer's view. They start waiting for value the moment they pay. It captures handoff delays between sales and post-sales, which other start points hide. It is also the easiest date to pull reliably from the CRM.
Kickoff call
This measures the onboarding team's own speed. It is useful for evaluating your onboarding process, but it hides any gap between signature and kickoff.
Workspace provisioned
For self-serve or product-led motions, the moment the account is created is often the cleanest start, because it is a product event with an exact timestamp.
Whichever you choose, use one primary start event across the company and document it. If different teams need different views, report the gaps between events separately, for example signature to kickoff, rather than redefining TTV.
Step 2: Define What Counts as Value
The end event is where most TTV definitions go wrong. Logins, page views and seats assigned are activity, not value. The end event should be an outcome the customer would recognize as the product working for them.
Separate time to first value from time to activation
Many teams track two end events, and it helps to name them separately:
- Time to first value: the first moment the customer gets a real outcome, such as a first report generated, a first workflow automated or a first production API call.
- Time to activation: the point at which the account is set up to keep getting value, typically when the core integration is live, the first value event has happened and the intended team is using the product.
Quivly's onboarding page shows a default journey that runs from "workspace provisioned" through "core integration live" and "first value event" to "team trained" and "health review." Whatever your journey looks like, pick one step as the end of TTV and make it an event your systems record automatically.
Make the end event observable
If the end event depends on a CSM ticking a box, your TTV data will be only as good as their memory. Tie it to a product event instead. Quivly's onboarding page notes that it ingests activation events from tools such as Segment, Amplitude and Mixpanel, or from a warehouse such as Snowflake, BigQuery or Redshift. The principle holds regardless of tooling: value should be something the data shows, not something someone reports.
Step 3: Report the Median, Not Just the Average
Once you have start and end events, you can compute TTV per account. How you summarize it across accounts matters as much as the definition.
- Use the median as the headline number. A few very slow enterprise rollouts can pull an average far away from the typical customer's experience. The median shows what the middle account experiences.
- Look at the spread. Two cohorts with the same median can feel very different if one has a long tail of stalled accounts. Track a slow-end figure too, such as how long the slowest quarter of accounts take.
- Count accounts that haven't finished. Report how many accounts in a cohort have not reached the end event yet and how long they've been waiting. Leaving them out flatters the number.
- Show the trend. A single TTV figure says little. The change versus the previous period tells you whether things are getting better.
Quivly's onboarding dashboard example puts this into one tile: a median time to value of 11 days, shown as down 18% versus last month. The figures are illustrative, but the format is a good model, with the median and the trend side by side.
Step 4: Set a Fixed-Day Activation Target
Median TTV tells you how long accounts take. It doesn't tell you, early on, whether a new cohort is on pace. That's what a fixed-day activation rate is for: the percentage of new accounts that reach activation by a set day after the start event.
Why a fixed day works
A fixed-day rate gives you a readout while the cohort is still young. You don't have to wait for every account to finish before seeing whether this month is better or worse than last. It is also easy to explain: "X% of new accounts were activated by day 14" needs no statistics background.
The day-14 example
Quivly's onboarding dashboard example tracks activation at day 14, showing 71% against a target of 68%. Treat those as an example of how to frame the metric rather than as an industry benchmark. The right checkpoint and target for you depend on your product's complexity and your typical rollout length. A lightweight self-serve product might check at day 7, while a product with a heavy integration may need day 30 or later.
How to set your own target
- Pick a checkpoint day that is long enough for a healthy account to activate but short enough to catch problems early.
- Calculate your current activation rate at that day for the last few cohorts.
- Set the target as a realistic step up from your recent baseline, not as a number borrowed from someone else.
- Review it once you've seen a few cohorts against it, and adjust.
Quivly's onboarding FAQ makes a similar point about the journey itself: most teams refine their blueprint over the first 60 days as they see where accounts commonly stall.
Step 5: Cut TTV by Cohort and Segment
A single company-wide TTV figure mixes accounts that shouldn't be compared. Two cuts make the number useful.
Start-date cohorts
Group accounts by the month or quarter their clock started. Compare each cohort's median TTV and activation rate with earlier cohorts. This is how you tell whether a process change actually helped, because you are comparing like with like.
Segments and onboarding tracks
An enterprise rollout and an SMB self-serve setup will never have the same TTV. Measure them separately. Quivly's onboarding page describes separate blueprints for segments such as SMB, mid-market and enterprise, with new accounts assigned to the right track based on CRM fields, contract value or another attribute. Measuring per track means each segment is held to a target that fits it.
For larger accounts, it can also help to look below the account level. Quivly's page notes that it tracks engagement at the contact level, so it can spot when a key stakeholder such as the IT admin, power user or executive sponsor hasn't been activated. An account can hit its value event while an important group is still not using the product.
Step 6: Put TTV on One Report
TTV is only useful if people look at it. Keep the report small and consistent, and refresh it automatically instead of rebuilding it by hand each quarter. A practical onboarding report includes:
- Median TTV for the current cohort, with the change versus the previous period.
- Activation rate at your checkpoint day, against target.
- Accounts in onboarding, so the numbers have a denominator.
- Share of milestones on track across active journeys.
- Stalled accounts, listed by how long they've been stuck and where.
These mirror the tiles in Quivly's onboarding dashboard example: median time to value, milestones on track, accounts in onboarding and activation at day 14. Review the report weekly with the onboarding team and roll it up for leadership monthly. Leadership demand for this view is common. In Quivly's Mycroft story, leadership had been asking for clear milestones and TTV metrics, and the team now tracks milestones and time to value by compliance framework in a live dashboard. For how TTV fits alongside retention and capacity metrics, see CS metrics for VPs.
FAQ
There is no universal number. TTV depends on product complexity, integration effort and segment. The most useful comparison is your own cohorts over time, measured with the same start and end events.
Contract signature reflects the customer's experience and captures handoff delays. Kickoff isolates the onboarding team's speed. Pick one as your primary definition and report the gap between them separately if you need both views.
TTV measures how long accounts take to reach value. Activation rate measures what share of a cohort has reached activation by a set day. TTV is the fuller picture, and activation rate is the early warning.
A few very slow accounts can pull the average away from what most customers experience. The median shows the typical account, and tracking the slowest accounts separately keeps the long tail visible. Want TTV and activation tracked automatically instead of logged by hand? See how Quivly's onboarding at scale maps every new account against your milestones, measures time to value and activation by segment and flags accounts the moment they fall behind.
