Syntic

Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

C-Level AdvisoryFree Safe

chief-customer-officer-advisor

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when designing retention strategy, decomposing GRR vs NRR, segmenting customers for differential investment, sizing a CS team's coverage model, or sequencing CS/AM/Support hires.

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md
---
name: chief-customer-officer-advisor
description: Use when designing retention strategy, decomposing GRR vs NRR, segmenting customers for differential investment, sizing a CS team's coverage model, or sequencing CS/AM/Support hires.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# Chief Customer Officer Advisor

Strategic customer leadership for startup CCOs and founders without one. Four decisions, no generic CS survey:

1. **What's our retention architecture — and is gross retention vs NRR honest?** — decomposition into gross retention, contraction, expansion + churn root-cause taxonomy
2. **How do we segment customers for differential investment?** — tier design + ICP fit scoring
3. **What's the CS team's coverage model, and when do we go pooled vs named?** — coverage ratio math + transition thresholds
4. **What CS role do we hire next?** — stage-to-role map (CS ≠ Support ≠ AM ≠ Implementation)

This is strategic guidance only — not tactical CS implementation (health-score tooling, CRM workflows, NPS survey infrastructure, onboarding automation); route those to the relevant execution teammate.

## Keywords
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, 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, implementation manager, CS operations, book of business, ARR-per-CSM, customer marketing, advocacy, voice of customer

## Key Questions (ask first)
- What's your GROSS retention rate? (Not NRR — NRR hides churn behind expansion. Ask gross first.)
- What's the #1 reason customers leave? (If you can't name it, you don't understand churn.)
- What's the median time-to-value (TTV) by segment? Long TTV in a low tier signals misfit; in a high tier, broken onboarding.
- Which customer would you fire today? ("None" means your segmentation is broken — some accounts cost more than they earn.)
- What's your ARR-per-CSM ratio, and is the model pooled or named?
- Is CS in your comp plan, distinct from Sales comp? Misalignment is a leading indicator of failure.

## 1. Retention Decomposition

**The trap:** "Our NRR is 115%, retention is great." 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.

**Decompose 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 |

Decompose cohort data quarter-by-quarter to separate GRR, logo retention, NRR, contraction, and expansion, then categorize churn against a 7-category root-cause taxonomy (e.g., product gap, poor onboarding, champion turnover, budget cut, competitive loss, pricing mismatch, support failure) to find the top leakage points.

## 2. Customer Segmentation

**The trap:** "Every customer is important." Reality: customers sit on a spectrum of ICP fit × strategic value. Treating them identically wastes CS capacity and misses 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 |

Score customers against an ICP-fit rubric plus current/potential ARR to assign tiers, flag customers below the investment floor for the kill list, and set differential investment per tier.

## 3. CS Team Coverage Model

**The trap:** one ratio ("one CSM per X customers") across all segments. Reality: the right model depends on segment, ACV, and complexity.

| Model | Best for | Ratio (ARR-per-CSM) | Trade-offs |
|---|---|---|---|
| Tech-touch (no human) | SMB, low ACV | $5M-15M+ | Automation cost; can't 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 |

Calculate required CSM headcount per segment from book composition and the ratio table, then flag the pooled-to-named transition threshold and when a manager layer is warranted.

## 4. CS Team Org Evolution

**Wrong question:** "CSM or Support engineer?" **Right question:** "What customer outcome are we failing to deliver, and what role unblocks it?"

| 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 |

## Workflows

**Quarterly retention review (~4 hours):** pull 8 quarters of cohort data, decompose GRR/NRR/contraction/expansion separately, for any cohort with GRR < 90% assign a churn root cause from the taxonomy, check the expansion math and product gaps with the relevant teammates, output top-3 leakage points + a 90-day mitigation plan.

**Customer segmentation audit (~1 day):** score the customer base against ARR + tenure + ICP-fit signals, identify tier migrations and the kill list, output new tier assignments + investment-per-tier for sales review.

**CS team sizing (~1 week):** build the current + planned book composition, calculate required CSM headcount per segment, compare to current team, check comp/leveling and cost with the relevant teammates, output a 12-month hiring plan.

**CS team roadmap (~1 week):** list the top 5 customer outcomes the company is failing to deliver, map each to the role that unblocks it (CSM/AM/IM/Support/CS Ops), sequence hires respecting prerequisite order.

## Output Standards
```
**Bottom Line:** [one sentence — decision and rationale]
**The Decision:** [retention | segmentation | coverage | next hire]
**The Evidence:** [numbers, not adjectives]
**How to Act:** [3 concrete next steps]
**Your Decision:** [the call only the founder can make]
```

## Disclaimer
Retention benchmarks vary significantly by ACV, segment, and industry. This is B2B SaaS-baseline guidance; consumer SaaS, marketplaces, and hardware have materially different retention math.

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

  1. 1. Create a dedicated folder for this skill in your local skills library.
  2. 2. Place SKILL.md into that folder.
  3. 3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

  1. 1. Save SKILL.md in your local Syntic Code skills directory.
  2. 2. Keep related files in the same skill folder.
  3. 3. Run in a safe environment and validate outputs.

Source

https://github.com/alirezarezvani/claude-skills/blob/main/c-level-advisor/chief-customer-officer-advisor/skills/chief-customer-officer-advisor/SKILL.md

Open Source Link
C-Level Advisory

Related Skills