Guide 06
Churn Risk Scoring Without a Data Team
A practical, rules-based approach to scoring churn risk using product usage and billing signals — no data science team or predictive model required.
Quick answer
You don't need a machine learning model to build a useful churn risk score. A weighted rules-based score built from 4-6 observable signals — usage frequency trend, feature-gate hits, support ticket sentiment, and billing events — catches the majority of at-risk accounts a full predictive model would, at a fraction of the setup cost.
The signals that matter most
Usage frequency trend: is this account's weekly active usage trending down over the last 4-6 weeks relative to its own baseline? This single signal, tracked consistently, catches more true churn risk than any other individual metric.
Seat or license utilization: for seat-based pricing, declining active-seat percentage relative to purchased seats is a leading indicator that often precedes formal cancellation by 60-90 days.
Support signals: a spike in support tickets, or a support ticket explicitly mentioning cancellation, competitors, or budget — these are lagging but high-confidence signals worth weighting heavily even from a small sample.
Billing events: failed payments, downgrade requests, or a seat reduction are near-certain churn signals and should trigger the highest-urgency intervention tier immediately, not wait for a weekly scoring cycle.
Building the score without machine learning
Assign each signal a weight based on how strongly it correlates with historical churn in your own customer base — this requires looking back at accounts that already churned and checking which signals were present beforehand, not guessing at weights.
Combine into three tiers (low, medium, high risk) rather than a continuous score — tiers are easier to attach specific interventions to, and most teams don't have enough data volume to meaningfully act on finer-grained scores anyway.
Re-score weekly, not monthly. Churn risk compounds quickly in usage-based products, and a monthly cadence means intervention often happens after the cancellation decision has effectively already been made.
Frequently Asked Questions
Do I need a machine learning model to score churn risk?
No. A weighted, rules-based score built from 4-6 observable signals — usage trend, seat utilization, support tickets, and billing events — catches most of the same at-risk accounts a predictive model would, without the setup cost of a data science team.
How often should churn risk scores be updated?
Weekly. Churn risk compounds fast in usage-based products; a monthly cadence means intervention often happens after the decision to leave has already been made.