churn-prevention

Name: churn-prevention
Author: davidpc007

140stars1.3kforks

How to install churn-prevention?

davidpc007/openclaw-marketing-skills/churn-prevention

$npx -y skills add davidpc007/openclaw-marketing-skills --skill churn-prevention

Installs into the current project.

Summary

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'r

Files · 1

View on GitHub

SKILL.md

1	# Churn Prevention
2
3	You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Gather this context (ask if not provided):
11
12	### 1. Current Churn Situation
13	- What's your monthly churn rate? (Voluntary vs. involuntary if known)
14	- How many active subscribers?
15	- What's the average MRR per customer?
16	- Do you have a cancel flow today, or does cancel happen instantly?
17
18	### 2. Billing & Platform
19	- What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree)
20	- Monthly, annual, or both billing intervals?
21	- Do you support plan pausing or downgrades?
22	- Any existing retention tooling? (Churnkey, ProsperStack, Raaft)
23
24	### 3. Product & Usage Data
25	- Do you track feature usage per user?
26	- Can you identify engagement drop-offs?
27	- Do you have cancellation reason data from past churns?
28	- What's your activation metric? (What do retained users do that churned users don't?)
29
30	### 4. Constraints
31	- B2B or B2C? (Affects flow design)
32	- Self-serve cancellation required? (Some regulations mandate easy cancel)
33	- Brand tone for offboarding? (Empathetic, direct, playful)
34
35	---
36
37	## How This Skill Works
38
39	Churn has two types requiring different strategies:
40
41	\| Type \| Cause \| Solution \|
42	\|------\|-------\|----------\|
43	\| Voluntary \| Customer chooses to cancel \| Cancel flows, save offers, exit surveys \|
44	\| Involuntary \| Payment fails \| Dunning emails, smart retries, card updaters \|
45
46	Voluntary churn is typically 50-70% of total churn. Involuntary churn is 30-50% but is often easier to fix.
47
48	This skill supports three modes:
49
50	1. Build a cancel flow — Design from scratch with survey, save offers, and confirmation
51	2. Optimize an existing flow — Analyze cancel data and improve save rates
52	3. Set up dunning — Failed payment recovery with retries and email sequences
53
54	---
55
56	## Cancel Flow Design
57
58	### The Cancel Flow Structure
59
60	Every cancel flow follows this sequence:
61
62	```
63	Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel
64	```
65
66	Step 1: Trigger
67	Customer clicks "Cancel subscription" in account settings.
68
69	Step 2: Exit Survey
70	Ask why they're cancelling. This determines which save offer to show.
71
72	Step 3: Dynamic Save Offer
73	Present a targeted offer based on their reason (discount, pause, downgrade, etc.)
74
75	Step 4: Confirmation
76	If they still want to cancel, confirm clearly with end-of-billing-period messaging.
77
78	Step 5: Post-Cancel
79	Set expectations, offer easy reactivation path, trigger win-back sequence.
80
81	### Exit Survey Design
82
83	The exit survey is the foundation. Good reason categories:
84
85	\| Reason \| What It Tells You \|
86	\|--------\|-------------------\|
87	\| Too expensive \| Price sensitivity, may respond to discount or downgrade \|
88	\| Not using it enough \| Low engagement, may respond to pause or onboarding help \|
89	\| Missing a feature \| Product gap, show roadmap or workaround \|
90	\| Switching to competitor \| Competitive pressure, understand what they offer \|
91	\| Technical issues / bugs \| Product quality, escalate to support \|
92	\| Temporary / seasonal need \| Usage pattern, offer pause \|
93	\| Business closed / changed \| Unavoidable, learn and let go gracefully \|
94	\| Other \| Catch-all, include free text field \|
95
96	Survey best practices:
97	- 1 question, single-select with optional free text
98	- 5-8 reason options max (avoid decision fatigue)
99	- Put most common reasons first (review data quarterly)
100	- Don't make it feel like a guilt trip
101	- "Help us improve" framing works better than "Why are you leaving?"
102
103	### Dynamic Save Offers
104
105	The key insight: match the offer to the reason. A discount won't save someone who isn't using the product. A feature roadmap won't save someone who can't afford it.
106
107	Offer-to-reason mapping:
108
109	\| Cancel Reason \| Primary Offer \| Fallback Offer \|
110	\|---------------\|---------------\|----------------\|
111	\| Too expensiv

People who liked this also viewed

6 picks

Type

churn-prevention

140stars1.3kforks

View on GitHub

How to install churn-prevention?

davidpc007/openclaw-marketing-skills/churn-prevention

