Your health score is green and the account is leaving
Health scores measure activity, not intent. Here's what they miss, the signals that actually predict churn, and how I use the score without trusting it.
Every CS tool sells the same picture: a dashboard of accounts, each with a colour. Green, amber, red. Look at the reds, save the day. It's a comforting picture and it's mostly wrong.
The problem isn't that health scores are useless. It's that they measure what's easy to measure, and what's easy to measure is activity. Logins. Feature usage. Tickets opened. Emails answered. All of that tells you whether people are using the product. None of it tells you whether they're going to keep paying for it. Those are different questions, and the gap between them is where accounts quietly walk out.
What a green score actually means
A green score usually means a handful of users are logging in regularly and nobody has shouted at support lately. That's it. It is entirely compatible with:
- The executive sponsor having left three months ago and nobody telling you
- The team using it daily because they have to, while a procurement review is already underway to replace it
- One power user carrying all the usage while the other forty seats sit idle
- A customer who is happy with the product and about to be acquired by a company that uses your competitor
I've watched accounts churn from green. Not from amber, not after a slow decline. Green on Monday, notice of non-renewal on Thursday. In every one of those cases the signal existed. It just wasn't a signal the score knew how to read.
The signals that actually predict churn
Over time I've come to trust a short list of things far more than the colour on the dashboard. None of them are in the score, because none of them are numbers in a database.
The champion's calendar. When your main contact starts declining your meetings, or sends a deputy, or moves your monthly check-in to quarterly "because things are busy", that's not scheduling. That's deprioritisation. People make time for things that matter to their job. If you've stopped mattering to their job, you're on the list.
Who asks the questions. In a healthy account, the customer asks you things. How do I do X. Can the product do Y. When is Z shipping. When the questions stop and every conversation is you presenting to them, the relationship has gone one-directional. One-directional relationships don't renew well.
Procurement and finance showing up. If you suddenly get a request for a security questionnaire, a copy of the contract, or a breakdown of seats and usage, and it didn't come through your champion, someone is building a case. It might be a case for you. Find out which.
The org chart moving. New VP, new CFO, a reorg that moves your team under a different leader. Every one of these resets your account to zero. The new person didn't buy you, doesn't know you, and has their own preferred tools. Your green score is based on a world that no longer exists.
Usage concentration. Not total usage, concentration. If 90% of activity comes from two people, you don't have an account, you have two users. If either of them leaves, so does the account, and the score won't move until long after it's too late.
How I actually use the score
I don't ignore it. I use it for the thing it's good at, which is catching the obvious. If an account goes from heavy use to nothing, I want to know, and the score will tell me faster than I'd notice on my own. Red scores are real. They're just the easy part.
What I do with green is treat it as "no information" rather than "safe". For every green account above a certain size I keep a separate, much shorter list of questions I should be able to answer:
- Who is the executive sponsor, and when did I last speak to them directly?
- Who would make the renewal decision, and do they know what we do for them?
- If my champion left tomorrow, who would I call?
- What has changed in their business in the last quarter?
If I can't answer those, the account isn't green. It's unknown. And unknown is where you do the work.
Stop reporting the score as if it's a forecast
The worst thing a health score does is get reported upward. A dashboard that says 85% of ARR is green becomes a statement to leadership that 85% of ARR is safe, and then when something churns from green the CSM gets asked what they missed. The honest answer is usually "nothing the score was looking at".
If you run a CS team, push back on this. Health scores are a triage tool for the team, not a forecast for the board. The forecast comes from the questions above, answered by a human who's actually talking to the customer. That's the job. The dashboard is just where you start.
Get the daily Briefing
Five customer success stories with Ron's take, every weekday morning. Two minutes to read. Free, and unsubscribe any time.