Health scores were built for the teams working accounts. Executives need the same event priced against the commitment, the quarter and the plan. The difference matters.
Most B2B SaaS companies already have churn detection of some kind — a health score, a usage trend, a risk flag on the account record. Those tools work, and they were built for a specific job: helping a customer success team decide which account to work next.
That is a queue-ordering problem, and a score solves it well. Rank the book, work the top of the list. The output is a priority, and a priority is exactly what someone managing a portfolio of accounts needs.
Why a score stops being useful one level up
An executive is not ordering a queue. They are deciding whether to change a forecast, whether a commitment is still credible, and where to spend attention that cannot be spent twice. A score of 42 does not answer any of those, because it has no denominator. It says an account is sick. It does not say what being sick costs.
The translation that is missing is the one a board already performs instinctively:
- What is the exposure in currency, not in points.
- What share of the period's commitment does that represent.
- Which planning assumptions stop holding if it goes the wrong way.
- How long is left to change the outcome.
The second gap: what the score can see
A health score built inside a customer success platform reads the systems that platform is connected to — typically product usage and support activity. That is a genuine view, but it is a partial one. It cannot see that the contract renews two weeks earlier than the CRM believes, or that the account is overdue on payment, because those facts live in the finance system.
This is not a criticism of those tools. It is a description of where they sit. A tool built for the team working accounts is connected to the systems that team uses.
Two different jobs, not two competing products
The distinction is worth stating plainly, because it is easy to hear as a comparison and it is not one. Detecting that an account is in trouble and deciding what the company should do about it are different jobs, and they are answered at different altitudes.
Severity decides who is sick. Size and seat decide who hears about it.
A company can run both, and most should. What is usually missing is the layer above: one reconciled position across the systems that hold the account, priced in the terms the board already uses, and delivered to the person accountable for that number while there is still time to act on it.
See it against your own book.
Thirty minutes to walk through what your executives would receive, what it takes to run, and whether your book is a fit.