Why Is Our Customer Health Score Distribution Mostly Green?

A customer health score distribution that is 90% green is common, and it is usually evidence about the thresholds, not about the customers. Start with the outcome you already know. SaaS Capital's September 2025 retention brief, a survey of more than 1,000 private B2B SaaS companies, puts median gross revenue retention at 91%, and High Alpha's 2025 report puts it between 88% and 92% by ARR band. Nine points of revenue leaves the median company every year. Because gross retention is revenue-weighted, an SMB-heavy account base loses a higher share of logos than that. A score saying 93% of accounts are healthy is asserting an outcome better than the market median, which might be true and should be checked.

Green churn is what a miscalibrated distribution feels like from the inside. Health scores are heavily discussed in our review corpus, with 459 of 4,978 public customer success platform reviews mentioning one (9.2%) and 83 mentioning a scorecard (1.7%), and the colour system comes up constantly while the shape of its output almost never does. Across 33,600 Reddit posts from May 2024 to September 2026, 106 discuss health scores and the recurring complaint is the same: the colours are there, the separation is not.

Three distribution shapes cover almost every account base we have looked at, and each one has a different cause and a different fix. Find your shape first, because the work that follows is not the same. The shares below are the pattern, not a rule to copy.

Forced thirds is the shape people mistake for rigour. A percentile-based cut point always produces the same distribution, so the chart cannot tell you the accounts got better or worse, and CSMs learn within a quarter that being red means sitting in the bottom third of a ranking, not being in trouble. The percentile version is defensible only for ranking a work queue, and it should never be shown to a board as a health distribution.

Derive the cut points from two numbers you already have: how many accounts leave in a window, and how many accounts a CSM can work in a quarter. The red budget sets the ceiling on red, capacity sets the floor on usefulness, and the score's own score distribution decides where the line lands to produce that share.

Capacity is the constraint people leave out, and it is the one that decides whether the distribution gets used. A score that marks 120 accounts red for a team of four turns red into background noise within a month. How many accounts per CSM is too many covers the coverage maths behind the capacity number.

A distribution with no spread means the inputs do not discriminate, and no threshold can rescue it. Check it in one query: take the score for every account and find the 25th and 75th percentile. If the middle half of the accounts sit within about 10 points on a 100-point scale, most accounts are scoring on inputs that every account passes, and moving the red line picks a different arbitrary set of accounts to worry about.

Variance collapse has three usual causes. Inputs that are nearly always true, like having an active contract, an admin user or any login in 90 days, contribute the same points to everyone. Weighted averages of many inputs pull every account toward the middle, which is what averaging does. And manual sentiment fields drift upward over time, compressing the top of the range. Is health score coverage a KPI worth chasing covers the manual-drift problem specifically.

Colour lift is worth computing before any redesign, because it tells you whether the problem is the thresholds or the inputs. A score with good lift and a bad distribution needs new cut points, which is an afternoon. A score with lift below 2 needs new inputs, which is a project. Why is my customer health score accuracy so poor covers the nine input-level failures that produce low lift.

Join a past distribution to what happened next, then read the churn rate by score decile. The check needs a historical snapshot of scores, a list of churn and contraction events with notice dates, and a spreadsheet. Running it on today's distribution tells you nothing, because today has no outcomes yet.

1. 1

   Take the score distribution as it stood two quarters ago

   One row per account with its score and colour on that date. If the platform cannot show a past date, rebuild scores from stored inputs, and if that is also impossible, start snapshotting monthly from today and come back in two quarters.

2. 2

   Join the outcome that followed

   Churn, contraction above 20%, or neither, using the notice date and not the contract end date. An account that gave notice in month five counts as an event even if its contract ran on.

3. 3

   Bucket by score decile and count

   Ten buckets, each with its account count and its observed event rate. A calibrated score produces rates that fall as the decile rises, without reversals in the middle.

4. 4

   Compute colour lift and the red budget

   Divide the red event rate by the green event rate, then compare the red share you ran with the forward churn rate you observed. Two numbers, and they tell you which of the two fixes you need.

5. 5

   Move the cut points, then leave them alone for two quarters

   Set red at the budget, yellow at the next band the team can review weekly, and hold. Cut points moved every month cannot be evaluated, because each change resets the outcome data.

6. 6

   Publish the calibration table beside the distribution

   Ten rows, event rate by decile, dated. A distribution shown with its calibration gets trusted for what it is. A pie chart on its own gets argued with.

Read that table the way a calibration check is meant to be read. Event rates fall from 19.6% to near zero across the deciles, which is a score that separates. The reversal in the top decile is small enough to be noise at 46 accounts per bucket. The first two deciles hold 14 of the 26 events, 54% of them, in 20% of the accounts. A red budget of 6% reaches about a fifth of the events where a 20% red band would reach 54%, which is the capacity trade-off made explicit. These figures are illustrative; run the join on your own snapshot. The customer success scorecard is a starting point if you have no historical scores to join yet.

Report the movement, and keep the distribution as context underneath it. A static distribution answers how the accounts look, which changes slowly and tells nobody what to do. A transition table answers what changed since last month, which is the work queue and the story a leadership meeting can act on.

Three numbers in that table matter more than the whole pie chart. Twenty-nine accounts slid from green to yellow, which is this month's proactive work. Four went green straight to red without passing through yellow, which means the score is reacting to an event instead of a trend, and those four are worth reading individually. One account churned straight out of green, and that single row is the start of the list you review every quarter. How do I backtest customer health score logic covers the fuller version of that review.

A customer health score distribution is a summary of a prediction, and a prediction that nobody scored against outcomes is a colour scheme. The teams who get value from the chart are the ones who can say what happened to the accounts in each band last time, which takes one join and about an hour.

GainTrace scores accounts on change against their own baselines, so the distribution spreads out instead of piling up at the top, and it keeps the history that makes a calibration table possible without a snapshot project. Cut points are derived from your own churn and your own capacity rather than set by hand. Health signals show the distribution with the movement between bands, and churn prediction shows which accounts moved and what drove each call.