Revenue operations

Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/revenue-operations, including the files SKILL.md points to.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/business-growth/skills/revenue-operations#main ~/.claude/skills/revenue-operations

For one project only, change the path to .claude/skills/revenue-operations. This skill also uses pipeline.json, forecast_data.json, gtm_data.json, current_pipeline.json, forecast_history.json, quarterly_data.json — copying SKILL.md alone won't be enough. See the folder on GitHub.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Revenue operations

Show the full text274 lines
namedescription
revenue-operationsAnalyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.

Revenue Operations

Pipeline analysis, forecast accuracy tracking, and GTM efficiency measurement for SaaS revenue teams.

Output formats: All scripts support --format text (human-readable) and --format json (dashboards/integrations).


Quick Start

# Analyze pipeline health and coverage
python scripts/pipeline_analyzer.py --input assets/sample_pipeline_data.json --format text

# Track forecast accuracy over multiple periods
python scripts/forecast_accuracy_tracker.py assets/sample_forecast_data.json --format text

# Calculate GTM efficiency metrics
python scripts/gtm_efficiency_calculator.py assets/sample_gtm_data.json --format text

Tools Overview

1. Pipeline Analyzer

Analyzes sales pipeline health including coverage ratios, stage conversion rates, deal velocity, aging risks, and concentration risks.

Input: JSON file with deals, quota, and stage configuration Output: Coverage ratios, conversion rates, velocity metrics, aging flags, risk assessment

Usage:

python scripts/pipeline_analyzer.py --input pipeline.json --format text

Key Metrics Calculated:

  • Pipeline Coverage Ratio -- Total pipeline value / quota target (healthy: 3-4x)
  • Stage Conversion Rates -- Stage-to-stage progression rates
  • Sales Velocity -- (Opportunities x Avg Deal Size x Win Rate) / Avg Sales Cycle
  • Deal Aging -- Flags deals exceeding 2x average cycle time per stage
  • Concentration Risk -- Warns when >40% of pipeline is in a single deal
  • Coverage Gap Analysis -- Identifies quarters with insufficient pipeline

Input Schema:

{
  "quota": 500000,
  "stages": ["Discovery", "Qualification", "Proposal", "Negotiation", "Closed Won"],
  "average_cycle_days": 45,
  "deals": [
    {
      "id": "D001",
      "name": "Acme Corp",
      "stage": "Proposal",
      "value": 85000,
      "age_days": 32,
      "close_date": "2025-03-15",
      "owner": "rep_1"
    }
  ]
}
2. Forecast Accuracy Tracker

Tracks forecast accuracy over time using MAPE, detects systematic bias, analyzes trends, and provides category-level breakdowns.

Input: JSON file with forecast periods and optional category breakdowns Output: MAPE score, bias analysis, trends, category breakdown, accuracy rating

Usage:

python scripts/forecast_accuracy_tracker.py forecast_data.json --format text

Key Metrics Calculated:

  • MAPE -- mean(|actual - forecast| / |actual|) x 100
  • Forecast Bias -- Over-forecasting (positive) vs under-forecasting (negative) tendency
  • Weighted Accuracy -- MAPE weighted by deal value for materiality
  • Period Trends -- Improving, stable, or declining accuracy over time
  • Category Breakdown -- Accuracy by rep, product, segment, or any custom dimension

Accuracy Ratings:

Rating MAPE Range Interpretation
Excellent <10% Highly predictable, data-driven process
Good 10-15% Reliable forecasting with minor variance
Fair 15-25% Needs process improvement
Poor >25% Significant forecasting methodology gaps

Input Schema:

{
  "forecast_periods": [
    {"period": "2025-Q1", "forecast": 480000, "actual": 520000},
    {"period": "2025-Q2", "forecast": 550000, "actual": 510000}
  ],
  "category_breakdowns": {
    "by_rep": [
      {"category": "Rep A", "forecast": 200000, "actual": 210000},
      {"category": "Rep B", "forecast": 280000, "actual": 310000}
    ]
  }
}
3. GTM Efficiency Calculator

Calculates core SaaS GTM efficiency metrics with industry benchmarking, ratings, and improvement recommendations.

