본문으로 건너뛰기
cccskills
무료GitHub에 공개

chief-customer-officer-advisor

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(7)

  • SKILL.md8.1 KB
  • references/customer-experience-strategy.md8.5 KB
  • references/retention-and-expansion-frameworks.md8.3 KB
  • references/voice-of-customer-program.md8.4 KB
  • scripts/churn_intervention_planner.py11.8 KB
  • scripts/cx_maturity_scorer.py15.8 KB
  • scripts/voc_program_designer.py11.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.
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.
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.
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.

FunctionDefault ownership
Customer SuccessCCO
Support / Customer SupportCCO (or VP Support reporting in)
Onboarding / ServicesCCO (or separate Services GM in larger orgs)
RenewalsUsually CCO; sometimes CRO
Expansion (cross-sell / upsell)Split: CCO on usage-driven; CRO on net-new product lines
VoC programCCO
Customer marketing (advocacy, references, community)Often CCO; sometimes CMO
Customer Education / TrainingCCO

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):

SegmentARR per CSM (USD)Accounts per CSM
Enterprise high-touch$4M–$10M10–25
Mid-Market$2M–$5M30–80
SMB / Pooled$1M–$2M200–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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9692026년 10월 7일 업데이트

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9692026년 10월 7일 업데이트

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9692026년 10월 7일 업데이트

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9692026년 10월 7일 업데이트

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9692026년 10월 7일 업데이트

aeo

무료

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

borghei/Claude-Skills9692026년 10월 7일 업데이트

borghei의 스킬 모두 보기

이 스킬의 문제 신고