Skip to content

borghei/Claude-Skills / c-level-advisor/chief-customer-officer-advisor

chief-customer-officer-advisor

Verified

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.

references/customer-experience-strategy.md

View on GitHub
# Customer Experience Strategy Reference

Practical reference for shaping a CX strategy that drives NRR and reduces
churn — without becoming a slogan.

## 1. What a CCO actually owns

The CCO mandate varies by company. Be explicit about which version you have:

| Flavor | Primary mandate | Common scope |
|--------|-----------------|---------------|
| **Retention CCO** | Keep customers from leaving | CS, Support, Renewals |
| **Growth CCO** | Drive NRR through expansion | CS, Renewals, Expansion, Customer Marketing |
| **Experience CCO** | Cross-functional CX | All post-sale + journey ownership across sales/marketing/product |
| **Services CCO** | Implementation + outcomes | Services, Onboarding, CS, Education |

Most early-stage SaaS companies need a Retention CCO. Most growth-stage
PLG companies need an Experience CCO. Most enterprise software companies
need either a Growth or Services CCO.

## 2. What a credible CX strategy answers

1. **What customer outcome are we accountable for?** (Not "great experience" — specific outcomes)
2. **How is the customer base segmented and what does each segment get?**
3. **What's the operating model?** (CS + Support + Services boundaries)
4. **What's the NRR thesis and how do we execute it?**
5. **What's the VoC architecture and action-loop discipline?**
6. **How is the CX function instrumented and measured?**
7. **What does success look like in 12 months?** (3–5 KPIs, attributable)

If "great customer experience" appears anywhere, replace it with the
specific outcome you mean.

## 3. The customer outcomes you can actually pursue

For each segment, pick one or two primary outcomes:

