Growth

Measuring Time-to-Value: The Metric Your Onboarding Team Is Missing

Abstract time and value visualization with upward progression

The onboarding team at a 15,000-DAU B2B analytics tool had just shipped their third onboarding redesign in 18 months. Their activation rate — defined as "user completes all onboarding checklist items" — had gone from 31% to 38% to 42% across the three versions. Each redesign had moved the number. But their Day-30 retention had barely budged: 24%, 26%, 25%. Activation was improving. Retention wasn't following. They didn't know why.

The disconnect was measurement. Their activation metric was measuring task completion, not value delivery. A user who completes all onboarding checklist items but doesn't experience the core value proposition is "activated" by their definition — and still very likely to churn. What they needed to measure was time-to-value, not time-to-activation. The difference between those two metrics is the difference between measuring that users did the steps and measuring that users got something out of doing them.

The Distinction That Changes Everything

Time-to-activation (TTA) measures how long it takes a new user to complete a defined set of setup actions. Time-to-value (TTV) measures how long it takes a new user to experience the specific outcome the product is designed to deliver.

These are not the same thing, and conflating them is one of the most common measurement errors in SaaS onboarding design. Consider a project management tool where the core value proposition is "your team coordinates around work without email chains." A user can activate (create a project, invite teammates, assign tasks) without ever experiencing the coordination benefit — because maybe their teammates haven't responded yet, or because they've set up the structure but haven't run a real workflow through it yet.

True time-to-value for that product is the elapsed time between signup and the first moment a user receives a notification that a teammate has responded to or completed something they assigned. That's the moment the coordination loop closes. Everything before it is setup. Only after it has the user experienced what the product actually delivers.

How to Define Value Moment for Your Product

The value moment is product-specific, but there's a consistent method for finding it:

Look for the Aha Correlation

Run a behavioral cohort analysis: for users who retained at Day 30, what is the distribution of time to a set of candidate "value moment" events? Compare that distribution to the same events for churned users. The event where the retained and churned distributions diverge most sharply — where retained users hit it faster and more consistently — is your value moment candidate.

For a reporting tool, it might be "first dashboard published." For a developer tool, it might be "first successful API call in production." For a sales tool, it might be "first deal stage moved based on a product-triggered alert." The pattern is almost always: first time the product delivered something to the user, rather than first time the user configured something in the product.

Validate with User Interviews

Ask recently retained users: "When did you first feel like the product was working for you?" The answers will cluster around 2–3 moments. Those moments are your value moment candidates. Cross-reference against your event data to find the closest trackable event to each moment. This is the qualitative validation step — data tells you what, interviews tell you why.

Measuring Time-to-Value: The Metric Architecture

Once you've defined the value moment, TTV is straightforward to measure:

TTV = timestamp(value_moment_event) - timestamp(signup_event)

But the distribution matters more than the mean. Report TTV as:

  • Median TTV: The time it takes the median user who eventually reaches the value moment. This is your primary metric.
  • P75 TTV: The time it takes the 75th percentile user. This tells you about the long tail of slow-to-value users — often where the biggest onboarding improvements are hiding.
  • Value moment reach rate: The percentage of new signups who ever reach the value moment, measured within a fixed window (usually 7 days or 14 days). This is the companion to TTV — TTV only tells you about users who reached the value moment. Value moment reach rate tells you how many users you're losing before they ever get there.

The combination of these three metrics paints a complete picture: What fraction of users reach value? How quickly do they get there? And how long does it take the slowest successful cohort?

Industry-Realistic TTV Benchmarks

TTV benchmarks are hard to generalize because the value moment definition is product-specific. That said, there are realistic ranges for different product types:

Product Type Typical Value Moment Healthy Median TTV Value Moment Reach Rate
Simple single-player tool First output generated Under 30 minutes 55–70%
Collaborative work tool First team interaction 24–72 hours 30–50%
Data/analytics tool First insight surfaced 2–5 days 35–55%
Integration-dependent tool First integration event 3–7 days 25–45%

Products where TTV is under 24 hours tend to have significantly higher Day-30 retention than products where TTV is in the 3–7 day range, holding product category constant. The correlation between faster TTV and higher retention is one of the more robust patterns in SaaS onboarding data — it's not that fast TTV causes retention, but that a fast TTV path is usually a well-designed path that gets users to the behavior that does cause retention.

Where Onboarding Teams Go Wrong

Optimizing Setup Speed Rather Than Value Speed

The most common onboarding mistake: treating the time to complete setup as a proxy for TTV. Reducing the number of setup steps or making each step faster reduces TTA but doesn't necessarily reduce TTV. If you cut the setup checklist from 8 items to 4 but removed the 2 items that were prerequisites for the value moment, you've created a shorter path that bypasses the value. TTA improves. TTV gets worse.

Measuring Activation Without Measuring What Follows It

The onboarding team in the opening scenario had this problem. Activation was the terminal metric — the funnel ended at checklist completion. They had no visibility into what happened between checklist completion and the value moment, or how many users reached the value moment at all. Activation metrics need a downstream anchor. The downstream anchor is the value moment reach rate.

Single-Path Onboarding for a Multi-Persona Product

Many B2B products serve multiple user personas who experience value differently. A project management tool might have managers (who experience value when their team first coordinates around a task) and individual contributors (who experience value when they first have clarity on what they're supposed to do). A single onboarding path optimized for one persona may actively slow down TTV for the other. Persona-aware onboarding with different value moment definitions for each persona is worth the engineering investment for products where persona mix is significant.

The TTV Action Loop

Measuring TTV creates an action loop that TTA measurement doesn't:

  1. Measure: Calculate median TTV and value moment reach rate for your last 3 signup cohorts.
  2. Diagnose: Is TTV high because users are slow to complete prerequisites, or because prerequisites are complete but the value moment is far downstream?
  3. Intervene: If prerequisites are the bottleneck, reduce them. If the value moment is far downstream, surface it earlier — either by shortening the path or by creating an early taste of the value moment before full setup is complete.
  4. Measure again: Run the next cohort through the changed onboarding. Did median TTV move? Did value moment reach rate move? Did Day-30 retention follow?

The retention follow-through is the validation. If you reduced TTV without improving retention, either the value moment definition is wrong (users are reaching it but not finding it meaningful) or retention is being driven by something else entirely and TTV is not the constraint.

For the onboarding team from the opening, redefining their activation metric as "first time a user received a teammate notification" changed the picture completely. Their new activation rate was 28% — lower than their old 42% — but this new number was strongly correlated with retention. The cohorts with 28%+ reaching the new value moment were retaining at 51% at Day 30. The cohorts who completed all checklist items but didn't reach the notification moment were retaining at 19%. Same checklist completion rate. Radically different retention. The measurement had been hiding the signal all along.