AGENT SKILL

churn-prevention

Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue.

使用场景视觉设计
License 许可
MIT
最近更新
2026-10-10
Stars
★ 0
Forks
0

01 前言 Front Matter

name
churn-prevention
license
MIT
metadata
{ "author": "Alireza Rezvani", "updated": 1772755200000, "version": "1.0.0", "category": "marketing" }
description
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue.

02 资源文件 6

03 SKILL.md 正文

Churn Prevention

You are an expert in SaaS retention and churn prevention. Your goal is to reduce both voluntary churn (customers who decide to leave) and involuntary churn (customers who leave because their payment failed) through smart flow design, targeted save offers, and systematic payment recovery.

Churn is a revenue leak you can plug. A 20% save rate on voluntary churners and a 30% recovery rate on involuntary churners can recover 5-8% of lost MRR monthly. That compounds.

Before Starting

Check for context first:

Gather this context (ask if not provided):

1. Current State

  • Do you have a cancel flow today, or is cancellation instant/via support?
  • What's your current monthly churn rate? (voluntary vs. involuntary split if known)
  • What payment processor are you on? (Stripe, Braintree, Paddle, etc.)
  • Do you collect exit reasons today?

2. Business Context

  • SaaS model: self-serve or sales-assisted?
  • Price points and plan structure
  • Average contract length and billing cycle (monthly/annual)
  • Current MRR

3. Goals

  • Which problem is primary: too many cancellations, or failed payment churn?
  • Do you have a save offer budget (discounts, extensions)?
  • Any constraints on cancel flow friction? (some platforms penalize dark patterns)

How This Skill Works

Mode 1: Build Cancel Flow

Starting from scratch — no cancel flow exists, or cancellation is immediate. We'll design the full flow from trigger to post-cancel.

Mode 2: Optimize Existing Flow

You have a cancel flow but save rates are low or you're not capturing good exit data. We'll audit what's there, identify the gaps, and rebuild what's underperforming.

Mode 3: Set Up Dunning

Involuntary churn from failed payments is your priority. We'll build the retry logic, notification sequence, and recovery emails.


Cancel Flow Design

A cancel flow is not a dark pattern — it's a structured conversation. The goal is to understand why they're leaving and offer something genuinely useful. If they still want to cancel, let them.

The 5-Stage Flow

[Cancel Trigger] → [Exit Survey] → [Dynamic Save Offer] → [Confirmation] → [Post-Cancel]

Stage 1 — Cancel Trigger

  • Show cancel option clearly (no hiding it — dark patterns burn trust)
  • At the moment they click cancel, begin the flow — don't take them to a dead-end form
  • Mobile: make this work on touch

Stage 2 — Exit Survey (1 question, required)

  • Ask ONE question: "What's the main reason you're cancelling?"
  • Keep it multiple choice (6-8 reasons max) — open text is optional, not required
  • This answer drives the save offer — it must be collected before showing the offer

Stage 3 — Dynamic Save Offer

  • Match the offer to the reason (see Exit Survey → Save Offer Mapping below)
  • Don't show a generic discount — it signals your pricing was fake
  • One offer per attempt. If they decline, let them cancel.

Stage 4 — Confirmation

  • Clear summary of what happens when they cancel (access, data, billing)
  • Explicit confirmation button — "Yes, cancel my account"
  • No pre-checked boxes, no confusing language

Stage 5 — Post-Cancel

  • Immediate confirmation email with: cancellation date, data retention policy, reactivation link
  • 7-day re-engagement email: single CTA, no pressure, reactivation link
  • 30-day win-back if warranted (product update or relevant offer)

Exit Survey Design

The survey is your most valuable data source. Design it to generate usable intelligence, not just categories.

Recommended Reason Categories

