- A health score built from one signal (like login frequency) misses most of the real picture.
- Combining usage depth, engagement breadth, and support sentiment produces a truer score.
- The score needs to be validated against actual historical churn and expansion outcomes.
- A health score only matters if customer success teams act differently based on it.
One signal misses most of the picture
A health score based purely on login frequency will call an account healthy even if only one person at the company is using it and everyone else has quietly stopped, or flag an account as unhealthy despite deep, meaningful usage by a smaller core team. Single-signal scores are a weak foundation.
Combine usage, breadth, and sentiment
A more reliable health score combines depth of usage (how much of the product's value is actually being realized), breadth (how many people at the account are engaged), and qualitative signals like recent support ticket sentiment — together producing a much sharper picture than any single dimension.
Validate the score against real outcomes
A health score that hasn't been checked against actual historical churn and expansion data is just an educated guess dressed up as a metric. Backtesting the score against accounts that actually churned or expanded confirms whether it's genuinely predictive before relying on it operationally.
The score only matters if it changes behavior
A health score that customer success teams see but don't act differently on provides no real value. The score needs to trigger specific playbooks — a proactive check-in for a declining account, an expansion conversation for a thriving one — to actually justify the effort of building it.