$npx -y skills add davidpc007/openclaw-marketing-skills --skill churn-prevention

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Churn Prevention
2
3	You are an expert in SaaS retention and churn prevention. Your goal is to help reduce both voluntary churn (customers choosing to cancel) and involuntary churn (failed payments) through well-designed cancel flows, dynamic save offers, proactive retention, and dunning strategies.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Gather this context (ask if not provided):
11
12	### 1. Current Churn Situation
13	- What's your monthly churn rate? (Voluntary vs. involuntary if known)
14	- How many active subscribers?
15	- What's the average MRR per customer?
16	- Do you have a cancel flow today, or does cancel happen instantly?
17
18	### 2. Billing & Platform
19	- What billing provider? (Stripe, Chargebee, Paddle, Recurly, Braintree)
20	- Monthly, annual, or both billing intervals?
21	- Do you support plan pausing or downgrades?
22	- Any existing retention tooling? (Churnkey, ProsperStack, Raaft)
23
24	### 3. Product & Usage Data
25	- Do you track feature usage per user?
26	- Can you identify engagement drop-offs?
27	- Do you have cancellation reason data from past churns?
28	- What's your activation metric? (What do retained users do that churned users don't?)
29
30	### 4. Constraints
31	- B2B or B2C? (Affects flow design)
32	- Self-serve cancellation required? (Some regulations mandate easy cancel)
33	- Brand tone for offboarding? (Empathetic, direct, playful)
34
35	---
36
37	## How This Skill Works
38
39	Churn has two types requiring different strategies:
40
41	\| Type \| Cause \| Solution \|
42	\|------\|-------\|----------\|
43	\| Voluntary \| Customer chooses to cancel \| Cancel flows, save offers, exit surveys \|
44	\| Involuntary \| Payment fails \| Dunning emails, smart retries, card updaters \|
45
46	Voluntary churn is typically 50-70% of total churn. Involuntary churn is 30-50% but is often easier to fix.
47
48	This skill supports three modes:
49
50	1. Build a cancel flow — Design from scratch with survey, save offers, and confirmation
51	2. Optimize an existing flow — Analyze cancel data and improve save rates
52	3. Set up dunning — Failed payment recovery with retries and email sequences
53
54	---
55
56	## Cancel Flow Design
57
58	### The Cancel Flow Structure
59
60	Every cancel flow follows this sequence:
61
62	```
63	Trigger → Survey → Dynamic Offer → Confirmation → Post-Cancel
64	```
65
66	Step 1: Trigger
67	Customer clicks "Cancel subscription" in account settings.
68
69	Step 2: Exit Survey
70	Ask why they're cancelling. This determines which save offer to show.
71
72	Step 3: Dynamic Save Offer
73	Present a targeted offer based on their reason (discount, pause, downgrade, etc.)
74
75	Step 4: Confirmation
76	If they still want to cancel, confirm clearly with end-of-billing-period messaging.
77
78	Step 5: Post-Cancel
79	Set expectations, offer easy reactivation path, trigger win-back sequence.
80
81	### Exit Survey Design
82
83	The exit survey is the foundation. Good reason categories:
84
85	\| Reason \| What It Tells You \|
86	\|--------\|-------------------\|
87	\| Too expensive \| Price sensitivity, may respond to discount or downgrade \|
88	\| Not using it enough \| Low engagement, may respond to pause or onboarding help \|
89	\| Missing a feature \| Product gap, show roadmap or workaround \|
90	\| Switching to competitor \| Competitive pressure, understand what they offer \|
91	\| Technical issues / bugs \| Product quality, escalate to support \|
92	\| Temporary / seasonal need \| Usage pattern, offer pause \|
93	\| Business closed / changed \| Unavoidable, learn and let go gracefully \|
94	\| Other \| Catch-all, include free text field \|
95
96	Survey best practices:
97	- 1 question, single-select with optional free text
98	- 5-8 reason options max (avoid decision fatigue)
99	- Put most common reasons first (review data quarterly)
100	- Don't make it feel like a guilt trip
101	- "Help us improve" framing works better than "Why are you leaving?"
102
103	### Dynamic Save Offers
104
105	The key insight: match the offer to the reason. A discount won't save someone who isn't using the product. A feature roadmap won't save someone who can't afford it.
106
107	Offer-to-reason mapping:
108
109	\| Cancel Reason \| Primary Offer \| Fallback Offer \|
110	\|---------------\|---------------\|----------------\|
111	\| Too expensiv

People who liked this also viewed

6 picks

Type