"Health scores have become universal in customer success — and they've been almost universally accepted as ineffective and useless. The logic makes sense on paper: identify the factors that play into whether a customer succeeds, track those, weight them by impact, create a composite score. If a factor is unhealthy, the score drops. If a combination of low-impact issues stacks up, that's slight risk; if a high-impact factor goes red, that's serious risk.
"The whole thing is fraught. Here's why.
"
Why it matters
The health score is the single most widely-built and least-effective construct in customer success operations. Companies invest millions in CSPs (customer success platforms) primarily to compute a health score, then build interventions around the resulting number - only to find that the number doesn't predict what they want it to predict, and worse, doesn't tell anyone what to do. Rebuilding the model around specific, time-bound risk factors instead of a composite score produces an operating system the CS team can actually execute against.
Example
A CS team replaces its 75-factor composite health score with a specific risk model: five outcome milestones the customer should hit by specific times - integrated with their CRM by day 14, deployed first workflow by day 30, hit Good benchmark on target metric by day 60, expanded to a second team by month 9, hit Best benchmark by month 12. Any account missing a milestone at its current time threshold is flagged with a specific named risk factor. The CSM no longer reports "this account is 32% at risk" - they report "this account is overdue on the day-30 deployment milestone; the intervention is a working session with their integration team this week." Risk becomes specific, time-bound, and operable.