Time to First Value

Signing the contract looks like the end of the job, so for months afterward nobody looks at that customer. The problem surfaces at renewal: you arrive at a meeting a year later, hear that the team never really got around to using it, and the next sentence is a cancellation.

It isn't that the year produced no signals. There was just no number that showed them. Login counts only say someone connected, satisfaction surveys arrive after the problem has set, and revenue retention isn't final until the contract ends, which leaves no time to act.

Time to first value exists to fill that gap. Measuring how long it took a customer to actually accomplish something with the product surfaces a stalled account now instead of at renewal. Three weeks past signing with no team having done real work in the product is, by itself, a signal that someone should step in, while there is still a year left to fix it.

It's the difference between two dates. The hard part is deciding what those two dates are. Five steps.

1. Define what first value means. The moment a customer does the thing they came for, once, is the first value milestone, and that definition is half the metric. Pagedeck set it at the point where five people on one team edit the same document together within a week. Completing signup or the first login can't serve as the bar, because those mark the start of preparation rather than the moment anything was gained.
2. Pick the start date. Use either the contract date or the date the account was created, and state which. At enterprise accounts, where two weeks can pass between signing and actually starting, that choice alone moves the number substantially, which is why the two versions should never be compared to each other.
3. Count the days between the two dates for each customer.
4. Group customers who arrived in the same month and take the median. Averages get pulled around by a few extremes. If eighteen of twenty accounts land between nine and fourteen days and two land at 120, the average is 25 days, and that 25 describes nobody's experience. The median is 12.
5. Decide how to treat customers who haven't reached it. Excluding them makes the number look better than it is, so the share that hasn't reached it goes next to the median. The 30-day non-arrival rate is this metric's companion.

Calculating separately by customer size and acquisition path matters too. A small team that signed up on its own and an enterprise account that came through sales travel different routes, so a combined figure represents neither. Splitting it also tells you which route is the one worth fixing first.

There is no correct absolute value, so pick two things to compare against: the same number last quarter, and the length of the free trial.

Where it should sit varies sharply by product type. A tool you sign up for and use immediately has to land inside the first day; a collaboration tool that only pays off once several people use it typically takes one to two weeks; an enterprise product requiring connections to existing systems and data takes four to eight. The same twelve days is normal for the first and a serious problem for the second.

If you run a free trial, its length is the ceiling. A fourteen-day trial with a median of eighteen days means most customers see the trial end before they see the value. Extending the trial only defers the symptom; the thing to work on is the route to first value. A trial that ends before the value lands converts on persistence rather than on the product.

Read it against retention as well. Calculate gross revenue retention separately for the cohort that arrived within two weeks and the cohort that didn't, and the two usually differ substantially. Once that difference is confirmed, the metric turns from something observed into a threshold for acting. Pagedeck used that calculation to set a rule: three weeks past signing with the milestone unreached, and someone from onboarding reaches out first.

Shortening it means shortening the route, not lowering the bar. If nine steps stand between signing and the milestone, the work is reducing the ones the customer has to perform to three.

"The median is twelve days, but 15 percent of customers are past thirty."

A healthy middle can sit on top of a separate group that's stuck.

"A fourteen-day trial with eighteen-day first value isn't a trial-length problem, it's a route problem."

The metric is pointing at product design.

"Redefine it as login and the number improves and stops meaning anything."

An easy definition makes the metric say nothing.

Mia and Sofia spent two weeks at Pagedeck settling on the definition. The first candidate was creating a single document, and measured that way nearly every customer reached it within two days — and a good share of them left three months later. The bar wasn't pointing at anything the customer had gained.

After switching to the current definition, the median went from two days to twelve, and the number became usable. The list of accounts that hadn't reached it started overlapping with the list of accounts genuinely at risk, which is the test of whether a definition is worth keeping.

The most common reading is that shorter is automatically better. It measures a duration, so cutting it looks like the goal. But this number shrinks as much as you like depending on where the bar goes. Define first value as the first login and the median becomes one day, and that day carries no information. The goal isn't a smaller number but an earlier moment at which the customer confirms the value.

The other belief is that it's a number customer success can move by trying harder. It lives on a customer success dashboard, so it reads like that team's scorecard. But most of the steps between signing and the milestone are inside the product. With a setup screen requiring twenty fields before anything starts, daily phone calls from an owner won't remove ten days. Outreach rescues stuck accounts; moving the number itself is product work. Which is why this metric belongs somewhere customer success and product both look at it.