What is time to value?
Time to value (TTV) is the time a new user or account takes to get the first meaningful result from a product after signing up. Teams track it because the longer it takes, the more new users leave before they see why they came.
How do you measure time to value?
You measure time to value as the elapsed time between sign-up and the first value event, reported as a median across a cohort of new users. The math is easy. Agreeing on the value event is the hard part.
A value event is the first moment the user gets the outcome they came for, not the first click. For an invoicing tool, that is sending a first invoice, not opening the invoice editor. For an analytics product, it is a chart built on the user's own data, not the sample dashboard.
The formula:
Time to value = time of first value event minus time of sign-up
Worked example: say 1,000 people sign up in March and 600 of them send a first invoice. Sort those 600 by elapsed time. If half of them sent it within three days and half took longer, your median TTV is three days. The other 400 have no TTV yet, and that share belongs in the same report.
Use the median, not the mean. A handful of users who come back after a month drag an average up and hide what most people experience.
There is no universal good TTV. It depends on how much setup the result needs (data import, integrations, inviting a team), who has to do that setup, and whether the buyer and the daily user are the same person. Compare each new cohort with your own earlier cohorts, and segment by plan and role.
What slows time to value down?
Almost always, setup that stands between the user and the result:
- Configuration before value. Fields, templates and permissions the user has to understand before anything useful happens.
- Other people. An admin has to connect single sign-on, IT has to approve an integration, a teammate has to accept an invite.
- Data that has to arrive first. Import a spreadsheet, connect a CRM, wait for a sync.
- Navigation. The user knows what they want but not where it lives in the product.
Picture a project-management tool where a new admin has to invite the team, import tasks and connect Slack before the board looks like their work. Each step is a place to stall. Product tours and checklists point at those steps, but the user still has to do each one.
How do you accelerate time to value?
Start by removing or deferring every setup step the first result doesn't need. Then:
- Pre-fill with sensible defaults, and with the user's own data where you already have it.
- Ask what the user is trying to do at sign-up and route them to that path, not a generic tour.
- Find where cohorts stall in funnels and session replays, and fix the step with the biggest drop.
- Track median TTV and the share who never reach value, cohort by cohort, so you know a change worked.
An in-product agent narrows the gap between knowing what you want and finding where to do it. The user says "import my tasks from this spreadsheet and invite my three leads", and the agent does the setup with them. With Foldspace, the Product Agent runs that setup through the product's own APIs, limited to what the signed-in user may do, which helps teams accelerate time to value.