chief-customer-officer-advisor

# 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

1. Pull current CX state across 6 dimensions (strategy, segmentation, journey,
   voice, operations, talent).
2. Run `cx_maturity_scorer.py` against the populated JSON.
3. Translate prioritized gaps into a quarterly CX OKR.

```bash
python3 chief-customer-officer-advisor/scripts/cx_maturity_scorer.py \
  --input cx_state.json --format markdown
```

### Workflow 2 — Plan churn interventions for the portfolio

1. Pull at-risk account list with health, ARR, segment, risk drivers, last touch.
2. Run `churn_intervention_planner.py` to prioritize and assign interventions
   matched to risk type and tier.
3. Use output for the weekly save-room and the CSM dashboards.

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

1. Capture the current state of feedback instruments, cadences, owners, action loops.
2. Run `voc_program_designer.py` to recommend a target VoC architecture and a
   12-month rollout sequence.
3. Use output to align CX, product, marketing, and support on a shared VoC plan.

```bash
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"
1. Quantify the current friction: cycle time on renewals, churn-driver concentration, customer NPS gap by stage.
2. Show the cost of inaction (NRR trajectory) and the expected delta.
3. Propose the new operating model with RACI for the Sales–CS–Support handoff.
4. Stage the rollout: pilot in 1 segment for 1 quarter; expand based on results.

### "Our NPS is fine but churn is rising"
1. Investigate the NPS sampling: who responded? who didn't? exec sponsors vs daily users?
2. Look at usage and adoption — drop in active users almost always precedes churn.
3. Pull the last 20 churn interviews; tag the drivers; concentrate on t