Are You Measuring Customer Value or Just Customer Activity?
Three places to look for signs your organization is losing the connection to customer value.
There’s a lot of conversation about Customer Success teams needing to focus more on business value and outcomes.
I agree.
But before asking CSMs to do more around value, I’d want to understand whether the organization can answer a more fundamental question:
Can you trace a clear line from why a customer bought your product to the value they ultimately achieved?
I think of this as Value Traceability.
As a customer moves from Product and positioning through Sales, implementation, adoption and ultimately realized value, our understanding of what they’re trying to achieve should deepen without losing the thread along the way. This is the Value Thread.
The question is: How do you know when that isn’t happening?
1) Start where the metrics don't make sense together
One of the first places I’d look is at metrics that appear healthy individually, but tell a contradictory story when you put them next to each other.
High adoption + weak retention
Customers are using the product, but they're still churning. That doesn't necessarily mean adoption doesn't matter. It raises a more interesting question: Are customers adopting the capabilities that actually create the value they bought for? Usage is evidence of activity. It isn't necessarily evidence of value.
Fast implementation + slow time-to-value
The organization may be getting very good at deploying the product without getting equally good at accelerating the customer outcome. If implementation success is defined primarily by milestones, scope and go-live, it's possible to improve implementation metrics while doing very little to improve how quickly customers realize value.
Strong health scores + surprise churn
If accounts the company considers healthy continue to churn unexpectedly, I'd want to understand what the health score is actually measuring. Product usage? Engagement? Support activity? Relationship strength? CSM judgment? What is measuring that the customer is achieving something they consider valuable?
These are just a few examples. The individual metrics are necessarily the problem, the disconnect between them in the clue.
What a broken Value Thread can look like:
What you see | What you assume | What might actually be happening |
High adoption + weak retention | CS isn't managing risk well enough | Adoption isn't connected to the outcomes customers bought for |
Fast implementation + slow time-to-value | Onboarding or implementation needs improvement | You're optimizing for deployment rather than the fastest path to customer value |
Strong health scores + surprise churn | The health score needs better signals | Health is measuring activity, engagement or relationships without enough evidence of realized value |
High CSAT/NPS + weak retention or expansion | CS needs to be more commercial | Customers like the product and the relationship, but can't connect the investment to enough business impact |
QBRs dominated by usage and activity | CSMs need better value-selling skills | The original business outcome has been lost or was never translated into something the organization can measure |
Sales and CS disagree about what the customer bought | The handoff process is broken | Expected value isn't traceable from discovery through delivery |
Great customer outcomes that are hard to repeat | Execution is inconsistent | You don't understand what created the value well enough to replicate it |
Strong customer outcomes + difficulty winning the next segment | Marketing or Sales positioning needs work | What you're learning from realized value isn't making its way back into ICP, positioning and how you sell |
Metrics can tell you where to start looking. The conversations inside the organization can tell you whether you've actually lost the thread.
2) Next, listen to how different people talk about the same customer
Metrics tell you part of the story. Conversations often tell you the rest. Pick a customer and ask people across the organization two simple questions: Why did this customer buy? What are they trying to achieve?
Ask the salesperson, the implementation lead and the CSM. If you can, ask the customer too. I wouldn't expect identical answers. In fact, I'd be concerned if the understanding hadn't evolved at all. The organization should know substantially more after discovery, implementation and adoption than it knew when the customer first entered the pipeline.
Imagine Sales tells you the customer bought to improve seller productivity. The implementation team describes success as deploying three use cases by the end of Q2. Customer Success is focused on getting adoption above 80%. Then you ask the customer, and they tell you they need their managers to spend less time figuring out what's happening in deals.
Those answers aren't necessarily incompatible. The question is whether anyone can connect them. Did we determine that those three use cases would improve seller productivity? Do we know whether 80% adoption is a meaningful leading indicator of that outcome? Did we learn during implementation that manager productivity was actually the more important problem? And if our understanding changed, did that change how we worked with the customer?
A healthy Value Thread doesn't mean the story stays the same. It means our understanding gets deeper without losing the connection to why the customer bought in the first place.
3) Then look at what gets measured after the contract is signed
A customer might buy because they want to reduce downtime. Once the contract is signed, success becomes going live by June. After launch, the focus shifts to reaching 75% adoption. By the QBR, the team is reporting that usage increased 12%.
Nothing about those measures is inherently wrong. Go-live may be necessary. Adoption may matter enormously. Usage may be a meaningful leading indicator. The problem is when those measures become substitutes for the outcome rather than evidence of progress toward it.
When internal measurements are gradually substituted for customer outcomes you've stopped measuring the path to valued and started measuring the path through your own process.
If we can't measure the ultimate outcome directly, we should at least understand the relationship between the things we can measure and the value the customer is trying to create. Otherwise, we haven't necessarily created a path to value. We've created a sequence of internal success measures.
Three places to look for a lost value thread
If you want to understand whether your organization is losing the value thread, I'd start in three places:
1. Metrics - Start where the metrics don't make sense together. Look for signals that should reinforce each other but don't: strong adoption with weak retention, fast implementation with slow time-to-value, healthy accounts that unexpectedly churn. The disconnect may tell you more than any individual metric.
2. Conversations - Listen to how people talk about the same customer. Ask different teams why the customer bought and what they're trying to achieve. The answers don't need to be identical, but you should be able to trace how the organization's understanding of value evolved as it learned more.
3. Measurement - Look at what gets measured after the contract is signed. Follow the progression from the customer's desired business outcome to the measures used during implementation and adoption. Have leading indicators been connected to the outcome, or have internal milestones gradually replaced it?
None of these alone proves you've lost the Value Thread, Together, they give you a pretty good place to start looking before a new mandate for CSMs.