Gut feel about who's at risk stops scaling somewhere around your fiftieth account. Here's how a churn prediction model replaces it — without a data science team.
Updated: 24 September 2026
Customer churn prediction is the practice of scoring every active account for cancellation risk before it cancels, by combining measurable signals — product usage, payment behaviour, support ticket volume, NPS and contract renewal date — into a single, explainable risk level per customer. Instead of finding out a customer was unhappy the day they cancel, your team sees the risk building weeks in advance and can intervene while there's still a relationship to save. Below: how the models actually work, what "explainable" means in practice, and how to get a prediction system running without hiring a data scientist.
Churn prediction doesn't tell you which customer will cancel tomorrow — it tells you which customers currently carry elevated risk, ranked so your customer success team can prioritise. That distinction matters: a good churn prediction system is a triage tool, not a crystal ball. It turns "I have a bad feeling about this account" into a specific, defensible risk score built from data your business already has — usage logs, invoices, support tickets, survey responses.
No single metric predicts churn reliably on its own. A drop in logins might mean disengagement, or it might mean the customer just finished onboarding and now uses the product efficiently. The signal comes from combining several weak predictors into one model:
Each of these on its own is a weak predictor with plenty of false positives. Combined and weighted against each other, they become a much stronger signal — which is exactly what a customer health score is built to do.
There are two broad approaches. A rule-based (weighted) model assigns a weight to each signal — usage counts for 30%, payment behaviour for 25%, and so on — and a customer's score is the weighted sum. It's simple to build, easy to explain, and easy to adjust when it's wrong. A machine-learning model trains on historical churn outcomes to find patterns a human wouldn't necessarily set as rules, and can outperform a weighted model once you have a large enough history of churned and retained accounts to train on.
In practice, most small and mid-sized teams are better served by a weighted model: it needs no training data, it's transparent to the people who have to act on it, and it can be tuned in an afternoon instead of retrained by a data scientist. Enterprise platforms often lead with machine learning because it sounds more sophisticated in a sales deck — but a black-box score your CSM team can't explain to a customer is a score they'll eventually stop trusting.
A churn prediction score only creates value if someone acts on it. If your customer success team can't see why an account scored high risk, they can't have an informed conversation with that customer, and they can't tell the difference between a genuine warning and a model quirk. An explainable model shows exactly which factors pushed a score up — falling usage plus a support escalation, say — so the team's outreach is specific instead of generic. That transparency also matters for compliance: under GDPR, a score that a human can inspect and override is treated very differently from an opaque automated decision.
Prediction without a next step is just a warning light nobody looks at. The output of a churn prediction system should be a prioritised worklist — highest risk first — with a suggested playbook attached, not a dashboard someone has to interpret from scratch. See reduce customer churn for the specific actions that follow once you've identified a risk account.
You don't need a data warehouse or a machine-learning engineer to start predicting churn. A weighted model that ships with sensible defaults can score every customer from a CSV export or a read-only database connection on day one, with the weighting adjustable through the UI rather than a config file. Lonieta runs this way as a self-hosted install on your own server — which also means the usage, payment and support data feeding the model never leaves your infrastructure. See how Lonieta handles security and data residency for the detail, and how it works for the full step-by-step from install to first risk score.
Customer churn prediction is the practice of scoring every active account for cancellation risk before it cancels, by combining signals like usage, payment behaviour, support tickets and NPS into a single explainable risk level per customer.
At minimum, product usage trends, payment or billing history, support ticket volume, and contract renewal dates. NPS or survey data adds a useful additional signal but isn't required to get started.
No. A weighted, rule-based model that combines the same signals is simpler to build, easier to explain to your team, and doesn't require a large history of churned accounts to train on — which makes it the more practical starting point for most small and mid-sized companies.
Perfect accuracy isn't the goal — useful prioritisation is. A model that correctly flags most of your genuinely at-risk accounts, with explainable reasoning your team can act on, is more valuable than a marginally more accurate black-box model nobody trusts enough to use.
Play with the live demo, or talk to us about installing Lonieta on your own server.