churn-reduction
Skill0 starsChanged 39 days agoMITView on GitHub
Diagnoses SaaS churn root causes through cohort analysis and a seven-category taxonomy, then builds segmented intervention playbooks ranked by frequency, revenue at stake, and addressability - including save-offer economics. Use when someone asks "why is our churn so high", "build a churn reduction plan", "should we offer discounts to cancelling customers", or when NRR/GRR is slipping and the team needs a diagnosis before prescriptions. Do NOT use for gym or fitness-studio member retention - use retention-and-churn-killer instead. Do NOT use for re-acquiring customers who already left - use win-back-campaign instead. Do NOT use for growing existing accounts - use expansion-revenue instead.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- SkillMedev/customer-support-copilotword for word, first seen Oct 8, 2026
- SkillMedev/saas-growth-stackword for word, first seen Oct 5, 2026
- sidchaudhary/gtm-skillstheir own version, first seen Aug 21, 2026
Other versions3 projects use a version of this.
Word for word · 2
- SkillMedev/customer-support-copilot★ 0100% same
- SkillMedev/saas-growth-stack★ 0100% same
Edited · 0
None found.
Wrote their own version · 1
- sidchaudhary/gtm-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- email-deliverabilitySkill
- email-drip-builderSkill
- email-newsletter-proSkill
- lifecycle-journey-mapSkill
- push-notification-copySkill
- segmentation-strategySkill
- win-back-campaignSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 99
Do not prescribe from blended churn - averages hide the cohort where the problem lives.
- Distinctive: line 100
Do not read NRR alone; expansion from a few accounts can mask a gross-retention leak that GRR exposes.
- Distinctive: line 101
Do not treat bad-fit churn as a CS problem - the fix is qualification, and every dollar spent "saving" a bad-fit account is wasted twice.
- Distinctive: line 102
Do not offer discounts reflexively in the cancel flow.
- Distinctive: line 103
Do not skip the involuntary-churn check - recovering failed payments is the cheapest 20-40% of the problem.
- Distinctive: line 104
Do not count a save as a save until the account clears 90 days post-intervention.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Churn Reduction
Churn is the silent killer of SaaS - 5% monthly churn caps the business no matter how fast acquisition runs, because it compounds into LTV, NRR, and valuation. The costly mistake this skill prevents is prescribing before diagnosing: launching a save-offer program or a CS hiring spree against a blended churn number, when the real leak is bad-fit acquisition or failed onboarding that no discount can fix.
Operating procedure
Diagnosis strictly precedes intervention. Steps 1-3 establish what is actually leaking; only then do playbooks get built.
Step 1: Gather inputs
- Monthly logo churn and revenue churn for the trailing 12 months. Track both - a small customer leaving and a whale leaving are different problems.
- GRR and NRR. Gross revenue retention (churn + contraction only) isolates the leak; net revenue retention (includes expansion) can hide it. An NRR of 105% with GRR of 82% is a leaky bucket propped up by a few expanding whales.
- Customer list with segment, plan, signup month, acquisition channel, ACV.
- Cancellation reasons, exit interviews, and support history where they exist. Default: sparse - plan interviews in Step 3.
- Payment-failure data (involuntary churn is often invisible in "reasons").
Label any estimated figure as an estimate.
Step 2: Cohort before concluding
Blended churn averages away the insight. Cut retention three ways minimum: by signup month (is the product getting stickier?), by segment (SMB vs mid-market behave differently), and by acquisition channel (a cheap channel with 2x churn is not cheap). Benchmarks to read against: SMB-serving SaaS commonly runs 3-7% monthly logo churn; mid-market/enterprise should be at or under 1-2% monthly (10-15% annually); GRR of 90%+ is healthy for SMB, 95%+ for enterprise. A cohort more than double its peer cohorts is where the diagnosis starts.
Step 3: Categorize every churn - the seven-category taxonomy
Interview churned customers and read cancellation reasons; the categories shift the roadmap, not just CS scripts. Assign every churned account to exactly one primary category:
- Bad fit - never the ICP. Fix: tighten qualification, not retention. Cheapest churn to eliminate (stop acquiring them).
- Poor onboarding - never reached first value. Fix: time-to-value and activation. Often the single biggest lever.
- Low adoption - bought it, never embedded it in workflow.
- Missing value - used it, did not get the outcome. Fix: product or success motion.
- Champion left - the sponsor changed jobs. Fix: multi-thread accounts.
- Price/budget - economic, often macro-driven.
- Competitor - lost head-to-head. Fix: product or positioning.
Diagnosis decision tree
Churned account
├─ Did payment fail (card decline, expiry)?
│ → INVOLUNTARY: dunning/card-update/retry fix. Check share first -
│ often 20-40% of all churn and the easiest to recover.
├─ Did they ever hit the activation milestone?
│ NO → Did they match the ICP at signup?
│ NO → (1) BAD FIT - fix qualification upstream
│ YES → (2) POOR ONBOARDING - fix time-to-value
│ YES → Was usage healthy in the last 90 days?
│ NO → Did the champion/sponsor leave or disengage?
│ YES → (5) CHAMPION LEFT - multi-thread
│ NO → (3) LOW ADOPTION - never embedded in workflow
│ YES → Did they cite outcome shortfall?
│ YES → (4) MISSING VALUE - product/success motion
│ NO → Did they move to a rival?
│ YES → (7) COMPETITOR - product/positioning
│ NO → (6) PRICE/BUDGET - economicStep 4: Build the early-warning system
Churn is decided months before it happens. Score accounts on leading indicators and trigger intervention before renewal, not at it:
- Declining usage or login frequency
- Drop in active seats
- Champion disengagement (no QBR attendance, slow email replies)
- Support escalations or unresolved tickets
- Failure to hit the activation milestone in onboarding
An account flagging two or more indicators enters the at-risk queue.
Step 5: Build segmented intervention playbooks
- Onboarding churn: structured first-30-day activation program with a clear "aha" milestone.
- Adoption churn: usage nudges, training, executive business reviews to re-anchor value (pair with customer-success-qbr).
- At-risk accounts: a save play - executive outreach, success plan reset, targeted offer if the driver is economic.
- Involuntary churn: dunning, card-update flows, retry logic. Often 20-40% of churn and the easiest to recover - fix this before anything heroic.
Save-offer economics - run the math before offering discounts. A save offer pays only when: (expected additional lifetime margin retained × save rate) > (discount cost + CS time). Rules of thumb: cap discounts at 20-30% for a maximum of 3 months; a healthy save play converts 15-30% of at-risk accounts; a "saved" account that churns within 90 days anyway was a deferral, not a save - track 90-day post-save retention separately. Never train customers that threatening to cancel earns a discount: gate offers to genuinely economic-category churn, never volunteer them in the cancel flow by default.
Step 6: Prioritize the fix
Rank causes by frequency × revenue at stake × addressability. Fixing onboarding usually beats heroic save plays because it prevents churn at scale rather than rescuing one account at a time. Bad-fit churn is fixed in sales and marketing, not CS - route it upstream.
Deliverable
Produce a churn analysis containing: retention by cohort (signup month, segment, channel), GRR/NRR with the gap explained, a root-cause breakdown across the seven categories with involuntary churn quantified separately, a leading-indicator early-warning model with trigger thresholds, save-offer economics for the economic segment, and intervention playbooks ranked by frequency × revenue × addressability.
Metrics to track ongoing
Gross and net revenue retention by cohort; churn by root-cause category; activation rate and time-to-value; save rate on at-risk interventions plus 90-day post-save retention.
Do NOT
- Do not prescribe from blended churn - averages hide the cohort where the problem lives.
- Do not read NRR alone; expansion from a few accounts can mask a gross-retention leak that GRR exposes.
- Do not treat bad-fit churn as a CS problem - the fix is qualification, and every dollar spent "saving" a bad-fit account is wasted twice.
- Do not offer discounts reflexively in the cancel flow; it trains the base to threaten cancellation and erodes price integrity.
- Do not skip the involuntary-churn check - recovering failed payments is the cheapest 20-40% of the problem.
- Do not count a save as a save until the account clears 90 days post-intervention.
Quality bar
Ship only when: every churned account in the analysis window has one primary category; cohort cuts exist on all three axes; the early-warning model names concrete trigger thresholds; every recommended save offer has its economics shown; and the top-priority fix is justified by the frequency × revenue × addressability ranking, not by which intervention is most familiar.
Escalation
Gym and fitness-studio retention has its own economics and playbook - use retention-and-churn-killer. Customers already churned belong to win-back-campaign; account growth belongs to expansion-revenue; recurring QBR motion belongs to customer-success-qbr.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

