cyberneticlibrary

Reduce SaaS churn with save offers

churn-preventionskillsetup L3137
borghei/Claude-Skills
What it does

Reduce SaaS churn via save offers, dunning, and win-back

Best for

Systematically reducing voluntary churn through dynamic save offers mapped to exit reasons and preventing involuntary churn via smart retries.

Inputs
  • · Current churn rate (voluntary/involuntary split)
  • · Cancel flow architecture
  • · Payment processor (Stripe/Braintree/Paddle)
  • · Customer MRR, contract value
Outputs
  • · Exit survey structure
  • · Save offer mapping
  • · Dunning sequence
  • · Win-back campaign template
  • · Churn impact model
Requires
  • · Stripe/Braintree/Paddle dunning APIs
  • · Email automation (Klaviyo, Segment)
Preconditions
  • · Cancel flow exists or needs building
  • · Payment processor connected
  • · Exit survey data available
Failure modes
  • · Involuntary churn recovery requires card updater service (expensive)
  • · Save offers generic (same for all exit reasons)
  • · Dunning sequence too aggressive causes more churn
  • · Win-back emails to lapsed users without re-qualification
Trust signals
  • · Churn taxonomy (8 voluntary types, 5 involuntary causes)
  • · 5-stage cancel flow with exit survey rules
  • · Dunning sequence timing with retry logic
  • · Metrics: 40-50% payment recovery rate from expired cards