Time to value: how to measure it and shorten it

Time to value (TTV) is the time from a user's sign-up to the first moment they get the outcome they came for. Picture a founder watching 14-day trials expire while most new accounts never connect a data source.

Or a board member asks "what is our time to value?" and the dashboard shows an average nobody trusts. That average mixes users who got value in ten minutes with users who needed a week. Users who never got there at all don't appear in it. A useful answer needs one clear value event, two numbers per cohort and a short list of fixes.

What time to value measures

Time to value measures how long a new user takes to get real benefit from your product. Amplitude defines it as "the elapsed time between when a user signs up and when they experience meaningful benefit from your product." The start is easy to log. The end is the hard part, because "meaningful benefit" has to become an event you can see in your data.

Two clocks start at sign-up and stop at different moments. Amplitude draws the line like this: "Time to activation measures how quickly users complete a key action, such as creating an account, adding their first item, or inviting a teammate. Time to value measures how quickly they experience the benefit of that action and understand why it matters."

In a reporting tool, building a first report is activation. Using that report in a Monday meeting is value. Amplitude also warns: "You can easily have high activation with low retention if activated users never experience the benefit they came for." So a fast activation clock can look healthy while the value clock never stops for many users.

Vendors don't use the term the same way. Userpilot's benchmark report labels its figures "time to value", but it measures the time to each customer's activation event. In Amplitude's split, that is time to activation. Pick one value event, name it in every report and say which clock you mean.

Sales-led B2B products start the clock at contract signature or kickoff instead, and the FAQ covers that case.

Why time to value matters

The window for getting users to value is measured in days, not months. Amplitude's 2025 Product Benchmark Report, built on more than 2,600 companies, puts the 90th percentile product at around 21% activation on Day 1. In Amplitude's data, that rate drops to roughly 12% by Day 7 and about 9% by Day 14.

Read those figures as activation rates on each day, not as the retention of one cohort. They also come from Amplitude customers across product types, not SaaS alone.

Amplitude's post has a sharper line for the median case: "For half of all products, more than 98% of new users aren't active two weeks after their first action." That sentence describes the median product and activity after a first action, so it is a different cut from the 90th percentile rates above. Both point the same way: most new users go quiet within two weeks.

Amplitude also found that "69% of products with strong early activation were also strong three-month retention performers." Amplitude itself calls this a correlation. Products that activate users early tend to retain them too. The data does not show that a faster time to value causes better retention on its own.

Taken together, the findings point to a practical choice of units. If most of the drop happens in two weeks, a monthly average is far too coarse. Measure time to value in hours and days, per weekly cohort.

How to measure time to value

You can measure time to value from your own event data in five steps. You need a start event, a value event and a timestamp for each, per user.

1. Pick the start event. For self-serve products, use account creation. For sales-led products, use contract signature or kickoff. Keep the same event in every report.
2. Pick the value event. Choose an outcome, not a setup step, and make sure it is observable in your data. Amplitude's guide to TTV adds: "Use the first occurrence of the value event to avoid inflating numbers from repeat actions." Then validate it like an activation event: users who reach it should retain better than users who don't.
3. Compute it per user, per weekly cohort. Subtract the start timestamp from the first value timestamp for each user. Group users by the week they signed up.
4. Report two numbers. First, the share of the cohort that reached value within a fixed window, such as 14 days. Second, the median time among those who reached it. Amplitude's guide advises medians over averages because TTV distributions often have long tails. It also suggests watching the 50th, 75th and 90th percentiles. Report a cohort only after its full window has passed, or its share will look too low.
5. Segment the result. Amplitude's blog recommends mapping TTV "by acquisition channel, user role, company size". Add plan type if you sell more than one plan.

The two numbers in step 4 protect each other. A median of reachers only describes the users who got there. If a change pushes slow users out before they reach value, the median falls and looks like progress. The share reaching value falls at the same moment, and that number tells you what really happened.

The value event depends on what your product does. The rows below are illustrative examples, not benchmarks.

What is a good time to value?

There is no universal good time to value. The right number depends on the outcome: a shared report can take minutes, while a first payroll run waits for a pay cycle.

Userpilot's benchmark report shows how wide the spread is across industries. Its averages come from 62 companies, each measured to its own activation event.

