Communitygithub.com

cbrock84/retention

診斷並降低客戶流失率——涵蓋取消流程、挽留優惠、付款失敗復原、流失風險偵測,以及背後的產品與服務成因。當流失率上升或原因不明、需要設計取消或挽回流程、恢復非自願流失、在客戶離開前識別高風險帳戶,或判斷流失問題是否源於產品問題時,請使用此技能。

retention 是什麼?

此技能提供一套系統化方法,用於診斷並降低客戶流失率。它首先要求區分非自願流失(付款失敗)與自願流失(客戶選擇離開),並指出公司應優先修復非自願流失,因為它通常佔流失率很大比例,且修復成本最低。技能涵蓋自願流失的診斷方法,包括按使用時長、方案、獲取渠道和激活狀態進行分群,以找出根本原因(例如早期流失通常代表激活問題,而非保留問題)。它還詳細說明如何設計有效的取消流程(強調簡潔、收集高品質回饋、並根據原因提供有針對性的挽留方案)、被動流失恢復策略(智慧重試、催款郵件、寬限期),以及建立簡單的流失風險偵測信號(使用量下降、客服升級等)。此技能適用於 Claude Code、Copilot、Cline 等支援 Markdown 技能的 AI 代理平台,透過結構化指南幫助開發者和產品經理將抽象的流失問題轉化為具體、可行動的步驟。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/retention

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

retention 是做什麼的?

首先區分兩種流失

它們除了結果相同外毫無共同點,混為一談只會浪費精力:

  • 非自願 — 付款失敗。通常佔總流失率的很大比例,完全是機械性問題,而且是整個業務中最便宜的修復項目。
  • 自願 — 客戶選擇離開。

先修復非自願流失。按照合理的時間表進行信用卡重試、發送能觸達真人用戶的催款郵件、在到期前進行通知,以及提供不會立即停止服務的寬限期。這是大多數公司尚未觸及的、可回收的收入。

診斷自願流失

詢問客戶實際上是在何時做出離開決定的。這個決定幾乎從不在取消服務的那一刻做出——而是在幾週前,當一個期望落空、一個未解決的支援問題出現,或是一個關鍵支持者離開時就已經做出。

按使用時長、方案、獲取渠道和激活狀態對流失客戶進行分群。集中的流失率能告訴你原因:

  • 早期流失 — 激活問題,而非保留問題。修復入職流程。
  • 續約時流失 — 產品價值不足以證明其費用的合理性。
  • 特定事件後流失 — 找出該事件:價格變動、服務中斷、產品重新設計、關鍵支持者離職。
  • 集中在某個渠道的流失 — 獲取問題。你正在獲取錯誤的客戶,任何保留工作都無法解決這個問題。

取消流程

讓取消服務變得簡單直接。設置障礙會引發拒付(chargebacks)、公開投訴,並且在越來越多司法管轄區會帶來監管風險。

務必詢問原因,提供具體選項加上自由文字——這是你將收到的最高品質產品回饋,來自那些沒有理由禮貌的用戶。

僅在針對所述原因時才提供挽留方案。對於因缺少某個功能而離開的客戶提供折扣,只會確認你沒有在聽。暫停服務通常是更好的提議,但卻很少提供。

流失風險偵測

從使用量下降、客服升級、關鍵支持者變得安靜,或席位數量減少等跡象建立一個簡單的信號。然後在仍有可能進行干預時採取行動——一個沒有人跟進的健康分數只是一個儀表板,而不是一個計畫。

絕對不要

  • 在未檢查他們是否在一個季度後仍留下來的情況下,就將成功挽留的取消視為保留。
  • 在數據顯示這是產品或獲取問題時,卻將其視為服務問題來處理。
  • 要求取消服務必須透過電話進行。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/org-design

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/sales-enablement

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

cbrock84/visual-content

Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.

相關技能