borghei/Claude-Skills / c-level-advisor/chief-customer-officer-advisor
chief-customer-officer-advisor
VerifiedCustomer 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| references/customer-experience-strategy.md | markdown | 8.5 KB |
| references/retention-and-expansion-frameworks.md | markdown | 8.3 KB |
| references/voice-of-customer-program.md | markdown | 8.4 KB |
| scripts/churn_intervention_planner.py | script | 11.8 KB |
| scripts/cx_maturity_scorer.py | script | 15.8 KB |
| scripts/voc_program_designer.py | script | 11.1 KB |
references/voice-of-customer-program.md
View on GitHub# Voice of Customer (VoC) Program Reference
Practical reference for designing or refreshing a VoC program that actually
moves the product and customer outcomes — not one that just runs surveys.
## 1. What a VoC program is (and isn't)
VoC is the systematic capture, synthesis, and action on customer feedback
across the lifecycle. It is NOT:
- A standalone NPS dashboard
- An annual survey
- A product feedback inbox
- Customer marketing testimonials
A real VoC program has four pillars:
1. **Multi-channel capture** (survey + interview + behavioral + support + community)
2. **Synthesis** (themes, frequency, severity, segment)
3. **Action loop** (closure to customer + change in the business)
4. **Measurement** (was the action effective?)
## 2. VoC instruments — what each one is for
| Instrument | When | What it tells you |
|------------|------|-------------------|
| **NPS — relationship** | Quarterly | Long-term loyalty signal; segmentation insight |
| **NPS — transactional** | Post-event (onboarding, support, milestone) | Specific moment quality |
| **CSAT** | Post-interaction (ticket, training session) | Episode quality |
| **CES (Customer Effort Score)** | Post-task | Friction in specific workflow |
| **In-app micro-surveys** | Triggered (after feature use, after error) | Granular feature feedback |
| **Win/loss interview** | Within 30 days of close | Sales motion and product gaps |
| **Churn interview** | Within 30 days of cancellation | Why they left, structurally |
| **Renewal interview** | Pre/post renewal | Decision drivers, risks |
| **Health-score signals** | Continuous | Behavioral feedback (no asking required) |
| **Support ticket categories** | Continuous | Product friction taxonomy |
| **Community / forum posts** | Continuous | Voluntary qualitative |
| **Product analytics** | Continuous | Actual behavior; the loudest VoC |
| **Strategic interview / advisory board** | Quarterly | Top-account themes |
A mature program runs 6–10 of these in coordination. A starter program
runs 3–4 well.
## 3. The starter VoC stack
If you have nothing, start here:
1. **Relationship NPS quarterly** by segment
2. **Onboarding NPS** post-onboarding (transactional)
3. **Support CSAT** post-ticket
4. **Churn interview** every churned account > defined ACV
5. **Win/loss interview** for top-3 deals each quarter
6. **Quarterly synthesis report** to product, CS, marketing leadership
That's it. Layer in more once you've shown action discipline on these.
## 4. NPS — running it without making it cargo cult
NPS done badly is mostly noise. Done well, it's a leading indicator.
### Sampling rules
- Sample by **persona × segment**, not "the customer"
- Daily users + decision makers + technical buyers — they answer differently
- Cap the frequency: a customer sees NPS no more than 2x/year
- 30-day quiet period after a major incident or upset event
### Calculation
NPS = % promoters (9-10) − % detractors (0-6)
Reported as a number (e.g., +35), not a percentage.
### Segmentation
- By segment: Enterprise / Mid-Market / SMB
- By persona: admin / power user / executive
- By tenure: <90 days / 90 days – 1 year / 1 year+
- By product line (if multi-product)
- By region
A single company-wide NPS is decorative; segmented NPS is operational.
### Benchmarks (illustrative — your industry matters)
| Industry / segment | NPS bench | Top decile |
|--------------------|-----------|------------|
| Enterprise SaaS | +20 to +35 | +45+ |
| Mid-Market SaaS | +25 to +40 | +50+ |
| SMB SaaS | +15 to +30 | +45+ |
| Consumer SaaS | +30 to +50 | +60+ |
### Action thresholds
- Detractor (0–6): mandatory follow-up, structured root cause, response within 5 days
- Promoter (9–10): advocacy ask (case study, reference, referral)
- Passive (7–8): no action by default; sample for interviews
## 5. The interview program — where real signal lives
NPS gives you a number. Interviews give you why.
### Coverage targets
- **Churn interviews:** 100% of cancellations > $X ACV (set X by segment)
- **Win/loss:** top 3 wins + top 3 losses per quarter
- **Renewal:** sample of renewed (find what worked) + churned (counterfactual)
- **Strategic:** top-20 accounts annually
### Conducting interviews well
- 30–45 minute calls; record (with consent); transcribe
- Use a discussion guide — don't wing it
- Interviewer is NOT the CSM who lost the account (bias)
- Closure: thank the customer; commit to share back what changed
### Synthesis
- Tag drivers using a published taxonomy
- Quote bank (anonymized) for board / product reviews
- Theme reports: top 5 drivers per quarter, with frequency and severity
## 6. Behavioral VoC — listen without asking
Product analytics + support data + community = behavioral VoC.
### What to track
- **Activation funnels** — where do people drop?
- **Feature usage by cohort** — does new feature stick at 30 days?
- **Time-on-task** (CES proxy) for key workflows
- **Support ticket categorization** — Pareto on root causes
- **Search queries** in app and in support — gaps people are looking for
- **Frustration signals:** rage clicks, repeated retries, error rates
### Why behavioral matters more than survey
Customers tell you what they think they want; behavior tells you what they
do. When behavior contradicts survey response, behavior usually wins.
## 7. The action loop — the whole point
Survey + interview without action is a one-way pipe that customers learn
to ignore. A real action loop:
### Per piece of feedback
1. Acknowledge to the customer
2. Route to owner (product, CS, marketing, support, eng)
3. Decision: accept / decline / defer (with rationale)
4. Implement
5. Close the loop with the customer ("you said X; we did Y")
### Per theme
1. Quarterly synthesis report
2. Top themes reviewed by product / CCO / CMO
3. Roadmap or program response with named owner
4. External communication when implemented ("you told us; here's what changed")
### Closure metrics
- % of detractor responses with follow-up in 5 days
- Median time from theme detection to roadmap commitment
- % of committed responses delivered on time
- Customer-confirmed "you fixed it" rate
## 8. VoC governance — keep it from atrophying
### Roles
- **VoC program owner** (head of CX ops; reports to CCO)
- **Theme owners** (product, support, CS, marketing)
- **Action approver** (varies by theme; usually CCO + CPO for product themes)
### Cadence
- Weekly: detractor follow-up review
- Monthly: action loop status; aging items
- Quarterly: synthesis report + action commitments
- Annually: VoC instrument review; sunset / add tools
### Forum
A monthly VoC committee with product, CS, support, marketing — short
agenda, action-focused, not a feedback re-read.
## 9. Common VoC anti-patterns
- **Survey fatigue from over-sampling.** A customer surveyed monthly stops responding to any of it.
- **Detractor follow-up that's a sales pitch.** Ruins the relationship; ruins the data.
- **Survey results without action.** Trains the org to ignore the next survey.
- **NPS as the headline metric.** Pair with adoption + retention or it's vanity.
- **Annual customer advisory board as the whole program.** Episodic; doesn't replace continuous capture.
- **Two surveys asking the same thing in different tools.** Consolidate the stack.
- **Interview program owned by the team being measured.** Independence matters.
## 10. The VoC program at scale — what mature looks like
A mature VoC program at $100M+ ARR usually has:
- Dedicated VoC ops team (3–8 people)
- 6–10 active feedback instruments
- Closed-loop response rate > 80% within SLA
- Quarterly synthesis published company-wide
- Direct line into product prioritization (named slot in product council)
- External communication cadence ("you told us; here's what changed")
- Annual customer advisory board (8–12 customers)
- Reference program with 30+ active customers
- Public NPS reporting (selectively — only if it's a strength)
If you're missing more than 3 of these at $100M+, the VoC program is undersized.
## 11. Common pitfalls
- **Confusing VoC with customer marketing.** Different functions, different outcomes.
- **NPS as the only VoC instrument.** Cargo cult.
- **Quarterly synthesis with no recipients.** Send to a forum that decides; tracking matters.
- **Ignoring behavioral signals because they don't have words.** Behavior speaks loudest.
- **Owning VoC inside product or marketing only.** It should be CCO-owned with cross-functional consumers.
- **Reporting VoC to the board without segmentation.** Segmented or it's noise.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |