Communitygithub.com

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

retention 是什么?

retention is a Claude Code agent skill that diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

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

在你喜欢的 AI 中提问

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

文档

retention 是做什么的?

Separate the two churns first

They have nothing in common but the outcome, and conflating them wastes effort:

  • Involuntary — payment failed. Often a large share of total churn, entirely mechanical, and the cheapest thing to fix in the whole business.
  • Voluntary — they chose to leave.

Fix involuntary first. Card retries on a sensible schedule, dunning emails that reach a human, pre-expiry notification, and a grace period that does not immediately cut off access. This is recoverable revenue sitting untouched in most companies.

Diagnosing voluntary churn

Ask when the decision was actually made. It is almost never at cancellation — it is weeks earlier, at a failed expectation, an unresolved support issue, or a champion leaving.

Segment churn by tenure, plan, acquisition channel, and activation status. Concentrations tell you the cause:

  • Early churn — activation problem, not retention. Fix onboarding.
  • Churn at renewal — value not visible enough to justify the line item.
  • Churn after a specific event — find the event: a price change, an outage, a redesign, a champion departure.
  • Churn concentrated in one channel — an acquisition problem. You are buying the wrong customers, and no retention work fixes that.

Cancellation flow

Make canceling straightforward. Obstruction generates chargebacks, public complaints, and in a growing number of jurisdictions, regulatory exposure.

Do ask why, with specific options plus free text — this is the highest-quality product feedback you will ever receive, from people with no reason to be polite.

Offer a save only where it addresses the stated reason. A discount offered to someone leaving because a feature is missing confirms you were not listening. Pause is often the better offer and is rarely available.

At-risk detection

Build a simple signal from declining usage, a support escalation, a champion going quiet, or a seat count dropping. Then act on it while intervention is still possible — a health score nobody works is a dashboard, not a program.

Never

  • Count a saved cancellation as retained without checking whether they stayed a quarter later.
  • Treat retention as a service problem when the data says it is a product or acquisition problem.
  • Make cancellation require a phone call.

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.

相关技能