Input: JSON file with revenue, cost, and customer metrics Output: Magic Number, LTV:CAC, CAC Payback, Burn Multiple, Rule of 40, NDR with ratings

Usage:

python scripts/gtm_efficiency_calculator.py gtm_data.json --format text

Key Metrics Calculated:

Metric Formula Target
Magic Number Net New ARR / Prior Period S&M Spend >0.75
LTV:CAC (ARPA x Gross Margin / Churn Rate) / CAC >3:1
CAC Payback CAC / (ARPA x Gross Margin) months <18 months
Burn Multiple Net Burn / Net New ARR <2x
Rule of 40 Revenue Growth % + FCF Margin % >40%
Net Dollar Retention (Begin ARR + Expansion - Contraction - Churn) / Begin ARR >110%

Input Schema:

{
  "revenue": {
    "current_arr": 5000000,
    "prior_arr": 3800000,
    "net_new_arr": 1200000,
    "arpa_monthly": 2500,
    "revenue_growth_pct": 31.6
  },
  "costs": {
    "sales_marketing_spend": 1800000,
    "cac": 18000,
    "gross_margin_pct": 78,
    "total_operating_expense": 6500000,
    "net_burn": 1500000,
    "fcf_margin_pct": 8.4
  },
  "customers": {
    "beginning_arr": 3800000,
    "expansion_arr": 600000,
    "contraction_arr": 100000,
    "churned_arr": 300000,
    "annual_churn_rate_pct": 8
  }
}

Revenue Operations Workflows

Weekly Pipeline Review

Use this workflow for your weekly pipeline inspection cadence.

  1. Verify input data: Confirm pipeline export is current and all required fields (stage, value, close_date, owner) are populated before proceeding.

  2. Generate pipeline report:

    python scripts/pipeline_analyzer.py --input current_pipeline.json --format text
    
  3. Cross-check output totals against your CRM source system to confirm data integrity.

  4. Review key indicators:

    • Pipeline coverage ratio (is it above 3x quota?)
    • Deals aging beyond threshold (which deals need intervention?)
    • Concentration risk (are we over-reliant on a few large deals?)
    • Stage distribution (is there a healthy funnel shape?)
  5. Document using template: Use assets/pipeline_review_template.md

  6. Action items: Address aging deals, redistribute pipeline concentration, fill coverage gaps

Forecast Accuracy Review

Use monthly or quarterly to evaluate and improve forecasting discipline.

  1. Verify input data: Confirm all forecast periods have corresponding actuals and no periods are missing before running.

  2. Generate accuracy report:

    python scripts/forecast_accuracy_tracker.py forecast_history.json --format text
    
  3. Cross-check actuals against closed-won records in your CRM before drawing conclusions.

  4. Analyze patterns:

    • Is MAPE trending down (improving)?
    • Which reps or segments have the highest error rates?
    • Is there systematic over- or under-forecasting?
  5. Document using template: Use assets/forecast_report_template.md

  6. Improvement actions: Coach high-bias reps, adjust methodology, improve data hygiene

GTM Efficiency Audit

Use quarterly or during board prep to evaluate go-to-market efficiency.

  1. Verify input data: Confirm revenue, cost, and customer figures reconcile with finance records before running.

  2. Calculate efficiency metrics:

    python scripts/gtm_efficiency_calculator.py quarterly_data.json --format text
    
  3. Cross-check computed ARR and spend totals against your finance system before sharing results.

  4. Benchmark against targets:

    • Magic Number (>0.75)
    • LTV:CAC (>3:1)
    • CAC Payback (<18 months)
    • Rule of 40 (>40%)
  5. Document using template: Use assets/gtm_dashboard_template.md

  6. Strategic decisions: Adjust spend allocation, optimize channels, improve retention

Quarterly Business Review

Combine all three tools for a comprehensive QBR analysis.

  1. Run pipeline analyzer for forward-looking coverage
  2. Run forecast tracker for backward-looking accuracy
  3. Run GTM calculator for efficiency benchmarks
  4. Cross-reference pipeline health with forecast accuracy
  5. Align GTM efficiency metrics with growth targets

Reference Documentation

