cro-advisor
by alirezarezvanicro-advisor is a Claude skill for B2B SaaS revenue leadership, RevOps, ARR forecasting, NRR and churn analysis, pricing strategy, sales process design, and board-ready CRO recommendations using included playbooks and Python scripts.
This skill scores 80/100, making it a solid listing candidate for directory users who want a CRO-style B2B SaaS revenue advisor. It appears triggerable and materially more actionable than a generic prompt because it combines explicit use cases, revenue frameworks, and runnable forecasting/retention scripts, though adoption would be easier with clearer install and worked-example guidance.
- Clear trigger surface: the description and keywords explicitly cover CRO, revenue strategy, ARR growth, forecasting, NRR, churn, pricing, quotas, and sales capacity.
- Operational substance is present through two stdlib Python tools for pipeline forecasting and churn/retention analysis, each with usage commands and CSV input formats.
- Supporting references add real workflow value across NRR, pricing strategy, and sales playbook topics rather than remaining a placeholder or demo.
- No install command or README is present, so users must infer installation from the repository path and SKILL.md.
- The provided excerpts show strong general SaaS revenue frameworks, but limited evidence of end-to-end worked examples tying user questions to specific script inputs/outputs.
Overview of cro-advisor skill
What cro-advisor is for
cro-advisor is a Claude skill for B2B SaaS revenue leadership work: forecasting ARR, diagnosing churn and retention, shaping pricing strategy, designing sales process, and preparing CRO-level recommendations for board or executive use. It is best suited for founders, RevOps teams, sales leaders, finance partners, and operators who need structured revenue analysis rather than a generic “give me a growth plan” answer.
Best-fit Revenue Operations use cases
The strongest fit for cro-advisor for Revenue Operations is when you already have partial revenue data and need a practical operating view: pipeline by stage, ARR by segment, churned accounts, expansion/contraction, sales capacity, quota assumptions, or pricing model options. It can help turn messy inputs into forecasts, NRR analysis, sales process recommendations, pricing tradeoffs, and board-ready narratives.
What makes this skill different
The skill includes three substantive reference playbooks—references/nrr_playbook.md, references/pricing_strategy.md, and references/sales_playbook.md—plus two stdlib-only Python tools: scripts/revenue_forecast_model.py and scripts/churn_analyzer.py. That combination matters: the agent is not only prompted to advise like a CRO, it has concrete formulas, benchmark ranges, sales-stage logic, pricing models, and runnable analysis scripts to ground the output.
When not to use it
Do not treat cro-advisor as a replacement for audited finance work, legal pricing review, compensation design approval, or CRM hygiene. It also works poorly if you only provide vague goals such as “increase revenue” without segment, pipeline, retention, or pricing context. For consumer apps, marketplaces, ads businesses, or non-recurring revenue models, expect to adapt the SaaS assumptions heavily.
How to Use cro-advisor skill
cro-advisor install and first files to inspect
Install from the repository with:
npx skills add alirezarezvani/claude-skills --skill cro-advisor
After installation, read SKILL.md first to understand the trigger scope and workflows. Then inspect:
references/nrr_playbook.mdfor GRR, NRR, churn, expansion, and benchmark framingreferences/pricing_strategy.mdfor seat-based, usage-based, tiered, and value-based pricing tradeoffsreferences/sales_playbook.mdfor funnel stages, qualification, discovery, and sales operating designscripts/revenue_forecast_model.pyif you need pipeline-weighted forecastingscripts/churn_analyzer.pyif you need customer-level retention analysis
Inputs that produce better CRO advice
For cro-advisor usage, provide the business model and revenue context before asking for recommendations. Useful inputs include ARR/MRR, ICP, segment mix, ACV, sales cycle, pipeline stages, win rates, churn, expansion, contraction, quota capacity, headcount, CAC payback, and current pricing. If data is incomplete, say what is estimated and what is known.
A weak prompt is:
Help us improve revenue.
A stronger prompt is:
Use cro-advisor to assess our B2B SaaS revenue engine. We are at $6.5M ARR, 72% mid-market and 28% SMB, $18K blended ACV, 94% GRR, 108% NRR, 4 AEs, $850K quota each, 23% win rate, 74-day sales cycle, and a $9M weighted pipeline for the next two quarters. Identify the biggest constraint, forecast likely ARR range, and recommend the next 3 RevOps moves.
Running the included scripts
The scripts can be used directly when you have CSV data. From the skill directory, try:
python scripts/revenue_forecast_model.py --csv pipeline.csv --scenario base
python scripts/revenue_forecast_model.py --csv pipeline.csv --scenario conservative
python scripts/churn_analyzer.py --csv customers.csv --period 2026-Q1 --output summary
Expected pipeline CSV fields are deal_id, name, stage, arr_value, close_date, rep, segment. Expected customer CSV fields are customer_id, name, segment, arr, start_date, churn_date, expansion_arr, contraction_arr. The scripts use Python stdlib only, which reduces setup friction and makes them easy to run in lightweight environments.
Workflow for board-ready output
A practical cro-advisor guide workflow is: first ask for metric diagnosis, then run or summarize forecast/retention calculations, then request recommendations ranked by revenue impact and execution risk. For executive outputs, ask the skill to separate “observed data,” “assumptions,” “risks,” and “recommended actions.” This prevents the response from blending facts with guesses and makes it easier to reuse in operating reviews.
cro-advisor skill FAQ
Is cro-advisor only for CROs?
No. The cro-advisor skill is useful for CROs, CEOs, founders, RevOps, sales ops, customer success leaders, and finance teams working on SaaS revenue mechanics. It is especially helpful when the question crosses functions, such as whether weak growth is caused by pipeline, conversion, pricing, retention, sales capacity, or expansion motion.
How is it better than an ordinary prompt?
An ordinary prompt may produce plausible but generic revenue advice. cro-advisor has embedded SaaS-specific playbooks and scripts, so it can reason from NRR formulas, GRR/NRR benchmarks, sales-stage definitions, pricing model tradeoffs, and weighted-pipeline forecasting. The advantage is not magic accuracy; it is less guesswork and more consistent CRO operating structure.
Can beginners use this skill?
Yes, but beginners should start with a specific business question and a small dataset. For example, ask it to explain NRR from your customer data, compare pricing model options, or review pipeline coverage for the next quarter. If you do not know a metric, say so; the skill can often identify which missing metric blocks the decision.
What are the main limitations?
cro-advisor depends on the quality and freshness of your inputs. CRM stage probabilities, churn reasons, expansion ARR, and close dates are often messy, so outputs should be reviewed against actual systems of record. It also does not automatically connect to your CRM, billing platform, or data warehouse; you must provide exports or summaries.
How to Improve cro-advisor skill
Improve cro-advisor prompts with decision context
To get better cro-advisor results, state the decision you need to make, not just the topic. “Should we hire two more AEs?” is better than “analyze sales.” Include the time horizon, constraints, and success metric: cash efficiency, ARR growth, NRR, CAC payback, quota attainment, enterprise mix, or churn reduction. This helps the skill choose between growth, retention, pricing, and capacity levers.
Provide cleaner RevOps data
The most common failure mode is asking for precision from inconsistent data. Before using the skill, normalize stage names, remove duplicate opportunities, separate new ARR from expansion ARR, and label customer segment consistently. For churn analysis, distinguish logo churn, revenue churn, contraction, and downgrade. For forecasting, include close dates and current stage, not just deal value.
Ask for assumptions and sensitivity ranges
Revenue plans are assumption-heavy. Ask cro-advisor to show the assumptions behind win rate, sales cycle, quota productivity, ramp time, NRR, and pricing lift. Then request conservative, base, and upside scenarios. This is especially useful when preparing board materials, because it exposes which assumption actually drives the plan.
Iterate from diagnosis to operating plan
Use the first answer as a diagnosis, not the final plan. Follow up with: “Which recommendation has the fastest payback?”, “What data would disprove this?”, “What should RevOps instrument next?”, or “Convert this into a 30/60/90-day operating plan.” cro-advisor becomes more useful when you force tradeoffs between pipeline creation, conversion improvement, retention repair, pricing changes, and sales hiring.