churn-prevention

Designs cancel flows, save offers, and dunning sequences to reduce SaaS churn.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/samuelgabrielsikorjak-sys/techscope-website --skill churn-prevention-samuelgabrielsikorjak-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: churn-prevention
Source: https://github.com/samuelgabrielsikorjak-sys/techscope-website/tree/main/.claude/skills/marketingskills-main/skills/churn-prevention
Command: npx skills add https://github.com/samuelgabrielsikorjak-sys/techscope-website --skill churn-prevention-samuelgabrielsikorjak-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SaaS businesses lose subscribers to both voluntary cancellations and failed payments, often without any system to save them. This Skill provides a complete framework for building cancel flows, targeted save offers, churn prediction, and payment recovery sequences. ## Core Features & Use Cases - Cancel Flow Design: Build a multi-step flow (exit survey, dynamic save offers, confirmation, post-cancel) with reason-to-offer mapping and UI patterns. - Involuntary Churn Recovery: Implement the full dunning stack including pre-dunning card expiry alerts, smart retry schedules, and a 4-email recovery sequence. - Churn Prediction: Create a weighted health score from usage, support, and billing signals with tiered proactive interventions. - Use Case: A $49/month SaaS with 7% monthly churn uses this Skill to design an exit survey, map save offers to each cancellation reason, and set up Stripe Smart Retries with dunning emails, cutting churn within a quarter. ## Quick Start Ask the assistant to design a cancel flow with exit survey and save offers for your subscription product, including a dunning email sequence for failed payments.

Frequently Asked Questions about churn-prevention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a cancel flow to reduce SaaS churn?

Build a five-step flow: cancel trigger, one-question exit survey, a dynamic save offer matched to the cancellation reason, clear confirmation, and a post-cancel reactivation path. Keep the continue-cancelling option visible to avoid dark patterns.

What save offers work best for each cancellation reason?

Match offers to reasons: 20-30% discounts for price concerns, 1-3 month pauses for low usage, roadmap previews for missing features, and support escalation for technical issues. Avoid discounts over 30%, which train cancel-for-deal behavior.

How do I recover failed subscription payments with dunning?

Use the dunning stack: pre-dunning card expiry alerts, smart retries over 7-10 days based on decline type, a four-email sequence with escalating urgency, then a grace period before pausing. Effective dunning recovers 50-60% of failed payments.

Does Stripe support automatic payment retries for failed charges?

Yes, Stripe Smart Retries uses machine learning to pick optimal retry timing and is enabled in Dashboard under Billing settings. It typically recovers about 15% more payments than fixed-schedule retries and includes automatic card updater services.

How do I predict which customers will churn before they cancel?

Build a 0-100 health score from weighted signals: login frequency (30%), feature usage (25%), support sentiment (15%), billing health (15%), and engagement (15%). Trigger interventions when scores drop below 60, such as re-engagement emails or personal outreach.

When should I not offer a discount to save a cancelling customer?

Skip discounts when the reason is business closure, when the customer is dormant and forgot the product, or when they previously accepted a discount and cancelled again. In these cases use pauses, onboarding help, or respectful offboarding instead.