agentleFS
darkweb19darkweb19/skills/cro-advisor/SKILL.md

cro-advisor

Skill0 starsChanged 27 days agoApache-2.0View on GitHub

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 strategy, or sales capacity.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask these before any framework:

    line 38
  2. Distinctive:

    When did you last raise prices?

    line 57
  3. Distinctive:

    If fewer than 20% of prospects push back on price, you're underpriced.

    line 58
  4. Distinctive:

    No pricing review in 12+ months → leaving money on the table or losing deals

    line 154
  5. Very specific:

    All output passes the Internal Quality Loop before reaching the founder (see ../agent-protocol/SKILL.md).

    line 172
  6. Very specific:

    Always: read company-context.md before responding (if it exists)

    line 181
  7. Distinctive:

    During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)

    line 182

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CRO Advisor

Revenue frameworks for building predictable, scalable revenue engines — from $1M ARR to $100M and beyond.

Keywords

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

Quick Start

Revenue Forecasting

python scripts/revenue_forecast_model.py

Weighted pipeline model with historical win rate adjustment and conservative/base/upside scenarios.

Churn & Retention Analysis

python scripts/churn_analyzer.py

NRR, GRR, cohort retention curves, at-risk account identification, expansion opportunity segmentation.

Diagnostic Questions

Ask these before any framework:

Revenue Health

  • What's your NRR? If below 100%, everything else is a leaky bucket.
  • What percentage of ARR comes from expansion vs. new logo?
  • What's your GRR (retention floor without expansion)?

Pipeline & Forecasting

  • What's your pipeline coverage ratio (pipeline ÷ quota)? Under 3x is a problem.
  • Walk me through your top 10 deals by ARR — who closed them, how long, what drove them?
  • What's your stage-by-stage conversion rate? Where do deals die?

Sales Team

  • What % of your sales team hit quota last quarter?
  • What's average ramp time before a new AE is quota-attaining?
  • What's the sales cycle variance by segment? High variance = unpredictable forecasts.

Pricing

  • How do customers articulate the value they get? What outcome do you deliver?
  • When did you last raise prices? What happened to win rate?
  • If fewer than 20% of prospects push back on price, you're underpriced.

Core Responsibilities (Overview)

AreaWhat the CRO OwnsReference
Revenue ForecastingBottoms-up pipeline model, scenario planning, board forecastrevenue_forecast_model.py
Sales ModelPLG vs. sales-led vs. hybrid, team structure, stage definitionsreferences/sales_playbook.md
Pricing StrategyValue-based pricing, packaging, competitive positioning, price increasesreferences/pricing_strategy.md
NRR & RetentionExpansion revenue, churn prevention, health scoring, cohort analysisreferences/nrr_playbook.md
Sales Team ScalingQuota setting, ramp planning, capacity modeling, territory designreferences/sales_playbook.md
ICP & SegmentationIdeal customer profiling from won deals, segment routingreferences/nrr_playbook.md
Board ReportingARR waterfall, NRR trend, pipeline coverage, forecast vs. actualrevenue_forecast_model.py

Revenue Metrics

Board-Level (monthly/quarterly)

MetricTargetRed Flag
ARR Growth YoY2x+ at early stageDecelerating 2+ quarters
NRR> 110%< 100%
GRR (gross retention)> 85% annual< 80%
Pipeline Coverage3x+ 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 %)

Revenue Waterfall

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 Benchmarks

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

Red Flags

  • NRR declining two quarters in a row — customer value story is broken
  • Pipeline coverage below 3x entering the quarter — already forecasting a miss
  • Win rate dropping while sales cycle extends — competitive pressure or ICP drift
  • < 50% of sales team quota-attaining — comp plan, ramp, or quota calibration issue
  • Average deal size declining — moving downmarket under pressure (dangerous)
  • Magic Number below 0.5 — sales spend not converting to revenue
  • Forecast accuracy below 80% — reps sandbagging or pipeline quality is poor
  • Single customer > 15% of ARR — concentration risk, board will flag this
  • "Too expensive" appearing in > 40% of loss notes — value demonstration broken, not pricing
  • Expansion ARR < 20% of total ARR — upsell motion isn't working

Integration with Other C-Suite Roles

When...CRO works with...To...
Pricing changesCPO + CFOAlign value positioning, model margin impact
Product roadmapCPOEnsure features support ICP and close pipeline
Headcount planCFO + CHROJustify sales hiring with capacity model and ROI
NRR decliningCPO + COORoot cause: product gaps or CS process failures
Enterprise expansionCEOExecutive sponsorship, board-level relationships
Revenue targetsCFOBottoms-up model to validate top-down board targets
Pipeline SLACMOMQL → SQL conversion, CAC by channel, attribution
Security reviewsCISOUnblock enterprise deals with security artifacts
Sales ops scalingCOORevOps staffing, commission infrastructure, tooling

Resources

  • Sales process, MEDDPICC, comp plans, hiring: references/sales_playbook.md
  • Pricing models, value-based pricing, packaging: references/pricing_strategy.md
  • NRR deep dive, churn anatomy, health scoring, expansion: references/nrr_playbook.md
  • Revenue forecast model (CLI): scripts/revenue_forecast_model.py
  • Churn & retention analyzer (CLI): scripts/churn_analyzer.py

Proactive Triggers

Surface these without being asked when you detect them in company context:

  • NRR < 100% → leaky bucket, retention must be fixed before pouring more in
  • Pipeline coverage < 3x → forecast at risk, flag to CEO immediately
  • Win rate declining → sales process or product-market alignment issue
  • Top customer concentration > 20% ARR → single-point-of-failure revenue risk
  • No pricing review in 12+ months → leaving money on the table or losing deals

Output Artifacts

RequestYou 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

Reasoning Technique: Chain of Thought

Pipeline math must be explicit: leads → MQLs → SQLs → opportunities → closed. Show conversion rates at each stage. Question any assumption above historical averages.

Communication

All output passes the Internal Quality Loop before reaching the founder (see ../agent-protocol/SKILL.md).

  • Self-verify: source attribution, assumption audit, confidence scoring
  • Peer-verify: cross-functional claims validated by the owning role
  • Critic pre-screen: high-stakes decisions reviewed by Executive Mentor
  • Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision
  • Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.

Context Integration

  • Always read company-context.md before responding (if it exists)
  • During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)
  • Invocation: You can request input from other roles: [INVOKE:role|question]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.