Time to Value — How to Measure It and Shorten It
Time to value is how long a new user takes to get the first real benefit from your product. Learn how to define and measure it, why the median matters more than the average, and where the time usually goes.
Short answer: time to value is the elapsed time between signup and the first moment a user gets what they came for. Measure it as the median time from the signup event to your activation event, and also record what share of users reach it within a day and within a week. Shorten it by removing or deferring every step between the two that does not itself deliver value.
Table of Contents
Definition
Two timestamps:
- Start: the user signs up.
- End: the user reaches value, which you represent with an activation event (finding it).
The gap is time to value.
Be precise about the end point. "Created an account" and "completed the tour" are not value. "Sent the first invoice" is.
There are useful variants:
| Variant | Measures |
|---|---|
| Time to first value | Signup to the first benefit |
| Time to habit | Signup to regular use |
| Time to paid | Signup to first payment |
| Time to team value | Signup to a second person getting value |
Start with the first.
How to Measure
Track both ends as events and tie them to a user:
deepsync("identify", user.id, { signupDate: user.createdAt });
deepsync("track", "signup_completed");
deepsync("track", "activated");Report three numbers per signup cohort:
- Median time from signup to activation, among those who activated.
- Share activated within one hour, one day, and seven days.
- Share never activated.
The third is essential. If you report only the median for users who made it, you ignore everyone who did not. A product where ten percent activate in five minutes and ninety percent never do has a wonderful median and a serious problem.
Also measure in two units:
- Elapsed time, including the hours they were away.
- Active time, the minutes of real effort inside the product. A user who took three days may have spent ten minutes in the product and two days waiting for a colleague.
Why the Median
Time to value is heavily skewed. Most users who activate do it quickly. A few come back three weeks later and finish.
Illustrative: nine users take ten minutes, one takes twenty days. The average is two days. Nobody took two days.
Use the median and the share within fixed windows. They describe what typical users experience.
Where the Time Goes
Build a funnel from signup to activation and note the time between each pair of steps. Then watch first sessions.
| Delay | Typical cause |
|---|---|
| Signup to first screen | Email verification, long signup form |
| First screen to first action | Empty state with no direction |
| First action to setup complete | Integration, import, or installation needing someone else |
| Setup to result | Waiting for data or processing |
| Result to understanding | An output the user cannot interpret |
The longest delays are usually waits on something outside the product: a developer to install a snippet, an administrator to grant access, data to accumulate. These turn minutes into days, and many users never return from them.
Recordings show the active-time problems: hesitation, wrong turns, and errors. They do not show the hours away, which is where the funnel timings help.
How to Shorten It
- Remove steps. Every field and screen before value is a delay.
- Defer what can wait. Verification, team setup, billing details, profile completion.
- Show value before setup. Sample data, a demo workspace, a template.
- Make the hard step easier. Copy-paste snippets, guided integration, a link the user can forward to their developer.
- Do the work for them. Import from what they already use.
- Shorten external waits. Instant feedback that setup worked, and a notification when the result is ready.
- Offer help at the hard step, not at the start.
- Bring them back. A message when the data arrives or the teammate joins.
- Fix the faults. Check JavaScript errors on onboarding pages.
For DeepSync, time to value is the gap between creating a project and seeing the first session. The docs' quickstart is built around that, and a project shows as verified once its first real session lands (quickstart).
Then re-measure for the next cohort. The goal is more users activated within a day, not only a smaller median.
Report "activated within 24 hours" as your headline
It combines speed and reach in one number, and it is hard to flatter.
Key Takeaways
- Time to value runs from signup to a real benefit.
- Report the median, the share within fixed windows, and the share who never arrive.
- The largest delays are waits on things outside the product.
- Remove, defer, and pre-fill to shorten it.
Conclusion
Every hour between signup and value is an hour in which a new user can lose interest. Measure the gap, find where it is spent, and close it.
Frequently Asked Questions
Related articles
Stay in the loop
Get the latest insights on product analytics and user behavior delivered to your inbox.



