For most B2B companies, the unit economics of growth hinge on two numbers: how much it costs to acquire a customer and how long that customer stays. If you spend $10,000 to acquire a customer who churns in 12 months, you cannot build a profitable business at scale. If that same customer stays for 3 years and expands to twice the initial contract, the math changes completely. Customer success is the function that moves the needle on both retention and expansion, which is why it is not optional for subscription businesses past their early stage.
The challenge for most teams is that customer success is operationally harder to run than sales. It requires visibility into the health of dozens or hundreds of accounts simultaneously, systematic touchpoints that happen even when no one has raised their hand, and the ability to distinguish accounts that are healthy but quiet from accounts that are at risk but not saying so yet. HubSpot is where you build and run that system.
Setting Up Your Customer Health Framework in HubSpot
Company-Level Properties for CS
Customer success operates at the company level, not the contact level. The company record in HubSpot is where you track the health of the relationship. Add these custom properties to your company object:
- Health Score: a numeric 1 to 100 rating updated by workflow or manually by the CSM
- Health Status: dropdown with Red / Yellow / Green (set by workflow based on Health Score)
- Renewal Date: date field for the contract anniversary or renewal deadline
- ARR: annual recurring revenue, used to prioritize CSM time and define at-risk revenue exposure
- Customer Tier: Standard / Growth / Strategic, used to determine touch frequency and coverage model
- Last CSM Touch: date field updated every time the CSM logs an activity
- NPS Score: pulled from HubSpot survey responses
Customer Health Score Logic
A health score combines 3 to 5 signals into a single rating that drives workflow automation. The specific signals vary by business model, but a common B2B SaaS structure weights them roughly as follows:
| Signal | Weight | Red trigger |
|---|---|---|
| Product usage frequency | 35% | No login in 14+ days |
| NPS score | 25% | Score of 6 or below (Detractor) |
| Open ticket volume | 20% | 3+ unresolved tickets |
| Engagement with CS | 20% | No CSM touch in 45+ days |
When the composite score drops below a threshold (commonly 60), a workflow sets the Health Status to Red and creates a task for the CSM with the context for the intervention. This is the system that allows one CSM to manage 50 to 100 accounts without anything falling through the cracks. The workflow does the monitoring. The CSM does the relationship work.
The CS Playbook in HubSpot
Onboarding: The First 90 Days
The majority of churn is decided in the first 90 days. If a customer does not achieve a clear win from your product within the first 30 to 60 days, their likelihood of renewal drops significantly. The onboarding workflow in HubSpot should trigger when a deal closes and the lifecycle stage is set to Customer, and should include structured touchpoints at Day 1 (kickoff call), Day 14 (progress check), Day 30 (first milestone review), Day 60 (usage review), and Day 90 (QBR or success review).
Each touchpoint should be a task assigned to the CSM with a template for the conversation, not a generic calendar reminder. The goal is to make every CSM conversation productive and documented in HubSpot so the team can learn what onboarding conversations drive the best long-term outcomes.
Customer Success
Want to build a CS motion in HubSpot that reduces churn and turns renewals into expansions?
We build customer health frameworks, onboarding workflows, renewal pipelines, and CS dashboards in HubSpot. Book a call to start.
Book a Free CallRenewal Pipeline
Create a separate pipeline in HubSpot for renewals. Each customer should have a deal in the renewal pipeline that is created automatically 90 days before their renewal date, assigned to their CSM, and valued at the ARR at stake. The renewal pipeline stages mirror the risk conversation: At Risk, Nurturing, Expansion Discussion, Renewal Confirmed.
This makes churn risk visible in HubSpot alongside new business pipeline. Revenue leadership can see in one view how much ARR is at risk, which CSM owns it, and what stage each renewal conversation is at. That visibility is not possible if renewal tracking lives in a spreadsheet separate from HubSpot.
Expansion Triggers
Expansion revenue (upsells, cross-sells, seat additions) often comes from the same customers who are most engaged with the product. Set up workflows in HubSpot that flag expansion opportunities: contacts who have logged in more than 20 times in the past 30 days, companies with a Health Score above 80 and more than 6 months as a customer, or accounts that have submitted feature requests for capabilities in your next tier. When these signals fire, create a task for the CSM to have an expansion conversation, and open an Expansion deal in the pipeline. Treated systematically, expansion triggers are a significant source of low-cost incremental revenue.