Guide
Customer health score in HubSpot – spotting the customers who are about to leave
How to build a health score from usage, meetings, sentiment and renewals, and a workflow that alerts the CSM when the score drops. With a worked example.
By Viktor Olsson, founder and RevOps consultant
Guide · Customer success· Updated · 12 min read
A customer health score is a score that shows how satisfied and active an existing customer is, and how likely they are to leave. It's built from four things: how much the customer uses the product, what the relationship looks like, what the customer says and how things stand ahead of the renewal. In HubSpot the score is recalculated automatically, and a workflow alerts the customer success manager (CSM) as soon as it drops. That gives you months to act before the renewal.
Why customers leave without warning
A customer that doesn't renew has often shown signs for months: fewer logins, a ticket that drags on, an email to the rep about a competitor. Each signal sits with a different person, and nobody sees the whole picture. We work out what that costs in What does it cost when sales, marketing and support aren't aligned?.
A health score gathers the signals in one place and adds them up. The CSM's gut feeling is still needed. The score makes sure it has something to react to in time.
Four areas that make up the score
-
Max 30 points
Product usage
- Share of licences in use
- Key feature in use
-
Max 25 points
Relationship and meetings
- Meeting in the last 90 days
- Contact with the decision maker
- Your contact person responds
-
Max 25 points
Sentiment
- Latest NPS response
- Open high-priority tickets
- Warning signs in emails and calls
-
Max 20 points
Contract and renewal
- Invoices paid on time
- Contract expanded in the last year
- Renewal prepared
Healthy 70–100
Watch 40–69
At risk 0–39
Product usage is the clearest signal for a product customers log in to. When the share of active users drops, the customer has often started losing interest long before anyone says so.
Relationship and meetings captures whether you're still in touch with the right people. A customer you haven't met in six months, where your contact person has left, is a risk even if usage looks fine.
Sentiment is what the customer says and feels: NPS responses, tickets that escalate, and words like "competitor", "cancel" or "the budget is under review" in emails and calls.
Contract and renewal is about the money: does the customer pay on time, have they grown with you, and is the renewal prepared as it gets closer.
Where the data comes from
The score is never better than the data it's calculated on. This is what needs to be on the company in HubSpot:
- Usage: the number of active users and whether the key feature is used, sent from your product to HubSpot through an integration, for example once a day. Since autumn 2026 you can set in the customer success workspace which of these events count as activation and which count as ongoing usage, and how often they should happen. It needs Service Hub Professional or Enterprise, and you can track up to ten events.
- Meetings and emails: logged automatically when calendars and inboxes are connected to HubSpot.
- NPS: a survey sent from HubSpot after onboarding and then twice a year.
- Tickets: support tickets with a priority, on the same company. How to set up the tickets is in Customer support in HubSpot.
- Warning signs: an AI step can read new emails and call notes and flag when a competitor, a cancellation or a budget cut is mentioned. More on that in Context is king. HubSpot has also started showing its own churn risk signal drawn from emails, calls and notes. Compare it with your AI step on a few customers before you choose which one the score should use.
- Invoices and renewal dates: from the accounting system, or from HubSpot if you invoice there. How payment status can come back from Fortnox is in From quote to invoice in HubSpot.
A scoring model to start from
This is a model we usually start with for B2B companies on annual contracts. Adjust the weights to your own customers, but the structure holds.
Product usage, max 30 points
| Criterion | Points |
|---|---|
| 80% or more of licences used in the last 30 days | +20 |
| 50–79% of licences used | +12 |
| Under 50% of licences used | +4 |
| Key feature used in the last 30 days | +10 |
Relationship and meetings, max 25 points
| Criterion | Points |
|---|---|
| Meeting with the customer in the last 90 days | +10 |
| Contact with the decision maker in the last 90 days | +10 |
| Your contact person at the customer is still there and responds | +5 |
Sentiment, max 25 points
| Criterion | Points |
|---|---|
| Latest NPS response 9–10 | +15 |
| Latest NPS response 7–8 | +8 |
| No open high-priority tickets | +10 |
| Warning sign in an email or call in the last 30 days | −15 |
Contract and renewal, max 20 points
| Criterion | Points |
|---|---|
| Invoices paid on time | +10 |
| Contract expanded in the last 12 months | +5 |
| More than 90 days to renewal, or a renewal meeting booked | +5 |
Thresholds: Healthy 70–100, Watch 40–69, At risk 0–39. A total below 0 counts as 0.
The level and the trend
A customer who has sat at 55 for a year is often less worrying than one who went from 85 to 60 in a month. The first has always looked like that. The second has something that just happened.
That's why the model alerts on two things: when the score falls below 40, and when it drops 15 points or more in 30 days, whatever the level. To see the trend, a workflow saves the score once a month in its own field, "health score 30 days ago", which the new score is compared with.
The workflow: when the score drops, the CSM gets an alert
The company's health score changes
Health score and trend
Under 40, or at least 15 points lower than 30 days ago
Alert the CSM, copy the head of customer success
Call the customer. High priority, due in 2 working days
Summarise the customer's last 90 days as a note
Renewal close: alerts the rep if the renewal is within 90 days
40–69
Contact the customer. Due in a week
Follow-up = Weekly meeting
Healthy: 70 or more
Swipe sideways to see the whole flow.
The workflow step by step:
- Trigger. The workflow starts whenever the health score changes.
- Branch on risk. The first branch catches both a low level and a fast drop: the score is under 40, or at least 15 points lower than 30 days ago. HubSpot reads branches from the left, so risk goes first.
- Alert. The CSM gets a notification in HubSpot or Slack and a high-priority task due within two working days. The head of customer success gets a copy.
- Background. An AI step writes a summary of the customer's last 90 days, with tickets, emails, meetings and NPS, and saves it as a note on the company. The CSM doesn't have to dig before the call.
- Renewal close. The at-risk customer is enrolled in a separate workflow that reads the renewal date. If there are less than 90 days left, the rep who owns the customer is notified too, so nobody is surprised in the renewal conversation.
- Watch. A task within a week, and the Follow-up field is set to Weekly meeting. That puts the customer in the saved view that's reviewed at the weekly meeting.
- Healthy. No condition is met and the workflow ends. The renewal deal is created by a separate workflow based on the renewal date, 120 days before the contract ends. We describe what the handover from customer success to sales can look like in One customer, one place.
- Follow-up. If no call or meeting has been logged on an at-risk customer after two working days, a reminder goes to the head of customer success.
An example: three months in points
Take the example customer Ekbacka Logistik AB, with 25 licences and a contract that ends in December.
August
Healthy
September
−28 in a month: alert
October
At risk: alert, and the rep is told
| Area | August | September | October |
|---|---|---|---|
| Product usage (max 30) | 30 | 22 | 4 |
| Relationship and meetings (max 25) | 25 | 25 | 10 |
| Sentiment (max 25) | 18 | 8 | −5 |
| Contract and renewal (max 20) | 15 | 5 | 10 |
| Health score | 88 | 60 | 19 |
August, 88. 22 of 25 licences are in use and the reports are used every week. A meeting in June, contact with the CFO, Karin Sjö, and the IT contact, Martin Ahl, responds. The latest NPS response is 8, there are no open tickets and invoices are paid.
September, 60. Active users drop to 16. An invoicing error becomes a high-priority ticket, and the invoice isn't paid until it's resolved. The score is still yellow, but it has dropped 28 points in a month. This is where the alert comes. The CSM calls and learns that a new administrator never got any training and that the invoicing error is annoying the CFO. Two things to fix, three months before the renewal.
October, 19. If nobody acts, it continues. Active users drop to 11, there has been no meeting in over 90 days and Martin doesn't respond. The NPS response is 5, and in an email Karin asks how long the notice period is. Now there are less than 90 days left and the rep gets the alert too.
Without the score, the signals sit with different people in different teams. With it, the first alert comes in September, before Karin asks about the notice period.
How to build it in HubSpot
- Gather the data on the company: connect inboxes and calendars, send usage data from the product, set up the NPS survey, and store the renewal date and invoice status as fields.
- Set up the health score in HubSpot's customer success workspace (Service → Customer Success): the criteria, weights and thresholds for green, yellow and red above.
- Add the trend field, "health score 30 days ago", and a small workflow that fills it in once a month.
- Build the alert workflow with the branches above and the AI step for the summary.
- Show the score where CSMs work: a column in the customer success workspace and a saved "my at-risk customers" view, sorted by renewal date.
- Build a report showing how many customers in each group renew, cancel or expand. Since autumn 2026 Service Hub has ready-made reports for how much revenue you keep, gross and net (GRR and NRR). Split them by healthy, watch and at risk.
How to know the score works
Go through the customers who cancelled in the last year:
- Did they have a low score or a drop 60–90 days before? If not, a signal is missing from the model.
- How many alerts were false alarms? If CSMs get alerts about customers who are fine, they stop reading them. Raise the threshold or change the weights.
- What do the CSMs say? They know the customers. If the score often contradicts them, it's worth finding out who's right.
Adjust every month for the first quarter, then every quarter.
Common mistakes
- Usage only. A customer can log in every day and still have a decision maker who has decided to switch supplier.
- Level only. Without the trend you miss customers who are falling fast but haven't reached red yet.
- Too many alerts. Five alerts a week per CSM is too many. Start with a high threshold and lower it.
- No explanation. The alert should show which criteria dropped, or every call starts with detective work.
- Alerts without a task. A notification gets lost in the feed. A task with a deadline and a reminder to the manager means someone calls.
Common questions
What is a customer health score? A score that shows how satisfied, active and profitable an existing customer is, and how likely they are to leave. It's calculated from signals such as product usage, meetings, NPS, tickets and contract data, and it's used so CSMs can act before it's too late.
Which HubSpot licence do you need for a health score? Health scores are in HubSpot's customer success workspace in Service Hub, at the Professional and Enterprise tiers, and anyone working in the workspace needs a Service seat. Features change often, so check what's included in your licence.
What's the difference between a lead score and a health score? A lead score ranks leads before the deal, so reps know who to call first. A health score ranks existing customers by risk, so CSMs know who to call first. The principle is the same, and we describe lead scoring in Lead scoring in HubSpot.
What if we don't have usage data in HubSpot? Start with relationship, sentiment and contract, and give them more weight. Usage data can be added later with an integration from your product, and the score usually gets a lot more reliable then. Once the events are in HubSpot, you set what counts as active use in the customer success workspace.
How often should the health score update? Usage data once a day is enough for most companies. The score is recalculated automatically when the data changes, and the model itself is adjusted every quarter.
About the author
Viktor Olsson, founder and RevOps consultant
Viktor has worked with HubSpot for six years, with teams from 3 people to organisations with 30 sales reps across the Nordics. He also works in RevOps at an international SaaS company.