Communitygithub.com

cbrock84/retention

诊断并降低用户流失——包括取消流程、挽留优惠、支付失败恢复、流失风险检测以及背后的产品与服务原因。在流失率上升或原因不明时使用,用于设计取消或赢回流程、恢复非自愿流失、在用户离开前识别高风险账户,或判断流失问题是否为产品问题。

retention 是什么?

该技能提供了一套系统化的方法论,用于分析和减少用户流失(churn)。它首先强调区分非自愿流失(支付失败)和自愿流失(主动离开),并指出大多数公司忽略了通过简单的支付重试和邮件提醒即可挽回的非自愿流失收入。对于自愿流失,技能指导通过细分流失用户(按使用时长、套餐、渠道等)来定位根本原因,例如早期流失往往是激活问题而非留存问题。它提供了设计取消流程的最佳实践(如提供明确原因选项、根据原因定制挽留策略而非盲目打折)以及构建流失风险检测信号的方法(如使用率下降、支持工单升级等)。该技能适用于多种AI编程助手平台,如Claude Code、Cursor、Codex等,帮助开发者将留存问题从服务层面分离,识别产品或获客层面的根本缺陷,并避免常见的错误做法(如强行挽留、要求电话取消等)。

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

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

留存

首先区分两种流失

它们除了结果相同外毫无共同点,混淆它们会浪费精力:

  • 非自愿流失 — 支付失败。通常占总流失的很大比例,完全是机械性问题,且是整个业务中最廉价可修复的问题。
  • 自愿流失 — 用户主动选择离开。

先修复非自愿流失。在合理的日程上重试扣款、发送能触达真实用户的催款邮件、到期前提醒、以及不立即切断访问的宽限期。在大多数公司中,这笔可挽回的收入都被忽视。

诊断自愿流失

询问决策实际发生的时间点。它几乎从不发生在取消那一刻——而是早在几周前,源于一次未达成的期望、一个未解决的支持工单、或一位关键用户的离开。

按使用时长、套餐、获客渠道和激活状态对流失进行细分。集中度会告诉你原因:

  • 早期流失 — 是激活问题,而非留存问题。修复引导流程。
  • 续约时流失 — 价值不够明显,不足以证明续费合理性。
  • 特定事件后流失 — 找到该事件:价格变更、服务中断、界面改版、关键用户离开。
  • 集中在一个渠道的流失 — 是获客问题。你吸引了错误类型的用户,任何留存工作都无法修复。

取消流程

让取消操作简单直接。设置障碍会导致退单、公开投诉,并在越来越多的司法管辖区引发合规风险。

务必询问原因,提供具体选项加自由输入——这是你能获得的最高质量的产品反馈,来自没有理由客气的用户。

仅当挽留措施针对用户提供的具体原因时才提供。对因功能缺失而离开的用户提供折扣,相当于承认你没有倾听。暂停权限往往是更好的选择,却很少被提供。

风险检测

基于使用率下降、支持工单升级、关键用户沉默或席位减少等信号构建简单指标。然后在干预仍有可能时采取行动——一个无人执行的健康分指标只是一块仪表盘,而非一项计划。

绝对不要

  • 将一次被挽留的取消计为留存成功,而不检查用户是否在三个月后仍留存。
  • 在数据显示问题是产品或获客问题时,却将其当作服务问题处理。
  • 强制要求通过电话才能取消。

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.

相关技能