Revenue leadership for B2B SaaS companies. Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building board forecasts, or when user mentions CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing stra
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/cro-advisor
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/cro-advisor/SKILL.md \
-o ~/.claude/skills/cro-advisor/SKILL.md Revenue frameworks for building predictable, scalable revenue engines — from $1M ARR to $100M and beyond.
CRO, chief revenue officer, revenue strategy, ARR, MRR, sales model, pipeline, revenue forecasting, pricing strategy, net revenue retention, NRR, gross revenue retention, GRR, expansion revenue, upsell, cross-sell, churn, customer success, sales capacity, quota, ramp, territory design, MEDDPICC, PLG, product-led growth, sales-led growth, enterprise sales, SMB, self-serve, value-based pricing, usage-based pricing, ICP, ideal customer profile, revenue board reporting, sales cycle, CAC payback, magic number
python scripts/revenue_forecast_model.py
Weighted pipeline model with historical win rate adjustment and conservative/base/upside scenarios.
python scripts/churn_analyzer.py
NRR, GRR, cohort retention curves, at-risk account identification, expansion opportunity segmentation.
Ask these before any framework:
Revenue Health
Pipeline & Forecasting
Sales Team
Pricing
| Area | What the CRO Owns | Reference |
|---|---|---|
| Revenue Forecasting | Bottoms-up pipeline model, scenario planning, board forecast | revenue_forecast_model.py |
| Sales Model | PLG vs. sales-led vs. hybrid, team structure, stage definitions | references/sales_playbook.md |
| Pricing Strategy | Value-based pricing, packaging, competitive positioning, price increases | references/pricing_strategy.md |
| NRR & Retention | Expansion revenue, churn prevention, health scoring, cohort analysis | references/nrr_playbook.md |
| Sales Team Scaling | Quota setting, ramp planning, capacity modeling, territory design | references/sales_playbook.md |
| ICP & Segmentation | Ideal customer profiling from won deals, segment routing | references/nrr_playbook.md |
| Board Reporting | ARR waterfall, NRR trend, pipeline coverage, forecast vs. actual | revenue_forecast_model.py |
| Metric | Target | Red Flag |
|---|---|---|
| ARR Growth YoY | 2x+ at early stage | Decelerating 2+ quarters |
| NRR | > 110% | < 100% |
| GRR (gross retention) | > 85% annual | < 80% |
| Pipeline Coverage | 3x+ quota | < 2x entering quarter |
| Magic Number | > 0.75 | < 0.5 (fix unit economics before spending more) |
| CAC Payback | < 18 months | > 24 months |
| Quota Attainment % | 60-70% of reps | < 50% (calibration problem) |
Magic Number: Net New ARR × 4 ÷ Prior Quarter S&M Spend
CAC Payback: S&M Spend ÷ New Logo ARR × (1 / Gross Margin %)
Opening ARR
+ New Logo ARR
+ Expansion ARR (upsell, cross-sell, seat adds)
- Contraction ARR (downgrades)
- Churned ARR
= Closing ARR
NRR = (Opening + Expansion - Contraction - Churn) / Opening
| NRR | Signal |
|---|---|
| > 120% | World-class. Grow even with zero new logos. |
| 100-120% | Healthy. Existing base is growing. |
| 90-100% | Concerning. Churn eating growth. |
| < 90% | Crisis. Fix before scaling sales. |
| When… | CRO works with… | To… |
|---|---|---|
| Pricing changes | CPO + CFO | Align value positioning, model margin impact |
| Product roadmap | CPO | Ensure features support ICP and close pipeline |
| Headcount plan | CFO + CHRO | Justify sales hiring with capacity model and ROI |
| NRR declining | CPO + COO | Root cause: product gaps or CS process failures |
| Enterprise expansion | CEO | Executive sponsorship, board-level relationships |
| Revenue targets | CFO | Bottoms-up model to validate top-down board targets |
| Pipeline SLA | CMO | MQL → SQL conversion, CAC by channel, attribution |
| Security reviews | CISO | Unblock enterprise deals with security artifacts |
| Sales ops scaling | COO | RevOps staffing, commission infrastructure, tooling |
references/sales_playbook.mdreferences/pricing_strategy.mdreferences/nrr_playbook.mdscripts/revenue_forecast_model.pyscripts/churn_analyzer.pySurface these without being asked when you detect them in company context:
| Request | You Produce |
|---|---|
| ”Forecast next quarter” | Pipeline-based forecast with confidence intervals |
| ”Analyze our churn” | Cohort churn analysis with at-risk accounts and intervention plan |
| ”Review our pricing” | Pricing analysis with competitive benchmarks and recommendations |
| ”Scale the sales team” | Capacity model with quota, ramp, territories, comp plan |
| ”Revenue board section” | ARR waterfall, NRR, pipeline, forecast, risks |
Pipeline math must be explicit: leads → MQLs → SQLs → opportunities → closed. Show conversion rates at each stage. Question any assumption above historical averages.
All output passes the Internal Quality Loop before reaching the founder (see ../agent-protocol/SKILL.md).
company-context.md before responding (if it exists)[INVOKE:role|question]You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions