chief-customer-officer-advisor

Overview of chief-customer-officer-advisor skill

What chief-customer-officer-advisor is for

chief-customer-officer-advisor is a strategic Customer Success leadership skill for founders, startup CCOs, RevOps leaders, and operators who need sharper decisions about retention, segmentation, CS coverage, and customer-facing org design. It is not a generic “write a CS plan” prompt. The skill is organized around four executive decisions: whether retention is honestly healthy, which customers deserve different investment levels, how many CSMs are needed, and which customer-facing role to hire next.

Best-fit users and decisions

The chief-customer-officer-advisor skill is strongest for B2B SaaS or subscription businesses with enough customer and ARR data to make tradeoffs visible. Use it when you are preparing a board retention narrative, redesigning customer tiers, deciding between tech-touch, pooled, named CSM, or named-plus-exec coverage, or separating Customer Success from Support, Account Management, and Implementation. It is especially useful as chief-customer-officer-advisor for Customer Success planning because it combines qualitative operating judgment with deterministic helper scripts.

What makes it different from a normal CS prompt

The differentiator is structure. The repository includes references for retention decomposition, customer segmentation strategy, CS coverage models, and CS team org evolution, plus Python scripts for retention analysis, segmentation design, and coverage calculation. That means the skill can move from “advise me” to “diagnose this book of business and recommend operating changes” when you provide clean inputs.

How to Use chief-customer-officer-advisor skill

chief-customer-officer-advisor install context

Install from the GitHub skill repository path:

npx skills add alirezarezvani/claude-skills --skill chief-customer-officer-advisor

If your skill runner requires a local path, use the repository location:

c-level-advisor/skills/chief-customer-officer-advisor

For a quick adoption check, read SKILL.md first, then the four decision references: references/retention_decomposition.md, references/customer_segmentation_strategy.md, references/cs_coverage_model.md, and references/cs_team_org_evolution.md. Review the scripts only after you know which decision you are trying to answer.

Inputs that make the skill useful

Good chief-customer-officer-advisor usage depends on business context, not just a question. Provide stage, ACV range, ARR by segment, customer count, current CSM headcount, renewal motion, expansion model, churn symptoms, and what decision is due. For retention work, include starting ARR, renewed ARR, expansion ARR, contraction ARR, customer counts, and churn reasons by cohort. For segmentation, include customer ARR, tenure, ICP signals, expansion potential, executive sponsor presence, and approximate support cost.

A weak prompt is: “Create a CS strategy for us.”
A stronger prompt is: “We are a Series A B2B SaaS company at $4.8M ARR, 280 customers, median ACV $12K. NRR is 112%, but GRR may be around 82%. We have 2 CSMs and 1 support lead. Diagnose whether our retention is healthy, propose customer tiers, and recommend whether to move from pooled to named CSM coverage.”

Practical workflow and files to run

Start with one decision, not the whole CCO function. If the problem is churn truth, use retention_decomposition.md and optionally run scripts/retention_decomposition_analyzer.py with cohort JSON. If the problem is “who gets CSM time,” use customer_segmentation_strategy.md and scripts/customer_segmentation_designer.py. If the problem is headcount, use cs_coverage_model.md and scripts/cs_coverage_calculator.py. If the problem is hiring sequence, use cs_team_org_evolution.md.

The scripts are stdlib-only Python tools and can be run with embedded samples or your own JSON, for example:

python scripts/cs_coverage_calculator.py book.json --output json

Use script output as evidence for the agent, then ask the skill to interpret tradeoffs, risks, and executive actions.

Prompt pattern for better results

Use this structure: context, data, decision, constraints, output format. Example:

“Using chief-customer-officer-advisor, analyze our CS coverage. Context: Series B SaaS, $14M ARR, enterprise and mid-market customers. Data: Strategic tier has 12 customers and $5.2M ARR with 1 CSM; enterprise has 55 customers and $6.1M ARR with 2 CSMs; mid-market has 180 customers and $2.7M ARR with 1 CSM. Constraint: no more than two hires this year. Output: recommended coverage model, headcount gap, 12-month hiring sequence, and risks if we delay.”

chief-customer-officer-advisor skill FAQ

Is chief-customer-officer-advisor only for startups?

It is designed around startup and scale-up operating decisions, especially B2B SaaS. Later-stage companies can still use it for segmentation or retention decomposition, but the default thresholds and hiring logic may need adjustment for mature enterprise CS organizations, regulated industries, or complex global account structures.

Does it replace a Customer Success consultant?

No. The chief-customer-officer-advisor skill helps structure analysis, expose hidden retention problems, and turn customer data into decision options. It does not interview customers, inspect CRM hygiene, validate political realities, or negotiate headcount tradeoffs with executives. Treat it as a strategy analyst and decision framework, not as a full operating owner.

When should I not use this skill?

Do not use it for frontline support macros, product onboarding copy, sales playbooks, or tactical account plans unless those artifacts are connected to a higher-level CCO decision. It is also a poor fit if you have no customer data at all. In that case, first gather ARR, churn, expansion, support cost, and segment information.

How is it different from general business-growth skills?

General growth skills often emphasize acquisition, funnel conversion, or revenue tactics. This skill focuses on post-sale customer economics: GRR versus NRR, contraction versus expansion, ICP fit, differential investment, CSM capacity, and role clarity across Support, CS, AM, and Implementation.

How to Improve chief-customer-officer-advisor skill

Make chief-customer-officer-advisor outputs more specific

The fastest improvement is better input granularity. Replace blended averages with tier-level data. Instead of “we have 500 customers and 5 CSMs,” provide customer count, ARR, current CSMs, ACV range, and churn pattern by segment. The skill’s recommendations become more actionable when it can see where CS time is over-invested or under-invested.

Avoid common failure modes

The main failure mode is asking for a universal CS strategy when the real decision is narrower. Another is optimizing NRR while ignoring weak GRR. A third is asking for hiring advice without naming the failed customer outcome: slow onboarding, unresolved support load, missed renewals, low expansion, or weak executive relationships. Anchor the prompt to the failure mode.

Iterate after the first answer

After the first output, ask for a pressure test: “What assumptions would change this recommendation?” Then ask for an executive version, an operating plan, and a data request list. For board or leadership use, have the skill separate facts, assumptions, risks, and decisions needed. This prevents confident but under-evidenced recommendations.

Customize thresholds to your business

The built-in references use practical SaaS baselines, but your market may differ. Adjust ACV bands, tier names, ARR-per-CSM expectations, ICP signals, and churn taxonomy before relying on final recommendations. A PLG company, an enterprise implementation-heavy product, and a services-assisted SaaS business should not use identical coverage thresholds.