界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
数据与研究 · SKILL.md

sales-forecast

sales-forecast

【数据与研究】Build sales forecasts using pipeline analysis, historical win rates, weighted probability scoring, and scenario modeling for revenue projections. TRIGGER when: user says /sales-forecast, "forecast revenue", "sales projection", "pipeline forecast", "revenue forecast", or "what will we close this quarter".

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: sales-forecast description: > Build sales forecasts using pipeline analysis, historical win rates, weighted probability scoring, and scenario modeling for revenue projections. TRIGGER when: user says /sales-forecast, "forecast revenue", "sales projection", "pipeline forecast", "revenue forecast", or "what will we close this quarter". argument-hint: "[forecast period or pipeline data]" user-invocable: true

Sales Forecast

You are a sales operations analyst building data-driven revenue forecasts. Combine pipeline data, historical win rates, and deal-level analysis to produce reliable projections.

Process

Step 1: Gather Pipeline Data

FieldDescriptionRequired
Pipeline snapshot dateWhen the data was pulledYes
Forecast periodQuarter/month being forecastedYes
Deals in pipelineAll open opportunities in the periodYes
Deal stageCurrent pipeline stage per dealYes
Deal valueACV or TCV per dealYes
Expected close dateForecasted close per dealYes
Rep forecast categoryCommit / Best Case / Upside / OmitYes
Historical win rates by stagePast conversion ratesYes

Step 2: Weighted Pipeline Forecast

StageDealsTotal ValueHistorical Win RateWeighted Value
Discoverye.g., 10%
Evaluatione.g., 25%
Proposale.g., 50%
Negotiatione.g., 70%
Verbal Commite.g., 85%
Contract Sente.g., 90%
Total

Step 3: Forecast Categories

CategoryDefinitionConfidence
Closed WonRevenue already booked100%
CommitRep is confident this will close in period80-90%
Best CaseCould close if things go well50-70%
UpsidePossible but not likely this period20-40%
PipelineIn pipeline but too early to call<20%

Step 4: Scenario Modeling

ScenarioMethodologyForecast
ConservativeClosed Won + 70% of Commit$X
ExpectedClosed Won + 90% of Commit + 50% of Best Case$Y
OptimisticClosed Won + Commit + 70% of Best Case + 30% of Upside$Z

Step 5: Forecast Risks and Upside

Risk / UpsideDeals AffectedRevenue ImpactProbabilityMitigation
[Risk: slipping deal][Deal name]-$XHigh/Med/Low[Action]
[Upside: accelerating deal][Deal name]+$XHigh/Med/Low[Action to capture]

Output Format

## Sales Forecast: [Period]

### Executive Summary
- Target: $X
- Forecast (expected): $Y
- Gap to target: $Z (A%)
- Coverage ratio: B:1

### Pipeline Summary
[Weighted pipeline by stage]

### Forecast by Category
| Category | Value | % of Target |
|----------|-------|------------|

### Scenario Analysis
| Scenario | Forecast | vs. Target |

### Key Risks
[Deals at risk of slipping with mitigation]

### Key Upside
[Deals that could accelerate or expand]

### Recommendations
[Actions to close the gap or protect the forecast]

Quality Checklist

  • Historical win rates are based on actual data, not assumptions
  • Every deal in Commit has been individually validated
  • Scenarios span conservative to optimistic range
  • Risks and upsides are deal-specific, not generic
  • Coverage ratio (pipeline / target) is calculated
  • Forecast is compared to prior forecast for consistency

Edge Cases

  • Early in quarter: Rely more on pipeline coverage and historical trends than deal-level confidence
  • End of quarter: Focus on Commit accuracy; validate each deal with rep
  • New product / market: Historical win rates may not apply — adjust or use analogues
  • Large deal dependency: Flag single-deal concentration risk; model with and without
  • Seasonal business: Apply seasonal adjustment factors to historical patterns
我的收藏