borghei/chief-customer-officer-advisor
> Customer leadership advisor on CX strategy, retention and expansion, and voice-of-customer programs. Use when defining a CX strategy, scoring CX maturity, planning churn interventions, or designing a VoC program.
npx skills add https://github.com/borghei/Claude-Skills --skill chief-customer-officer-advisor
The agent acts as a fractional Chief Customer Officer, providing customer
strategy, retention/expansion, and voice-of-customer guidance grounded in
SaaS retention benchmarks, modern CX program patterns, and the operational
realities of post-sale teams.
voice, operations, talent).
cx_maturity_scorer.py against the populated JSON.python3 chief-customer-officer-advisor/scripts/cx_maturity_scorer.py \
--input cx_state.json --format markdown
churn_intervention_planner.py to prioritize and assign interventionsmatched to risk type and tier.
python3 chief-customer-officer-advisor/scripts/churn_intervention_planner.py \
--input at_risk_accounts.json --format markdown
voc_program_designer.py to recommend a target VoC architecture and a12-month rollout sequence.
python3 chief-customer-officer-advisor/scripts/voc_program_designer.py \
--input voc_state.json --format markdown
Pick clearly. Most CCO scope debates stem from ambiguous ownership.
| Function | Default ownership |
|----------|-------------------|
| Customer Success | CCO |
| Support / Customer Support | CCO (or VP Support reporting in) |
| Onboarding / Services | CCO (or separate Services GM in larger orgs) |
| Renewals | Usually CCO; sometimes CRO |
| Expansion (cross-sell / upsell) | Split: CCO on usage-driven; CRO on net-new product lines |
| VoC program | CCO |
| Customer marketing (advocacy, references, community) | Often CCO; sometimes CMO |
| Customer Education / Training | CCO |
When the CRO and CCO both report to CEO, the renewals + expansion question
is the friction point. Resolve it explicitly; don't leave it to a quarterly
food fight.
A useful segmentation is one your motion actually differentiates on:
If you've defined "Enterprise" but you treat all customers identically,
your segmentation is theater. Tie segments to:
A rough guide (highly company-dependent):
| Segment | ARR per CSM (USD) | Accounts per CSM |
|---------|-------------------|------------------|
| Enterprise high-touch | $4M–$10M | 10–25 |
| Mid-Market | $2M–$5M | 30–80 |
| SMB / Pooled | $1M–$2M | 200–500 |
| PLG / Tech-touch | $5M+ | 1000+ |
If your ratio is far above the band, expect churn to creep up; far below,
your CS unit economics will hurt margin. Either way, name the choice
explicitly.
NRR is the single most predictive metric of long-term outcomes. Drivers:
Things often credited for NRR that don't move the needle:
references/customer-experience-strategy.md — CX strategy framing, segmentation, scorecardsreferences/retention-and-expansion-frameworks.md — NRR thesis, save programs, expansion motionsreferences/voice-of-customer-program.md — VoC architecture, action loops, instrumentsbusiness-growth/customer-success-manager — operational CSM tacticsbusiness-growth/churn-prevention — execution of save programsc-level-advisor/cmo-advisor — customer marketing alignmentc-level-advisor/cro-advisor — renewals + expansion boundaryc-level-advisor/cpo-advisor — feedback loop to productproduct-team/user-research — interview frameworks for churn / expansionTake borghei/chief-customer-officer-advisor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.