What customer health scores are, what signals to include, why most homemade scores get abandoned within a quarter, and how AI changes the math. A practical guide for SaaS CS teams in 2026.
Short answer
What is a customer health score, and how do you calculate one?
A customer health score is a single 0–100 number summarising how likely an account is to renew, expand, or churn, computed as a weighted aggregate of login frequency, adoption depth, support sentiment, NPS, champion status, and billing health. Build it from four to six signals you collect for everyaccount, score each against that account's own baseline, and ship the reasons next to the number. A score with no explanation never enters a workflow.
Most SaaS teams have heard of customer health scoring, half have tried to build one, and a third have quietly stopped trusting the one they built. The reason is almost never that the concept is bad - it's that homemade health scores decay faster than anyone expects, and the ownership of keeping them current rarely sticks to a single person. This guide covers what a customer health score actually is, what signals belong in one, why most homemade scores get abandoned within a quarter, and how AI scoring changes the math.
A customer health score is a single number - typically 0–100 - that summarizes a customer's likelihood to renew, expand, or churn. Mechanically, it's a weighted aggregate of leading indicators: login frequency, feature adoption depth, support sentiment, NPS, champion status, billing health, and so on. The output is one number per customer, refreshed at some cadence (daily is ideal, weekly is acceptable, monthly is too slow).
The score itself is not the value. The value is in the explanation - the “why” behind the number. A score of 78 with no context is a chart on a dashboard. A score of 78 with login down 62%, NPS dropped 9 → 6, champion changed roles is a brief - three sentences, decision-ready, ready for a CSM to act on this morning.
The signals that consistently predict outcomes across SaaS verticals:
The temptation when building a homemade score is to include every signal you can think of. Resist it. The marginal predictive value of the seventh signal is small; the marginal maintenance cost is not.
The lifecycle of a typical homemade health score looks like this:
The problem isn't that the formula was bad. The problem is that nobody's job is to keep it current. As long as scoring depends on a hand-tuned formula, the formula needs a maintainer - and CS Ops headcount almost never extends to ongoing model maintenance.
The shift in 2024–2026 has been from configurable scoring (you design the formula) to learned scoring (the model designs itself and abstains where it is blind). The trade-off is real: you give up configurability in exchange for not needing a maintainer. For most SaaS teams under ~5,000 customers, that trade is unambiguously favorable.
A vendor-tuned scorecard has three operational advantages over a formula you maintain yourself:
A customer health score is a single number, usually on a 0–100 scale, that summarises how likely a customer is to renew, expand, or churn. It is a weighted aggregate of leading indicators such as login frequency, feature adoption depth, support sentiment, NPS, champion status, and billing health, recomputed on a cadence. Daily is ideal, weekly is acceptable, monthly is too slow to act on.
Build a customer health score by picking four to six signals you already collect reliably, scoring each against the account's own historical baseline rather than an absolute threshold, weighting them by how well each one predicted churn in your own history, and shipping the explanation alongside the number. A score without the two or three reasons behind it produces a dashboard, not a decision.
A customer health score should include login or usage frequency measured as drift from the account's own baseline, feature adoption depth, support ticket volume and tone, NPS movement between responses, champion status and role changes, and billing health including failed payments and downgrades. Signals you cannot collect for every account do more harm than good, because a score that silently means different things for different customers cannot be compared.
Most customer health scores fail because nobody owns recalibrating the weights, so the score drifts away from reality over a quarter or two and the team quietly stops trusting it. The second cause is a score with no explanation attached: a CSM who sees 78 and no reason has no action to take, so the score never enters a workflow and its decay goes unnoticed.
There is no universal good customer health score, because the scale is yours and the weights are yours. What makes a score good is calibration: accounts scoring in your bottom band should churn at a visibly higher rate than accounts in your top band. If they do not, the number is decoration. Check that separation against your own churned accounts before trusting any threshold.
A manual customer health score uses fixed weights a human chose once. An AI customer health score learns the weights from which accounts actually churned in your own history, re-derives them as the pattern changes, and writes the explanation in language a CSM can act on. The practical difference is maintenance: the failure mode of the manual version is that nobody updates it, and that failure mode disappears.
A score is useful only insofar as it triggers action. The pattern that works:
For a deeper dive into the inputs, read the six signals that predict churn. For the productized version, see the customer health score feature page.
Keep reading
Plans & pricing
14 min read · Jul 22, 2026
Getting started
19 min read · Jul 22, 2026
Automation
9 min read · Jul 16, 2026
First scores in 15 minutes. Full accuracy in 24 hours. From $299/mo. AI health scoring with the top three drivers per customer, refreshed daily.
Not ready to switch? Run the free 60-second revenue leak scan and see what staying put costs.