chief-customer-officer-advisor
Customer leadership advisor for Chief Customer Officers on customer experience strategy, retention and expansion, voice-of-customer programs, CX organizational design, and customer outcomes accountability. Use when defining a CX strategy, scoring CX maturity, planning churn interventions, designing a VoC program, or preparing the customer section of a board update.
What this skill does
# 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 the top 3. 4. Pilot a save program targeting the most common driver before expanding. ### "Help me build the CCO board section" 1. NRR / GRR for the trailing quarter + 4-quarter trend. 2. NPS (relationship + transactional) with segment breakdown. 3. Top 3 churn drivers, with a counter-action and an owner. 4. Top 3 expansion drivers and their adoption rate. 5. 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
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.