Reference Description
RevOps Metrics Guide Complete metrics hierarchy, definitions, formulas, and interpretation
Pipeline Management Framework Pipeline best practices, stage definitions, conversion benchmarks
GTM Efficiency Benchmarks SaaS benchmarks by stage, industry standards, improvement strategies

Templates

Template Use Case
Pipeline Review Template Weekly/monthly pipeline inspection documentation
Forecast Report Template Forecast accuracy reporting and trend analysis
GTM Dashboard Template GTM efficiency dashboard for leadership review
Sample Pipeline Data Example input for pipeline_analyzer.py
Expected Output Reference output from pipeline_analyzer.py
1---
2name: "revenue-operations"
3description: Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization. Use when analyzing sales pipeline coverage, forecasting revenue, evaluating go-to-market performance, reviewing sales metrics, assessing pipeline analysis, tracking forecast accuracy with MAPE, calculating GTM efficiency, or measuring sales efficiency and unit economics for SaaS teams.
4---
5 
6# Revenue Operations
7 
8Pipeline analysis, forecast accuracy tracking, and GTM efficiency measurement for SaaS revenue teams.
9 
10> **Output formats:** All scripts support `--format text` (human-readable) and `--format json` (dashboards/integrations).
11 
12---
13 
14## Quick Start
15 
16```bash
17# Analyze pipeline health and coverage
18python scripts/pipeline_analyzer.py --input assets/sample_pipeline_data.json --format text
19 
20# Track forecast accuracy over multiple periods
21python scripts/forecast_accuracy_tracker.py assets/sample_forecast_data.json --format text
22 
23# Calculate GTM efficiency metrics
24python scripts/gtm_efficiency_calculator.py assets/sample_gtm_data.json --format text
25```
26 
27---
28 
29## Tools Overview
30 
31### 1. Pipeline Analyzer
32 
33Analyzes sales pipeline health including coverage ratios, stage conversion rates, deal velocity, aging risks, and concentration risks.
34 
35**Input:** JSON file with deals, quota, and stage configuration
36**Output:** Coverage ratios, conversion rates, velocity metrics, aging flags, risk assessment
37 
38**Usage:**
39 
40```bash
41python scripts/pipeline_analyzer.py --input pipeline.json --format text
42```
43 
44**Key Metrics Calculated:**
45- **Pipeline Coverage Ratio** -- Total pipeline value / quota target (healthy: 3-4x)
46- **Stage Conversion Rates** -- Stage-to-stage progression rates
47- **Sales Velocity** -- (Opportunities x Avg Deal Size x Win Rate) / Avg Sales Cycle
48- **Deal Aging** -- Flags deals exceeding 2x average cycle time per stage
49- **Concentration Risk** -- Warns when >40% of pipeline is in a single deal
50- **Coverage Gap Analysis** -- Identifies quarters with insufficient pipeline
51 
52**Input Schema:**
53 
54```json
55{
56 "quota": 500000,
57 "stages": ["Discovery", "Qualification", "Proposal", "Negotiation", "Closed Won"],
58 "average_cycle_days": 45,
59 "deals": [
60 {
61 "id": "D001",
62 "name": "Acme Corp",
63 "stage": "Proposal",
64 "value": 85000,
65 "age_days": 32,
66 "close_date": "2025-03-15",
67 "owner": "rep_1"
68 }
69 ]
70}
71```
72 
73### 2. Forecast Accuracy Tracker
74 
75Tracks forecast accuracy over time using MAPE, detects systematic bias, analyzes trends, and provides category-level breakdowns.
76 
77**Input:** JSON file with forecast periods and optional category breakdowns
78**Output:** MAPE score, bias analysis, trends, category breakdown, accuracy rating
79 
80**Usage:**
81 
82```bash
83python scripts/forecast_accuracy_tracker.py forecast_data.json --format text
84```
85 
86**Key Metrics Calculated:**
87- **MAPE** -- mean(|actual - forecast| / |actual|) x 100
88- **Forecast Bias** -- Over-forecasting (positive) vs under-forecasting (negative) tendency
89- **Weighted Accuracy** -- MAPE weighted by deal value for materiality
90- **Period Trends** -- Improving, stable, or declining accuracy over time
91- **Category Breakdown** -- Accuracy by rep, product, segment, or any custom dimension
92 
93**Accuracy Ratings:**
94| Rating | MAPE Range | Interpretation |
95|--------|-----------|----------------|
96| Excellent | <10% | Highly predictable, data-driven process |
97| Good | 10-15% | Reliable forecasting with minor variance |
98| Fair | 15-25% | Needs process improvement |
99| Poor | >25% | Significant forecasting methodology gaps |
100 
101**Input Schema:**
102 
103```json
104{
105 "forecast_periods": [
106 {"period": "2025-Q1", "forecast": 480000, "actual": 520000},
107 {"period": "2025-Q2", "forecast": 550000, "actual": 510000}
108 ],
109 "category_breakdowns": {
110 "by_rep": [
111 {"category": "Rep A", "forecast": 200000, "actual": 210000},
112 {"category": "Rep B", "forecast": 280000, "actual": 310000}
113 ]
114 }
115}
116```
117 
118### 3. GTM Efficiency Calculator
119 
120Calculates core SaaS GTM efficiency metrics with industry benchmarking, ratings, and improvement recommendations.
121 
122**Input:** JSON file with revenue, cost, and customer metrics
123**Output:** Magic Number, LTV:CAC, CAC Payback, Burn Multiple, Rule of 40, NDR with ratings
124 
125**Usage:**
126 
127```bash
128python scripts/gtm_efficiency_calculator.py gtm_data.json --format text
129```
130 
131**Key Metrics Calculated:**
132 
133| Metric | Formula | Target |
134|--------|---------|--------|
135| Magic Number | Net New ARR / Prior Period S&M Spend | >0.75 |
136| LTV:CAC | (ARPA x Gross Margin / Churn Rate) / CAC | >3:1 |
137| CAC Payback | CAC / (ARPA x Gross Margin) months | <18 months |
138| Burn Multiple | Net Burn / Net New ARR | <2x |
139| Rule of 40 | Revenue Growth % + FCF Margin % | >40% |
140| Net Dollar Retention | (Begin ARR + Expansion - Contraction - Churn) / Begin ARR | >110% |
141 
142**Input Schema:**
143 
144```json
145{
146 "revenue": {
147 "current_arr": 5000000,
148 "prior_arr": 3800000,
149 "net_new_arr": 1200000,
150 "arpa_monthly": 2500,
151 "revenue_growth_pct": 31.6
152 },
153 "costs": {
154 "sales_marketing_spend": 1800000,
155 "cac": 18000,
156 "gross_margin_pct": 78,
157 "total_operating_expense": 6500000,
158 "net_burn": 1500000,
159 "fcf_margin_pct": 8.4
160 },
161 "customers": {
162 "beginning_arr": 3800000,
163 "expansion_arr": 600000,
164 "contraction_arr": 100000,
165 "churned_arr": 300000,
166 "annual_churn_rate_pct": 8
167 }
168}
169```
170 
171---
172 
173## Revenue Operations Workflows
174 
175### Weekly Pipeline Review
176 
177Use this workflow for your weekly pipeline inspection cadence.
178 
1791. **Verify input data:** Confirm pipeline export is current and all required fields (stage, value, close_date, owner) are populated before proceeding.
180 
1812. **Generate pipeline report:**
182 ```bash
183 python scripts/pipeline_analyzer.py --input current_pipeline.json --format text
184 ```
185 
1863. **Cross-check output totals** against your CRM source system to confirm data integrity.
187 
1884. **Review key indicators:**
189 - Pipeline coverage ratio (is it above 3x quota?)
190 - Deals aging beyond threshold (which deals need intervention?)
191 - Concentration risk (are we over-reliant on a few large deals?)
192 - Stage distribution (is there a healthy funnel shape?)
193 
1945. **Document using template:** Use `assets/pipeline_review_template.md`
195 
1966. **Action items:** Address aging deals, redistribute pipeline concentration, fill coverage gaps
197 
198### Forecast Accuracy Review
199 
200Use monthly or quarterly to evaluate and improve forecasting discipline.
201 
2021. **Verify input data:** Confirm all forecast periods have corresponding actuals and no periods are missing before running.
203 
2042. **Generate accuracy report:**
205 ```bash
206 python scripts/forecast_accuracy_tracker.py forecast_history.json --format text
207 ```
208 
2093. **Cross-check actuals** against closed-won records in your CRM before drawing conclusions.
210 
2114. **Analyze patterns:**
212 - Is MAPE trending down (improving)?
213 - Which reps or segments have the highest error rates?
214 - Is there systematic over- or under-forecasting?
215 
2165. **Document using template:** Use `assets/forecast_report_template.md`
217 
2186. **Improvement actions:** Coach high-bias reps, adjust methodology, improve data hygiene
219 
220### GTM Efficiency Audit
221 
222Use quarterly or during board prep to evaluate go-to-market efficiency.
223 
2241. **Verify input data:** Confirm revenue, cost, and customer figures reconcile with finance records before running.
225 
2262. **Calculate efficiency metrics:**
227 ```bash
228 python scripts/gtm_efficiency_calculator.py quarterly_data.json --format text
229 ```
230 
2313. **Cross-check computed ARR and spend totals** against your finance system before sharing results.
232 
2334. **Benchmark against targets:**
234 - Magic Number (>0.75)
235 - LTV:CAC (>3:1)
236 - CAC Payback (<18 months)
237 - Rule of 40 (>40%)
238 
2395. **Document using template:** Use `assets/gtm_dashboard_template.md`
240 
2416. **Strategic decisions:** Adjust spend allocation, optimize channels, improve retention
242 
243### Quarterly Business Review
244 
245Combine all three tools for a comprehensive QBR analysis.
246 
2471. Run pipeline analyzer for forward-looking coverage
2482. Run forecast tracker for backward-looking accuracy
2493. Run GTM calculator for efficiency benchmarks
2504. Cross-reference pipeline health with forecast accuracy
2515. Align GTM efficiency metrics with growth targets
252 
253---
254 
255## Reference Documentation
256 
257| Reference | Description |
258|-----------|-------------|
259| [RevOps Metrics Guide](references/revops-metrics-guide.md) | Complete metrics hierarchy, definitions, formulas, and interpretation |
260| [Pipeline Management Framework](references/pipeline-management-framework.md) | Pipeline best practices, stage definitions, conversion benchmarks |
261| [GTM Efficiency Benchmarks](references/gtm-efficiency-benchmarks.md) | SaaS benchmarks by stage, industry standards, improvement strategies |
262 
263---
264 
265## Templates
266 
267| Template | Use Case |
268|----------|----------|
269| [Pipeline Review Template](assets/pipeline_review_template.md) | Weekly/monthly pipeline inspection documentation |
270| [Forecast Report Template](assets/forecast_report_template.md) | Forecast accuracy reporting and trend analysis |
271| [GTM Dashboard Template](assets/gtm_dashboard_template.md) | GTM efficiency dashboard for leadership review |
272| [Sample Pipeline Data](assets/sample_pipeline_data.json) | Example input for pipeline_analyzer.py |
273| [Expected Output](assets/expected_output.json) | Reference output from pipeline_analyzer.py |
274 

Discussion

Alternatives

Also in Pipeline & forecastSee all 138 in Sales →
ThoughtLeaders Data AnalystQuery and analyze YouTube sponsorship data using the `tl` CLI. Use this skill for finding channels, brands and sponsorships, and for data exploration, including counts, metrics, trends, time-series, distributions, single-record drill-downs, revenue / pipeline-weighting math, view-curve analysis, cross-source business questions. Examples: "How many deals did we close last quarter?", "What's the weighted pipeline by sales owner?", "Show me the view curve for video X", "Find mentions of Surfshark in transcripts", "Investigate this video", "Find channels...", "Find brands...".Creator · MITArbor — Autonomous Optimization via Hypothesis Tree RefinementAutonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.Science · MIT/cs:cro-review — CRO Forcing Questions/cs:cro-review <plan> — Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time. Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team.Sales & ecommerce · MITFix How You Run Your TeamYou describe how you currently run your team, meetings, and week. You get back an honest scorecard and a short list of the exact changes that would make you a better manager.Business & ops · MIT