-1.svg)
Key Takeaways
-
A customer health score in HubSpot combines a few weighted signals into one number that shows customer success where to look first.
-
Start with five or six signals you already capture reliably, such as usage, support tickets, feedback, engagement and payment status.
-
Weight each signal by how strongly it preceded churn or growth in your own accounts, not by ease of tracking.
-
Set three bands, healthy, watch and at risk, and attach a named owner and a specific action to each band before launch.
-
Test the score against accounts your team knows well, then review the weights each quarter as renewal and churn outcomes arrive.
A health score is only useful if it changes what a customer success manager does next week. Building one in HubSpot runs from choosing signals to deciding what each band triggers.
What is a customer health score in HubSpot, and what should it do?
A customer health score in HubSpot is a single value on the company record that summarizes how an account is doing. It combines several signals, such as product usage, open tickets and recent feedback, into one number and a band that a customer success team can sort and filter by.
For B2B companies, build the score on the company rather than the contact. HubSpot offers more than one way to build it. Service Hub includes customer success tools with health scoring for accounts, and you can also assemble a score from your own properties with calculated properties and workflows. Your portal and subscription decide which scoring methods are open to you, so confirm that before you choose one.
What this means for you: before you choose a single signal, write down the decision the score will drive. If nobody can name the action a low score triggers, the team has no reason to check the score.
Which signals should a customer health score in HubSpot use?
Choose signals that pass four tests. Each one should plausibly come before churn or growth, be captured reliably, be available on or rolled up to the company record, and update often enough to matter.
Six signal types make a reasonable first list for B2B accounts:
-
Product usage: active users compared with licensed users, synced from your product into a company property.
-
Support load: open tickets and escalations associated with the company.
-
Feedback: the latest survey responses from contacts at the account.
-
Engagement with your team: meetings, calls and emails logged against the company.
-
Payment status: whether invoices are paid on time, from HubSpot or from synced finance data.
-
Champion in place: whether your main sponsor at the account is still there and still engaged.
Leave out signals you cannot capture consistently. In the scores we review, a common weakness is a long input list with several fields blank for many accounts, which makes the result easy to dismiss.
Questions to ask: Which of these signals do we already capture for every account today? Which signal would our customer success team trust least, and why?
How do you weight signals in a HubSpot customer health score?
Weight signals by evidence from your own accounts. Pull the accounts that churned and the accounts that expanded over the last year, and look at what each signal showed in the months before the outcome. Signals that separated the two groups deserve the larger weights.
Where you have little history, the model below gives you something to calibrate rather than a method to adopt. Its weights and thresholds are a Markivis recommendation for B2B companies selling annual software or service contracts, not a benchmark, and we would expect most of them to move after the first back-test. Each signal scores full points when healthy, half points in watch, and zero when at risk, and the points add up to 100.
At a glance: an example starting model for a HubSpot health score, to be recalibrated against your own accounts.
|
Signal |
Data source |
Weight |
Healthy / watch / at-risk threshold |
|
Product usage |
Usage data synced to a company property |
30 points |
Healthy: three quarters or more of licensed users active monthly. Watch: half to three quarters. At risk: under half |
|
Support load |
Tickets associated with the company |
20 points |
Healthy: no open high-priority tickets. Watch: one open. At risk: two or more, or any escalation |
|
Feedback |
Survey responses from contacts at the company |
15 points |
Healthy: latest response positive. Watch: neutral. At risk: negative from a decision maker |
|
Engagement with your team |
Meetings, calls and emails logged on the company |
15 points |
Healthy: contact in the last 30 days. Watch: 31 to 60 days. At risk: none for over 60 days |
|
Payment status |
Invoice or payment records, or synced finance data |
10 points |
Healthy: paid on time. Watch: one invoice overdue. At risk: invoices overdue beyond 30 days |
|
Champion in place |
Association label or property on the key contact |
10 points |
Healthy: champion active. Watch: champion quiet for 60 days. At risk: champion has left |
As a first pass, use 75 to 100 for healthy, 50 to 74 for watch and below 50 for at risk. Move the cut-offs once you see how real accounts distribute.
How do you build the customer health score in HubSpot?
Build it in five steps.
Create the input properties: add a company property for each signal, such as active user ratio or days since the last logged meeting. Calculated and rollup properties can derive some of these, such as a count of tickets on associated records.
Convert each signal to points: use workflows, or HubSpot's built-in scoring tools, to assign full, half or zero points to each signal based on its threshold.
Combine the points into one score: a calculated property can add the signal points together. If you use the health scoring in Service Hub's customer success tools, you can configure the same signals and weights there instead.
Set the band: create a dropdown property with healthy, watch and at risk, and use a workflow to set it from the score.
Test against known accounts: pick ten accounts your team knows well, including two that recently churned. Compare the score with what the account owners expect, and investigate every disagreement before launch.
A health score that customer success disagrees with on accounts they know well will be ignored on the accounts they do not.
What this means for you: schedule the test session with account owners before you build the reports. Their disagreements tell you which weights are wrong while changes are still cheap.
What should each customer health score band trigger in HubSpot?
Each band needs an owner and an action, or the score changes nothing. We would typically set it up like this:
Healthy: no automatic task. The account stays on its normal check-in rhythm, and the customer success manager can consider it for a referral request or a growth conversation.
Watch: a workflow creates a task for the customer success manager to review the account within five working days and record a reason for the dip on the company record.
At risk: a workflow sets the at-risk band on the company, creates a same-day task and notifies the customer success lead. A contact list reads that band through the company association, and with that list excluded from promotional sends, the account's contacts receive no promotional email until the band improves.
Trigger these actions when the band changes, not whenever the score recalculates. A workflow that re-enrolls on every recalculation can create duplicate tasks and train your team to ignore them.
Questions to ask: Who owns each band, and how will we know an action happened? What does a customer success manager record when they disagree with the score?
How do you measure whether your customer health score in HubSpot works?
Measure the score against outcomes, not activity. Each quarter, take the accounts that churned, renewed or expanded, and check what band each one sat in 90 days earlier. A useful score will have flagged churned accounts as watch or at risk ahead of time, and it will not have flagged many accounts that went on to renew comfortably.
Alongside that test, track how many at-risk tasks were completed on time and how many accounts recovered to healthy. Adjust one or two weights at a time, and record each change with its date so you can compare quarters fairly.
What this means for you: put the quarterly back-test in the calendar on launch day. Without it, the starting weights tend to stay in place long after your account outcomes have shown they need to change.
The Bottom Line
A useful customer health score in HubSpot is simple enough to explain to an account owner and specific enough to trigger an action. Five or six reliably captured signals, weights drawn from your own churn and growth history, and three bands with named owners give customer success a short list of accounts to open first, and the quarterly back-test shows when a weight needs to change.
The Markivis Approach
The weights come from history, so the customer success team starts by reviewing last year's churned and expanded accounts and what each showed before the outcome. From that review we agree signals, weights and band actions, then build the properties, workflows and bands and run the known-account test before launch. The score is built alongside the CRM setup it depends on, within our HubSpot services.
The Slimstock case study records recurring revenue of $6.77M. The figure comes from a wider engagement spanning HubSpot, CRM, lifecycle and demand generation work, and we would not attribute any part of it to a health score.
