Tracking time to value

Time to value is the time between signup and the moment a user first gets real value from your product. If that number is creeping up, trials go quiet before anyone notices why.

Why this number gets missed

Most teams track whether a user activated. Fewer track how long it took. That gap matters: a user who reaches activation on day one behaves very differently from one who reaches it on day twelve of a fourteen-day trial. Both count as "activated" in a simple yes/no view, but only one of them is a healthy signal.

Without a time dimension, a slow drift goes unnoticed for months. Onboarding gets a little more complex, a new step gets added to setup, and time to value quietly stretches from two days to six. Nobody decided that on purpose. Nobody sees it either, until trial conversion drops and the cause isn't obvious.

What to measure

You need two timestamps: the moment a user signs up, and the moment they hit the activation event you've already defined for your product (see what counts as activation in PLG if that definition isn't settled yet). The difference between the two is time to value for that user. Averaged or put into a median across a cohort, it becomes a trend you can watch.

In Funnelsight, the activation event you define applies consistently across every report, so the same event used to flag activation is the one used to calculate this delay. No separate configuration needed for a second metric.

Start with a rough version

You don't need every plan tier or every persona covered on day one. Pick your main self-serve segment, measure time to value for that group alone, and expand later. A spreadsheet export of signup dates and activation dates is enough to get a first median. Batch data, checked once a week, tells you if the number is moving before you invest in anything more automated.

What matters is that the two dates you're comparing are accurate, not that you cover every account type at once. Start narrow, stay rigorous on the data itself, then widen the scope.

What to do once you're tracking it

A rising time to value is usually a symptom, not the disease. Common causes: a new onboarding step, a change in default settings, a feature that used to be visible and got buried in a redesign. Once you have the trend, cross it against product changes on a rough timeline and the likely cause tends to jump out.

Teams already watching activation metrics closely often add this as a second layer, not a replacement. See tracking activation metrics for the broader setup this fits into.