Help us improve
Share bugs, ideas, or general feedback.
From chief-customer-officer-advisor
Chief Customer Officer advisory for startups: retention decomposition (gross retention vs NRR honesty, churn root-cause taxonomy), customer segmentation strategy (differential investment across tiers + ICP fit scoring), CS team coverage model (pooled vs named CSM thresholds + ratio math), and CS team org evolution (CS vs Support vs AM distinctions). Use when designing retention strategy, segmenting customers for differential investment, sizing CS team, or sequencing CS hires. Strategic only — does not duplicate engineering/business-growth tactical skills.
npx claudepluginhub ciciliaeth/claude-skills --plugin chief-customer-officer-advisorHow this skill is triggered — by the user, by Claude, or both
Slash command
/chief-customer-officer-advisor:chief-customer-officer-advisorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Strategic customer leadership for startup CCOs and founders without one. **Four decisions, no generic CS survey:**
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Creates, reads, edits, and analyzes .docx files using docx-js for new documents, pandoc for text extraction, Python scripts for XML unpacking/validation/changes, and LibreOffice for conversions.
Share bugs, ideas, or general feedback.
Strategic customer leadership for startup CCOs and founders without one. Four decisions, no generic CS survey:
This skill does not cover tactical CS implementation. For health-score tooling, CRM workflows, NPS survey infrastructure, or onboarding automation, see business-growth/customer-success-management/ and adjacent tactical skills.
CCO, chief customer officer, customer success, retention strategy, gross retention, net retention, NRR, GRR, logo retention, dollar retention, churn, contraction, expansion, downsell, customer lifetime value, CLV, LTV, time-to-value, TTV, time-to-first-value, customer health score, NPS, CSAT, customer effort score, segmentation, ICP fit, tier design, low-touch, high-touch, tech-touch, pooled CSM, named CSM, customer success manager, account manager, AM, implementation manager, IM, customer success operations, CS ops, book of business, ratio, ARR-per-CSM, customer marketing, advocacy, expansion playbook, voice of customer, VoC
# Decision A: Decompose retention honestly
python scripts/retention_decomposition_analyzer.py # embedded B2B SaaS sample
python scripts/retention_decomposition_analyzer.py path/to/cohorts.json
# Decision B: Design customer segmentation + differential investment
python scripts/customer_segmentation_designer.py # embedded 4-tier sample
python scripts/customer_segmentation_designer.py path/to/customers.json
# Decision C: Calculate CS team coverage model
python scripts/cs_coverage_calculator.py # embedded 350-customer sample
python scripts/cs_coverage_calculator.py path/to/book.json
The trap: "Our NRR is 115%, retention is great."
The truth: NRR = Gross Retention − Contraction + Expansion. A 115% NRR with 85% gross retention is a leaky bucket masked by upsells. A 115% NRR with 98% gross retention is a healthy product.
Mandatory decomposition every quarter:
| Metric | What it measures | Health threshold (B2B SaaS) |
|---|---|---|
| Gross Retention (GRR) | $ from existing customers minus churn + contraction | ≥ 90% at growth stage; ≥ 95% at scale |
| Logo Retention | % of customers who renewed | ≥ 85% at growth; ≥ 90% at scale |
| Net Revenue Retention (NRR) | GRR + expansion | ≥ 110% at growth; ≥ 120% at scale |
| Contraction | $ from existing customers reducing seats/usage | < 5% annually |
| Expansion | $ from existing customers growing | 15-25% annually at healthy |
Run retention_decomposition_analyzer.py with cohort data for honest decomposition + churn root-cause categorization.
See references/retention_decomposition.md for the 7-category churn taxonomy + leading indicator playbook.
The trap: "Every customer is important."
The reality: customers exist on a spectrum of ICP fit × strategic value. Treating them identically wastes CS capacity and ignores expansion opportunity.
4-tier framework (B2B SaaS baseline):
| Tier | ARR range | Coverage | Investment per account/yr |
|---|---|---|---|
| Strategic | Top 5%, often $100K+ | Named CSM + executive sponsor | $20K-50K |
| Enterprise | Next 15-20%, $20K-100K | Named CSM | $5K-15K |
| Mid-market | Next 30-40%, $5K-20K | Pooled CSM + automation | $1K-3K |
| SMB / Long-tail | Bottom 40-50%, <$5K | Tech-touch + self-serve | $50-500 |
Run customer_segmentation_designer.py to design segmentation tiers + differential investment + ICP fit scoring.
See references/customer_segmentation_strategy.md for ICP fit framework, tier transition triggers, and the kill list (customers below the investment floor).
The trap: "Hire one CSM per X customers" with a single ratio across all segments.
The reality: coverage model depends on segment, ACV, and complexity. Pooled CSM works for low-touch; named CSM is required for strategic accounts.
Coverage models:
| Model | Best for | Ratio (ARR-per-CSM) | Trade-offs |
|---|---|---|---|
| Tech-touch (no human) | SMB, low ACV | $5M-15M+ | Automation cost; cannot save high-stakes deals |
| Pooled CSM | Mid-market | $2M-5M | Lower cost; less account intimacy |
| Named CSM | Enterprise | $500K-2M | Higher cost; deeper relationships |
| Named CSM + exec sponsor | Strategic | $300K-1M | Highest cost; reserved for top accounts |
Run cs_coverage_calculator.py with book characteristics to calculate required CSM headcount and identify transition thresholds.
See references/cs_coverage_model.md for ratios, ramp curves, and the "when to add a manager" trigger.
The wrong question: "Should we hire a CSM or a Support engineer?" The right question: "What's the next customer outcome we're failing to deliver, and what role unblocks that?"
Critical distinctions (founders confuse these):
| Role | Owns | Does NOT own |
|---|---|---|
| Customer Support | Reactive issue resolution (ticket queue) | Renewal, expansion, success outcomes |
| Customer Success Manager | Proactive value realization + renewal + expansion lead | Day-to-day tickets, implementation |
| Account Manager | Commercial relationship + expansion close | Day-to-day success, technical depth |
| Implementation Manager | Onboarding + go-live | Ongoing success after launch |
| CS Operations | Tooling, data, analytics, playbooks | Direct customer relationships |
| Customer Marketing | Advocacy, case studies, references | 1:1 customer relationships |
See references/cs_team_org_evolution.md for stage-to-role map (seed → late-stage) + the AM-vs-CSM split decision.
Goal: Decompose retention honestly + identify top-3 churn drivers.
# 1. Pull cohort data: closed/won by quarter for last 8 quarters
python scripts/retention_decomposition_analyzer.py cohorts.json
# 2. Review GRR / NRR / contraction / expansion separately
# 3. For each cohort showing GRR < 90%: identify churn root cause (7-category taxonomy)
# 4. Cross-check with cs-cro-advisor: does the expansion math add up?
# 5. Cross-check with cs-cpo-advisor: are product gaps driving churn?
# 6. Output: top-3 leakage points + 90-day mitigation plan
Goal: Re-segment customer base + reset differential investment.
# 1. Build customers.json with ARR, tenure, ICP fit signals
python scripts/customer_segmentation_designer.py customers.json
# 2. Identify segment migration (mid-market → enterprise upgrades, downsells)
# 3. Identify kill list (customers below investment floor)
# 4. Output: new tier assignment + investment-per-tier + kill list for sales review
Goal: Size the CS team aligned to book composition + coverage model.
# 1. Build book.json with current customer base + planned acquisition
python scripts/cs_coverage_calculator.py book.json
# 2. Calculate required CSM headcount by segment
# 3. Compare to current team; identify gaps
# 4. Cross-check with cs-chro-advisor on comp + leveling
# 5. Cross-check with cs-cfo-advisor on the cost
# 6. Output: 12-month hiring plan + role sequence
Goal: Sequence next 18 months of CS hires aligned to customer outcomes.
**Bottom Line:** [one sentence — decision and rationale]
**The Decision:** [one of: retention | segmentation | coverage | next hire]
**The Evidence:** [numbers from the tool, not adjectives]
**How to Act:** [3 concrete next steps]
**Your Decision:** [the call only the founder can make]
../cro-advisor/ — Revenue math, NRR, expansion comp (CCO owns customer experience; CRO owns revenue math; clean split)../cpo-advisor/ — Product strategy, JTBD (CCO surfaces product gaps; CPO decides roadmap)../cmo-advisor/ — Customer marketing, advocacy, references../cfo-advisor/ — CS team cost, retention-impact-on-revenue math../chro-advisor/ — CS team hiring + leveling../../../business-growth/ — Tactical CS execution: health scores, CRM workflows, onboarding toolingVersion: 1.0.0 Status: Production Ready Disclaimer: Retention benchmarks vary significantly by ACV, segment, and industry. This skill provides B2B SaaS-baseline guidance; consumer SaaS, marketplaces, and hardware all have materially different retention math.