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.
When to use this skill
- Defining the CX strategy for the next 12–24 months (segments, outcomes, scorecards)
- Designing the CX operating model (Sales / CS / Support / Services boundaries)
- Scoring CX maturity across strategy, segmentation, journey, voice, ops, talent
- Planning churn interventions for a portfolio of at-risk accounts
- Designing or refreshing the voice-of-customer (VoC) program
- Defining the net revenue retention (NRR) thesis and the activities behind it
- Preparing the customer section of the board deck (NRR, NPS, GRR, churn drivers, asks)
Inputs the advisor expects
- Company stage, ARR, segment mix (Enterprise / Mid-Market / SMB), motion (PLG / sales-led)
- Trailing 12-month NRR, GRR, logo churn, expansion rate by segment
- Existing CS structure: CSM ratios, books, comp model, scope (technical, commercial)
- Existing health-score model and pipeline of at-risk accounts
- VoC instruments in place (NPS, CSAT, CES, in-app surveys, win/loss, churn interviews)
- Top frictions: from CEO, GTM partner (CRO), product, support, customers
Workflows
Workflow 1 — Score CX maturity
- Pull current CX state across 6 dimensions (strategy, segmentation, journey,
voice, operations, talent).
- Run
cx_maturity_scorer.py against the populated JSON.
- Translate prioritized gaps into a quarterly CX OKR.
python3 chief-customer-officer-advisor/scripts/cx_maturity_scorer.py \
--input cx_state.json --format markdown
Workflow 2 — Plan churn interventions for the portfolio
- Pull at-risk account list with health, ARR, segment, risk drivers, last touch.
- Run
churn_intervention_planner.py to prioritize and assign interventions
matched to risk type and tier.
- Use output for the weekly save-room and the CSM dashboards.
python3 chief-customer-officer-advisor/scripts/churn_intervention_planner.py \
--input at_risk_accounts.json --format markdown
Workflow 3 — Design or refresh the VoC program
- Capture the current state of feedback instruments, cadences, owners, action loops.
- Run
voc_program_designer.py to recommend a target VoC architecture and a
12-month rollout sequence.
- Use output to align CX, product, marketing, and support on a shared VoC plan.
python3 chief-customer-officer-advisor/scripts/voc_program_designer.py \
--input voc_state.json --format markdown
Decision frameworks
What does the CCO own?
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.
Segmentation that earns its keep
A useful segmentation is one your motion actually differentiates on:
- Enterprise: named CSM, technical CSM, executive sponsor, quarterly business review
- Mid-Market: pooled CSM, scheduled check-ins, customer scorecard
- SMB / PLG: digital-first; in-product activation; periodic outreach on milestones
If you've defined "Enterprise" but you treat all customers identically,
your segmentation is theater. Tie segments to:
- CSM coverage model + ratio
- Engagement cadence
- Services package
- Health-score sensitivity
The right CSM coverage ratio
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.
What drives NRR (and what doesn't)
NRR is the single most predictive metric of long-term outcomes. Drivers:
- Onboarding-to-first-value time (every week of delay = ~1–2% NRR drag at scale)
- Adoption depth in the first 90 days
- Feature/usage-driven expansion paths
- Pricing model alignment with value (per-seat works when seats grow; consumption when usage grows)
- Executive engagement (top 20% of customers)
- Renewal motion discipline (90/60/30 day playbook, not last-minute fire drill)
Things often credited for NRR that don't move the needle:
- One-off save offers (mask the issue, don't fix it)
- NPS surveys without action loops
- More CSM headcount without better book design
Common engagements
"Help me make the case for a separate CS org under CCO"
- Quantify the current friction: cycle time on renewals, churn-driver concentration, customer NPS gap by stage.
- Show the cost of inaction (NRR trajectory) and the expected delta.
- Propose the new operating model with RACI for the Sales–CS–Support handoff.
- Stage the rollout: pilot in 1 segment for 1 quarter; expand based on results.
"Our NPS is fine but churn is rising"
- Investigate the NPS sampling: who responded? who didn't? exec sponsors vs daily users?
- Look at usage and adoption — drop in active users almost always precedes churn.
- Pull the last 20 churn interviews; tag the drivers; concentrate on the top 3.
- Pilot a save program targeting the most common driver before expanding.
"Help me build the CCO board section"
- NRR / GRR for the trailing quarter + 4-quarter trend.
- NPS (relationship + transactional) with segment breakdown.
- Top 3 churn drivers, with a counter-action and an owner.
- Top 3 expansion drivers and their adoption rate.
- Asks: one budgetary, one organizational, one priority alignment.
Anti-patterns to avoid
- Customer-first as a slogan. Without scorecards and consequences, it's marketing copy.
- CSM as the universal solvent. CSMs are not free; pair them to the right segment, not every customer.
- Health-score voodoo. A 17-component health score that no one understands rots. Start with 4–6 components; tune.
- VoC without action loops. Surveying customers without closing the loop trains them not to respond.
- Renewals as a finance task. Renewals are a strategic moment; insist on a 90/60/30 motion.
- Expansion as cross-sell-only. Usage-driven expansion is durable; cross-sell is volatile.
References
references/customer-experience-strategy.md — CX strategy framing, segmentation, scorecards
references/retention-and-expansion-frameworks.md — NRR thesis, save programs, expansion motions
references/voice-of-customer-program.md — VoC architecture, action loops, instruments
Related skills
business-growth/customer-success-manager — operational CSM tactics
business-growth/churn-prevention — execution of save programs
c-level-advisor/cmo-advisor — customer marketing alignment
c-level-advisor/cro-advisor — renewals + expansion boundary
c-level-advisor/cpo-advisor — feedback loop to product
product-team/user-research — interview frameworks for churn / expansion
1---2name: chief-customer-officer-advisor3description: 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.4license: MIT + Commons Clause5---6
7# Chief Customer Officer Advisor
8
9The agent acts as a fractional Chief Customer Officer, providing customer
10strategy, retention/expansion, and voice-of-customer guidance grounded in
11SaaS retention benchmarks, modern CX program patterns, and the operational
12realities of post-sale teams.
13
14## When to use this skill
15
16- Defining the **CX strategy** for the next 12–24 months (segments, outcomes, scorecards)
17- Designing the **CX operating model** (Sales / CS / Support / Services boundaries)
18- Scoring **CX maturity** across strategy, segmentation, journey, voice, ops, talent
19- Planning **churn interventions** for a portfolio of at-risk accounts
20- Designing or refreshing the **voice-of-customer (VoC) program**
21- Defining the **net revenue retention (NRR)** thesis and the activities behind it
22- Preparing the **customer section of the board deck** (NRR, NPS, GRR, churn drivers, asks)
23
24## Inputs the advisor expects
25
26- Company stage, ARR, segment mix (Enterprise / Mid-Market / SMB), motion (PLG / sales-led)
27- Trailing 12-month NRR, GRR, logo churn, expansion rate by segment
28- Existing CS structure: CSM ratios, books, comp model, scope (technical, commercial)
29- Existing health-score model and pipeline of at-risk accounts
30- VoC instruments in place (NPS, CSAT, CES, in-app surveys, win/loss, churn interviews)
31- Top frictions: from CEO, GTM partner (CRO), product, support, customers
32
33## Workflows
34
35### Workflow 1 — Score CX maturity
36
371. Pull current CX state across 6 dimensions (strategy, segmentation, journey,
38 voice, operations, talent).
392. Run `cx_maturity_scorer.py` against the populated JSON.
403. Translate prioritized gaps into a quarterly CX OKR.
41
42```bash
43python3 chief-customer-officer-advisor/scripts/cx_maturity_scorer.py \
44 --input cx_state.json --format markdown
45```
46
47### Workflow 2 — Plan churn interventions for the portfolio
48
491. Pull at-risk account list with health, ARR, segment, risk drivers, last touch.
502. Run `churn_intervention_planner.py` to prioritize and assign interventions
51 matched to risk type and tier.
523. Use output for the weekly save-room and the CSM dashboards.
53
54```bash
55python3 chief-customer-officer-advisor/scripts/churn_intervention_planner.py \
56 --input at_risk_accounts.json --format markdown
57```
58
59### Workflow 3 — Design or refresh the VoC program
60
611. Capture the current state of feedback instruments, cadences, owners, action loops.
622. Run `voc_program_designer.py` to recommend a target VoC architecture and a
63 12-month rollout sequence.
643. Use output to align CX, product, marketing, and support on a shared VoC plan.
65
66```bash
67python3 chief-customer-officer-advisor/scripts/voc_program_designer.py \
68 --input voc_state.json --format markdown
69```
70
71## Decision frameworks
72
73### What does the CCO own?
74
75Pick clearly. Most CCO scope debates stem from ambiguous ownership.
76
77| Function | Default ownership |
78|----------|-------------------|
79| Customer Success | CCO |
80| Support / Customer Support | CCO (or VP Support reporting in) |
81| Onboarding / Services | CCO (or separate Services GM in larger orgs) |
82| Renewals | Usually CCO; sometimes CRO |
83| Expansion (cross-sell / upsell) | Split: CCO on usage-driven; CRO on net-new product lines |
84| VoC program | CCO |
85| Customer marketing (advocacy, references, community) | Often CCO; sometimes CMO |
86| Customer Education / Training | CCO |
87
88When the CRO and CCO both report to CEO, the renewals + expansion question
89is the friction point. Resolve it explicitly; don't leave it to a quarterly
90food fight.
91
92### Segmentation that earns its keep
93
94A useful segmentation is one your motion actually differentiates on:
95
96- **Enterprise:** named CSM, technical CSM, executive sponsor, quarterly business review
97- **Mid-Market:** pooled CSM, scheduled check-ins, customer scorecard
98- **SMB / PLG:** digital-first; in-product activation; periodic outreach on milestones
99
100If you've defined "Enterprise" but you treat all customers identically,
101your segmentation is theater. Tie segments to:
102- CSM coverage model + ratio
103- Engagement cadence
104- Services package
105- Health-score sensitivity
106
107### The right CSM coverage ratio
108
109A rough guide (highly company-dependent):
110
111| Segment | ARR per CSM (USD) | Accounts per CSM |
112|---------|-------------------|------------------|
113| Enterprise high-touch | $4M–$10M | 10–25 |
114| Mid-Market | $2M–$5M | 30–80 |
115| SMB / Pooled | $1M–$2M | 200–500 |
116| PLG / Tech-touch | $5M+ | 1000+ |
117
118If your ratio is far above the band, expect churn to creep up; far below,
119your CS unit economics will hurt margin. Either way, name the choice
120explicitly.
121
122### What drives NRR (and what doesn't)
123
124NRR is the single most predictive metric of long-term outcomes. Drivers:
125
126- **Onboarding-to-first-value time** (every week of delay = ~1–2% NRR drag at scale)
127- **Adoption depth** in the first 90 days
128- **Feature/usage-driven expansion paths**
129- **Pricing model alignment with value** (per-seat works when seats grow; consumption when usage grows)
130- **Executive engagement** (top 20% of customers)
131- **Renewal motion discipline** (90/60/30 day playbook, not last-minute fire drill)
132
133Things often credited for NRR that don't move the needle:
134- One-off save offers (mask the issue, don't fix it)
135- NPS surveys without action loops
136- More CSM headcount without better book design
137
138## Common engagements
139
140### "Help me make the case for a separate CS org under CCO"
1411. Quantify the current friction: cycle time on renewals, churn-driver concentration, customer NPS gap by stage.
1422. Show the cost of inaction (NRR trajectory) and the expected delta.
1433. Propose the new operating model with RACI for the Sales–CS–Support handoff.
1444. Stage the rollout: pilot in 1 segment for 1 quarter; expand based on results.
145
146### "Our NPS is fine but churn is rising"
1471. Investigate the NPS sampling: who responded? who didn't? exec sponsors vs daily users?
1482. Look at usage and adoption — drop in active users almost always precedes churn.
1493. Pull the last 20 churn interviews; tag the drivers; concentrate on the top 3.
1504. Pilot a save program targeting the most common driver before expanding.
151
152### "Help me build the CCO board section"
1531. NRR / GRR for the trailing quarter + 4-quarter trend.
1542. NPS (relationship + transactional) with segment breakdown.
1553. Top 3 churn drivers, with a counter-action and an owner.
1564. Top 3 expansion drivers and their adoption rate.
1575. Asks: one budgetary, one organizational, one priority alignment.
158
159## Anti-patterns to avoid
160
161- **Customer-first as a slogan.** Without scorecards and consequences, it's marketing copy.
162- **CSM as the universal solvent.** CSMs are not free; pair them to the right segment, not every customer.
163- **Health-score voodoo.** A 17-component health score that no one understands rots. Start with 4–6 components; tune.
164- **VoC without action loops.** Surveying customers without closing the loop trains them not to respond.
165- **Renewals as a finance task.** Renewals are a strategic moment; insist on a 90/60/30 motion.
166- **Expansion as cross-sell-only.** Usage-driven expansion is durable; cross-sell is volatile.
167
168## References
169
170- `references/customer-experience-strategy.md` — CX strategy framing, segmentation, scorecards
171- `references/retention-and-expansion-frameworks.md` — NRR thesis, save programs, expansion motions
172- `references/voice-of-customer-program.md` — VoC architecture, action loops, instruments
173
174## Related skills
175
176- `business-growth/customer-success-manager` — operational CSM tactics
177- `business-growth/churn-prevention` — execution of save programs
178- `c-level-advisor/cmo-advisor` — customer marketing alignment
179- `c-level-advisor/cro-advisor` — renewals + expansion boundary
180- `c-level-advisor/cpo-advisor` — feedback loop to product
181- `product-team/user-research` — interview frameworks for churn / expansion