Time to Value (TTV): How Long a New User Takes to Get a Result
Time to value is the time between a new user’s first contact with your product and the first moment it does something useful for them, such as a first invoice sent or a first file checked. You measure it in minutes, hours or days from signup to a chosen value event. The shorter it is, the fewer people give up before they see why the product exists.
What is time to value, and what does it count?
It is a duration, and that is what separates it from its neighbours. Activation rate asks how many people reached the first useful moment. Time to value asks how long those people took. Both rely on the same value event, but one is a share and the other is a length of time, so a product can have a good share that takes two weeks, or a fast route that most people never take.
Start the clock at signup, or at the first visit if you let people try before signing up. Stop it at the value event you chose, written down before you look at the numbers. For a screenshot-annotation tool, that might be the first annotated image saved. For a code-snippet manager, the first snippet found again by search. The event is the point at which a user would say “this worked”.
How do you measure it with a handful of users?
Use the median, not the average. A few people who sign up at night and return the next afternoon stretch the average into something that describes nobody. The median is the middle value when you sort the times, and one extreme user cannot move it. Report it with the count of people it is based on.
| User | Signup to first invoice sent |
|---|---|
| A | 6 minutes |
| B | 9 minutes |
| C | 11 minutes |
| D | 14 minutes |
| E | 22 minutes |
| F | 1 day, 3 hours |
| G | never |
| H | never |
| I | 2 days |
Among the seven who got there, the median is 14 minutes: sorted, the times run 6, 9, 11, 14 and 22 minutes, then 27 hours and 2 days, and the fourth of seven is 14 minutes. The average of the same seven would be nearly eleven hours, a figure that describes none of them. The two who never arrived are a separate and more important fact. Report them as “2 of 9 had not reached value” instead of dropping them from the calculation, or the number flatters you.
To collect the data, log the signup time and the value-event time for each user in a spreadsheet, or read them from your database. Even better, sit with five new people while they try it, on a call or in person, and time them with a stopwatch. Their hesitations are more informative than any average.
How do you shorten it?
- Remove steps before the first result. Delay profile questions, team invitations and settings until after the first success.
- Provide sample data. An empty dashboard shows nothing. A preloaded example lets someone see the result before they enter their own.
- Offer an import. If people already have the data elsewhere, let them bring it in with one click or a paste.
- Set sensible defaults. Each choice you ask for at the start adds time and doubt.
- Do the first run by hand. For your first users, set it up for them on a call. You will see what slows people, and you can then automate that exact step.
- Write one useful email. A message after signup that says what to do first, with a link that goes straight there, replaces a week of wandering. The onboarding email sequence template gives wording.
Speed is not the only goal. If the first result is fast but meaningless, you have shortened a metric and not the user’s path. Check that the people who reach the event quickly also come back, which is what retention rate shows.
Why does it matter more for self-serve products?
Because nobody is there to help. In a sales-led product, a person guides the buyer through a demo and the onboarding call, so a long path is tolerable. In a product that people try alone, which the product-led growth entry describes, the product has to deliver the first result inside a single sitting, or the visitor leaves for the next tab. The smaller your audience, the more each lost visitor costs.
This applies to launches in a particular way. People who arrive from a listing are giving you a few minutes of attention, and the visitor who cannot reach a result in that sitting rarely returns. When you launch your product free, make the first screen offer the shortest route to the result, and test the route yourself on a phone. If your product is aimed at money questions, the finance app ideas on the board show how makers describe the first useful answer they want a user to get.
Where does measuring it go wrong?
- Ignoring the people who never arrive. Reporting only the times of successful users hides the loss. Show the count of those who did not reach it.
- Mixing wall-clock and active time. A user who signs up on Friday and returns on Monday has a long elapsed time and a short active time. Record both if you can.
- Choosing a vague event. “Used the product” cannot be timed. Pick a specific action.
- Optimising a rare path. If most users arrive from a source that needs a different first step, time that group separately.
Ask the people who left what they expected to happen, and compare that with what did. The feedback request template can help you word the question, and a private beta is a safe place to run these timings before launch day.
Frequently asked questions
What does time to value mean?
It is the length of time between a new user’s first contact with your product and the first moment it does something useful for them. You pick a value event, such as the first invoice sent, and measure from signup to that event. It is usually reported as a median, alongside the share of users who never arrived.
How is time to value different from activation rate?
Activation rate is a share: the portion of new signups who reach the value event. Time to value is a duration: how long the people who reached it took. They use the same event but answer different questions, so a product needs both to know how many arrive and how quickly.
Should I use the average or the median?
Use the median. A few users who wait overnight or return days later pull the average up so that it describes nobody. The median is the middle value of the sorted times and stays steady with a small sample. Report the number of people behind it and the number who never reached the event.
What is a good time to value?
There is no single answer, because it depends on the job. Some products can show value in minutes, while others, such as one that needs a data import or a team rollout, may take days. Measure your own first cohort, then judge each change against that figure with the same event.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.