AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Churn Prevention

skill-scayver-marketing-skills-churn-prevention · by scayver

>

— No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-scayver-marketing-skills-churn-prevention

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-scayver-marketing-skills-churn-prevention)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Churn Prevention? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Churn Prevention: Reducing Cancellations and Recovering Lost Customers

Mandatory Content Standards

  • Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.
  • Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.
  • Use short sentences. One idea per sentence. One focus per paragraph.
  • Use active voice. Never passive constructions.
  • Address the reader directly using "you" and "your."
  • Use bullet points only when they genuinely improve readability.
  • Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.
  • End every sentence with a period.
  • No hashtags, emojis, or asterisks.
  • No introductory or closing filler phrases such as "in conclusion," "in summary," or "in a world where."
  • No warnings, notes, or disclaimers. Stick to requested output.
  • No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."
  • No excessive adjectives or adverbs. Let specifics do the work.
  • No broad generalizations. Every claim tied to specific context.
  • Use specific examples, data, and scenarios.
  • Pose at least one thought-provoking question per skill.
  • Mobile-friendly: short paragraphs, clear headers, scannable.
  • Practical and actionable. Every section connects to a next step.

What This Skill Covers

This skill covers every component of a churn prevention program for SaaS and subscription businesses: voluntary churn (users who actively cancel), involuntary churn (users who churn due to failed payments), cancellation flow design, save offers, dunning sequences, exit surveys, pause subscriptions, churn prediction signals, and win-back campaigns for former customers.


Why Churn Deserves Systematic Treatment

A company with 5% monthly churn loses more than half of its customer base every year. A company with 1% monthly churn loses about 11% per year. The difference in growth trajectory between those two companies is dramatic, even with identical acquisition rates.

What makes churn particularly costly is that it hides inside growth numbers. A company acquiring 200 new customers per month and losing 150 appears to be growing, with 50 net new customers. But the 150 churned customers represent lost revenue, lost word-of-mouth, and, in many cases, customers who are now using a competitor.

Most companies underinvest in churn prevention because the customer acquisition team is visible and the revenue at risk from churn is not. Acquisition success is celebrated. Churn is treated as an unfortunate reality.

Here is the question worth confronting directly: do you know why your last 50 churned customers left, and have you done anything differently as a result?


Voluntary vs. Involuntary Churn

Churn falls into two categories, and they require completely different interventions.

Voluntary churn happens when a customer actively decides to cancel their subscription. The causes include finding a better alternative, budget pressure, dissatisfaction with the product, loss of the champion inside the customer organization, or changes in the customer's business that make your product irrelevant.

Involuntary churn happens when a subscription fails to renew due to a payment failure. The customer did not decide to leave. Their card expired, hit its limit, or was replaced after a fraud incident. In many SaaS businesses, involuntary churn accounts for 20% to 40% of total churn. It is often the most recoverable form of churn because the customer's intent is neutral.

Most churn prevention programs focus entirely on voluntary churn and ignore the equally large and more recoverable involuntary segment. Start with involuntary churn if you have not already built a dunning system. It typically generates the fastest revenue recovery.


Measuring Churn

Before you can improve churn, you need to measure it accurately.

Monthly Churn Rate

The basic churn rate formula: (customers lost during period / customers at start of period) x 100.

If you started January with 500 customers and ended with 470 (not counting new customers acquired during January), your January churn rate was (30 / 500) x 100 = 6%.

This calculation becomes complex when you are also adding customers during the period. Use the start-of-period customer count as the denominator, or use an average of start and end (start + end / 2). Be consistent across periods so your trends are comparable.

Revenue Churn vs. Customer Churn

Customer churn counts the number of customers lost. Revenue churn measures the MRR lost.

These numbers diverge when your customers are on different plans. Losing 10 customers on your $29 plan and gaining 2 customers on your $499 plan means customer churn is positive while net revenue retention is positive. Track both metrics.

Net Revenue Retention (NRR) or Net Revenue Churn is the metric that captures expansion revenue against revenue loss. The formula: (Starting MRR + Expansion MRR - Churned MRR - Contraction MRR) / Starting MRR x 100.

