Time to value (TTV) is the time between a customer starting with your product and reaching the first outcome they would call worth it. For a B2B SaaS free trial, that means the clock starts at signup and stops at the moment a user does something real and sees a result, not when they finish creating an account. Shorten that gap and more trial users stick around long enough to pay.
This guide covers how to define the value moment, how to calculate TTV without fooling yourself, what targets are reasonable for self-serve versus enterprise, and which parts of a trial usually slow users down. It is written for product leaders and founders who own trial conversion.
TL;DR
- Time to value is the elapsed time from signup (or contract) to a customer's first meaningful outcome. Account creation and setup steps are prerequisites, not value.
- Track the median, not the average, and split it by segment. A blended average hides where the path actually breaks.
- Self-serve B2B products should aim for days, not weeks. Enterprise products with data migration and training can reasonably need weeks.
- The biggest delays are usually self-inflicted: setup that comes before any payoff, prompts at the wrong moment, and unclear next steps.
- The fastest way to find the delay is to go through your own trial as a new user and time every step.
Table of Contents
- What time to value actually measures
- Why it matters for free trials
- How to define your value moment
- How to calculate it
- What a good target looks like
- Where trials lose time
- A step-by-step way to cut TTV
- Time to value for AI features and agents
- Our perspective
- Getting help with your own trial
- A short checklist before you start
- FAQ
- Sources
What time to value actually measures
TTV measures the duration from a customer's signup or purchase to their first meaningful outcome, often called the "aha moment." The important word is meaningful. Creating a workspace, verifying an email and connecting a calendar are all things a user does for you. Value is something the product does for them.
Two neighbors of the metric get confused with it:
- Time to first value (TTFV). Distilled CS defines TTFV as the number of days from contract signing to the customer's first defined success milestone, and notes that plain time to value may stretch to full go-live. In practice, teams use "time to value" for either; what matters is that you pick one definition and keep it.
- Activation rate. This is the share of users who reach the value event. TTV is how long it takes them. The two share a goal but call for different fixes: a low activation rate means many people never get there, while a long TTV means those who do get there are slow.
A useful sanity check: if the event you picked can be completed without the product producing anything the customer cares about, it is a setup step, not value.
Why it matters for free trials
A free trial is a countdown. Whether it is 7, 14 or 30 days, the user is deciding from the first session whether this product deserves their time. Every minute spent on configuration before a payoff is a minute they spend doubting.
The pattern shows up in the research. One 2026 analysis of 62 B2B SaaS companies, summarized by Onramp, put average user activation at 37.5%, meaning roughly two-thirds of new signups never experience the core value. That is an industry snapshot from a vendor's blog, not a law, but it matches what we see when we sign up for trials: most people leave before anything useful happens.
The cost compounds. A user who never reaches value never invites a colleague, never connects real data and never sees the pricing page with a reason to pay. Your sales and marketing spend acquired them; your first-session experience lost them.
How to define your value moment
You cannot measure time to value until you can name the value event. Most teams skip this and measure a convenient event instead, such as first login or "setup completed."
A practical way to find it:
- List the jobs the product is hired for. Not features, jobs. "Know which invoices are overdue" is a job. "Use the dashboard" is not.
- Find the earliest observable action where that job is done. A report generated from real data. A workflow that ran. A teammate who received the thing.
- Compare retained and churned users. Which action do paying customers almost always take in the first sessions that churned trial users do not? Research on user journeys using process mining suggests aha moments are not random: they are predictable milestones tied to specific user roles and product features, so map them from behavior rather than assumption.
- Define one event per role. An admin's first value is rarely the same as an end user's.
- Write it as a sentence. Project management guidance recommends distilling a goal to a single line: we will do X to make Y better, as measured by Z, which is worth W. The faculty note at UMass Lowell frames this as keeping the business case alive through delivery. Applied to TTV: "We will get a new admin to a live report from their own data, as measured by median hours from signup, which is worth more trial-to-paid conversions."
How to calculate it
The formula is simple: value event timestamp minus start timestamp, per user or account. The discipline is in the choices around it.
Choose the start line
For self-serve trials, start at signup. For sales-led deals, start at contract signing, or at kickoff if you want to isolate your onboarding from procurement delays. Say which one you use in every report.
Use the median
Distilled CS advises tracking the median TTV rather than the average, so a few very slow outlier accounts do not distort the picture of the typical user. We agree. Averages get dragged by the account that signed up on Friday and logged back in three weeks later.
Segment before you celebrate
The same source calls a blended average a vanity metric and recommends segmenting by customer size or use case. Split at least by:
- Plan or company size
- Role of the first user
- Acquisition channel
- Use case chosen at signup
A table of what you might see:
| Segment | Median TTV | Share reaching value in trial | Reading |
|---|---|---|---|
| Self-serve, small teams | 2 days | 45% | Healthy speed, many never arrive |
| Self-serve, mid-size | 6 days | 28% | Setup likely blocks value |
| Sales-assisted | 14 days | 60% | Fine if kickoff is booked early |
These numbers are illustrative, not benchmarks. The point of the layout is that each row suggests a different fix, which a single blended figure never would.
Watch the people who never arrive
Median TTV only counts users who reached value. Always pair it with the percentage who reached it at all, otherwise you can "improve" TTV simply because slow users dropped out of the sample.
What a good target looks like
There is no universal number. The target depends on how much the customer must do before the product can work.
According to Distilled CS, enterprise customers often need two to eight weeks to achieve value because of data migration and training, while self-serve B2B products should aim for one to seven days. Treat these as planning ranges and check them against your own retained customers.
For free trials the target is tighter than the product's full onboarding. If your trial lasts 14 days, the first value moment should arrive in the first session or two, leaving the rest of the trial for the user to build habits and see the product for what it is.
Where trials lose time
When we go through a B2B trial as a new user, the same delays keep appearing. None of them are exotic.
Setup that comes before any payoff
Long profile forms, mandatory integrations and team invites all sit between the user and their first result. Research on onboarding practice points the same way: practitioners focus on enabling aha moments through sample data or limited functionality before forcing users through complete account setup, since full setup acts as a bottleneck to initial value.
A good test: for each setup step, ask whether the product could show something useful without it. Often it can, with a template, sample dataset or a pre-built example.
Guidance that arrives at the wrong moment
Product tours that fire on first load, before the user has any context, get dismissed. A 2020 study of an interactive onboarding feature found that users given step-by-step, context-aware feature introductions completed activation requirements faster and activated at higher rates than users left to self-serve. The keyword is context: help should appear when the user is about to need it.
Unclear pricing and trial limits
If users do not know what the trial includes, what happens at the end or what a plan costs, they hold back effort. People do not invest in setting up a tool they suspect they cannot afford. Showing the plan structure early, and tying upgrade prompts to moments when the user has just gotten value, works better than a banner on day one.
Too many paths
A dashboard with twelve equal options is a decision. Pick the single most common first job and make it the obvious default, with the other paths available but quieter.
A hand-off to nobody
In sales-assisted products, value stalls between the signed contract and the first working workflow. If nobody owns the gap, the customer waits. Name an owner and a date for the first defined milestone.
A step-by-step way to cut TTV
- Walk the trial yourself. Sign up with a fresh email and a realistic use case. Record the screen and time every step until you see a result you would care about.
- Label each step. Prerequisite, value, or optional. Prerequisites are your cut list.
- Remove or defer. Move anything the product can do without into later sessions. Replace blank states with sample data.
- Pre-fill what you know. Signup data, email domain and chosen use case can set defaults.
- Introduce features in context. Trigger help from behavior, not the calendar.
- Re-measure by segment. Compare the median and the share who reached value before and after.
- Keep a one-line business case for each change, so the team remembers what the change is meant to improve.
For each experiment, change one thing at a time where traffic allows. If it does not, accept that you will be reasoning from smaller samples and lean on session recordings to see why a user paused.
Time to value for AI features and agents
Teams adding AI to a product face a stricter version of the problem. The model is rarely the bottleneck. According to a Valoir report on agentic AI, DIY projects averaged 75.5 months of cumulative development effort, versus 4.8 months on pre-built agentic platforms. Note that this is a vendor-adjacent study of a specific platform category, so read the figures as a comparison of approaches, not a promise for your stack. What it does support is the practical lesson: the time goes into guardrails, data integration and the user-facing workflow around the model.
For users, the same principle applies as in any trial. An AI assistant that needs an hour of configuration before it does anything will lose to one that produces a useful draft from the first prompt. A working prototype of one narrow workflow, tested with real users, tells you more about TTV than a broad roadmap.
Our perspective
Most TTV advice stops at "measure it and make it shorter." In our experience the harder part is seeing the delay at all. Teams know their funnel numbers, but they rarely feel what it is like to be a stranger in their own product, with no context, a half-hour of attention and a competing browser tab.
That is why we start with the trial itself. We sign up as a real user, go step by step and mark where the first value should have appeared and did not. The usual finding is not a missing feature. It is an order problem: the product asks for effort first and shows benefit later.
The second thing we push on is the value definition. If your team cannot agree on what the value moment is, no amount of onboarding polish will help, because everyone is optimizing a different finish line. Agree on one event per role, then fix the path to it.
Third, we are wary of dashboards that celebrate a falling average. Look at the median, look at who never arrived, and look at the segment that pays the most. Work we have done on product setup changes, such as the Supliful project, came from that kind of segmented reading of where people actually stalled, not from a redesign for its own sake.
— Edijs
Getting help with your own trial
If you own trial conversion and want an outside read on where users stall, our AI + UX Discovery engagement is the place to start: we go through the trial as a new user, map the drop-off points and show what to fix first and why, backed by research. When the fixes involve AI features or automated workflows, see AI Agents & Workflows, or browse all services.
A short checklist before you start
- One written definition of the value event for each key role
- Start line stated (signup, contract or kickoff)
- Median, not average, reported weekly
- Segment views for size, role and channel
- The share of users who never reach value shown beside the median
- A named owner for every defined milestone in sales-assisted accounts
- A list of setup steps labeled prerequisite, value or optional
FAQ
What is a good time to value for SaaS?
It depends on how much the customer has to do before the product works. Self-serve B2B products should aim for roughly one to seven days, while enterprise products with migration and training often take two to eight weeks, per Distilled CS. Compare against your retained customers rather than a generic benchmark.
What is the difference between time to value and time to first value?
Time to first value is the earliest meaningful milestone, while time to value can extend to full go-live or the full outcome the customer bought. Many teams use the terms interchangeably, so write down which one you track. Consistency matters more than the label.
How do you reduce time to value?
Remove or defer setup that comes before any result, use sample data or templates to show the product working, and introduce features when the user needs them. Then re-measure the median by segment. Walking through your own trial as a new user is the quickest way to find the first steps to cut.
Should I track the average or the median?
Track the median. A handful of slow accounts can pull the average far from the typical experience. Report it alongside the percentage of users who reached value at all.
Sources
- Time to First Value (TTFV), Distilled CS
- What is Time to Value? Onramp
- Interactive user onboarding and its effect on activation rates, DiVA portal
- Process mining and user onboarding research, SCITEPRESS
- Benefits realization and project goals, UMass Lowell
- Accelerating agentic AI time to value, Valoir