# Predicting and preventing churn: usage signals to intervention playbooks
Ninety days before an enterprise account cancels, the software usually tells you first. Logins drop from daily to twice a week. The power user who ran every report goes quiet. Support tickets shift in tone from "how do I" to "why doesn't this work." By the time the renewal email bounces around procurement, the decision was made months ago in the telemetry.
Let's trace one of these accounts, then build the system that catches it earlier.
Meet "Northwind Logistics," a composite enterprise account (not a real company) on a $180,000 annual contract for a workflow SaaS product. Here is what the data showed over its final two quarters.
Month 1 to 2 (healthy): 45 weekly active users out of 60 licenses. The champion, a VPVPA clear statement of the benefits your product delivers, the problems it solves and why customers should choose you over alternatives.Voir la définition complète → of operations, logs in daily. Three integrations are live. Feature adoption is broad.
Month 3 (first cracks):
Month 4 to 5 (drift): A reorg moves the champion to a new role. Nobody inherits ownership. Active users fall to 22. Support tickets spike, then go silent (a bad sign: silence often means people stopped trying).
Month 6 (terminal): 11 active users. The renewal conversation opens cold. Procurement asks for a discount, which is often a polite exit.
Every one of those shifts was visible in data. The failure was not detection capability. It was that no one had turned the signals into a health score (a single composite metric summarizing account risk) and routed it to a human in time.
Not all telemetry matters equally. The strongest leading indicators tend to fall into four buckets.
Enterprise deals live and die on individuals. Track your key contacts explicitly. A champion who stops logging in is a five-alarm event, even if aggregate usage looks fine.
Did the customer achieve the outcome they bought? If they purchased your tool to cut report time and they never ran a report, adoption numbers are hollow.
Sync errors, failed APIAPIApplication Programming Interface: a standardised interface that lets applications communicate and exchange data without knowing each other's internal workings.Voir la définition complète → calls, rising support ticket volume, then sudden silence. Silence after friction is worse than complaints.
A useful mental model: leading indicators (usage patterns that predict future churn) beat lagging indicators (the cancellation itself, NPSNPSNet Promoter Score (NPS) measures customer loyalty by asking how likely customers are to recommend a brand, then subtracting detractors from promoters.Voir la définition complète → after the fact). You want to act on the former.
Start simple. A weighted composite beats a black box you cannot explain to a customer success manager (CSM).
# Simple, explainable account health score (0-100)
def health_score(account):
active_ratio = account.weekly_active / account.licenses # 0 to 1
feature_depth = min(account.features_used / 5, 1.0) # cap at 5
champion_active = 1.0 if account.champion_logins_7d > 0 else 0.0
error_rate = min(account.sync_errors_7d / 10, 1.0) # penalty
score = (
0.35 * active_ratio +
0.25 * feature_depth +
0.25 * champion_active +
0.15 * (1 - error_rate)
)
return round(score * 100)Weights are a starting hypothesis, not gospel. The point is transparency: when a CSM asks "why is Northwind red," you can say "champion inactive and active ratio at 37 percent," not "the model said so."
Once you have historical churn data, you can validate and reweight with a logistic regression or gradient-boosted model. But keep a human-readable layer on top. Salesforce's own research on customer success emphasizes that adoption and outcome data must be actionable by frontline teams, not just data scientists. See the general principles in the Salesforce customer success resources.
A score of 60 that fell from 90 is more dangerous than a stable 55. Model the slope, not just the level. Northwind was arguably "fine" at month 3 on absolute numbers. The velocity of decline was the tell.
🎬 [VIDEO: "How to Reduce Churn with Customer Health Scores" — youtube.com — a practical walkthrough of building and operationalizing SaaS health scoring]
Usage telemetry is customer data. In 2026, that means real obligations, not just optics.
Define product telemetry vs. personal data. Aggregate usage counts are lower risk. Individual login tracking of named users (your champion analysis) is personal data under regulations like the EU General Data Protection Regulation (GDPR) and similar frameworks. Personal data means information relating to an identifiable person.
Practical guardrails:
The EU's official GDPR overview is a solid free primer for non-lawyers. When in doubt, involve your privacy or legal team. This lesson is not legal advice.
A health score nobody acts on is a vanity dashboard. The value is in the closed loop: signal, trigger, action, outcome, feedback.
Tie score bands and specific signals to defined plays.
| Signal | Play |
|---|---|
| Champion inactive 14 days | CSM emails champion, offers a 20-minute check-in |
| Active ratio drops below 40 percent | Trigger adoption campaign, offer training webinar |
| Sync errors rising | Proactive support outreach before customer complains |
| Score falls 20+ points in a month | Escalate to CSM manager, flag renewal risk in CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.Voir la définition complète → |
Weight the queue by contract value. A red $180,000 account outranks a red $12,000 account for scarce CSM time. Surface at-risk annual recurring revenue (ARR) as the headline number executives care about.
Track intervention outcomes. Did the check-in call move the score? If a play never changes trajectory, kill it. Over time you learn which interventions earn their cost.
For Northwind, the loop that should have fired: at month 3, champion inactivity plus a falling active ratio triggers a play. The CSM discovers the reorg, gets introduced to the new owner, and re-onboards the team. Cost: a few hours. Value protected: a six-figure renewal.
Vérification des acquis
1. According to the lesson, why is the sudden silence of support tickets after a spike considered a warning sign rather than an improvement?
2. The lesson argues that the Northwind account's churn represented what kind of failure?
3. Why does a customer's request for a discount during a cold renewal conversation function as a churn signal in this context?
4. What is the primary purpose of a 'health score' as defined in the lesson?
5. Select ALL correct answers. Based on the Northwind case, which events acted as meaningful early churn indicators that could have prompted intervention?
Sélectionnez toutes les réponses correctes.
6. Select ALL correct answers. What lessons about leading indicators of churn does the Northwind example illustrate?
Sélectionnez toutes les réponses correctes.
Alert fatigue. If everything is red, nothing is. Tune thresholds so CSMs get a manageable, prioritized queue, not noise.
Scoring the wrong outcome. Some accounts have low logins because the product runs automatically in the background. Context matters; a fraud-detection tool that quietly works is healthy, not churning.
Ignoring expansion signals. The same data that predicts churn predicts upsell. An account hitting usage limits is a growth signal, not a risk. Build both plays.
Data latency. A score computed monthly misses fast declines. For enterprise accounts, refresh weekly at minimum. Northwind's decline would have been caught faster on a weekly cadence.
Over-automating the human moment. Automation should surface and route. The retention conversation itself, especially at enterprise value, is human work. A well-timed call from someone who understands the customer's business beats any email sequence.