cco-review

Pressure-tests customer retention, segmentation, and CS team plans using six Chief Customer Officer questions.

25.3k|3.6k|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/alirezarezvani/claude-skills --skill cco-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cco-review
Source: https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cco-review
Command: npx skills add https://github.com/alirezarezvani/claude-skills --skill cco-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retention claims, CS headcount requests, and customer segmentation changes often reach leadership without rigorous scrutiny, letting vanity NRR metrics hide gross retention leaks and mis-sized CS teams. This Skill applies a Chief Customer Officer's interrogation framework to any plan touching customer experience before it is approved.

Core Features & Use Cases

  • Six-Question CCO Framework: Challenges gross retention rate, top churn driver, time-to-value by segment, customer kill list, ARR-per-CSM coverage model, and CS comp plan alignment.
  • Retention Decomposition: Separates gross retention from NRR to expose leaky-bucket patterns where expansion masks product failure, using a 7-category churn taxonomy to distinguish preventable from structural churn.
  • Coverage and Org Sizing: Evaluates named vs pooled vs tech-touch CS models against ARR-per-CSM benchmarks and identifies the next correct CS hire (CSM, AM, IM, CS Ops, or Customer Marketing).
  • Use Case: Before approving a plan to hire five new CSMs, run the review to check whether GRR justifies expansion, whether segmentation is broken, and whether the coverage model matches the customer tiers.

Quick Start

Run /cs:cco-review on your customer success hiring plan to pressure-test the retention assumptions and team sizing before approval.

Frequently Asked Questions about cco-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pressure-test a customer success hiring plan?

Run the CCO review on the plan to check gross retention rate, ARR-per-CSM coverage ratios, and whether the next hire should be a CSM, AM, Implementation Manager, or CS Ops role. It returns a ship, sharpen, or block verdict with concrete next steps.

What is the difference between gross retention and net revenue retention?

Gross retention rate measures revenue kept excluding expansion, while NRR includes upsells that can mask churn. If GRR is below 85% but NRR exceeds 100%, expansion is hiding a leaky bucket where the product fails a significant share of customers.

How do I identify which customers to fire or downgrade?

Use the segmentation audit to surface accounts where support cost exceeds 50% of ARR combined with low ICP fit. Kill candidates have three paths: non-renewal, downgrade to tech-touch, or raising price to recover cost.

What ARR-per-CSM ratio should my CS team target?

Benchmarks vary by segment: strategic accounts use named CSMs at $300K-$1M ARR each, enterprise at $500K-$2M, mid-market pooled at $2M-$5M, and SMB tech-touch above $5M. The coverage calculator sizes the team against these ranges.

When should I not rely on NRR as a retention metric?

Avoid relying on NRR when gross retention is slipping, because expansion revenue from healthy accounts conceals churn in failing segments. Always decompose retention into gross and expansion components before making board-level retention claims.