Short answer: Measuring product value starts with defining the outcome your customer account is trying to achieve, then tracking whether they consistently complete the workflows that produce that outcome. Activity can be useful context, but value is better reflected by adoption depth and dependency at the account level. If you can explain “this account is getting value because they do X every week,” you are usually close to the right metric.
Explanation
Most SaaS teams measure what is easy to count: logins, active users, events, time in app. Those numbers are not worthless, but they are often weak proxies for value. They describe movement, not whether the customer is getting the result they paid for.
Value is not a generic definition either. In B2B SaaS, value tends to come from a small number of workflows that are tied to an outcome: shipping code faster, closing deals with fewer steps, reducing risk, making reporting reliable. If you cannot name the outcome and the workflow, it is difficult to measure value without drifting into vanity metrics.
Why it happens in practice
In practice, teams inherit dashboards built for activity. Those dashboards look stable even when adoption is shallow, because a small group of users can keep numbers up. The account can remain “active” while the product stays optional, and that is the exact state where churn and downsell become possible without a dramatic drop in usage.
This also tends to happen when metrics are defined from the product’s perspective instead of the customer’s. A feature can be used frequently and still not matter to retention if it is not part of the value path. Meanwhile, the workflow that does drive value might be used less often but with more consistency, by more roles, and with clearer outcomes.
What most teams misunderstand
A common misunderstanding is that value must be measured as a single score. Scores can be helpful for prioritization, but they are often treated as a substitute for definitions. If the team cannot explain what the score is made of in plain language, it becomes hard to trust when renewals are at risk.
Another misunderstanding is to measure value at the user level in a B2B context. Renewals and revenue happen at the account level, so the unit of analysis needs to match. One enthusiastic user does not mean the account has embedded the product, and high activity does not mean the account would miss the product if it disappeared.
What actually works
Start by writing down a value definition that a customer would recognize. Tie it to one or two concrete workflows, then translate those workflows into a small number of measurable signals. In many cases, “value” can be approximated with consistency and spread: the account completes the workflow repeatedly over time, and usage is not concentrated in one person.
Once you have those signals, look at them over time per account, not as a global average. Value usually shows up as a pattern: adoption of the core workflow, then steadier repetition, then expansion to more teams or adjacent workflows. When those patterns are missing, retention risk can exist even if activity metrics look fine.
Conclusion
Measuring product value is less about inventing a complex model and more about aligning metrics with customer outcomes. Define the account-level workflows that produce value, measure whether those workflows are used consistently, and watch whether adoption spreads across the account. When your value metric matches how revenue is renewed, it becomes a calm, practical tool instead of another dashboard.
Ultimately, value only matters if it translates into retention. Here’s what actually predicts that: What metrics actually predict SaaS retention?.