[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792W2C80ECEEMYRZF6A5FNW":3,"skill-same:01M792W2C80ECEEMYRZF6A5FNW":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M792W2C80ECEEMYRZF6A5FNW","retention",null,"Cut churn with cancel flows, save offers, dunning, exit surveys and account health signals. Use when diagnosing churn, building retention loops, or cohort analysis.","poorvith-mp\u002Fskills-marketing","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792P4C4Z12T0V4B97Z9MNX3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fretention\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: retention\nlast_reviewed: 2026-09-06\ngroup: Lifecycle\ndescription: >-\n  Cut churn with cancel flows, save offers, dunning, exit surveys and account health signals. Use\n  when diagnosing churn, building retention loops, or cohort analysis.\n---\n\n# retention\n\n## Core Philosophy\nCustomer acquisition without retention is a treadmill to company failure. If you lose 5% of your customer base each month, you must replace 46% of your revenue every year just to stay flat. True retention is not achieved through aggressive cancellation barriers; it is driven by deep workflow habituation, early proactive health monitoring, dynamic save offers, and automated involuntary churn recovery.\n\n---\n\n## 4-Step Retention Engineering Framework\n\n### Step 1: Churn Taxonomy & Telemetry Instrumentation\n1. **Classify Churn Sources**:\n   - *Involuntary Churn (Payment Failures)*: Typically 20–40% of total SaaS churn (expired cards, bank declines, fraud flags).\n   - *Voluntary Churn (Cancellations)*: Customers actively requesting account closure or subscription termination.\n2. **Cohort Retention Curves**:\n   - Plot user and revenue retention by signup cohort across Months 1, 3, 6, 12.\n   - Benchmark against target: Healthy B2B SaaS requires $> 85\\%$ annual logo retention and $> 105\\%$ Net Revenue Retention (NRR).\n3. **Health Score Signals**:\n   - Calculate composite account health scores (0–100):\n     - Frequency of key action execution (e.g. 5 team logins\u002Fweek).\n     - Integration connectivity status (e.g. webhook still active).\n     - Support ticket volume and sentiment.\n     - Drop in daily active usage $> 40\\%$ over 14 days flags account as \"At Risk\".\n\n### Step 2: Automated Involuntary Churn Recovery (Dunning)\n1. **Pre-Dunning Notifications**:\n   - Detect cards expiring within 14 days and prompt update via in-app banner.\n2. **Smart Retries & Cadence**:\n   - Use smart retry logic (Stripe Smart Retries or exponential retry on days 1, 3, 5, 8).\n   - Retry during standard banking business hours (9:00 AM local time).\n3. **Communication Sequence**:\n   - *Day 1*: Subtle in-app notification: \"Update payment method to maintain uninterrupted service.\"\n   - *Day 3*: Email 1 (Transactional & polite): \"Payment issue with your account.\"\n   - *Day 7*: Email 2 (Urgent): \"Service interruption scheduled in 48 hours.\"\n   - *Day 14*: Account moves to grace period (read-only mode, data preserved for 30 days).\n\n### Step 3: Cancellation Flow & Dynamic Save Strategy\n1. **Friction-Free Cancellation with Data Gathering**:\n   - Never force users to call or email support to cancel; self-serve cancellation is mandatory.\n   - Multi-step structured exit survey:\n     - 1. Reason for leaving (Pricing, Missing Feature, Project Finished, Bugs, Switching to Competitor).\n     - 2. Specific qualitative feedback input.\n2. **Dynamic Save Offers (Reason-Matched)**:\n   - *Finished Project \u002F Seasonal*: Offer 1-click subscription pause for 1–3 months (freezing billing, saving data).\n   - *Too Expensive*: Offer a temporary 50% discount for 3 months or automated downgrade to a lower tier.\n   - *Missing Feature*: Connect instantly with a technical founder or route to roadmap voter.\n3. **Graceful Exit**:\n   - Confirm cancellation immediately, email receipt, and outline export\u002Fdata-retention timelines (e.g., \"Your data is safe for 60 days\").\n\n### Step 4: Executive Re-Engagement & Win-Back Loops\n1. **Champion Turnover Protocol**:\n   - Monitor key account executive bounce backs (e.g., primary contact left the company).\n   - Automatically trigger an executive check-in to secondary admins.\n2. **Win-Back Cadence**:\n   - Re-contact canceled accounts 60–90 days post-churn only when a major feature they explicitly requested is deployed to production.\n\n---\n\n## Deliverable Format: Retention Playbook & Dunning Matrix (`RETENTION-PLAYBOOK.md`)\n\n```markdown\n# Retention & Churn Reduction Playbook: [Product Name]\n\n## 1. Baseline Metrics & Churn Diagnostics\n- **Monthly Gross Logo Churn**: [Current %] (Target: \u003C 1.5%)\n- **Net Revenue Retention (NRR)**: [Current %] (Target: > 110%)\n- **Involuntary vs Voluntary Ratio**: [Split, e.g. 35% involuntary \u002F 65% voluntary]\n\n## 2. Involuntary Churn Dunning Sequence\n| Day | Trigger Event | Channel | Action \u002F Copy Message |\n|---|---|---|---|\n| Day 0 | Initial Charge Decline | Webhook | Retry in 24h; silent |\n| Day 1 | Second Decline | In-App Banner | \"Please update billing info\" |\n| Day 4 | Third Decline | Email 1 | \"Payment failed - update card\" |\n| Day 8 | Fourth Decline | Email 2 + In-App Modal | \"Account locking in 48 hours\" |\n| Day 14 | Final Failure | System | Soft downgrade to Read-Only |\n\n## 3. Self-Serve Cancellation Flow & Save Logic\n- **Exit Survey Options**: [List of 5 core reasons]\n- **Dynamic Save Offers**:\n  - If *Pricing*: Offer [Pause for 60 days \u002F 50% off 2 months]\n  - If *Technical Bug*: Prompt [Instant priority ticket to engineering]\n- **Data Retention Period**: [e.g. 60 days post-cancellation]\n\n## 4. Account Health Scoring Rubric\n- **Green (Score 80-100)**: [Specific usage thresholds]\n- **Yellow (Score 50-79)**: [Action drop triggers]\n- **Red (Score \u003C 50)**: [Trigger automated CSM check-in]\n```\n\n---\n\n## Worked Example: SaaS Churn Intervention\n\n- **Diagnosis**: 40% of churn cited \"temporary reduction in project volume\".\n- **Intervention**: Added a 1-click \"Pause Account for 60 Days\" option in the cancellation flow.\n- **Result**: 31% of users who clicked cancel selected the Pause option instead; 64% of paused accounts resumed billing after 60 days, cutting gross monthly churn from 4.8% to 3.2%.\n\n---\n\n## Verification Checklist\n\n- [ ] Self-serve cancellation is available in-app with zero mandatory sales calls.\n- [ ] Dunning sequence includes automated smart card retries and multi-touch email notifications.\n- [ ] Canceled users are offered a 1-click Pause option rather than binary account deletion.\n- [ ] Telemetry tracks at least 3 early health degradation signals (e.g. login drop, webhook failures).\n- [ ] Data retention and export guidelines are explicitly stated upon cancellation confirmation.\n\n---\n\n## Anti-Patterns\n\n- **Roach Motel Cancellation**: Hiding the cancellation button or requiring phone calls during business hours.\n- **Immediate Data Destruction**: Purging user data the second a subscription is canceled, destroying win-back potential.\n- **Ignoring Involuntary Churn**: Blaming product-market fit when 30% of cancellations are simply expired credit cards.\n","# retention\n\n## Core Philosophy\nCustomer acquisition without retention is a treadmill to company failure. If you lose 5% of your customer base each month, you must replace 46% of your revenue every year just to stay flat. True retention is not achieved through aggressive cancellation barriers; it is driven by deep workflow habituation, early proactive health monitoring, dynamic save offers, and automated involuntary churn recovery.\n\n---\n\n## 4-Step Retention Engineering Framework\n\n### Step 1: Churn Taxonomy & Telemetry Instrumentation\n1. **Classify Churn Sources**:\n   - *Involuntary Churn (Payment Failures)*: Typically 20–40% of total SaaS churn (expired cards, bank declines, fraud flags).\n   - *Voluntary Churn (Cancellations)*: Customers actively requesting account closure or subscription termination.\n2. **Cohort Retention Curves**:\n   - Plot user and revenue retention by signup cohort across Months 1, 3, 6, 12.\n   - Benchmark against target: Healthy B2B SaaS requires $> 85\\%$ annual logo retention and $> 105\\%$ Net Revenue Retention (NRR).\n3. **Health Score Signals**:\n   - Calculate composite account health scores (0–100):\n     - Frequency of key action execution (e.g. 5 team logins\u002Fweek).\n     - Integration connectivity status (e.g. webhook still active).\n     - Support ticket volume and sentiment.\n     - Drop in daily active usage $> 40\\%$ over 14 days flags account as \"At Risk\".\n\n### Step 2: Automated Involuntary Churn Recovery (Dunning)\n1. **Pre-Dunning Notifications**:\n   - Detect cards expiring within 14 days and prompt update via in-app banner.\n2. **Smart Retries & Cadence**:\n   - Use smart retry logic (Stripe Smart Retries or exponential retry on days 1, 3, 5, 8).\n   - Retry during standard banking business hours (9:00 AM local time).\n3. **Communication Sequence**:\n   - *Day 1*: Subtle in-app notification: \"Update payment method to maintain uninterrupted service.\"\n   - *Day 3*: Email 1 (Transactional & polite): \"Payment issue with your account.\"\n   - *Day 7*: Email 2 (Urgent): \"Service interruption scheduled in 48 hours.\"\n   - *Day 14*: Account moves to grace period (read-only mode, data preserved for 30 days).\n\n### Step 3: Cancellation Flow & Dynamic Save Strategy\n1. **Friction-Free Cancellation with Data Gathering**:\n   - Never force users to call or email support to cancel; self-serve cancellation is mandatory.\n   - Multi-step structured exit survey:\n     - 1. Reason for leaving (Pricing, Missing Feature, Project Finished, Bugs, Switching to Competitor).\n     - 2. Specific qualitative feedback input.\n2. **Dynamic Save Offers (Reason-Matched)**:\n   - *Finished Project \u002F Seasonal*: Offer 1-click subscription pause for 1–3 months (freezing billing, saving data).\n   - *Too Expensive*: Offer a temporary 50% discount for 3 months or automated downgrade to a lower tier.\n   - *Missing Feature*: Connect instantly with a technical founder or route to roadmap voter.\n3. **Graceful Exit**:\n   - Confirm cancellation immediately, email receipt, and outline export\u002Fdata-retention timelines (e.g., \"Your data is safe for 60 days\").\n\n### Step 4: Executive Re-Engagement & Win-Back Loops\n1. **Champion Turnover Protocol**:\n   - Monitor key account executive bounce backs (e.g., primary contact left the company).\n   - Automatically trigger an executive check-in to secondary admins.\n2. **Win-Back Cadence**:\n   - Re-contact canceled accounts 60–90 days post-churn only when a major feature they explicitly requested is deployed to production.\n\n---\n\n## Deliverable Format: Retention Playbook & Dunning Matrix (`RETENTION-PLAYBOOK.md`)\n\n```markdown\n# Retention & Churn Reduction Playbook: [Product Name]\n\n## 1. Baseline Metrics & Churn Diagnostics\n- **Monthly Gross Logo Churn**: [Current %] (Target: \u003C 1.5%)\n- **Net Revenue Retention (NRR)**: [Current %] (Target: > 110%)\n- **Involuntary vs Voluntary Ratio**: [Split, e.g. 35% involuntary \u002F 65% voluntary]\n\n## 2. Involuntary Churn Dunning Sequence\n| Day | Trigger Event | Channel | Action \u002F Copy Message |\n|---|---|---|---|\n| Day 0 | Initial Charge Decline | Webhook | Retry in 24h; silent |\n| Day 1 | Second Decline | In-App Banner | \"Please update billing info\" |\n| Day 4 | Third Decline | Email 1 | \"Payment failed - update card\" |\n| Day 8 | Fourth Decline | Email 2 + In-App Modal | \"Account locking in 48 hours\" |\n| Day 14 | Final Failure | System | Soft downgrade to Read-Only |\n\n## 3. Self-Serve Cancellation Flow & Save Logic\n- **Exit Survey Options**: [List of 5 core reasons]\n- **Dynamic Save Offers**:\n  - If *Pricing*: Offer [Pause for 60 days \u002F 50% off 2 months]\n  - If *Technical Bug*: Prompt [Instant priority ticket to engineering]\n- **Data Retention Period**: [e.g. 60 days post-cancellation]\n\n## 4. Account Health Scoring Rubric\n- **Green (Score 80-100)**: [Specific usage thresholds]\n- **Yellow (Score 50-79)**: [Action drop triggers]\n- **Red (Score \u003C 50)**: [Trigger automated CSM check-in]\n```\n\n---\n\n## Worked Example: SaaS Churn Intervention\n\n- **Diagnosis**: 40% of churn cited \"temporary reduction in project volume\".\n- **Intervention**: Added a 1-click \"Pause Account for 60 Days\" option in the cancellation flow.\n- **Result**: 31% of users who clicked cancel selected the Pause option instead; 64% of paused accounts resumed billing after 60 days, cutting gross monthly churn from 4.8% to 3.2%.\n\n---\n\n## Verification Checklist\n\n- [ ] Self-serve cancellation is available in-app with zero mandatory sales calls.\n- [ ] Dunning sequence includes automated smart card retries and multi-touch email notifications.\n- [ ] Canceled users are offered a 1-click Pause option rather than binary account deletion.\n- [ ] Telemetry tracks at least 3 early health degradation signals (e.g. login drop, webhook failures).\n- [ ] Data retention and export guidelines are explicitly stated upon cancellation confirmation.\n\n---\n\n## Anti-Patterns\n\n- **Roach Motel Cancellation**: Hiding the cancellation button or requiring phone calls during business hours.\n- **Immediate Data Destruction**: Purging user data the second a subscription is canceled, destroying win-back potential.\n- **Ignoring Involuntary Churn**: Blaming product-market fit when 30% of cancellations are simply expired credit cards.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Lifecycle",1788652800000,"main","e9ea1069b8d051ec6f88c3bdc4290183b8e68c94","skills\u002Fretention","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:44",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add poorvith-mp\u002Fskills-marketing --skill retention",{"tool":41,"command":42},"bunx","bunx skills add poorvith-mp\u002Fskills-marketing --skill retention",{"tool":44,"command":45},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-marketing --skill retention","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fretention\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Frouting.yaml","REFERENCE","参考文档",960,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fretention\u002Fevals\u002Frouting.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"retention.skill","OTHER","其他",3827,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fretention\u002Fretention.skill",[62,69,75,81,88,94],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M792Y3WSAZ5ABHX58QPMWXMH","youtube-clipper","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M792Y1ABERS38QWQCJ9CKWJB","youtube-b-roll-maker","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-b-roll-maker\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M792XZCWKZV16GNK3QQR9M2X","x-twitter-intelligence-analyst","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-intelligence-analyst\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M792XTYRW8ZSHPSPVMK301QW","visual-assets","Generate on-brand images: OG cards, blog heroes, social graphics and mockups. Use when creating Open Graph cards, hero visuals, or brand graphics.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-assets\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M792XR5BZ510MFZETMPAAJBW","viral-hook-generator","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fviral-hook-generator\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M792XPJB02Q3HQTKKYZTKJ8A","video-script-writer","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-script-writer\u002FSKILL.md",[],[]]