- **Time to first value** (median days from contract to first usable result)
- **Adoption depth** (% of paid seats / features active monthly)
- **Customer-defined success** (custom outcome per account from contract or onboarding)
- **Renewal probability** (proxy: health score)
- **Expansion probability** (proxy: usage-based signals)
- **Reference / advocacy capacity** (NPS promoters who'll act)

Choose outcomes that:
- Are measurable from the data you already have
- The customer themselves cares about
- The CX team has levers to move

## 4. Segmentation that drives operating model

A useful segmentation differentiates how you serve, not just how you bill.

| Tier | ARR band | Touch model | Owner |
|------|----------|-------------|-------|
| Strategic / Top 20 | Largest deals + lighthouse logos | Named CSM, executive sponsor, technical resources | Senior CSM |
| Enterprise | Mid-six to seven figures | Named CSM, QBR, professional services | CSM |
| Mid-Market | Mid-five to mid-six | Pooled / shared CSM, scheduled outreach | Pooled CSM |
| SMB | Small-five to mid-five | Tech-touch with periodic human escalation | Tech-touch team |
| PLG / Self-serve | < $5K ACV | Digital-first, in-product | PLG ops |

Match coverage to economics: an enterprise CSM costs $200K–$300K fully
loaded — they have to drive at least 5x in retention + expansion to make sense.

## 5. Outcome scorecards per segment

Different segments deserve different scorecards. Suggested templates:

### Strategic / Enterprise
- Executive sponsor engaged in last 90 days?
- Onboarding milestones met on time?
- Adoption depth ≥ target?
- QBR conducted in current quarter?
- Customer-defined success metric trending positively?
- NPS ≥ benchmark from key personas?

### Mid-Market
- Adoption depth ≥ target?
- Health score in green band?
- Renewal on track (≥120 days out from renewal date)?
- Expansion conversation initiated when usage triggers fire?

### SMB / PLG
- Activation milestones met within X days?
- Active in last 30 days?
- Renewed automatically without intervention?
- In-product behavior consistent with healthy cohort?

## 6. The customer journey — what to map and what to skip

A practical customer journey has 5 to 7 stages. Common picks:

1. **Prospect** (Marketing) — not your stage
2. **Buy** (Sales) — handoff is yours
3. **Onboard** — fastest path to first value
4. **Adopt** — depth across features and use cases
5. **Renew** — execute the renewal motion
6. **Expand** — usage / cross-sell
7. **Advocate** — references, community, case studies

For each stage:
- Who owns the customer experience?
- What's the success criterion for the stage?
- What instrumentation tells you it happened?
- What's the handoff to the next stage?

Skip:
- 60-stage journey maps that no one updates
- Personas without behavioral data
- "Moments of truth" without a metric attached

## 7. KPIs (pick 3–5 for the board)

### Tier 1 — non-negotiable
- **Net Revenue Retention (NRR)** — TTM, by segment
- **Gross Revenue Retention (GRR)** — TTM, by segment
- **Logo churn rate** — TTM, by segment
- **Net Promoter Score (NPS)** — relationship + segment

### Tier 2 — directional
- **Customer health distribution** (red/yellow/green %)
- **Time to first value** (median + P75)
- **Adoption depth** (% of seats active in 30 days)
- **Renewal motion adherence** (% of renewals worked at 90/60/30 day cadence)

### Tier 3 — operational
- **Save rate** in at-risk save room
- **Expansion ARR per quarter**
- **CSM ratio** (ARR per CSM, accounts per CSM)
- **Support CSAT / first response / resolution time**

### Avoid
- Vanity metrics with no action loop
- Composite "customer score" that buries underlying signals
- NPS without segmentation

## 8. The CX operating model — RACI

For each customer-facing activity, name the owner. Common splits:

| Activity | R | A | C | I |
|----------|---|---|---|---|
| Onboarding success | CS Lead | CCO | Sales, Services | CRO, CPO |
| Renewal cycle | Renewals / CSM | CCO | Sales | CRO, CFO |
| Expansion (usage-led) | CSM | CCO | Sales | CRO, CPO |
| Expansion (cross-sell new product) | Account Manager | CRO | CSM | CCO |
| Support escalations | Support lead | CCO | Engineering | CTO |
| VoC program | Head of CX Ops | CCO | Product, Marketing | CEO |
| Customer advocacy / references | Customer Marketing | CCO or CMO | CSM, Sales | CMO |

If you don't have a written RACI, you have a turf war waiting to happen.

## 9. Common operating-model failures

- **CS and Sales fight over renewals.** Pick: same person who sold owns renewal? Or separate renewals team owns it? Either works; in-between doesn't.
- **CSMs become unpaid AEs.** If CSMs carry expansion quota, the CS function is now a sales function. That's fine — name it.
- **Support reports to engineering.** Often a sign of cost-control bias; CX suffers.
- **Services as a profit center conflicting with onboarding speed.** Resolve: services as enabler (charged at cost) or as a margin business (charged at market). Don't pretend both.

## 10. CX strategy in 90/180/360

**Day 0–90 — Listen and align**
- Customer listening tour: 20+ structured interviews across segments
- Pull existing data: NRR, GRR, NPS, churn drivers, save rates, CSM ratios
- Publish the customer health rubric (interim) and the segment definitions
- Ratify the CX strategy with CEO and CRO; resolve renewals + expansion boundary

**Day 91–180 — Instrument and standardize**
- Implement (or refresh) the health score; calibrate to actual outcomes
- Stand up the save room; define the playbook
- Roll out the VoC architecture v1; close the first loop with action
- Define the QBR + EBR standard; pilot in one segment

**Day 181–360 — Drive outcomes**
- Move NRR by 2–4 points in the first year (modest target; aggressive is rare)
- Publish customer outcomes scorecards by segment
- Build the customer advocacy bench (10–30 reference customers)
- Plan year 2 from instrumented baselines

## 11. Common executive frictions and the moves

| Friction | Move |
|----------|------|
| CRO wants renewals + expansion | Name the boundary explicitly; pick one model |
| Product team won't action customer feedback | Build the VoC action loop; track resolved-vs-rejected feedback rate |
| Support reports through engineering | Negotiate a dotted line to CCO; align KPIs |
| CFO wants to cut CS as a cost center | Show NRR drag from CSM-less segments; quantify |
| CSMs becoming demoralized | Compensation, book design, career path — usually it's book design |
| Board fixates on NPS | Pair NPS with adoption + retention; reframe |

## 12. Common pitfalls

- **"Customer-first" without scorecards.** Slogan with no teeth.
- **Onboarding owned by services as a profit center.** Misaligned incentives.
- **CSMs sized as if they're a free resource.** Math the ratio.
- **One health score across all segments.** Customize the model.
- **Save room without root-cause analysis.** You're treating symptoms.
- **No exec sponsorship of top-20 accounts.** A guaranteed source of preventable churn.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall