Most customer health score models were built for a specific kind of business: product-led, high-volume, self-serve. Usage frequency, feature adoption, and login activity are strong signals when the product is the whole relationship and the data is sitting right there in the app.
Complex B2B accounts don't work that way. The relationship spans procurement, IT, the economic buyer, the day-to-day users, and a champion who may never touch the product directly at all. A health score built only on usage can show green right up until the week the champion leaves the company, and by then the deal is already at risk.
What a typical customer health score measures
The standard model, borrowed from product-led businesses, usually weighs a handful of inputs into a single score or tier.
| Input | What it's meant to signal |
|---|---|
| Product usage / login frequency | Whether the customer is actively using what they bought. |
| Support ticket volume | Whether the account is running into friction. |
| NPS or survey response | Self-reported sentiment, gathered periodically. |
| Billing and contract signals | Payment health and time to renewal. |
These are real signals, and they work well in the businesses they were designed for. In complex B2B, they cover only part of the picture, and sometimes very little of it.
Where usage-only health scores go blind
A customer can log in every day while the one relationship that actually matters, the champion who sold the deal internally, has gone quiet or moved on. Usage tells you the product is being touched. It doesn't tell you whether the people who drive the renewal decision are still engaged, still aligned, or still even at the company.
Recent churn-prediction research backs this up directly. One analysis of health-scoring failures found that relationship signals typically surface trouble 30 to 90 days before usage metrics do, and identifies champion departure as one of the clearest predictors of churn in mid-market SaaS accounts. A health score that only watches the product is watching the wrong half of the relationship, and by the time telemetry catches up, the renewal decision may already be made.
What a B2B customer health score needs beyond usage
| Signal | What it adds that usage data can't |
|---|---|
| Stakeholder engagement trend | Whether the people who championed the deal are still actively engaged, not just whether someone at the company logged in. |
| Executive and champion coverage | A relationship concentrated in one contact is a risk regardless of how healthy usage looks. |
| Meeting and touchpoint cadence | Whether the account relationship is active or has quietly gone cold. |
| Renewal-date proximity without recent engagement | A renewal approaching with no real touchpoint in weeks is a risk signal a usage score won't catch. |
Signs your health score has a blind spot
| Warning sign | What it actually tells you |
|---|---|
| The score is green, but the champion hasn't responded in a month | Usage can stay steady even as the relationship that drives renewal deteriorates. |
| Health scoring resets to zero when an account transfers to a new CSM | The new owner inherits a number, not the context behind it. |
| The score only updates from a quarterly survey | A quarter is a long time for a relationship to change without anyone noticing. |
| Renewal risk shows up for the first time in the QBR | If the QBR is where you first learn about risk, the score wasn't catching it early enough to act. |
What to look for in a B2B customer health scoring approach
For accounts where the relationship, not just the product, drives the renewal, the score needs inputs a usage-only model was never built to capture.
| Capability | Why it matters |
|---|---|
| Tracks stakeholder engagement from real activity | Emails, meetings, and calls show whether the relationship is active, not just whether the product is. |
| Flags declining executive or champion engagement | The earliest and most reliable renewal-risk signal in complex B2B accounts is often relational, not usage-based. |
| Carries account context through CS handoffs | A new account owner should inherit the full story, not a blank slate and a number. |
| Works without native product-usage telemetry | Health scoring shouldn't depend on owning the product. Relationship and CRM activity data can carry the signal on their own. |
| Surfaces risk before the next scheduled check-in | Waiting for the quarterly review to learn about risk is waiting too long to act on it. |
What to read next
Health scoring is only useful if the people behind the score are mapped correctly. Read Stakeholder Mapping Tools → to see how coverage gets tracked across every account, pre-sale and post-sale.
For the full picture on account-level risk and expansion, see the Account Strategy solution →.
Backstory carries the full account context through pre-sale and post-sale — why the customer bought, who championed it, and which stakeholders are engaged — so Customer Success doesn't inherit a blank slate at renewal time. Risks, expansion opportunities, and renewal health are grounded in complete activity data, not a quarterly survey. See the Account Strategy solution →
Source: Vandfort, "73% of Health Scores Can't Predict Churn — How to Fix Yours"
See Backstory in action,
no meeting required
See the platform for yourself, or get the guide to help you evaluate it.