# Customer Health Scoring — Standard Operating Procedure > Source: https://b2bprocess.com/customer-health-scoring > Last updated: 2026-07-11. Adapt owners, tools, and thresholds to your organization. ## 1. Purpose Customer health scoring is the process of combining multiple signals — product usage depth and breadth, support ticket volume and sentiment, engagement with the CS team, contract and billing status, and relationship strength with key stakeholders — into a single score or banded rating (e.g., green/yellow/red) per account. The score gives customer success, sales, and leadership a shared, at-a-glance answer to 'is this account in good shape,' surfaced early enough to act on rather than discovered at the renewal conversation. ## 2. Scope & prerequisites Worth building once a CS team manages enough accounts that a CSM cannot personally track the state of every one from memory — typically 30+ accounts per CSM, or any pooled/tech-touch segment with no dedicated owner. Prerequisites: reliable product usage data (event tracking or a proxy for it), a CRM or CS platform to host the score, and at least a few renewal cycles of outcome history to calibrate the model against — without outcome history, the score is a plausible-looking guess. ## 3. Roles & responsibilities | Role | Responsibility | | --- | --- | | CS Operations / RevOps | Owns the scoring model design, signal weighting, and periodic validation against outcomes. | | Customer Success Manager | Acts on the score day-to-day; feeds back qualitative context the model can't see. | | CS leadership | Defines what 'healthy' means for the business, owns playbooks tied to each health band, and holds the model to renewal/expansion outcomes. | | Product / Product Analytics | Provides usage event data and helps identify which product behaviors correlate with retention. | | Sales leadership | Uses health bands in renewal forecasting and expansion qualification; partners on save plans for at-risk accounts. | ## 4. Procedure ### Step 1: Define what 'healthy' means for this product and segment **Owner:** CS leadership + Product Before choosing inputs, agree what a healthy account actually looks like in outcome terms — renews, expands, references the product — and work backward to the leading indicators that correlate with those outcomes for this specific product and customer segment. A B2B collaboration tool and a compliance system have different usage patterns that signal health. - [ ] Pull a sample of renewed/expanded vs. churned/downgraded accounts - [ ] Identify usage and engagement patterns that differ between the two groups - [ ] Document the health definition per segment if usage patterns differ materially ### Step 2: Select and weight the input signals **Owner:** CS Operations / RevOps Choose a small number of signal categories — product usage (depth, breadth, frequency, key-feature adoption), support (ticket volume, severity, resolution sentiment), relationship (executive sponsor engagement, stakeholder turnover), and commercial (payment status, contract terms) — and weight them by how strongly each actually predicted past outcomes, not by ease of access. - [ ] Score usage signals: login frequency, active users, core-workflow completion, feature depth - [ ] Score support signals: ticket volume trend, escalations, CSAT on tickets - [ ] Score relationship signals: sponsor engagement, stakeholder/champion turnover, QBR attendance - [ ] Weight each category against back-tested correlation with churn/expansion ### Step 3: Build the composite score and bands **Owner:** CS Operations / RevOps Combine weighted signals into a single score (commonly 0–100) and define bands (e.g., green/yellow/red) with clear, written criteria for each band, so 'yellow' means something specific and consistent across every CSM rather than a gut feeling dressed up as a number. ### Step 4: Surface the score with reasons, not just a color **Owner:** CS Operations Display the score on the account record alongside the specific signals driving it — which usage metrics dropped, which tickets escalated, which stakeholder went quiet — so the CSM can act on the cause, not just react to a color change. ### Step 5: Wire the score into playbooks and escalation **Owner:** CS leadership + CSM team Define what happens when an account crosses into yellow or red: a specific playbook (re-engagement outreach, executive check-in, risk escalation to CS leadership), an owner, and an SLA. A score with no attached action is a dashboard decoration. ### Step 6: Validate the model against renewal and expansion outcomes **Owner:** CS Operations + RevOps Each quarter, compare renewal and expansion rates by health band from the prior period. If red accounts renew at similar rates to green accounts, the model isn't predictive and the weights need revisiting rather than being trusted at face value. ### Step 7: Feed the score into forecasting and account planning **Owner:** CS leadership + Sales leadership Use health bands as an input to renewal forecasting, expansion pipeline qualification, and account planning discussions with sales — a red account should change the renewal forecast and trigger a joint save plan, not sit unnoticed in a CS-only dashboard. ### Step 8: Recalibrate signals and weights periodically **Owner:** CS Operations / RevOps Revisit input weights, thresholds, and even the signal set itself as the product, ICP, or customer base changes — a health model built for last year's product usage patterns silently drifts out of relevance without a deliberate refresh. ## 5. Metrics to monitor | Metric | Definition | Formula | Target | | --- | --- | --- | --- | | Health-band predictive accuracy | How much better green accounts renew/expand versus red accounts — the core validity check of the model. | Green-band renewal rate ÷ red-band renewal rate | typical target: meaningfully separated, e.g. 1.5–2x or more | | Red-account renewal rate | Renewal rate of accounts flagged red, showing whether the model catches real risk in time to act. | Renewed red accounts ÷ total red accounts | typical target: below green/yellow renewal rate by a wide, actionable margin | | Score coverage | Share of the active customer base with a computed, up-to-date health score. | Accounts with a current score ÷ total active accounts | typical target: above 95% | | Time in red before action | Days between an account entering the red band and a documented save-plan action. | First save-plan action date − date entered red | typical target: under 5 business days | | False positive rate | Share of red-flagged accounts that renew/expand normally despite the flag, indicating over-sensitive scoring. | Red accounts that renewed/expanded ÷ total red accounts | typical target: below 30% | ## 6. Known failure modes | Failure | Symptom | Corrective action | | --- | --- | --- | | Score built on convenient data, not predictive data | The composite doesn't separate renewing from churning accounts; CSMs stop trusting it. | Back-test every signal against actual renewal/expansion outcomes before including it, and drop ones with no lift. | | One blended score with no visible drivers | CSMs see 'yellow' but not why, and can't act on the score without redoing the diagnosis manually. | Surface the specific signals driving the score alongside the composite number. | | No action attached to band changes | Accounts sit in red for months with nobody assigned to respond. | Define a specific playbook, owner, and SLA for every band transition, especially into yellow and red. | | Model never revalidated | Health bands stop correlating with outcomes as the product and customer base evolve, but nobody notices. | Quarterly validation comparing renewal/expansion rates by band; recalibrate weights when the correlation weakens. | | Relationship signals ignored in favor of usage data alone | Accounts with strong usage churn anyway after a champion leaves or a sponsor disengages. | Include stakeholder turnover and sponsor engagement as explicit signal categories, not an afterthought. | | Score hidden from sales and leadership | A red account renews as a surprise-loss because only CS ever saw the risk. | Feed health bands into renewal forecasting and account planning visible to sales and CS leadership jointly. | --- This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.