Customer churn prediction
Classification models, such as logistic regression and gradient-boosted trees (XGBoost), that score each customer's likelihood of churning, with SHAP explanations of the main drivers.
Descriptive reporting tells you what happened. Predictive analytics uses your historical data to estimate what is likely to happen next, such as which customers are at risk of leaving or what next quarter's revenue could look like, so you can act earlier. Every model comes with an honest account of how well it performs and where it should not be relied on.
What does your history show about churn, demand or revenue, and how stable are those patterns?
Which factors are most strongly associated with the outcome, and how much does each one matter?
Which customers, products or periods need attention first, and what is the likely range of outcomes?
Classification models, such as logistic regression and gradient-boosted trees (XGBoost), that score each customer's likelihood of churning, with SHAP explanations of the main drivers.
Models for other outcomes such as conversion, repeat purchase or predicted customer lifetime value, validated on held-out data.
Time-series forecasts of revenue, orders or demand that account for seasonality and calendar effects, delivered as conservative, base and growth scenarios with uncertainty ranges.
Customer risk scores and tiers that can be fed into a CRM, so retention teams know who to contact first.
Early signals of high-value or at-risk behaviour, such as falling purchase frequency or shrinking order values, turned into rules your team can act on.
Power analysis, sample-size planning and significance testing, so changes are evaluated properly before they are rolled out.
Accuracy alone can be misleading. If only 1 in 10 customers churns, a model that predicts “no churn” for everyone is 90% accurate and of no practical use. We report metrics suited to the problem, such as ROC-AUC, precision, recall and precision-recall curves, alongside the base rate. Decision thresholds are set by weighing the cost of an intervention against the cost of missing an at-risk customer.
Scope depends on your data and question. It is agreed after the discovery call and data audit.
Portfolio projects built on demonstration datasets. They are not client engagements, and their figures describe the datasets and models, not real business results.
A portfolio A/B test evaluation comparing two email variants across the full funnel, from opens to purchases, with statistical significance testing.
Synthetic dataset: 25,000 records · 2 variants · 4 funnel metrics tested
Read the email A/B test case studyA portfolio marketing mix model that estimates each channel's contribution to revenue from two years of weekly data and tests how a fixed budget could be reallocated.
Synthetic dataset: 104 weeks · 4 paid channels · R² 0.957 (in-sample)
Read the marketing mix modelling case studyA portfolio analysis of subscription revenue health (MRR movements, retention, acquisition channels, usage and support signals) combined into a rule-based customer health score.
Synthetic dataset: 86,402 rows · 6 tables · MRR at risk quantified
Read the SaaS churn case studyIt depends on how many churn events you have, not only how many customers. A model needs enough examples of customers who did and did not churn. We check this during the data audit, and we will tell you if a simpler approach such as RFM or cohort analysis is more appropriate.
That cannot be known before seeing the data, so we do not promise a figure. Models are evaluated on data they were not trained on, and the results are reported honestly, including where the model is weak.
Yes. Scores can be delivered as a table, a scheduled file or a dashboard, ready to import into a CRM or email platform.
Share the question you are trying to answer and the data you have. We will reply with practical next steps.
Prefer email? [email protected]