A NRR above 100% means your existing customers are growing in aggregate, even after accounting for cancellations. Companies with NRR above 120% can grow significantly even with modest new customer acquisition.


Churn Prediction Signals

The most effective churn prevention happens before a customer reaches the cancellation page. Predictive intervention, reaching customers when they are at risk before they have decided to leave, is substantially more effective than trying to save customers who have already decided to cancel.

Leading Indicators of Churn Risk

Product engagement decline: users who were logging in daily and now log in weekly, or users who were using five features and now use one, are exhibiting early churn signals. Set up automated alerts or cohort reports in your product analytics tool for engagement declines.

Feature abandonment: if a user stops using a feature they previously relied on, investigate why. The most common reasons are confusion, a product change that broke their workflow, or finding an alternative solution.

Support ticket volume increase: users who contact support more frequently are often encountering friction. A spike in support contact from a customer is a churn signal, not just a support demand signal.

Login frequency: declining login frequency is one of the most reliable churn predictors across SaaS categories. A user who has not logged in for 21 days in a monthly subscription product is at significantly higher churn risk than their average.

NPS score and qualitative feedback: users who respond to NPS surveys with low scores (0-6) and describe specific frustrations are at elevated churn risk. Trigger a follow-up from a customer success manager within 24 hours of a low NPS response.

Payment method aging: customers with credit cards expiring within 60 days are at elevated involuntary churn risk. Prompt them to update before the expiration.

Building a Churn Prediction Score

If you have sufficient historical data (typically 12 or more months of customer behavior data and a sample of at least 500 churned customers), you can build a churn prediction model.

The simplest approach is a logistic regression or tree-based model trained on the behavioral signals above, using known churn outcomes as the target variable. Tools like Mixpanel, Amplitude, and Segment have built-in churn prediction features. Customer success platforms like Gainsight and ChurnZero include health score models.

A churn prediction score gives your customer success team a prioritized list of at-risk accounts to work through each week.


Cancellation Flow Design

When a user clicks "Cancel Subscription," how your product responds has a measurable impact on whether they follow through.

A well-designed cancellation flow serves two purposes. It gives genuinely unhappy customers a respectful exit path. It also surfaces save offers and alternatives to customers who might stay with the right prompt.

The Four-Step Cancellation Flow

Step 1: the reason survey. Ask the customer why they are canceling before showing them any save offers. Use a multiple-choice question with five to eight options that reflect your actual churn reasons.

Common reasons to include:

  • Too expensive for my budget
  • Not using it enough to justify the cost
  • Missing a feature I need
  • Switching to a different tool
  • My business is changing (fewer team members, project complete, etc.)
  • Technical problems or bugs
  • Too difficult to use

Add an optional free-text field for additional context. The data you collect here is essential for improving your product and identifying systematic issues.

Step 2: the contextual save offer. Based on the reason they selected, show a targeted save offer. This personalization substantially outperforms a generic discount offer.

For "too expensive": offer a temporary discount (20% to 30% off for three to six months) or a plan downgrade. For "not using it enough": offer a pause option or show a usage summary that demonstrates value they may not have noticed. For "missing a feature": acknowledge the gap, provide a workaround if one exists, and optionally add them to a feature waitlist. For "switching to a different tool": ask which tool and why. This data is valuable. Consider a brief exit interview.

Step 3: the final confirmation. If they do not accept the save offer, confirm the cancellation with clear information about when their access ends and what they will lose. Avoid dark patterns: do not make the cancellation button difficult to find or use confusing labels like "I don't want to save money."

Step 4: the post-cancellation experience. After cancellation is confirmed, send a confirmation email that includes their cancellation date, what they retain access to, and a clear path to reactivate. This is also a good moment to offer a survey link for customers willing to provide more detail.

Pause Subscription

Offering a subscription pause reduces immediate churn from customers who need a temporary break rather than a permanent exit.

Paused customers convert back to active subscribers at higher rates than new customer acquisition. They have already onboarded, already built habits around your product, and already trust you. A three-month pause that converts back to active is worth significantly more than the MRR lost during the pause.

