Cco Review

Pressure-tests plans affecting customer retention, segmentation, or CS team sizing by asking six forcing questions about gross retention, churn drivers, time-to-value, customer profitability, ARR-per-CSM ratios, and compensation alignment. Use before approving retention narratives, headcount changes, or major CS hires.

skills.sh installs: 380
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill cco-review --agent claude-code

Installs into .claude/skills of the current project.

Files

/c-level-agents:cco-review — CCO Forcing Questions

Command: /c-level-agents: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

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly