The churn math that doesn’t lie
A 4% monthly churn rate means you’re losing 40% of your customer base every year. To grow from $100k MRR to $150k MRR at 4% monthly churn, you need to acquire $52,000 in new MRR — not $50,000 — just to absorb the hole. That’s $2,000 in extra acquisition spend every single month just to stay on plan.
Drop that churn rate to 2% and the required new MRR acquisition falls to $26,000. You’ve just freed up $26,000/month in acquisition budget — or equivalently, nearly doubled your growth rate with the same acquisition spend.
Churn recovery isn’t a nice-to-have. It directly determines how capital-efficient your growth is.
Who this is for
- SaaS founders at $20k–$300k MRR where monthly churn sits above 3% and every recovery attempt is still manual (a Slack message, a personal email, a CS rep chasing cancellation tickets).
- VP of Customer Success who has a team but no systematic cancellation intercept — the team finds out about churns when they’re already done.
- Revenue Operations leads who know the dunning recovery rate is terrible but haven’t had the bandwidth to rebuild it.
- GHL agencies who want to deliver a churn defense system to SaaS clients without building the workflows from scratch on every engagement.
The two churn types and why one is much easier to recover
Voluntary churn: the customer decided to leave
Voluntary churn is deliberate. The user weighed the options and chose to cancel. The intervention window is narrow — it starts the moment they click the cancel button and closes roughly 10 minutes later. Most SaaS products let that window pass with a single confirmation dialog.
The snapshot replaces the passive cancel flow with a structured intercept:
Step 1 — Exit survey fires immediately. Three questions in 60 seconds: reason for canceling, follow-up qualifying question based on reason, optional call offer. GHL receives the answers and branches automatically.
Step 2 — Save offer is delivered based on exit reason:
- “Too expensive” → 30-day pause offer (billing paused, not canceled), downgrade to a lower tier, or a time-limited discount. The pause offer is particularly effective — it buys time without a permanent price reduction.
- “Not getting enough value” → 1:1 success call booking with a “we’ll set everything up for you in 30 minutes” framing, or a guided activation sequence if they haven’t fully activated.
- “Missing a feature” → roadmap preview with ETA, or a workaround walkthrough.
- “Switching to a competitor” → a specific side-by-side comparison of the feature they’re leaving for, plus a reason to stay that’s specific to their usage.
- “No longer need it” → pause offer plus a “reactivate when you do” future sequence.
Step 3 — If the save offer fails, the contact is tagged “churned — save attempted” and enters the win-back sequence. The exit reason data is permanently attached to the contact record.
Involuntary churn: the payment failed
Involuntary churn (dunning failures) typically represents 20–40% of total MRR churn for SaaS companies. Unlike voluntary churn, the customer didn’t choose to leave — their card expired, they hit a spending limit, or the bank flagged an international charge. These are among the most recoverable churns because the intent to continue is still there.
The snapshot’s dunning sequence:
| Day | Channel | Message strategy |
|---|---|---|
| 0 | Email + SMS | Failed payment notification. Direct link to billing update portal. No judgment — “quick billing hiccup.” |
| 3 | Reminder. “Your account is still active — but access pauses in 4 days if billing isn’t updated.” Deadline creates urgency without panic. | |
| 7 | Email + SMS | Final warning before access restriction. “One step to stay active.” Frictionless billing update link. |
| 10 | Account paused notice. “Here’s exactly what you lose access to and how to restore it in 30 seconds.” | |
| 14 | Last recovery attempt. “Account closes in 48 hours — your data will be deleted unless you update billing.” Final urgency. |
SMS touches on days 0 and 7 are the highest-performing channels — they reach customers who aren’t monitoring email. GHL’s native SMS handles this without a separate Twilio account.
Health score monitoring: catching churn before it becomes intent
The snapshot’s behavioral health score runs alongside the reactive flows. Every 24 hours, GHL recalculates a health score for each active customer based on product usage signals you feed in via webhook:
| Signal | Direction | Default weight |
|---|---|---|
| Login in last 7 days | ↑ | +15 |
| Core feature used | ↑ | +20 |
| Active seats / team members | ↑ | +10 |
| Support ticket opened | ↓ | -10 |
| No login in 14 days | ↓ | -25 |
| Feature usage drop (>50% WoW) | ↓ | -20 |
| Pricing page visited | mixed | +10 (recent signup) / -15 (existing customer) |
When a health score drops below your at-risk threshold (default: 35), the snapshot fires:
- CS alert — a high-priority task in GHL with the account’s health score, the signals that triggered the drop, and the customer’s full interaction history.
- Proactive outreach sequence — a personal email from the account owner: “I noticed your team’s activity has changed — I wanted to check in and make sure [product] is still working for you.”
The intervention at health score 35 is a completely different conversation than the intervention at cancellation. The customer hasn’t made a decision yet. The retention rate on proactive CS outreach at the at-risk stage is 3–5× higher than on voluntary cancellation intervention.
Win-back sequences: the long-tail recovery
Not every churn can be saved in real time. For customers who have already canceled, the snapshot ships two win-back tracks:
Track A — 30-day win-back (0–30 days post-churn):
- Day 1: “We’d genuinely love to know what we missed.” Short survey, 2 questions.
- Day 8: Product update — what’s new since they left. One feature directly relevant to their stated exit reason.
- Day 16: Return offer — 30% off first month back, framed as “we’ve made changes, try the improved version.”
- Day 25: Case study from a similar customer who stayed and the outcome they achieved.
Track B — Long-term win-back (31–180 days post-churn):
- Triggered by major product releases that address common exit reasons.
- Segmented by exit reason data from the cancellation survey — a “missing feature” churner gets a “that feature is now live” message; a “too expensive” churner gets a new pricing tier announcement.
- 2-touch sequence with a re-engagement offer specific to the cohort.
Workflows included in the snapshot
- Cancellation intercept + exit survey — fires at cancellation initiation, routes by exit reason.
- Save flow: pause offer — 30-day billing pause + reactivation sequence.
- Save flow: success call booking — calendar embed + CS rep task creation.
- Save flow: downgrade path — routes to lower tier with prorated credit math.
- Failed payment dunning — 5-touch, 14-day sequence, email + SMS.
- Account pause notification — fires when access is restricted at day 10.
- Health score calculation — daily recalculation from product event webhooks.
- At-risk CS alert + proactive outreach — fires when health score drops below threshold.
- Win-back Track A — 4-touch, 25-day sequence for 0–30 day churns.
- Win-back Track B — 2-touch segmented sequence for 31–180 day churns.
- Churn reason tagging and reporting pipeline — visual pipeline of churned, save-attempted, saved, and recovered.
The outcome metrics this moves
- Net MRR churn — every save and every dunning recovery reduces net churn directly.
- Involuntary churn recovery rate — structured dunning moves this from ~15% to 45–65%.
- Voluntary churn save rate — cancel-flow intercept saves 15–30% of users who engage with the save offer.
- GRR (Gross Revenue Retention) — the floor metric. Every recovered account raises GRR, which is what investors look at when evaluating your business at a price multiple.