Skip to main content

> ML_RECIPE // SAAS-CUSTOMER-CHURN-PREDICTION_v1.0

SaaS Subscription Churn Prediction

Identify accounts at high risk of cancelling 60 days before contract renewal, enabling proactive CSM intervention.

binary classificationsaas ecommerceApache-2.0low-cloud
Back to All Recipes

Business Outcome

Identify accounts at high risk of cancelling 60 days before contract renewal, enabling proactive CSM intervention.

Acceptance Criteria:

Model must achieve higher Top-Decile Lift than simple heuristic rule (days since last login).

Heuristic Baseline

Heuristic rule: Flag any account where primary admin login has been inactive for > 30 days.

Baseline Evaluation:

Heuristic inactivity rule achieves PR-AUC 0.48 and Top-10% precision 0.38.

Phase 1: Prototype Path

Export 12 months of aggregated usage features from data warehouse. Train LightGBM baseline on developer laptop (CPU). Evaluate PR-AUC and Top-10% Capture Rate.

Hardware: Any standard laptop (4+ CPU cores, 8GB RAM)

Phase 2: Production Path

Automate weekly feature transformations in dbt/Feast. Package LightGBM model as versioned artifact in MLflow. Run batch CPU inference on server with Evidently drift alerts.

Hardware: General-purpose CPU server (e.g. 4 cores, 16GB RAM, no GPU required)

Compute & Placement Topologies

Training Placement

Scheduled batch pipeline on CPU server (e.g. 4 cores, 16GB RAM)

Inference Placement

Scheduled weekly batch job writing churn probabilities back to CRM

3-Plan Placement Alternatives

Plan A: Simplest Viable

Local developer laptop cron script running monthly CSV export and scoring.

Plan B: Hardware-Fitted

Multi-core CPU server running containerized batch inference on existing data warehouse cluster.

Plan C: Production-Ready

Scheduled dbt/Feast feature pipeline + MLflow artifact registry + containerized CPU batch inference with Evidently drift monitoring and Slack/CRM alerts.

Recommended Libraries & Tools

★ PRIMARY TOOLLightGBMMicrosoft
View
XGBoostDMLC (Distributed Machine Learning Community)
View
scikit-learnscikit-learn Consortium / Inria
View
CatBoostYandex / Open Source
View

Governance, Safeguards & Risks

Governance Safeguards:
  • Prohibit using protected demographic attributes as input features.
  • Enforce model explainability (TreeSHAP) so customer success managers understand why an account was flagged.
  • Maintain a shadow run for 30 days before triggering automated marketing emails.