marketing-churn-prevention

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

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill marketing-churn-prevention-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marketing-churn-prevention
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/marketing-churn-prevention
Command: npx skills add https://github.com/avel123111/triplanio --skill marketing-churn-prevention-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Subscription businesses lose revenue to both voluntary churn (customers cancelling) and involuntary churn (failed payments), often without any retention system in place. This Skill provides structured guidance for building cancel flows, targeted save offers, churn prediction signals, and payment recovery sequences. ## Core Features & Use Cases - Cancel Flow Design: Build exit surveys with reason categories mapped to dynamic save offers such as discounts, pauses, downgrades, and personal outreach. - Churn Prediction & Proactive Retention: Define health scores from usage signals and trigger interventions before customers reach the cancel button. - Dunning & Payment Recovery: Configure pre-dunning alerts, smart retry schedules, and a four-email dunning sequence with provider-specific setup for Stripe, Chargebee, Paddle, and Recurly. - Use Case: A SaaS founder notices a 6% monthly churn rate. Use this Skill to design a cancel flow with an exit survey, map save offers to each cancel reason, and set up Stripe Smart Retries with dunning emails to recover failed payments. ## Quick Start Help me design a cancel flow with an exit survey and save offers for my subscription product, and set up a dunning email sequence for failed payments.

Frequently Asked Questions about marketing-churn-prevention

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

FAQPage Schema
How do I design a cancel flow that reduces churn?

Structure the flow as trigger, exit survey, dynamic save offer, confirmation, and post-cancel steps. Map each cancel reason to a matching offer, such as a 20-30% discount for price concerns or a 1-3 month pause for low usage, while keeping the continue-cancelling option visible.

How do I recover failed subscription payments with dunning?

Combine pre-dunning card expiry alerts, smart retries over 7-10 days, and a four-email dunning sequence sent on days 0, 3, 7, and 10. Stripe Smart Retries automates retry timing and typically recovers 50-60% of failed payments.

What save offer should I show for each cancellation reason?

Match the offer to the reason: discounts for price sensitivity, pauses for low usage or temporary needs, downgrades for plan fit, roadmap previews for missing features, and support escalation for technical issues. Avoid offering discounts for non-price reasons.

Does this work with Stripe, Chargebee, and Paddle?

Yes, the Skill covers provider-specific dunning setup for Stripe, Chargebee, Paddle, Recurly, and Braintree, including smart retry configuration, webhook events like invoice.payment_failed, and built-in card updater services.

What is a good cancel flow save rate benchmark?

A typical cancel flow saves 25-35% of cancelling sessions, with offer acceptance rates of 15-25%. B2C automated flows average 20-30% saves, while B2B flows with personal outreach can reach 30-45%.

When should I not offer a discount to prevent cancellation?

Avoid discounts when the reason is low usage, missing features, or business closure, since price is not the cause. Never exceed 30% discounts, as deeper discounts train customers to cancel repeatedly for deals.