跳到正文
cccskills
免费在 GitHub 公开

cco-review

Review customer retention and customer success plans through six focused questions. Examine churn causes, customer segments, staffing capacity, hiring, and compensation, then produce a decision report with a verdict and three concrete next steps.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.

查看安装方法

适用场景

  • Investigating declining customer retention
  • Reviewing a proposed customer success team expansion
  • Reassessing customer segments and service levels
  • Checking customer success hiring and compensation plans

包含的文件(1)

  • SKILL.md5.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

/cs:cco-review — CCO Forcing Questions

Command: /cs:cco-review <plan>

The retention-obsessed CCO pressure-tests any plan that touches customer experience. Six questions before any retention claim, segmentation change, CS team expansion, or major CS hire.

When to Run

  • Before any board narrative that includes a retention number
  • Before approving a CS team headcount expansion
  • Before re-segmenting the customer base or changing tier definitions
  • Before launching a customer marketing or advocacy program
  • Before a major CS hire (CSM, AM, Implementation, Customer Marketing)
  • When NRR is "great" but churn complaints from CSMs are increasing
  • Before deciding whether to add an AM role separate from CSM

The Six CCO Questions

1. What's the GROSS retention rate?

Not NRR. Gross. NRR can hide a leaky bucket behind expansion.

  • GRR healthy ≥ 90% at growth stage, ≥ 95% at scale
  • If GRR < 85% but NRR > 100%, the product is failing for 15%+ of customers; expansion is masking the failure
  • Run retention_decomposition_analyzer.py

2. What's the #1 reason customers leave?

If you can't name it, you don't understand churn.

  • 7-category taxonomy: product_fit / competitor_loss / no_value_realized / pricing / champion_left / company_event / tactical_failure
  • Preventable churn = product_fit + no_value_realized + tactical_failure
  • If preventable > 50%, CS has clear leverage; if < 30%, churn is structural (ICP, market, competition)

3. What's the median time-to-value (TTV) by segment?

Long TTV signals different problems by segment.

  • Long TTV in low tier = ICP misfit; downgrade or kill
  • Long TTV in high tier = onboarding broken; fix the Implementation Manager handoff
  • TTV is a leading indicator of GRR

4. Which customer would you fire today?

If "none" — your segmentation is broken.

  • Some accounts cost more than they earn (support cost > 50% of ARR + low ICP fit)
  • Run customer_segmentation_designer.py to surface kill list
  • The 3 paths for kill candidates: non-renewal / downgrade-to-tech-touch / raise-price-to-cost-recover

5. What's the ARR-per-CSM ratio, and is the model pooled or named?

Wrong model wastes capacity.

  • Strategic: named + exec sponsor, $300K-$1M ARR/CSM
  • Enterprise: named, $500K-$2M
  • Mid-market: pooled, $2M-$5M
  • SMB: tech-touch, $5M+
  • Run cs_coverage_calculator.py to size the team

6. Is CS in your comp plan, and how is it different from Sales comp?

Misalignment is the leading indicator of CS failure.

  • CS comp: 70/30 base/variable typical
  • Variable: 50% gross retention + 30% net retention + 20% activity
  • Anti-pattern: comp CSMs on NPS — they game it
  • Anti-pattern: comp CSMs same as Sales — they sell instead of serve

Workflow

# 1. Retention decomposition (always start here)
python ../../../c-level-advisor/skills/chief-customer-officer-advisor/scripts/retention_decomposition_analyzer.py cohorts.json

# 2. Segmentation audit
python ../../../c-level-advisor/skills/chief-customer-officer-advisor/scripts/customer_segmentation_designer.py customers.json

# 3. Coverage sizing (if making CS team changes)
python ../../../c-level-advisor/skills/chief-customer-officer-advisor/scripts/cs_coverage_calculator.py book.json

Output Format

# CCO Review: <plan>
**Date:** YYYY-MM-DD

## The Decision Being Made
[one sentence — retention | segmentation | coverage | next hire]

## Retention (if applicable)
- GRR: X% (vs vanity NRR of Y%)
- Top churn driver: <category> at X% of churn
- Preventable churn: X% (CS-controllable)
- Leaky-bucket pattern? yes/no

## Segmentation (if applicable)
- Tier distribution: Strategic X / Enterprise X / Mid-market X / SMB X
- Kill list size: N customers (X% of customers, Y% of ARR)
- Upgrade candidates: N

## Coverage (if applicable)
- Current CSMs: N | Required now: M | Required 12mo: P
- Annual cost (12mo): $X
- Manager trigger fired: yes/no

## Org (if applicable)
- Next hire: <CSM | Support | AM | IM | CS Ops | Customer Marketing>
- Why this, not the alternative: <one line>
- Customer outcome unblocked: <specific>

## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK

## Next Steps
[3 concrete actions]

Routing

  • /cs:cpo-review — if churn root cause is product_fit or no_value_realized
  • /cs:cro-review — if expansion math or comp alignment is in question
  • /cs:cfo-review — for CS cost commitments and retention-impact-on-revenue
  • cs-chro-advisor agent — for CS hires, comp, ladder
  • /cs:decide — log the verdict
  • /cs:freeze 30 — on multi-year CS comp plan changes

Related


Version: 1.0.0

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

中文简介正在准备中。当前显示英语简介。

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills2.8万2026年8月30日 更新

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

中文简介正在准备中。当前显示英语简介。

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills2.8万2026年8月30日 更新

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

中文简介正在准备中。当前显示英语简介。

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills2.8万2026年8月30日 更新

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

中文简介正在准备中。当前显示英语简介。

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills2.8万2026年8月30日 更新

aeo

免费

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

中文简介正在准备中。当前显示英语简介。

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills2.8万2026年8月30日 更新

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

中文简介正在准备中。当前显示英语简介。

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills2.8万2026年8月30日 更新

查看 alirezarezvani 的全部技能

报告此技能的问题