I’ve been noticing a significant number of references to Time To First Value (TTFV) as an important metric for Customer Success teams. But when I dig deeper, asking for specific examples of what actual value is being tracked or what time period is being measured, the responses are fuzzy. Some mention starting the clock when the initial contract is signed, others don’t begin until the implementation/onboarding formally initiates. The value point is also variable: some are satisfied using the completion of onboarding, activation of licenses, and/or actual logons as proof of value’s beginning. Others want to go deeper to the accomplishment of a specific job or task by the customer, perhaps even to get the customer’s agreement that they have indeed realized specific value from their use of the technology. The definition of Time To First Value matters because there is a very substantial difference between a feel-good metric for the CS team and a solid customer retention indicator that can be used to predict continuing revenue.
When does the clock start ticking?

What exactly is the First Value?

Note that you may well need multiple specific jobs/tasks to be included in the definition of First Value, especially where you have multiple user personas involved with the product.
Who Owns Time to First Value?
The initial definition process will need to involve Sales, Product, ProServe/Onboarding, and Customer Success — and definitely requires considerable domain expertise. Once a working definition has been established as a foundation, then the customers need to be brought in to get their agreement. After that, the tracking and reporting should belong to Customer Success.
Reactions?
I’d really like to find a company and CS exec who is really good at the TTFV challenge to interview for a Case Study. If that’s you, please reach out to me here or via the Customer Success Forum on LinkedIn. Here’s the link to the discussion there if you want to join in the conversation.




