revenue-operations
alirezarezvani/claude-skills
分析銷售管道狀況、營收預測準確度以及市場推廣效率指標,以優化 SaaS 營收。
...展開全部營收營運
針對 SaaS 營收團隊的銷售管道分析、預測準確度追蹤,以及市場進入效率測量。
輸出格式:所有腳本均支援
--format text(人可讀)及--format json(儀表板/整合)。
快速入門
# 分析銷售管道健康狀況與覆蓋率
python scripts/pipeline_analyzer.py --input assets/sample_pipeline_data.json --format text
# 追蹤多個期間的預測準確度
python scripts/forecast_accuracy_tracker.py assets/sample_forecast_data.json --format text
# 計算 GTM 效率指標
python scripts/gtm_efficiency_calculator.py assets/sample_gtm_data.json --format text
工具概覽
1. 銷售管道分析器
分析銷售管線健康狀況,包括覆蓋率、階段轉換率、交易速度、陳舊風險及集中風險。
輸入:包含交易、配額及階段設定的 JSON 檔案 輸出:覆蓋率、轉換率、推進速度指標、滯留警示、風險評估
使用方式:
python scripts/pipeline_analyzer.py --input pipeline.json --format text
計算之關鍵指標:
- 銷售管道覆蓋率—— 銷售管道總價值 / 配額目標(健康範圍:3-4 倍)
- 階段轉換率-- 各階段之間的推進率
- 銷售動能—— (商機數 × 平均交易規模 × 成交率) / 平均銷售週期
- 交易滯留時間—— 標記各階段超過平均週期時間 2 倍的交易
- 集中風險—— 當銷售管道中超過 40% 集中於單一交易時發出警示
- 覆蓋缺口分析—— 識別銷售管道不足的季度
輸入結構:
{
"quota": 500000,
"stages": ["探索期", "資格審查", "提案期", "協商期", "成交"],
"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. 預測準確度追蹤器
利用 MAPE 追蹤預測精確度隨時間的變化,偵測系統性偏差,分析趨勢,並提供類別層級的細項分析。
輸入:包含預測期間及可選類別細分的 JSON 檔案 輸出:MAPE 分數、偏差分析、趨勢、類別細分、準確度評級
使用方法:
python scripts/forecast_accuracy_tracker.py forecast_data.json --format text
計算之關鍵指標:
- MAPE—— (|實際值 - 預測值| / |實際值|) 的平均值 × 100
- 預測偏差—— 高估(正值)與低估(負值)的傾向
- 加權準確度—— 根據交易金額的重要性對 MAPE 進行加權
- 期間趨勢— 準確度隨時間推移呈現改善、穩定或下降的趨勢
- 類別細分—— 按業務代表、產品、細分市場或任何自訂維度劃分的準確度
準確度評級:
| 評級 | MAPE 範圍 | 解讀 |
|---|---|---|
| 優異 | <10% | 高度可預測、以數據為導向的流程 |
| 良好 | 10–15% | 預測結果可靠,波動幅度較小 |
| 尚可 | 15–25% | 需要改善流程 |
| 差 | >25% | 預測方法論存在顯著缺口 |
輸入結構:
{
"forecast_periods": [
{"period": "2025-Q1", "forecast": 480000, "actual": 520000},
{"period": "2025-Q2", "forecast": 550000, "actual": 510000}
],
"category_breakdowns": {
"by_rep": [
{"category": "業務代表 A", "forecast": 200000, "actual": 210000},
{"類別": "業務代表 B", "預測": 280000, "實際": 310000}
]
}
}
3. GTM 效率計算器
計算核心 SaaS 市場進入效率指標,並提供業界基準比較、評級及改善建議。
輸入:包含營收、成本及客戶指標的 JSON 檔案 輸出:魔術數字、LTV:CAC、CAC 回收期、資金消耗倍數、40 法則、附評級的 NDR
使用方法:
python scripts/gtm_efficiency_calculator.py gtm_data.json --format text
計算之關鍵指標:
| 指標 | 公式 | 目標 |
|---|---|---|
| 魔術數字 | 淨新增 ARR / 前期銷售與行銷支出 | >0.75 |
| LTV:CAC | (ARPA × 毛利率 / 流失率) / CAC | >3:1 |
| CAC 回收期 | CAC / (ARPA × 毛利率) 個月 | <18 個月 |
| 資金消耗倍數 | 淨現金消耗 / 淨新增 ARR | <2倍 |
| 40 法則 | 營收成長率 % + 自由現金流利潤率 % | >40% |
| 淨美元留存率 | (期初 ARR + 擴張 - 萎縮 - 流失) / 期初 ARR | >110% |
輸入結構:
{
"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,
"毛利率": 78,
"總營運支出": 6500000,
"淨現金消耗": 1500000,
"自由現金流利潤率 (%)": 8.4
},
"客戶": {
"期初年經常性收入": 3800000,
"擴張期年經常性收入": 600000,
"縮減收入": 100000,
"流失收入": 300000,
"年度流失率 (%)": 8
}
}
營收營運工作流程
每週銷售管道審查
請使用此工作流程來執行每週的銷售管道審查。
驗證輸入資料:在繼續之前,請確認銷售管道匯出檔為最新版本,且所有必填欄位(階段、數值、關閉日期、負責人)均已填寫。
產生銷售管道報告:
python scripts/pipeline_analyzer.py --input current_pipeline.json --format text將輸出總計與您的 CRM 來源系統進行交叉核對,以確認資料完整性。
檢視關鍵指標:
- 銷售管道覆蓋率(是否高於配額的 3 倍?)
- 超過閾值的交易滯留時間(哪些交易需要介入處理?)
- 集中風險(是否過度依賴少數大型交易?)
- 階段分布(銷售漏斗形狀是否健康?)
使用範本記錄:請使用
assets/pipeline_review_template.md待辦事項:處理滯留案件、重新分配銷售管道集中度、填補覆蓋缺口
預測準確度審查
採用每月或每季頻率來評估並改善預測紀律。
驗證輸入資料:執行前請確認所有預測期間均有對應的實際數據,且無任何期間遺漏。
產生準確度報告:
python scripts/forecast_accuracy_tracker.py forecast_history.json --format text在得出結論前,請將實際數據與 CRM 中的「已結案且成交」記錄進行交叉核對。
分析趨勢:
- MAPE 是否呈現下降趨勢(即精準度提升)?
- 哪些業務代表或客群的誤差率最高?
- 是否存在系統性的過高或過低預測?
使用範本記錄:請使用
assets/forecast_report_template.md改善措施:指導偏差較大的業務代表、調整預測方法、改善資料品質
市場進入效率審計
每季或於董事會前進行,以評估市場進入效率。
驗證輸入資料:執行前請確認營收、成本及客戶數據與財務紀錄相符。
計算效率指標:
python scripts/gtm_efficiency_calculator.py quarterly_data.json --format text在分享結果前,請將計算出的 ARR 和總支出與貴公司的財務系統進行交叉核對。
與目標進行基準比較:
- 魔術數字(>0.75)
- LTV:CAC(>3:1)
- CAC 回收期 (<18 個月)
- 40 法則(>40%)
使用範本撰寫文件:請使用
assets/gtm_dashboard_template.md策略決策:調整支出分配、優化管道、提升留存率
季度業務檢討
整合這三項工具,進行全面的季度業務檢討(QBR)分析。
- 執行銷售管道分析器以進行前瞻性分析
- 執行預測追蹤器以評估回溯準確度
- 執行 GTM 計算器以建立效率基準
- 將銷售管道健康狀況與預測準確度進行交叉比對
- 將 GTM 效率指標與成長目標對齊
參考文件
| 參考 | 說明 |
|---|---|
| RevOps 指標指南 | 完整的指標層級結構、定義、計算公式及解讀 |
| 管道管理框架 | 銷售管道最佳實踐、階段定義及轉換基準 |
| 市場進入(GTM)效率基準 | 按階段劃分的 SaaS 基準值、產業標準與改善策略 |
範本
| 範本 | 應用案例 |
|---|---|
| 銷售管道審查範本 | 每週/每月銷售管道檢視文件 |
| 預測報告範本 | 預測準確度報告與趨勢分析 |
| GTM 儀表板範本 | 供高層審閱的 GTM 效率儀表板 |
| 銷售管道資料範例 | pipeline_analyzer.py 的輸入範例 |
| 預期輸出 | 來自 pipeline_analyzer.py 的參考輸出 |
---
name: revenue-operations
description: Analyzes sales pipeline health, revenue forecasting accuracy, and go-to-market efficiency metrics for SaaS revenue optimization.
---
# 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 |
所有檔案
0 個檔案安裝 revenue-operations
請下載並將技能檔案解壓縮至您的 .claude/skills/ 目錄中。
下載 ZIP複製儲存庫並將技能檔案複製到您的專案中。
git clone https://github.com/alirezarezvani/claude-skills/tree/main/business-growth/skills/revenue-operations # Copy SKILL.md to your .claude/skills/ directory
複製





首頁
