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.
What this skill does
# 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: 1. **Churn type**: Voluntary (active cancel) vs involuntary (payment failure) 2. **Signals**: Login frequency, feature usage, support tickets 3. **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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".