skills/strategies/launch/retention/SKILL.md
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
npx skillsauth add kostja94/marketing-skills retention-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guides customer retention and churn prevention. Acquiring new customers costs 5–25× more than retaining; 5% retention improvement can increase profitability 25–95%. Use this skill when reducing churn, building retention programs, or identifying at-risk customers.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 4 (Audience), 9 (Documentation).
Identify:
| Type | Share | Causes | |------|-------|--------| | Voluntary | 60–80% | Pricing, missing features, poor onboarding, relationship | | Involuntary | 20–40% | Payment failures, expired cards, billing |
Predictability: Most churn is predictable 30–90 days before cancellation via behavioral signals.
| Approach | Conversion | |----------|------------| | Reactive (after cancel) | 15–20% | | Proactive (before decision) | 60–80% |
Move from lagging indicator to early warning systems.
| Strategy | Use | |----------|-----| | Health scoring | Behavioral + transactional + relationship signals | | Loyalty programs | 5–15 percentage point retention lift | | Segmentation | Predictive modeling for at-risk | | Onboarding | Prevent low value realization early | | Dunning | Retry logic; pre-expiry card updates for involuntary |
| Dimension | Use | |-----------|-----| | Product value | Registration; feature usage; payment | | Marketing value | Testimonials; customer stories; webinar guests; feedback, bug reports, feature requests | | Feedback analysis | Email, community, reviews—AI-assisted analysis; prioritize by impact; route to product vs ops |
Avoid: Treating users only as MAU/registration denominators. See creator-program for creator ecosystem.
Retention occurs after conversion; ongoing investment in customer success, not isolated campaigns. Map touchpoints: onboarding → adoption → expansion → renewal.
testing
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
development
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
testing
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.