Agencies rarely lose clients without warning. The warnings are usually spread across different people: the project lead knows a milestone has slipped, accounts knows the last invoice was paid late, and the account lead has noticed the sponsor has gone quiet. A customer health score pulls those signals into one place so someone can act while there is still time.
What signals should an agency track?
Track signals you already collect and can check without asking the client. Five groups cover most of what matters:
- Delivery: are milestones on time, is the project within scope, are there open issues or complaints?
- Payment: are invoices paid on time, is anything overdue, has the client queried recent invoices?
- Engagement: does the client’s sponsor attend reviews, reply promptly, and give feedback?
- Commercial trend: is spend steady, growing or shrinking? Is there renewal or follow-on work in discussion?
- Sentiment: what the client says when asked, including a recommendation score.
A change of sponsor on the client side deserves its own flag. A new decision-maker who did not choose you is one of the most reliable early warnings there is.
What is NPS, and what are its limits?
NPS, or Net Promoter Score, asks one question: how likely are you to recommend us to a colleague, on a scale of 0 to 10? People scoring 9 or 10 are promoters, 7 or 8 are passives, and 0 to 6 are detractors. The score is the percentage of promoters minus the percentage of detractors.
NPS is useful, but it has real limits for a firm with 20 or 40 clients:
- Small numbers swing wildly. One client moving from 9 to 6 can shift your overall score by several points. Look at each client’s history, not just the total.
- It is one person’s view. The person answering may not be the person who renews.
- It lags. By the time a score drops, the cause is often weeks old.
- It can be gamed. Asking only after a good meeting inflates it.
- Declines are not detractors. If a client will not give a number, record that separately. Counting it as zero corrupts the average.
The most useful NPS signal for an agency is movement. A client going from 9 to 7 over two reviews tells you more than a flat 7.
What does a simple health model look like?
A simple model scores each signal green, amber or red and adds them up. Keep it small enough to fill in from memory in a monthly review:
| Signal | Green (2) | Amber (1) | Red (0) |
|---|---|---|---|
| Delivery | On time, in scope | One slipped milestone or open issue | Repeated slips or an escalation |
| Payment | Paid within terms | One invoice up to 30 days late | Overdue more than 30 days, or disputed |
| Engagement | Sponsor active, reviews attended | Slower replies, missed review | Sponsor gone quiet or changed |
| Commercial | Growing or renewal agreed | Flat, nothing new discussed | Reducing scope or notice given |
| Sentiment | Recommendation score 9–10 | 7–8, or dropped since last time | 0–6 |
A total of 8–10 is healthy, 5–7 needs watching, and 4 or under is at risk. Any single red should also trigger a conversation, whatever the total.
A worked example with invented figures. Take a 40-person agency reviewing a £120,000-a-year retainer client. Delivery is green (2). One invoice is 20 days late (1). The client’s marketing director, who hired the agency, left last month (0). Spend is flat (1). The last recommendation score was 8, down from 9 (1). The total is 5: amber, with a red on engagement. The action is clear: the account owner books a meeting with the new director within two weeks and brings a short summary of results so far.
How often should you review customer health?
Review it monthly for every active client, and immediately when a red signal appears. The monthly review should take minutes per account if the data is already in one place.
Ask for recommendation scores on a steady cadence, such as at each quarterly progress review, rather than only after good news. A steady cadence is what makes movement meaningful.
Who should own an at-risk account?
Every at-risk account needs one named account owner, a written next step and a date. Shared ownership of an at-risk client usually means nobody calls them.
The owner is normally the account or client services lead, not the project manager. Their job is to understand the cause, agree a mitigation, and record it. Closing an at-risk flag should require that mitigation to be written down. Otherwise “we spoke to them” becomes the default fix for everything.
Escalate to a director when the client’s spend is significant or the relationship needs a senior voice. Tie actions into your planning rhythm, such as 90-day plans, so recovery work is not treated as an optional extra.
What mistakes should you avoid?
Avoid building a model that is more precise than your data. A 100-point formula with weighted decimals looks rigorous but is usually a guess with extra steps. Keep the model simple and change it as you learn which signals actually preceded losses.
Also avoid scoring only the clients you are worried about. Healthy clients drift too, and the monthly review is how you notice.
Where OpsUPLOOP fits, and where it doesn’t
OpsUPLOOP records client recommendation scores on a cadence and shows each customer’s history as a heat map, so movement is visible rather than buried in an average. A declined answer is kept separate from a low score. A drop or a detractor opens an action automatically, and closing it requires the mitigation to be written down. Delivery milestones, billing and payment sit in the same records, with a named owner. See OpsUPLOOP Delivery.
It is not a full customer-success platform, and it does not predict churn. It will not tell you a client is about to leave. It makes the signals you already have visible to the person who owns the relationship, and the judgement stays with them.
Other questions
How is a customer health score different from NPS?
NPS is one signal, the client's stated willingness to recommend you. A health score combines several signals, including delivery, payment and engagement, so it can flag risk the client has not said out loud.
Should the client see their health score?
Usually not the score itself. Share the underlying facts, such as a slipping milestone or a late invoice, and what you are doing about them.
What should happen when a client declines to give an NPS score?
Record it as declined rather than as a zero or a detractor. A refusal is information, but it is not the same as a low score, and mixing them distorts your averages.