Structure your pause option clearly:

  • Offer one, two, or three month pause options
  • Communicate clearly what happens to their data and settings during the pause
  • Explain how they reactivate
  • Send a reactivation reminder email two weeks before the pause ends

Save Offers: What Works and What Does Not

A save offer is an incentive presented at the point of cancellation to retain a customer who has initiated the cancellation process. Save offers work best when they are targeted to the specific reason for cancellation.

Effective Save Offer Types

Temporary discount: offer 20% to 30% off for the next two to three months. This works best for price-sensitive churn. A deep discount (50%+) can attract non-genuine saves who stay for the discount period and then cancel.

Plan downgrade: offer a lower-tier plan rather than cancellation. A customer downgrading from $99 to $29 per month retains 30% of the revenue and keeps the customer relationship. Downgrades are significantly more valuable than cancellations.

Extended trial or free period: "Stay for two more months, on us" works for customers who feel they have not gotten enough value yet. This buys time for the customer to experience more value.

Feature unlock: if a customer is canceling because they cannot access a specific feature, consider whether a temporary feature grant would retain them. A customer who stays because they got access to the feature they needed may convert to a higher plan.

Human escalation: for high-value accounts, route the cancellation to a customer success manager rather than letting it proceed automatically. A personal call or email from a human is more effective than any automated save offer for accounts above a threshold value.

Save Rate Benchmarks

A typical cancellation flow without save offers has a save rate near 0%. A well-designed flow with contextual save offers typically achieves a 15% to 30% save rate, meaning 15% to 30% of customers who initiate cancellation are retained.

Measure your save rate monthly. Track save rates by cancellation reason. Identify which offers are working and which are not. Iterate based on data.


Dunning: Recovering Failed Payments

Dunning is the process of communicating with customers about failed payments and recovering the subscription before it cancels.

Failed payments are common. Industry data suggests that 5% to 8% of subscription payments fail in any given month due to expired cards, exceeded credit limits, bank fraud blocks, or insufficient funds.

Smart Retry Logic

Before communicating with the customer, retry the failed payment automatically. Most payment processors (Stripe, Braintree, Recurly) have smart retry logic that retries payments at optimal times based on bank and card network data.

Stripe's smart retry, for example, analyzes millions of payment data points to determine the best time to retry a failed charge. This alone recovers a significant percentage of failed payments without any customer action.

Configure your retry schedule carefully. Retry immediately on failure, then at 3 days, then at 7 days, then at 14 days. Spread retries to avoid concentrating all attempts on the same day of the month when bank systems are busiest.

The Dunning Email Sequence

Beyond automatic retries, email your customers when their payment fails. Communicate clearly, without accusation, and make it easy to update their payment method.

Email 1 (day of failure): subject line: "Action needed: your payment didn't go through." Explain the issue plainly. Provide a direct link to update payment method. Do not alarm the customer. Many failed payments resolve on the first or second retry.

Email 2 (3 days later if not resolved): increase urgency slightly. Explain when their access will be affected if the payment is not resolved.

Email 3 (7 days later if not resolved): emphasize that access will end soon. Provide the specific date. Make the payment update link highly visible.

Final email (2 to 3 days before access ends): final notice. Provide the exact date and time access ends. Include a one-click payment update link if your platform supports it.

After access ends: send a payment-declined cancellation email with a clear reactivation path. This customer did not intend to leave. Make it easy to come back.

Dunning Communication Tone

Never shame a customer for a failed payment. The language should be practical and helpful, not punitive. "Your card on file was declined" is factual and neutral. "Your payment failed again" starts to feel accusatory after the third message.

Include customer service contact information in every dunning email. Some customers prefer to resolve this through human contact rather than a self-serve portal.


Exit Surveys: Turning Departures into Intelligence

Every churned customer who answers an exit survey provides information that no amount of product analytics can replicate. They tell you, in their own words, why your product failed to retain them.

Exit Survey Structure

Keep the survey short. Three to five questions maximum. Long surveys get abandoned.

The core question: "What was the main reason you canceled?" Use the same categories as your in-app cancellation flow so you can compare rates.

A follow-up open text question: "Is there anyt

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.