A readout to a client's leadership team
Case study

MasterControl flags customer churn 90 days early with 85% accuracy

Customer success learned an account was at risk too late to save it, with renewals worth $100K or more a year at stake.

MasterControl

MasterControl · Sponsor · Sixth Street · Client onboarding and service · L2

85%accuracy predicting churn 90 days ahead

The workflow before

MasterControl's customer success team judged account health with simple rules of thumb. Product usage, support tickets, contract and payment history, and training data sat in separate systems, so building a view of any one account was manual work. Warning signs were usually spotted close to renewal, when there was little time left to act.

What we built

Over 12 weeks we built a churn prediction model on AWS SageMaker trained on 3 years of customer history. It combines product usage trends, support ticket patterns, contract and payment history, firmographics and training completion into one score per account, predicting churn within a 90-day window.

The model runs behind a SageMaker endpoint and feeds a dashboard for the customer success team, with SHAP explanations showing why each account is flagged. We paired it with intervention playbooks matched to the main risk drivers: falling engagement, rising ticket volume, low adoption of advanced features, contract reductions and declining training completion.

Before and after

MeasureBeforeAfter
At-risk account identificationRules of thumb, near renewalModel score, 90 days ahead
Churn rate in flagged accountsNo rankingTop 20% flagged churn at 3x the base rate
Account health reviewManual pulls from 5 systemsOne scored dashboard with reasons

What's next

Next is pushing scores and alerts into Salesforce so account managers act inside their daily workflow, and retraining on intervention outcomes. Protecting even a few points of churn on $200M of recurring revenue is worth about $2M a year.

ShareLinkedInEmail

Data from product telemetry, support, finance, CRM and training systems lands in Amazon S3, cataloged by AWS Glue, with customer records joined from Amazon RDS. Features include 30, 60 and 90-day rolling usage trends, composite engagement scores, ticket severity and resolution patterns, payment timeliness and module adoption depth.

The model is gradient boosted trees (XGBoost) trained in SageMaker with time-series cross-validation to prevent leakage. Holdout results: 85% accuracy, 78% precision, 82% recall, AUC 0.89. Predictions are served from a SageMaker endpoint, explained with SHAP values, and visualized in Amazon QuickSight; SageMaker Model Monitor tracks drift.

Next step

Let's build the case study we tell next.