B2B SaaS churn prediction:
how to build the model.
A churn prediction model turns the signals already in your data into a ranked risk score. Learn how to predict customer churn, which metrics drive the model, and how to act before the cancellation email arrives.
Churn prediction is early warning, not late notice.
Most SaaS teams find out a customer is leaving when the cancellation email arrives. By then, the decision has usually been made weeks or months earlier inside the customer's organisation.
Churn prediction can be done with machine learning. It reads the same signals a great customer success manager would notice, but across every account, every week. It ranks accounts by risk score so your team can intervene before churn is decided.
The goal is not a perfect crystal ball. It's a prioritised list that tells CS and sales where to spend their time this week to protect and grow revenue.
How churn prediction works
A five-step loop that turns historical data into a live risk score.
Collect historical signals
Pull together every signal that preceded past churn: product usage, support tickets, billing, NPS, contract changes, and stakeholder activity.
Build account-level features
Translate raw events into features per account: trend over time, velocity of change, concentration of usage, and ratio of active to inactive users.
Train a model on past churn
Train on which accounts actually churned and which renewed. The model learns your patterns, not generic benchmarks, so it fits your business.
Score live accounts
Run the model against current accounts each week to rank them by risk. High-risk accounts surface before the cancellation email lands.
Act with the team
Turn the ranked risk list into specific plays: outreach, expansion checks, health calls, or renewal prep. Insights only matter when they drive action.
The churn metrics that drive the prediction
No single metric predicts churn. You should combine these signals into a single risk score.
Engagement decline
Logins, sessions, or core feature usage dropping over 30–90 days. A slowing account is often the first sign of disengagement.
Support ticket velocity
Sudden spikes or unresolved issues in support. Friction compounds quickly and can push otherwise healthy accounts toward churn.
Contract / seat utilization
Seats, licenses, or usage volumes sitting far below the contracted limit. Low utilization means low switching cost at renewal.
Payment behaviour
Late payments, failed charges, or invoice disputes. Payment friction is one of the strongest short-term churn predictors.
Champion / stakeholder change
Your main contact leaves, stops logging in, or gets replaced. Losing the internal champion is a leading cause of churn.
Product usage trend
Breadth and depth of usage shrinking. Accounts that stop exploring new features or drop back to a single use case are at risk.
NPS movement
Falling satisfaction scores or survey feedback. Negative sentiment rarely appears alone; it usually precedes usage and payment signals.
Common mistakes to avoid
Waiting for the cancellation email
By the time a customer says they are leaving, the decision is already made. Churn prediction is about finding the earlier signals.
Only looking at product usage
Usage is important, but billing, support, and relationship changes often tell the fuller story. The best models combine all three.
Using generic benchmarks
Every SaaS has different buying cycles, user behaviour, and contract structures. A model trained on someone else's data will miss yours.
Scoring accounts without a follow-up plan
A risk score is useless if no one acts on it. Prediction must be paired with clear ownership, playbooks, and deadlines.
Go deeper on churn
Want a churn model trained on your data?
Senpai builds models on your historical churn and expansion patterns. Not generic benchmarks and delivers account-level insights with weekly guidance from our team.