A churned customer is usually discovered at the renewal meeting. The CSM opens the account and finds that usage dropped in March, that the champion left in May, and that the last support ticket closed without a reply. None of it was a surprise. It was just that nobody had been looking until the meeting was in the diary.
The signals existed the whole time. They were in the product, in the ticketing queue, and in the email thread. What was missing was a place where they added up, and a rule that said what happens when they do.
That place should be the CRM. What follows is how we build it in HubSpot: the properties, the pipeline, and the workflows.
Why renewals fail quietly
New business gets a pipeline, stages, a forecast and a weekly meeting. Renewals get a spreadsheet and a calendar reminder ninety days out. That is an odd way to treat the revenue you already hold the most data on.
The reason is structural. A sale has a natural sequence of buyer actions to track, and a renewal has none, because a customer on the way to churning isn't doing anything. They are doing less, and less doesn't create a record in the CRM unless you decide that it should.
So the first decision is to treat the renewal as a deal with its own pipeline, and the customer's behaviour between renewals as the stages of that deal. Once you've made that decision, everything else is configuration.
How do you build a customer health score in HubSpot?
A customer health score is one property on the company record that says whether an account is likely to renew. It is only as good as what feeds it, and the temptation is to feed it everything. Don't. Four or five inputs with a clear source each will beat fifteen you can't explain to a CSM.
The inputs that hold up across the SaaS portals we work in:
Product usage — logins, active seats, or one core action, whichever your product's value depends on. This is the leading indicator, and it has to come from the product itself, through an integration or a nightly sync. If usage isn't in HubSpot, the score is guessing.
Support load and sentiment — open tickets, time to resolution, and whether the last ticket ended with a reply or with silence. Service Hub already holds this; it needs rolling up to the company record.
Champion status — is the person who bought still there, and still replying? A contact whose emails bounce, or whose job title changed, is a churn signal that no usage metric will show you.
Commercial engagement — did they open the last QBR invite or the last invoice? Low engagement alongside healthy usage is a different problem from low usage, and the score should tell them apart.
Time to renewal — the multiplier on everything above. A yellow account at eleven months out is a note; at sixty days out it is a task.
Weight them so usage and champion status dominate, and calculate the score with a workflow or a calculated property. Store the previous score as well, because the change matters more than the level. An account that fell from 85 to 60 in a month needs a call. An account that has sat at 60 for a year is just a 60.
What does a renewal pipeline look like?
Create a second deal pipeline and name it for what it is. Define the stages by what has to be true at each point — the same rule that keeps new-business deals moving — and it matters more here, because renewal stages are the easiest in the business to skip.
A structure that works for annual B2B contracts:
Renewal created (day 0) — a workflow creates the renewal deal when the previous deal closes won, carrying the amount, the renewal date and the owner across. Nothing is typed.
Health reviewed (−120 days) — the CSM has looked at the health score and its trend and written one sentence on the deal: what the risk is, and what we are doing about it. Exit criterion: the sentence exists.
Value confirmed (−90 days) — the customer has agreed, in a meeting or in writing, on the value they got this year, which is a different question from how much they used. This is the stage most teams skip, and the one that decides the price conversation.
Terms proposed (−60 days) — the renewal quote is out, with any expansion in it.
Commercially agreed (−30 days) — a named person on the customer side has said yes. Procurement and legal still to run.
Closed won / Closed lost — with a reason on the loss. Always.
The dates are relative to the renewal date, which means every deal in the pipeline can be measured against where it should be by now. A renewal at forty days out still sitting in "Health reviewed" is stuck, and the stuck-deals workflow catches it.
Which workflows catch churn early?
Three automations carry most of the weight.
The first watches the score. When health falls below a threshold, or drops by more than a set amount in thirty days, set a "needs attention" property on the company and open a task for the account owner phrased as a question: what changed, and who do we need to talk to? Don't email the manager on the first trigger, because a manager who gets every alert stops reading them.
The second watches the champion. When the primary contact's company changes, their email bounces or their job title updates, flag the account whatever the score currently says, and open a task to find out who owns the relationship now. This is the one signal that shouldn't wait for the score to catch up.
The third watches the calendar. When a renewal deal is past the date its current stage should have closed, notify the owner. A week later, if it still hasn't moved, notify the manager. Once. The escalation exists to surface the deal, and nothing more.
One boundary worth writing down: no workflow should move a renewal between stages, and none should close a renewal as lost on the renewal date. A renewal that lapsed in the system without a human deciding it lapsed is a data-quality problem you will be cleaning up at the next board meeting.
The report that makes it a management tool
Two views, both built on the renewal pipeline.
Renewals at risk, by quarter — open renewal deals grouped by renewal quarter, coloured by health score, with the ARR total per band. This is the retention forecast, and it belongs in the same meeting as the new-business forecast.
Health trend by owner — the average health score of each CSM's book, this month against last. It exists to spot a book that is sliding before its renewals come due.
If the renewal forecast and the new-business forecast don't sit on the same dashboard, retention will keep being the thing discussed after the pipeline review runs out of time.
Frequently asked questions
How do you build a customer health score in HubSpot?
Create a number property on the company record and calculate it with a workflow from four or five inputs: product usage synced from the product, support load from Service Hub, champion status from the contact record, and commercial engagement. Store the previous score as well, so workflows can trigger on the change rather than the level.
Can HubSpot Service Hub track renewals?
Yes, with a dedicated renewal pipeline. Create the renewal deal automatically when the original deal closes, define each stage by what must be true at that point before the renewal date, and let the health score and the stage dates drive the alerts.
What churn signals matter most for B2B SaaS?
Product usage and champion status. A drop in usage is the earliest signal; a champion leaving is the most decisive one, and usage won't show it. Support sentiment and commercial engagement add resolution but rarely change the answer on their own.
Should you automate renewal reminders?
Automate the deal creation and the alerts. Leave the stage moves and the close to a person. A renewal should move because a CSM confirmed something with the customer, not because a date passed.
Who sets this up?
IV-Lead builds customer success and renewal processes in HubSpot for B2B SaaS companies in Israel and abroad, as a HubSpot Gold Solutions Partner — the product-usage integration, the health score, the renewal pipeline and the workflows, in English and Hebrew.
Book a 30-minute portal audit and we will look at your renewal data as it stands today.