How to Build a Customer Health Score Your Team Will Actually Trust

A customer health score is a single number that summarizes how likely an account is to renew, expand or churn. Done well, it tells a customer-success manager where to spend the week. Done badly, it is a number everyone ignores because nobody can explain why it moved.

This guide walks through how to build a health score that holds up: the signals worth tracking, how to combine them, and the habits that keep a score trustworthy as your customer base grows.

What a customer health score is for

The score has one job: rank accounts by how much attention they need right now. It is not a forecast to report to the board and it is not a grade for the CSM. If a score helps a team decide which three customers to call today, it is working.

The signals that matter

Most useful health scores draw on four families of signal. You do not need all of them on day one; start with what you can measure reliably.

• Engagement: how often the customer's users log in, which features they use, and whether usage is growing or shrinking month over month.
• Relationship: how recently you spoke with the account, whether your champion still replies, and the tone of recent conversations.
• Support: open ticket count, time to resolution, and escalations in the last 90 days.
• Commercial: days to renewal, contract value, payment history and any downgrade requests.

Weighting: keep it simple and visible

Resist the urge to build a twenty-factor model. Pick four to six signals, give each a weight that adds up to 100, and write the weights down where the whole team can see them. A score that drops from 78 to 52 should come with a sentence: engagement fell 40% and the champion has not replied in three weeks.

Revisit weights each quarter by looking at the accounts that churned. If most of them had healthy scores 90 days before they left, a signal is missing or under-weighted.

Three bands are enough

Bands matter more than decimals. Three bands, Healthy, At Risk and Critical, are enough for a CSM to act on. Agree on what each band means in practice: a Critical account gets an outreach within two business days; an At Risk account gets reviewed in the weekly team meeting.

Turn the score into action

A score that changes and triggers nothing is a vanity metric. Tie each band change to a response. When an account drops to Critical, open a task for the owner, send a check-in from their mailbox, and alert their manager if the renewal is inside 60 days.

In tracview, that response is a Playbook: a reusable sequence of tasks, emails and notifications that a Trigger can launch when a customer's health score falls below a level you choose, so no struggling account waits for someone to notice.

Common mistakes

• Scoring on data you cannot refresh automatically, so the score goes stale within a month.
• Hiding the formula, so CSMs override the score with their gut.
• Treating every account the same. A ten-seat startup and a thousand-seat enterprise rarely share the same healthy usage pattern.
• Measuring the score and never the outcome. Track renewal rate by band to prove the score predicts anything.

Where to start this week

Pick three signals you already have: last login, open tickets and days to renewal. Weight them evenly, score every account, and look at the bottom ten with your team. You will learn more from that conversation than from any model you design in a spreadsheet.