retention-analysis
# retention-analysis This Claude Code skill structures retention analysis and churn investigation for product teams by diagnosing why users leave and identifying what drives long-term engagement. Use it when analyzing user retention curves, investigating churn rates, measuring DAU/MAU ratios, or building retention improvement plans. It produces a retention snapshot with root cause hypotheses, aha-moment correlations identifying early predictive behaviors, and prioritized interventions based on segmented cohort analysis and inflection point identification rather than generic recommendations.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/retention-analysis && cp -r /tmp/retention-analysis/plugins/pm-analytics/skills/retention-analysis ~/.claude/skills/retention-analysisSKILL.md
# Retention Analysis Skill Diagnose why users leave, identify what keeps them, and recommend specific, testable interventions — not vague "improve onboarding" suggestions. ## Retention Fundamentals **The retention curve has two components:** 1. **Steepness of initial drop** (D1–D7) — onboarding problem 2. **Long-term floor level** — product-market fit indicator A product with PMF has a retention curve that flattens. If it trends to zero, you have a PMF problem, not an onboarding problem. Name this distinction explicitly. --- ## Retention Metrics Definitions | Metric | Formula | What It Tells You | |---|---|---| | D1 Retention | Users who return on day 2 ÷ new users day 1 | Quality of first experience | | D7 Retention | Users active on day 8 ÷ users who joined 7 days ago | Early habit formation | | D30 Retention | Users active on day 31 ÷ users who joined 30 days ago | Product-market fit signal | | DAU/MAU Ratio | Daily active users ÷ monthly active users | Stickiness (>20% good, >50% excellent) | | Churn Rate | Users lost in period ÷ users at start of period | Monthly or annual | | Net Revenue Retention | MRR at end of period ÷ MRR at start (same cohort) | Revenue health including expansion | --- ## Retention Investigation Framework ### Step 1: Segment the problem Don't analyse "retention" — analyse retention for specific cohorts: - New vs returning users - Paid vs free - Acquisition channel (organic vs paid vs referral) - Onboarding path completed vs not - Feature usage (power users vs lurkers) ### Step 2: Find the inflection points Where does the drop happen? D1? D7? Month 3? - D1 drop → First session experience - D7 drop → Habit loop not formed - D30 drop → Value not delivered at depth - Month 3+ drop → Boredom, competition, or lifecycle event ### Step 3: Identify the "aha moment" correlation Which early behaviour predicts long-term retention? - Run correlation: users who did [X] in first 7 days vs 30-day retention - Common patterns: connected an integration, invited a teammate, completed a core action N times ### Step 4: Qualify the churn Interview churned users — never skip this. Survey data alone is insufficient. - "What was the trigger that led you to cancel/stop?" - "What were you trying to accomplish that you couldn't?" - "What would need to change for you to come back?" --- ## Output Format ### Retention Analysis — [Product/Segment] — [Date] **Question:** [Specific retention question being answered] **Period Analysed:** [Date range] **Segment:** [Which users] --- **Current Retention Snapshot:** | Metric | Current | Industry Benchmark | Status | |---|---|---|---| | D1 Retention | [X%] | 25–40% | 🔴/🟡/🟢 | | D7 Retention | [X%] | 10–25% | 🔴/🟡/🟢 | | D30 Retention | [X%] | 5–15% | 🔴/🟡/🟢 | | DAU/MAU | [X%] | 10–20% typical | 🔴/🟡/🟢 | **Retention Curve Shape:** [Flattening / Still declining / Trending to zero] **PMF Signal:** [Strong / Weak / Absent — based on curve shape] --- **Root Cause Hypotheses:** | Hypothesis | Evidence | Confidence | Test | |---|---|---|---| | [Cause] | [Data point] | H/M/L | [How to validate] | **"Aha Moment" Correlation:** Users who [specific action] in first [N] days retain at [X%] vs [Y%] for those who don't. --- **Recommended Interventions:** | Intervention | Target Drop | Expected Lift | Effort | Priority | |---|---|---|---|---| | [Specific change] | D1 / D7 / D30 | [X%] | S/M/L | 1/2/3 | **Monitoring Plan:** - Metric to track: [X] - Review cadence: [Weekly / Monthly] - Alert threshold: [If X drops below Y, investigate immediately] --- ## Required Inputs Ask the user for these if not provided: - **Product and business model** (SaaS / consumer app / marketplace / other) - **Current retention metrics** (D1, D7, D30 if available) - **Segment to analyse** (all users / paid / free / a specific cohort) - **Key question to answer** (why is retention dropping? what drives retention?) - **Available data** (analytics events, churn surveys, interview notes) ## Quality Checks - [ ] Retention curve shape is diagnosed (flattening vs trending to zero = PMF vs onboarding) - [ ] Cohorts are segmented before analysis (not all users lumped together) - [ ] "Aha moment" correlation is identified or flagged as unknown - [ ] Interventions are specific (not "improve onboarding") - [ ] Churned user interviews are recommended (not just data analysis) - [ ] Monitoring plan includes an alert threshold ## Anti-Patterns - [ ] Do not recommend "improve onboarding" without specifying what specific step to change and why - [ ] Do not analyse retention without segmenting by cohort — aggregate retention curves hide cohort-specific patterns - [ ] Do not treat DAU/MAU below 5% as a retention problem — at that level, it is a product-market fit problem - [ ] Do not skip qualitative research — churned user interviews reveal reasons that quantitative data cannot - [ ] Do not set a monitoring alert without specifying the threshold that triggers it ## Guidelines - Never recommend "improve onboarding" without specifying *what* to change and *why* - Benchmark against industry — consumer apps, SaaS, and marketplaces have very different retention norms - If DAU/MAU is below 5%, that's a PMF conversation, not a retention tactics conversation - Always recommend talking to churned users — no amount of data replaces understanding the *reason*
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.