# Churn Prevention

SaaS churn reduction covering cancel flow design, dynamic save offers, exit survey...

- Repository: https://github.com/borghei/Claude-Skills (1026 stars)
- Category: Design
- License: MIT + Commons Clause
- Last updated: 2026-10-23
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add borghei/Claude-Skills --skill churn-prevention -g -a claude-code -y`
Codex: `npx skills add borghei/Claude-Skills --skill churn-prevention -g -a codex -y`
Cursor: `npx skills add borghei/Claude-Skills --skill churn-prevention -g -a cursor -y`
Gemini CLI: `npx skills add borghei/Claude-Skills --skill churn-prevention -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add borghei/Claude-Skills`

## Description

SaaS churn reduction covering cancel flow design, dynamic save offers, exit survey architecture, dunning sequences, payment recovery, win-back campaigns, and churn impact modeling.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Churn Prevention

Production-grade SaaS churn reduction framework covering cancel flow architecture, dynamic save offer mapping, exit survey design, dunning sequence engineering, payment recovery optimization, win-back campaigns, and churn impact modeling. Addresses both voluntary churn (customers who decide to leave) and involuntary churn (customers who leave due to payment failure).

---

## Table of Contents

- [Initial Assessment](#initial-assessment)
- [Churn Taxonomy](#churn-taxonomy)
- [Cancel Flow Architecture](#cancel-flow-architecture)
- [Exit Survey Design](#exit-survey-design)
- [Dynamic Save Offer System](#dynamic-save-offer-system)
- [Dunning Sequence Engineering](#dunning-sequence-engineering)
- [Win-Back Campaign Framework](#win-back-campaign-framework)
- [Churn Health Scoring](#churn-health-scoring)
- [Metrics and Benchmarks](#metrics-and-benchmarks)
- [Churn Impact Calculator](#churn-impact-calculator)
- [Output Artifacts](#output-artifacts)
- [Related Skills](#related-skills)

---

## Clarify First

Before designing the churn-prevention system, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

- **Voluntary vs involuntary churn split:** which dominates (determines whether to build cancel flow/save offers or dunning/payment recovery).
- **Existing cancel flow vs instant/support cancellation:** sets build-from-scratch vs optimize mode.
- **Current MRR + ARPU + billing cycle:** sizes the dollar impact and the save-offer budget.
- **Payment processor:** Stripe / Braintree / Paddle / Recurly (determines card-updater and dunning retry implementation).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

## Initial Assessment

### Required Context

The rest: https://github.com/borghei/Claude-Skills/blob/HEAD/business-growth/churn-prevention/SKILL.md