retention-strategy
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.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- retention-strategy
- metadata
- { "version": "1.1.1" }
- description
- 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.
03 SKILL.md 正文
Strategies: Retention
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.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 4 (Audience), 9 (Documentation).
Identify:
- Churn type: Voluntary (active cancel) vs involuntary (payment failure)
- Signals: Login frequency, feature usage, support tickets
- Stage: Onboarding, expansion, renewal
Churn Types
| 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.
Proactive vs Reactive
| Approach | Conversion |
|---|---|
| Reactive (after cancel) | 15–20% |
| Proactive (before decision) | 60–80% |
Move from lagging indicator to early warning systems.
Retention Strategies
| 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 |
User Value & Feedback
| 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.
Lifecycle Integration
Retention occurs after conversion; ongoing investment in customer success, not isolated campaigns. Map touchpoints: onboarding → adoption → expansion → renewal.
Output Format
- Churn analysis (voluntary vs involuntary; signals)
- Retention tactics (by stage)
- Health score framework (if applicable)
- Intervention playbook (at-risk triggers)
Related Skills
- email-marketing: Onboarding sequences; win-back campaigns
- pmf-strategy: Retention as PMF signal; churn as anti-signal
- cold-start-strategy: First users; differs from retention
- analytics-tracking: Usage data; churn signals
- traffic-analysis: Attribution; retention cohort analysis
04 同仓库更多 Skills
youtube
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY/SOLID/YAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs /plan-eng-review as an independent double-check before execution.
worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
validate-idea
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.