Health score

A health score is a calculated metric that quantifies customer satisfaction, engagement, and likelihood to renew or expand. Health scores typically combine multiple data points: product usage frequency, feature adoption, support ticket volume, customer engagement responsiveness, and other indicators, into a single numerical score (often 0-100). Health scores help customer success teams prioritise at-risk accounts and identify expansion opportunities.

Health scores bridge the gap between intuition and data. Customer success managers often sense which customers are thriving and which are struggling, but without quantitative health scores, prioritisation is arbitrary. Health scores create objective criteria for identifying which customers need intervention, which are at churn risk, and which are ready for expansion conversations.

Common health score components

• Product usage: Frequency and consistency of product logins and feature usage
• Feature adoption: Whether customers are using advanced or new features
• Support interactions: Number and sentiment of support tickets
• Engagement response: How quickly customers respond to communications
• Expansion indicators: Headcount growth in organisation, new use cases, increasing usage volume
• Churn risk signals: Decreased usage, executive transitions, missing renewal conversations
• Contract metrics: Expansion deals closed, renewal rates, upsell achieved

Health score accuracy depends on data quality and scoring model validation. A health score model built on biased data produces biased results. Health scores require regular review and adjustment as your product and customer base evolve.

Health scores enable proactive customer success rather than reactive problem solving. Rather than waiting for customers to complain or churn, health scores identify risk early when intervention has maximum impact. Early warning allows customer success teams to engage before customers decide to leave.

Health scores improve team efficiency. Customer success teams manage hundreds of customers; they can't monitor each actively. Health scores automatically prioritise workload: focus intense effort on low-health accounts where intervention can prevent churn, moderate effort on medium-health accounts, and light touch on thriving accounts where intervention isn't needed.

Health scores quantify expansion readiness. Rather than guessing which customers might buy more, health scores identify customers with strong engagement and usage patterns indicating readiness for expansion conversations. This guides sales teams toward highest-probability expansion opportunities.

Define health score components based on your business model. For usage-based products, product usage is heavily weighted. For seat-based products, user count and adoption matter more. Build health score around the metrics that actually predict churn and expansion in your business, not generic models.

Weight components based on predictive power. Components that most accurately predict churn should be weighted highest. Use historical data: look at customers who churned and trace what their health score components looked like before churn. Weighting should reflect what actually predicts customer success.

Build health score with leading indicators, not lagging indicators. Customer satisfaction surveys are lagging indicators: customers are already unhappy by the time they answer surveys. Product usage and engagement patterns are leading indicators: they predict churn before it happens. Weight leading indicators most heavily.

Review and adjust health scores quarterly. Customer needs evolve, products change, markets shift. Health score models built a year ago may be outdated. Regularly review which health score components accurately predict current outcomes and adjust weightings accordingly.

A SaaS company built a health score combining: weekly product logins (weighted 30%), adoption of new features (20%), support ticket sentiment (20%), and expansion buying behaviour (30%). Customers scoring below 40 were flagged for immediate customer success intervention. The team discovered customers with low health scores typically didn't churn immediately: they churned 45-60 days later. By intervening at low health score, the team could often identify missing features, misalignments with intended usage, or training gaps. Proactive health score-based intervention reduced churn rate from 8% to 4% within six months, directly improving lifetime value and profitability.

An enterprise software company using SaaS pricing built a health score emphasising feature adoption and user count. When health scores were high, it typically meant the organisation had successfully deployed the software and was expanding user count. Customer success team used high health scores to identify expansion conversations. Rather than waiting for customers to request additional seats, they proactively presented expansion options. Proactive expansion conversations (based on health score signals) closed at 35% rate, compared to 8% for customers contacted randomly.

A B2B services firm built initial health scores around support ticket volume and response times. However, comparing health scores to actual renewal and churn patterns showed this model was inaccurate. Low-ticket customers often churned; high-ticket customers often renewed. Deeper analysis revealed that low ticket volume meant customers weren't getting value (no questions to ask), whilst high ticket volume meant active engagement and value realisation. The company completely inverted the support metric weighting. This adjustment aligned health scores to actual churn prediction, making them useful for customer success prioritisation.