IntermediateAgent Skill

Revenue Operations

Analyze pipeline coverage, forecast accuracy, and SaaS go-to-market efficiency from JSON exports.

Views
0
Copies
0
Favorites
0
Editorial Score
80/100
Supported Platforms
Claude Code · Codex
01

What this Skill does

Analyze pipeline coverage, forecast accuracy, and SaaS go-to-market efficiency from JSON exports. Three Python tools separate deal pipeline diagnostics, forecast errors, and unit-economics calculations.

02

What makes it different

01

Approach and advantage

Three Python tools separate deal pipeline diagnostics, forecast errors, and unit-economics calculations.

02

What you can use it for

Inspect merchant-software pipeline coverage and aging; Compare forecast error across completed periods; Review GTM efficiency using consistent revenue and cost definitions.

03

Before you install

Inputs to prepare

Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.

Agent and runtime

Use a Skill-capable agent with file access. Python 3 is required for the bundled Python helpers; inspect their sample schemas before supplying data.

Scope to confirm

Designed for B2B/SaaS sales. Pipeline coverage is not storefront order forecasting; no CRM sync or future revenue guarantee is provided.

04

Install and get started

Codex

The repository installer copies this complete Skill into your Codex skills directory. Git and the installer’s shell/Python requirements must be available.

  1. Choose the method for your agent and install the complete package, not just the displayed SKILL.md.
  2. Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.
  3. Start a new agent session and explicitly ask to use revenue-operations. Try one use case below with a small sample and review the output.
git clone https://github.com/alirezarezvani/claude-skills.git cd claude-skills git checkout 6d2f02ea077eead1bee5411a31bcc6db5a11a70c ./scripts/codex-install.sh --skill revenue-operations
05

Original Skill.md

This is the unchanged source SKILL.md for the reviewed version. Install the complete package to retain referenced scripts, assets, and instructions. Starter prompts below are EcomAgentTools examples.

Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.

View the reviewed source · MIT

License notice
MIT License

Copyright (c) 2025 Alireza Rezvani

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
---
name: "revenue-operations"
description: 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.
---

# 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

```bash
# 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:**

```bash
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:**

```json
{
  "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:**

```bash
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:**

```json
{
  "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:**

```bash
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:**

```json
{
  "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:**
   ```bash
   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:**
   ```bash
   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:**
   ```bash
   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](references/revops-metrics-guide.md) | Complete metrics hierarchy, definitions, formulas, and interpretation |
| [Pipeline Management Framework](references/pipeline-management-framework.md) | Pipeline best practices, stage definitions, conversion benchmarks |
| [GTM Efficiency Benchmarks](references/gtm-efficiency-benchmarks.md) | SaaS benchmarks by stage, industry standards, improvement strategies |

---

## Templates

| Template | Use Case |
|----------|----------|
| [Pipeline Review Template](assets/pipeline_review_template.md) | Weekly/monthly pipeline inspection documentation |
| [Forecast Report Template](assets/forecast_report_template.md) | Forecast accuracy reporting and trend analysis |
| [GTM Dashboard Template](assets/gtm_dashboard_template.md) | GTM efficiency dashboard for leadership review |
| [Sample Pipeline Data](assets/sample_pipeline_data.json) | Example input for pipeline_analyzer.py |
| [Expected Output](assets/expected_output.json) | Reference output from pipeline_analyzer.py |
06

Get started

Starter prompts for the main use cases—copy and use them directly.

01

Inspect merchant-software pipeline coverage and aging

Inspect merchant-software pipeline coverage and aging Use for: Inspect merchant-software pipeline coverage and aging. Prepare: Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.

Show prompt and variablesHide prompt and variables
Use the installed revenue-operations Skill. Task: Inspect merchant-software pipeline coverage and aging. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. Designed for B2B/SaaS sales. Pipeline coverage is not storefront order forecasting; no CRM sync or future revenue guarantee is provided.

Replace these variables

[INPUT]
Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.
[CONSTRAINTS]
Scope, allowed actions, output format, and review requirements.
02

Compare forecast error across completed periods

Compare forecast error across completed periods Use for: Compare forecast error across completed periods. Prepare: Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.

Show prompt and variablesHide prompt and variables
Use the installed revenue-operations Skill. Task: Compare forecast error across completed periods. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. Designed for B2B/SaaS sales. Pipeline coverage is not storefront order forecasting; no CRM sync or future revenue guarantee is provided.

Replace these variables

[INPUT]
Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.
[CONSTRAINTS]
Scope, allowed actions, output format, and review requirements.
03

Review GTM efficiency using consistent revenue and cost definitions

Review GTM efficiency using consistent revenue and cost definitions Use for: Review GTM efficiency using consistent revenue and cost definitions. Prepare: Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.

Show prompt and variablesHide prompt and variables
Use the installed revenue-operations Skill. Task: Review GTM efficiency using consistent revenue and cost definitions. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. Designed for B2B/SaaS sales. Pipeline coverage is not storefront order forecasting; no CRM sync or future revenue guarantee is provided.

Replace these variables

[INPUT]
Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions.
[CONSTRAINTS]
Scope, allowed actions, output format, and review requirements.
07

Risks and operating notes

Known limits

Designed for B2B/SaaS sales. Pipeline coverage is not storefront order forecasting; no CRM sync or future revenue guarantee is provided.

Evidence and review

Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.

Before acting on the result

Use authorized inputs and keep secrets out of prompts. Review customer-facing claims, calculations, code changes, and any proposed external action before applying them.

Frequently asked questions

What does it do, and what is the advantage?

Analyze pipeline coverage, forecast accuracy, and SaaS go-to-market efficiency from JSON exports. Three Python tools separate deal pipeline diagnostics, forecast errors, and unit-economics calculations.

How do I install it and start?

Choose the method for your agent and install the complete package, not just the displayed SKILL.md. Deal-stage data, quota, historical forecasts and actuals, acquisition costs, and revenue definitions. Start a new agent session and explicitly ask to use revenue-operations. Try one use case below with a small sample and review the output.

Which situations is it useful for?

Inspect merchant-software pipeline coverage and aging; Compare forecast error across completed periods; Review GTM efficiency using consistent revenue and cost definitions

What limitations should I know?

Designed for B2B/SaaS sales. Pipeline coverage is not storefront order forecasting; no CRM sync or future revenue guarantee is provided.

What was checked for this page?

Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.

Community rating results

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result

No reviews yet.

Leave a review

Rate every dimension, then share your real experience.

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result
Author / maintainer

Alireza Rezvani

Source and package files reviewed on October 25, 2026: GitHub 6d2f02ea077e. This is a static review, not an installation or business-outcome test.

Content checked: