A Customer Health Score (CHS) is a composite metric used by Customer Success teams to predict the likelihood that a customer will renew, expand, or churn. It aggregates signals from multiple data sources — product usage, support interactions, engagement, NPS surveys, contract status, billing history, and stakeholder engagement — into a single score, typically on a 0–100 or 0–10 scale. The health score enables proactive intervention: instead of waiting for a customer to cancel or complain, Customer Success Managers (CSMs) can identify at-risk accounts early and take corrective action before churn occurs. The specific inputs to a health score vary by product type and business model. For a B2B SaaS company, core inputs typically include login frequency, feature adoption depth, number of active users relative to licensed seats, support ticket volume and resolution rate, time since last meaningful engagement with the CSM, NPS or CSAT score, and billing status (overdue invoices are a major churn signal). Each input is assigned a weight reflecting its predictive importance — login frequency might carry 25% weight while NPS carries 15% and feature adoption 30%. Weights should be derived empirically by analyzing the historical correlation between each input and churn or renewal outcomes. Early-stage companies often start with intuition-based weights and refine them over 12–18 months as churn data accumulates. Health scores are typically color-coded: green (healthy, likely to renew), yellow (at-risk, needs attention), and red (critical risk, escalation required). This traffic-light system allows CSM teams to prioritize their portfolios and allocate attention to the accounts where intervention will have the greatest impact. Customer health scores are not static — they should update daily or weekly as new usage data flows in, and trend analysis (is the health score improving or declining?) is often more informative than the absolute score. A customer at 45 but trending up from 30 over three months is in a different position than a customer at 50 but declining from 70. Companies with robust health scoring programs report significantly higher net revenue retention because they catch at-risk customers before the cancellation window rather than after.
Health Score = SUM(Metric Weight x Metric Score) across all health inputs. This formula calculates customer health score by relating the input variables through their mathematical relationship. Each component represents a measurable quantity that can be independently verified.
- 1Gather the required input values: Importance weight assigned, Normalized score, Percentage of licensed, Net Promoter Score.
- 2Apply the core formula: Health Score = SUM(Metric Weight x Metric Score) across all health inputs.
- 3Compute intermediate values such as Weighted CHS if applicable.
- 4Verify that all units are consistent before combining terms.
- 5Calculate the final result and review it for reasonableness.
- 6Check whether any special cases or boundary conditions apply to your inputs.
- 7Interpret the result in context and compare with reference values if available.
This example demonstrates customer health score by computing 76.8 Health Score — Green zone; customer is engaged with good adoption; feature adoption at 60 warrants a check-in to drive deeper product value. 5-Dimension Health Score illustrates a typical scenario where the calculator produces a practically useful result from the given inputs.
This example demonstrates customer health score by computing 31.15 Health Score — Red zone; immediate CSM escalation required; usage, adoption, and NPS are all critically low. At-Risk Customer Identification illustrates a typical scenario where the calculator produces a practically useful result from the given inputs.
This example demonstrates customer health score by computing Declining trend requires immediate intervention — do not wait for score to reach red before engaging; early action has highest success probability. Health Score Trend Analysis illustrates a typical scenario where the calculator produces a practically useful result from the given inputs.
This example demonstrates customer health score by computing Account B is the highest-priority intervention despite a higher health score than C — ARR at risk must weight prioritization alongside absolute score. Portfolio Prioritization illustrates a typical scenario where the calculator produces a practically useful result from the given inputs.
CSM portfolio prioritization and workload management — This application is commonly used by professionals who need precise quantitative analysis to support decision-making, budgeting, and strategic planning in their respective fields
Proactive churn prevention campaign targeting — Industry practitioners rely on this calculation to benchmark performance, compare alternatives, and ensure compliance with established standards and regulatory requirements, helping analysts produce accurate results that support strategic planning, resource allocation, and performance benchmarking across organizations
Renewal risk forecasting for revenue projections — Academic researchers and students use this computation to validate theoretical models, complete coursework assignments, and develop deeper understanding of the underlying mathematical principles
Identifying expansion-ready accounts for upsell outreach — Financial analysts and planners incorporate this calculation into their workflow to produce accurate forecasts, evaluate risk scenarios, and present data-driven recommendations to stakeholders
Board reporting on customer base health and retention outlook. This application is commonly used by professionals who need precise quantitative analysis to support decision-making, budgeting, and strategic planning in their respective fields
Single-user SaaS tools (individual productivity) need different health score
Single-user SaaS tools (individual productivity) need different health score dimensions than multi-user enterprise platforms When encountering this scenario in customer health score calculations, users should verify that their input values fall within the expected range for the formula to produce meaningful results. Out-of-range inputs can lead to mathematically valid but practically meaningless outputs that do not reflect real-world conditions.
Usage-based pricing products should normalize usage scores by spend level — a
Usage-based pricing products should normalize usage scores by spend level — a high-spend customer using features proportionally may score differently than expected This edge case frequently arises in professional applications of customer health score where boundary conditions or extreme values are involved. Practitioners should document when this situation occurs and consider whether alternative calculation methods or adjustment factors are more appropriate for their specific use case.
Seasonal businesses have cyclical usage patterns — health scores need seasonal
Seasonal businesses have cyclical usage patterns — health scores need seasonal normalization to avoid false red alerts during off-peak periods In the context of customer health score, this special case requires careful interpretation because standard assumptions may not hold. Users should cross-reference results with domain expertise and consider consulting additional references or tools to validate the output under these atypical conditions.
Customers during implementation phases often show low usage scores — exclude or
Customers during implementation phases often show low usage scores — exclude or weight-adjust during onboarding periods (typically 0–90 days post-go-live) When encountering this scenario in customer health score calculations, users should verify that their input values fall within the expected range for the formula to produce meaningful results. Out-of-range inputs can lead to mathematically valid but practically meaningless outputs that do not reflect real-world conditions.
| Health Score Range | Status | Renewal Probability | Recommended Action |
|---|---|---|---|
| 80–100 | Healthy (Green) | 90–97% | Expansion conversation, reference request |
| 60–79 | Good (Light Green) | 75–89% | Regular cadence, feature adoption push |
| 40–59 | At Risk (Yellow) | 50–74% | Executive check-in, value realization review |
| 20–39 | Critical (Red) | 25–49% | Escalation, executive sponsor engagement |
| 0–19 | Churning (Dark Red) | < 25% | Save playbook or managed offboarding |
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
This relates to customer health score calculations. This is an important consideration when working with customer health score calculations in practical applications. The answer depends on the specific input values and the context in which the calculation is being applied. For best results, users should consider their specific requirements and validate the output against known benchmarks or professional standards.
Pro Tip
Correlate your health score bands with actual renewal rates quarterly. If green-scored customers renew at 97%, yellow at 78%, and red at 45%, your model is working. If green customers churn at 20%, your score is not predicting outcomes — time to recalibrate weights with your data science team.
Did you know?
Gainsight, the leading Customer Success platform, found in their annual CS survey that companies using formal customer health scores achieve net revenue retention rates averaging 8–12 percentage points higher than those relying on informal CSM assessments alone.
References
- ›Gainsight Customer Success Best Practices Guide
- ›Nick Mehta — Customer Success: How Innovative Companies Are Reducing Churn
- ›Totango Customer Health Score Framework
- ›ChurnZero Customer Health Score Playbook