How Do You Build a Churn Risk Flag in HubSpot?

How do you flag churn risk in HubSpot without a customer success platform?

Create a custom company property for churn risk, feed it two or three signals you already track, and use a workflow to set the flag and alert the account owner. You do not need a dedicated customer success tool to start. A simple, visible flag that someone acts on beats a complex health score nobody reads.

This tutorial is for one specific reader. You run a B2B software company or lead customer success at one, your customer records live in HubSpot, and you do not have a dedicated platform like Gainsight or ChurnZero. You want an early warning when an account starts to drift, so someone can step in before the renewal conversation.

I build CRM automations like this for B2B teams. The version below is deliberately simple. It is meant to be live within a day and improved over time, not perfect on launch.

What do you need before you start?

You need HubSpot with access to company properties and workflows, plus at least a couple of signals on your company records. HubSpot's knowledge base says workflows are available on Professional and Enterprise subscriptions, so confirm your plan first. You also need a named owner for each customer account, or the alerts will have nowhere useful to go.

Signals can come from many places. Product usage might arrive through an integration or a sync from your data warehouse. Support tickets may already live in HubSpot. Renewal dates are often a company or deal property. Start with whatever is reliably on the record today.

If you do not track renewal dates yet, set that up first. My tutorial on building a renewal date reminder in HubSpot covers it, and this flag builds on the same property.

Which signals should drive the churn risk flag?

Pick two or three signals that you trust and that change before customers leave. Good starting points are a drop in product usage, a spike in support tickets, a renewal date coming up soon, and the main champion leaving the company. Choose signals you can measure reliably on the company record, not the ones that sound most sophisticated.

Usage is usually the strongest signal if you have it. A sync that writes something like last active date or weekly active users to the company record gives you a clear trigger. If usage data is not available yet, support volume and champion changes are still useful.

Champion loss is underrated. When the person who bought your product leaves, the account is at risk even if usage looks fine. You can catch job changes with enrichment tools, as I showed in finding job change signals in Clay, and write the result back to HubSpot.

How do you create the churn risk property?

In HubSpot settings, open Properties, select company properties, and create a new property. Name it something clear like Churn risk, and make it a dropdown select with options such as Low, Medium, and High. HubSpot's knowledge base says creating a basic property is available on all plans, though the number of custom properties depends on your subscription.

Add a second property called Churn risk reason, as a single-line text or dropdown field. The flag tells the owner that something is wrong. The reason tells them what. Without it, every alert starts with detective work.

Add a third property for the date the flag was last set. This lets you report on how long accounts stay flagged and stops the workflow from re-alerting the owner every time it runs.

How do you build the workflow that sets the flag?

Create a company-based workflow. Set enrollment triggers for each risk signal, such as last active date older than your chosen threshold, open ticket count above a limit, or a champion change flag. Use branches to set Churn risk to Medium or High, write the matching reason, and stamp the flag date.

Keep the logic readable. One branch per signal, with a clear name, is easier to maintain than a single tangle of conditions. When someone asks why an account was flagged, you want to answer by looking at the workflow, not by reverse-engineering it.

Turn on re-enrollment carefully. Accounts should be able to re-enter if a new signal appears, but not every day for the same signal. The flag date property helps you control that with a simple check before the workflow sets anything.

How should the account owner be alerted?

When the flag changes to High, create a task for the company owner and send them a short internal notification or Slack message. Include the company name, the risk reason, the renewal date, and a link to the record. The owner should know in seconds what happened and what to look at first.

Use tasks rather than only notifications. A notification gets read and forgotten. A task sits in the owner's queue with a due date until someone acts. For High risk accounts, that difference matters.

For Medium risk, a weekly digest is often enough. Sending an urgent alert for every small change trains people to ignore the alerts, which defeats the purpose.

How do you clear the flag when risk goes away?

Build a second, small workflow that resets Churn risk to Low when the triggering signal recovers, such as usage returning above the threshold or tickets dropping back to normal. Write a reason like Recovered and update the flag date. Without a reset path, flags pile up and the list of at-risk accounts stops meaning anything.

Some flags should only be cleared by a person. A champion leaving is not fixed by a change in usage. For those, ask the owner to clear the flag manually after they have built a relationship with the new contact.

Review the rules after a month. If most flagged accounts renew without trouble, the thresholds are too sensitive. If accounts churn without ever being flagged, you are missing a signal.

How do you report on churn risk?

Create a saved view or list of companies where Churn risk is High, sorted by renewal date. Add a simple report showing flagged accounts by owner and by reason. Review it in a short weekly meeting. The report turns individual alerts into a pattern you can act on as a team.

The reason breakdown is the most useful part. If most risk comes from support volume, you may have a product or onboarding issue. If most comes from champion loss, you may need more contacts per account. Each pattern points to a different fix.

Connect the flag to retention work too. Accounts with low usage are often missing value they could get. I wrote about the content side of that in retention content that reduces B2B churn.

How do you test the setup?

Pick a test company record and change each signal one at a time. Confirm the flag, reason, and date update correctly, and that the owner receives the right task or alert. Then reverse each signal and confirm the reset workflow clears the flag. Finally, check that the same signal does not alert twice in a row.

Use a real but internal test account if you can, so you are not creating fake companies that pollute reports. Label it clearly and exclude it from customer reporting.

Write down the thresholds and the reasons you chose them. When someone asks in six months why the usage threshold is what it is, you will have an answer.

What should you do next?

Pick two signals you already trust, create the Churn risk, reason, and flag date properties, and build one workflow to set the flag and one to clear it. Route High risk to the owner as a task. Run the tests, then review flagged accounts weekly for a month and adjust the thresholds based on what actually happens at renewal.

A simple flag that the team trusts is the foundation for everything else in retention. You can add more signals and a proper health score later, once the habit of acting on risk is in place.

If you want help building churn signals and alerts in HubSpot, or syncing product usage into your CRM, reach out. This is the kind of revenue system I build for B2B teams.