First value against full value
Full time to value is the point where the product delivers the outcome the customer bought at the scale they expected. First value arrives well before that. It is the first report someone acted on, the first record that ran end to end, the first decision made using your output.
The reason to measure the earlier milestone separately is that it governs momentum. The sponsor who approved the purchase spent internal credibility to do it, and needs evidence in hand before anyone asks whether the spend was worth it. First value supplies that evidence. Full value, arriving months later, is what earns the renewal.
Onboarding completion measures neither. A customer can finish every configuration step and still have no result, which is why a checklist-based onboarding dashboard so often shows green against accounts that are already drifting.
Defining the event
The measurement only works with one instrumented event that fires when the customer received something, not when your team delivered something.
| Real first value event | Vendor activity dressed as value |
|---|---|
| First report exported and shared internally | Configuration marked complete |
| First transaction processed end to end | Training session attended |
| First decision made from your output | Data integration connected |
| First alert acted on by the customer's team | Kickoff call held |
Some first value milestones are set by the product itself. ORM's forecast models take four to six weeks to train on a company's historical sales performance, which means the first value milestone for an ORM customer is anchored to when the trained model starts producing output rather than to when the contract was signed.
Shortening it
Most onboarding plans delay first value by trying to deliver everything at once, so the first result waits behind every dependency in the project plan. Invert that. Pick one narrow workflow, deliver it end to end in the first two weeks, and expand from a customer who already has proof.
Then track the number as a cohort curve rather than an average, because averages hide the tail of accounts that never reach first value at all. Those accounts are the ones that quietly decide the renewal, and they are the reason net revenue retention so often disappoints in a year where onboarding metrics looked fine. Feed the milestone date into account scoring and the renewal forecast, where it improves forecast accuracy more than any survey response collected in the same window.
Frequently Asked Questions
How is time to first value different from time to value?
First value is the earliest moment the customer gets something real out of the product, such as a first report they act on. Full time to value is when the product delivers the outcome they bought it for at the scale they expected. First value is a confidence milestone that keeps the project funded. Full value is the thing that gets renewed.
How do you define the first value event?
Pick one observable action that only happens when the customer received a genuine result, then instrument it. Good candidates are the first report exported and shared, the first record processed end to end, or the first decision the customer made using your output. Reject anything that measures your work rather than theirs, such as completed configuration.
Why does time to first value predict churn?
Because the internal sponsor spends credibility on the purchase and needs something to show before the first budget review. A customer who can point to a result inside the first weeks has protected the line item. A customer still in setup has an unproven expense sitting on someone's desk, and that is where quiet disengagement starts.
What is the fastest way to shorten it?
Cut scope for the first milestone. Most onboarding plans try to deliver the full configuration before the customer sees anything, which pushes first value behind every dependency in the project. Deliver one narrow workflow end to end in the first two weeks, then build breadth around a customer who already believes.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like time to first value into prescriptive action for your team.
Schedule a Demo