Section C · DS inside a neocloud

Churn & Retention

Predicting churn in GPU-rental customers, intervening before it happens, and winning back churned accounts. Distinct dynamics for self-serve vs enterprise customers; DS investment matters at both ends.

The shape of churn

Churn at a neocloud takes several forms:

  • Self-serve drop-off. A user signs up, uses some compute, stops. Like SaaS freemium churn.
  • Account graduation. A small customer grows large and migrates to a bigger neocloud or hyperscaler that can handle their scale.
  • Enterprise non-renewal. A reserved-capacity customer doesn't renew at term end.
  • Workload migration. Customer keeps the account but moves spend to a competitor.
  • Vertical exit. Customer's AI initiative pauses or ends entirely.

Each requires different DS treatment.

Churn signals

Predictive signals for impending churn:

  • Usage trend down (week-over-week, month-over-month).
  • Decrease in unique jobs launched.
  • Reliability incidents (any pattern of customer-affecting failures).
  • Support ticket volume changes.
  • Reservation renewal approaching with no progress signals.
  • Payment payment-method changes or billing issues.
  • Login frequency decline.
  • Competitor sign-up signals (where observable).

The DE-side telemetry (covered in DE guide) provides most of these signals; DS transforms them into prediction.

Prediction

Standard churn-prediction approaches apply:

  • Tree-based models (XGBoost, LightGBM) on feature engineering of the above signals.
  • Logistic regression for interpretable baselines.
  • Survival analysis for "when will they churn" rather than "will they churn."
  • Sequence models if you have enough sequential behavior data.

For enterprise churn, the data is sparser — fewer customers, less history. Bayesian methods or expert-elicited priors complement the model.

Intervention

Predictions are useful only if they trigger action:

  • Account manager outreach. For enterprise, an AE call to high-risk accounts.
  • Targeted discounts or credits. Retention promotions to at-risk self-serve accounts.
  • Product improvements. Address common churn causes systemically.
  • Customer success interventions. Onboarding assists for accounts not getting value.

DS measures intervention effectiveness with hold-out groups when feasible.

Reactivation

Churned customers are still addressable. Reactivation programs:

  • Win-back campaigns with special offers.
  • Product changes that address their original reason for leaving.
  • Relationship reset by sales (for enterprise).

DS analyzes which reactivation programs work; the answer informs ongoing investment.

Enterprise-specific dynamics

Enterprise churn is qualitatively different:

  • Lead time is long. Decisions to switch take months.
  • Stakeholders multiply. Multiple buyer-side personas with different concerns.
  • Competitive forces. Direct competitor displacement requires understanding their offer.
  • Renewal as the moment of truth. Multi-year contracts come due; the renewal decision is consequential.

DS work for enterprise churn emphasizes account-level deep-dives, not population-level models. Each churn risk is its own narrative.

Takeaway

Churn analysis is fundamental SaaS-DS work applied with the specific dynamics of GPU rental. The next chapter examines capacity forecasting — the analytical work that drives some of the largest financial decisions in the company.