By István-Tamás Schneller, Founder, Auroranexis · Updated · 9 min read
Most advice on customer health scores is written for software companies. It tells you to score logins, feature adoption and product usage. If you run an agency, an IT service provider, an accounting firm or a facility services company, your clients do not log in to anything. They receive a service, and their health shows up in other places: in how reliably you deliver, how they respond to you, and how the commercial relationship develops.
A customer health score for a service business turns those signals into one simple rating per client, so you can see early which accounts need attention. This guide shows which signals to use, how to combine them, a worked example you can copy into a spreadsheet, and how to act on the result.
A customer health score is a regular, rule-based rating of how likely a client is to stay, grow or leave. It combines a few signals you already have into one number or colour, and it should always show which signals caused the rating.
It is not a prediction you can trust blindly, and it is not a replacement for talking to your clients. It is a way to make sure no account drifts for months without anyone noticing. A good score starts conversations; it does not end them.
Choose signals from four groups. You do not need all of them — four to six signals in total are enough for a first version.
A change of the main contact person deserves special attention. The person who chose you may be gone, and the new contact may not know what you deliver. Treat it as an early warning even when everything else looks fine.
Look back at clients you lost. Write down the clients who left or reduced their contract in the last one or two years, and what happened in the months before. Those patterns tell you which signals matter in your business.
Pick four to six signals. Choose signals you can measure every month without guessing. If a signal depends on someone's mood that day, define it more precisely or leave it out.
Set simple thresholds. For every signal, define what counts as healthy, watch and at risk. Three levels are enough; scoring them 100, 50 and 0 keeps the arithmetic easy.
Weight the signals. Give the signals that best explained past losses the highest weight. The weights must add up to 100%.
Calculate and set bands. Multiply each signal score by its weight and add the results. Then turn the number into a colour, for example green at 75 or above, amber from 50 to under 75, red below 50.
Assign an owner and an action per band. Every client needs one person responsible for its health, and every band needs an agreed next step. A score without an action is just another dashboard.
These thresholds are an example for a service provider with monthly reporting. Adapt them to your contracts and your clients.
Example — three levels per signal
One client, one month, using the thresholds above and these example weights: SLA attainment 30%, incidents 20%, responsiveness 20%, payment 15%, sentiment 15%. The numbers are illustrative; use your own.
Example — one client, one month
The total says amber, but the detail says more: delivery is fine, yet the client has stopped showing up. That is why every score must show its drivers. The right action here is not a technical fix but a conversation with the client about whether the service still meets their needs.
Bring the health history to your quarterly review with the client. Showing that you noticed a problem early and acted on it builds more trust than a perfect score.
It is a regular, rule-based rating of each client that combines a few signals — such as delivery quality, responsiveness, payment behaviour and feedback — into one number or colour, so you can see early which clients need attention.
Four to six is a good start. Fewer signals make the score easy to explain and to trust. Add more only when you can show that they would have warned you about a client you lost.
Give every signal a score — for example 100 for healthy, 50 for watch and 0 for at risk — multiply each score by the signal's weight, and add the results. Then translate the total into a band such as green, amber or red.
Usually not the score itself, because it includes internal judgements such as payment behaviour. Share the parts that describe your service — SLA results, incidents and open risks — in your regular reports instead.
Monthly is enough for most service businesses, ideally right before the monthly report. Review red clients weekly until they recover, and check the scoring rules themselves every six months.
Join the invite-only pilot program: six weeks of dedicated onboarding, influence on the roadmap and pilot pricing.