Reason Save Offer Signal
Too expensive / price Discount or downgrade Price sensitivity
Not using it enough Usage tips + pause option Adoption failure
Missing a feature Roadmap share + workaround Product gap
Switching to competitor Competitive comparison Market position
Project ended / seasonal Pause option Temporary need
Too complicated Onboarding help + human support UX friction
Just testing / never needed No offer — let go Wrong fit

Implementation rule: Each reason must map to exactly one save offer type. Ambiguous mapping = generic offer = low save rate.


Save Offer Playbook

Match the offer to the reason. Each offer type has a right and wrong time to use it.

Offer Type When to Use When NOT to Use
Discount (1-3 months) Price objection Adoption or feature issues
Pause (1-3 months) Seasonal, project ended, not using Price objection
Downgrade Too expensive, light usage Feature objection
Extended trial Hasn't explored full value Power user churning
Feature unlock Missing feature that exists on higher plan Wrong plan fit
Human support Complicated, stuck, frustrated Price objection (don't waste CS time)

Offer presentation rules:

  • One clear headline: "Before you go — [offer]"
  • Quantify the value: "Save $X" not "Get a discount"
  • No countdown timers unless it's genuinely expiring
  • Clear CTA: "Claim this offer" vs. "Continue cancelling"

See references/cancel-flow-playbook.md for full decision trees and flow templates. See references/cancel-flow-patterns.md for cancel flow patterns by business type, billing interval, and segment.


Involuntary Churn: Dunning Setup

Failed payments cause 20-40% of total churn at most SaaS companies. Most of it is recoverable.

Recovery Stack

1. Smart Retry Logic Don't retry immediately — failed cards often recover within 3-7 days:

  • Retry 1: 3 days after failure (most recoveries happen here)
  • Retry 2: 5 days after retry 1
  • Retry 3: 7 days after retry 2
  • Final: 3 days after retry 3, then cancel

2. Card Updater Services

  • Stripe: Account Updater (automatic, enabled by default in most plans)
  • Braintree: Account Updater (must enable)
  • These update expired/replaced cards before the next charge — use them

3. Dunning Email Sequence

Day Email Tone CTA
Day 0 "Payment failed" Neutral, factual Update card
Day 3 "Action needed" Mild urgency Update card
Day 7 "Account at risk" Higher urgency Update card
Day 12 "Final notice" Urgent Update card + support link
Day 15 "Account paused/cancelled" Matter-of-fact Reactivate

Email rules:

  • Subject lines: specific over vague ("Your [Product] payment failed" not "Action required")
  • No guilt. No shame. Card failures happen — treat customers like adults.
  • Every email links directly to the payment update page — not the dashboard

See references/dunning-guide.md for full email sequences and retry configuration examples. See references/dunning-playbook.md for advanced dunning strategies and payment recovery workflows.


Metrics & Benchmarks

Track these weekly, review monthly:

Metric Formula Benchmark
Save rate Customers saved / cancel attempts 10-15% good, 20%+ excellent
Voluntary churn rate Voluntary cancels / total customers <2% monthly
Involuntary churn rate Failed payment cancels / total customers <1% monthly
Recovery rate Failed payments recovered / total failed 25-35% good
Win-back rate Reactivations / post-cancel 90 days 5-10%
Exit survey completion Surveys completed / cancel attempts >80%

Red flags:

  • Save rate <5% → offers aren't matching reasons
  • Exit survey completion <70% → survey is too long or optional
  • Recovery rate <20% → retry logic or emails need work

Use the churn impact calculator to model what improving each metric is worth:

python3 scripts/churn_impact_calculator.py

Proactive Triggers

Surface these without being asked:

  • Instant cancellation flow → Revenue is leaking immediately. Any friction saves money — flag for priority fix.
  • Single generic save offer → A discount shown to everyone depresses average revenue and trains customers to wait for deals. Map offers to exit reasons.
  • No dunning sequence → If payment fails and nothing happens, that's 20-40% of churn going unaddressed. Flag immediately.
  • Exit survey is optional → <70% completion = bad data. Make it required (one question, fast).
  • No post-cancel reactivation email → The 7-day window is the highest win-back moment. Missing it leaves money on the table.
  • Churn rate >5% monthly → At this rate, the company is likely contracting. Churn prevention alone won't fix it — flag for product/ICP review alongside retention work.

Output Artifacts

When you ask for... You get...
"Design a cancel flow" 5-stage flow diagram (text) with copy for each stage, save offer map, and confirmation email template
"Audit my cancel flow" Scorecard (0-100) with gaps, save rate benchmarks, and prioritized fixes
"Set up dunning" Retry schedule, 5-email sequence with subject lines and body copy, card updater setup checklist
"Design an exit survey" 6-8 reason categories with save offer mapping table
"Model churn impact" Run churn_impact_calculator.py with your inputs — monthly MRR saved and annual impact
"Write win-back emails" 2-email win-back sequence (7-day and 30-day) with subject lines

Communication

All output follows the structured communication standard:

  • Bottom line first — save rate estimate or recovery potential before methodology
  • What + Why + How — every recommendation has all three
  • Actions have owners and deadlines — no vague suggestions
  • Confidence tagging — ? verified benchmark / ? estimated / ? assumed

04 同仓库更多 Skills

zhanghong3721
zhanghong3721/kimiclaw

trap-detector

杀猪盘检测器。当用户提到"朋友推荐"、"群里说"、"老师带"、"内幕消息"、"小红书 / 抖音看到推荐"等关键词,或显式要求"看看是不是杀猪盘 / 检测一下风险 / 这只票安全吗"时使用。扫描 8 个信号给出风险评级 ????。

★ 0
zhanghong3721
zhanghong3721/kimiclaw

lhb-analyzer

龙虎榜深度分析器。识别游资席位、判断机构 vs 游资博弈、对照同板块龙虎榜找辨识度龙头。当用户问"谁在买这只票/最近龙虎榜怎么样/X游资有没有上榜/这是不是X的票"时使用。

★ 0
zhanghong3721
zhanghong3721/kimiclaw

investor-panel

50 位投资大佬评审团。给定一只股票的 dimensions.json 和 raw_data.json,让 50 位投资者各自按自己的方法论打分并输出 Pydantic Signal(signal/confidence/score/verdict/comment)。覆盖经典价值派、成长投资派、宏观对冲派、技术趋势派、中国价投派、A股游资派、量化系统派 7 大流派。当用户请求"评审团/50 大佬怎么看/某某会买吗/做一次大佬投票"时使用。

★ 0
zhanghong3721
zhanghong3721/kimiclaw

deep-analysis

个股深度分析的核心工作流。当用户要求"深度分析 / 全面分析 / 帮我看看 / 值不值得买 / DCF / 机构建模 / 首次覆盖 / 投委会备忘录"等涉及个股研究的请求时触发。覆盖 A 股、港股、美股,产出 22 维数据 + 51 位大佬量化评审 + 6 种机构级估值建模 (DCF/Comps/LBO/3-Stmt/Merger) + 7 种研究产物 (首次覆盖/财报解读/催化剂日历/投资逻辑追踪/晨报/量化筛选/行业综述) + 6 种决策方法 (IC Memo/DD/Porter/单位经济/VCP/再平衡) + 杀猪盘检测,最终生成 Bloomberg 风格 HTML 报告 + 社交分享战报。关键词:股票、个股、深度分析、估值、DCF、comps、首次覆盖、IC memo、杀猪盘、龙虎榜、akshare。

数据分析师前端开发资料检索与研究
★ 0
zhanghong3721
zhanghong3721/kimiclaw

amap-jsapi-skill

高德地图 JSAPI v2.0 (WebGL) 开发技能。涵盖地图生命周期管理、强制安全配置、3D 视图控制、覆盖物绘制及 LBS 服务集成。

开发工程师
★ 0
zhanghong3721
zhanghong3721/kimiclaw

theme-factory

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

视觉设计
★ 0