What Is a Customer Health Score in SaaS?
A Customer Health Score aggregates product usage, support, and engagement signals into a single number that predicts whether an account will renew, expand, or churn.
Key Takeaways
- A health score aggregates multiple signals (usage, support, NPS, engagement) into one indicator
- Health scores enable proactive customer success rather than reactive firefighting
- The signals and weights should be validated against actual churn and renewal data
- Even a simple health score outperforms no system for spotting at-risk accounts
What goes into a health score
A Customer Health Score is a composite metric that combines multiple signals about an account into a single indicator — typically a number (0–100) or a colour (green/amber/red). Common inputs include: product usage frequency (DAU, MAU, feature adoption), breadth of adoption across the customer's team, support ticket volume and resolution time, NPS or CSAT survey responses, contract size and renewal date proximity, and executive engagement (are senior stakeholders still involved?). The specific signals and their weights should be calibrated to your product and customer base.
Building a basic health score
Start simple. Pick three to five signals you can reliably measure from your existing systems. Assign each a weight that reflects how strongly it correlates with renewal in your customer base. For example: product login frequency (30%), core feature usage (30%), last NPS score (20%), open support tickets (20%). Score each signal on a 0–10 scale and sum the weighted scores. Even this rudimentary approach gives customer success teams a prioritised list of at-risk accounts to focus on. Refine the weights over time as you gather renewal and churn data.
Using health scores operationally
A health score is only valuable if it changes how the customer success team operates. Define playbooks for each health band: green accounts get a quarterly check-in; amber accounts get a proactive call within two weeks to identify and resolve issues; red accounts get immediate escalation to the account owner and a 30-day recovery plan. Without defined playbooks, health scores become a reporting exercise rather than a tool that improves retention. The goal is to convert reactive churn firefighting into proactive, structured account management.
Improving health score accuracy
The most common flaw in health scores is using inputs that feel informative but do not actually predict renewal. Regularly validate your health score by checking whether low-scoring accounts churn at a higher rate than high-scoring accounts — if they do not, the score is measuring the wrong things. Refine inputs and weights based on this validation. Over time, layering in more granular product usage signals (specific high-value feature usage rather than generic login count) typically improves predictive accuracy significantly.