Those are averages of time to activation, the first clock above, taken from Userpilot's user activation dashboard. Userpilot also reports "no direct correlation between company size and time to value."

Don't set any of these as a target. Each company picked its own activation event, and averages are pulled up by the slow tail. Don't hold them next to Amplitude's activation rates either. The two vendors measure different events across different customer bases.

Your own history is the benchmark that works. Put your last eight weekly cohorts side by side, with both numbers for each. A good trend is a rising share reaching value while the median holds steady or falls.

How to shorten time to value

Shorten time to value by removing what stands between sign-up and the outcome. Work in the order below, because the first steps are cheap and tell you where to aim the rest.

Find the step where users stall

Build a funnel from the start event to the value event, with every required step in between. The stall step is the one with the lowest step-to-step conversion rate. Check the median time per step as well. A step that most users pass but that takes three days is your second target.

Delete or defer steps before value

Every field, screen and setting before the outcome adds time and another chance to quit. Amplitude's blog suggests making required fields optional, using smart defaults and making verification asynchronous. Move invites, profile details and billing until after the first win. Amplitude's own summary is short: "Deliver one clear win quickly."

Prefill and do the setup for users

Empty states slow people down. Offer templates and sample data so the first screen already shows a result. Where setup is heavy, do it for the user: import their spreadsheet, connect the data source on a call or build the first project together. Our guide to SaaS onboarding best practices walks through these patterns in more detail.

Give a first taste before the sign-up wall

Some products can show value before they ask for an account. For Masa, Kreto found that the mandatory sign-up wall was the biggest drop-off point: users left before experiencing any value. The team restructured the flow to show the core experience first and defer registration. Sign-up conversion rose from 32.7% to 63%. The case page reports sign-up conversion, not a time to value figure.

Moving a wall like this changes screens, copy and tracking at once. Move the start event to first app open, as in the consumer app row above. Plan it as product marketing work, not as a design tweak.

Pull users back to the next step

Many users leave before value and never come back on their own. Trigger an email or push message from the step they left at, with one action that leads to the next step. The onboarding email sequence post shows how to set up those triggers.

Shorten implementation in sales-led deals

In sales-led products, most of the time to value sits in implementation. Agree on a fixed kickoff plan at signature: who connects which system, by which date, and what first live use looks like. Track each account against that plan the way you track users through an onboarding funnel.

Common time to value mistakes

• Reporting the mean. A few users who take weeks pull the mean far from the typical user. Report the median and its tail percentiles instead.
• Reporting a median of reachers only. Users who never reached value vanish from the number. Put the share reaching value next to it every time.
• Using a setup step as the value event. "Data source connected" is a step toward value, not value itself. Check your candidate event against the retention curve of users who reach it.
• One number for all segments. Paid and organic users, or admins and invited members, often move at very different speeds. A blended number hides which group stalls.
• Reading the newest cohorts too early. A cohort that signed up five days ago has not had 14 days to reach value. Report its share only after the full window has passed.

FAQ

What is the difference between time to value and time to first value?

They describe the same idea. Time to first value is the time to the first outcome a user gets, which is what most teams mean by time to value. Later values follow, such as a second report or a repeat order. Measure the first one to judge onboarding, and track repeat value as part of retention.

How is time to value different from time to activation?

Time to activation stops when a user completes a key action. Time to value stops when that action pays off for them. In a simple product the two can be minutes apart; in a complex one, days. Report the clock you actually track and label it, because vendors and dashboards use the terms loosely.

How do you calculate time to value?

For each user, subtract the start event timestamp from the first value event timestamp. Group users into weekly sign-up cohorts. For each cohort, report the median time among users who reached value, plus the share who reached it within your window. Add the 75th and 90th percentiles to see how long the tail runs.

How do you measure time to value in B2B sales-led products?

Start the clock at contract signature, or at kickoff if implementation starts later. Define value as the first live use by the customer's team, such as the first real report run or the first order processed. Track accounts rather than users, and log each implementation milestone so you can see which one runs late.

Find the step that delays value

You now have a start event, a value event and two numbers for each weekly cohort. You also know the step with the lowest step-to-step rate between them. Often the fix crosses product screens, onboarding emails and the promise your ads make before sign-up. That cross-funnel work is what Kreto does as an outsourced growth team. If your stall step spans those areas, tell us what you found.