Metrics
Customer Health Score
A customer health score is a composite metric that predicts whether an account will renew, expand, or churn by combining product usage, support signals, and relationship data into a single number.
A customer health score is a composite number that predicts whether an account will renew, expand, or walk. It rolls product usage, support tickets, payment behavior, and relationship depth into one figure — usually 0 to 100, or a red/yellow/green band. The point is to see churn coming early enough to do something about it. A score that only turns red the month before a customer cancels is a smoke detector that goes off after the house burns down.
How a Customer Health Score Is Calculated
There's no universal formula, which is both the feature and the bug. Each company picks weighted inputs that correlate with its own renewals. A common build assigns weights across four buckets: product engagement (40%), support burden (20%), relationship strength (20%), and commercial signals like on-time payment and contract tenure (20%). Each input gets normalized to a 0–100 sub-score, multiplied by its weight, and summed. The math is trivial. The hard part is proving the inputs actually predict churn instead of just feeling like they should.
A Worked Example of a Health Score
Consider an account scored across four weighted inputs:
| Input | Weight | Raw signal | Sub-score | Weighted |
|---|---|---|---|---|
| Product engagement | 40% | Daily active users down 30% QoQ | 50 | 20.0 |
| Support burden | 20% | 3 escalations, 1 unresolved | 40 | 8.0 |
| Relationship | 20% | Champion left, no replacement | 30 | 6.0 |
| Commercial | 20% | Pays on time, 2-year tenure | 90 | 18.0 |
The composite lands at 52 — yellow, trending red. The commercial bucket looks healthy and masks the rot: usage is falling and the champion is gone. That single number, 52, is what triggers a save play before the renewal conversation, not during it. Read in isolation, the strong payment history would have lied to you.
When Sales and Success Teams Use Health Scores
Customer Success owns the score day to day, but it travels further than that. CS managers use it to triage their book and decide which accounts get a QBR versus an automated check-in. RevOps feeds health scores into renewal forecasts the same way pipeline stages feed new-business forecasts. Finance watches the aggregate to model net revenue retention and gross revenue retention. Account executives running expansion plays read it to know which customers are healthy enough to upsell and which need stabilizing first. A green account is a candidate for more; a red one is a candidate for a save.
Common Customer Health Score Gaming Patterns
The score gets green-washed because someone's compensation depends on it. When CS bonuses tie to portfolio health, managers nudge inputs upward — counting a one-time webinar login as "engagement," closing support tickets as resolved before the customer agrees, or marking a relationship "strong" off a single friendly email. The aggregate looks fine right up until the renewal misses. This is the same dysfunction as pipeline padding, moved downstream to retention.
The deeper flaw is correlation drift. A health model built on last year's churn data assumes this year's customers churn for the same reasons, and they often don't. A score can sit at 85 while a competitor quietly undercuts your pricing — nothing in the usage or support data captures a buying decision being made in a boardroom you're not in. Health scores measure the symptoms a company chose to track, not the ones it missed. The number tells you an account looks healthy by your definition. It does not tell you the definition is right, and it never tells you what the customer is about to do that you didn't think to measure. Validate the model against actual renewals every quarter, or you're scoring against a map of last year's territory.
Related terms
Ready to see your numbers?
Get your verified Alpha Score. Read-only CRM, score within minutes.
Get my Alpha Score