Weighted Forecast: Definition, Formula + Fairview Guide

Weighted Forecast — A revenue projection method that multiplies each open deal's value by its probability of closing based on pipeline stage. A $100K deal at a stage with 40% historical close rate contributes $40K to the weighted forecast. The method produces a probability-adjusted view of expected revenue.

TL;DR: A weighted forecast adjusts pipeline value by win probability at each stage. It gives operators a more realistic revenue projection than raw pipeline totals. Well-calibrated weighted forecasts land within 10-15% of actual closed revenue for companies with 6+ months of historical stage data (SaaStr, 2025).

What is a weighted forecast?

A weighted sales forecast (also called a probability-weighted forecast or stage-weighted pipeline forecast) is a revenue projection that assigns a closing probability to each deal based on its current stage in the pipeline. Instead of adding up every deal at face value, you multiply each deal's value by the likelihood it closes. The sum is the weighted forecast.

Raw pipeline is optimistic by design. Reps add deals at full value the moment a prospect shows interest. A $2M pipeline with a 30% average win rate will produce roughly $600K in closed revenue — not $2M. The weighted forecast corrects for this by applying probability to each stage. Early-stage deals are discounted heavily. Late-stage deals carry higher weight.

For B2B SaaS companies with a defined sales process (4-7 stages), a well-calibrated weighted forecast typically lands within 10-15% of actual results. The accuracy depends entirely on two factors: whether stage probabilities reflect real historical close rates, and whether reps move deals through stages honestly. If either breaks down, the forecast breaks with it.

A weighted forecast differs from a commit forecast. The weighted approach uses mathematical probabilities. The commit approach uses rep judgment — what they believe will close. Both have strengths. The weighted forecast removes rep bias. The commit forecast captures deal-specific context that probabilities miss.

Why weighted forecast matters for operators

Revenue planning depends on forecast accuracy. An operator who knows $620K will close this month can staff, spend, and commit with confidence. An operator guessing between $400K and $900K cannot.

The weighted forecast provides a probability-adjusted midpoint. It won't capture every deal surprise, but it removes the most common source of forecast error: treating all pipeline as equally likely to close. A $200K deal in discovery (10% probability) and a $200K deal in negotiation (70% probability) are not the same. The weighted forecast reflects this: $20K from the first, $140K from the second.

Operators who combine the weighted forecast with pipeline coverage ratio get a clearer picture. If the weighted forecast is $500K against a $600K target, coverage is 0.83x — below the 1:1 threshold. The operator knows immediately that either existing deals need to close at above-average rates or new pipeline must enter fast. Without the weighted view, the raw pipeline of $1.8M might make coverage look comfortable at 3x — hiding the probability-adjusted shortfall.

Weighted forecast formula

Weighted Forecast = Σ (Deal Value x Stage Probability)

Example pipeline:

| Deal        | Value     | Stage         | Probability | Weighted Value |
|-------------|-----------|---------------|-------------|----------------|
| Acme Corp   | $85,000   | Discovery     | 10%         | $8,500         |
| BetaCo      | $42,000   | Qualification | 25%         | $10,500        |
| GammaTech   | $128,000  | Proposal      | 50%         | $64,000        |
| Delta Inc   | $67,000   | Negotiation   | 70%         | $46,900        |
| Epsilon Ltd | $93,000   | Contract Sent | 90%         | $83,700        |

Raw Pipeline Total: $415,000
Weighted Forecast: $213,600

What each component means:

Deal Value: The expected contract value if the deal closes. Use the most current estimate, not the original amount entered. Deals often resize during negotiation.
Stage Probability: The historical close rate for deals reaching this stage. This should come from your actual CRM data — not default CRM stage percentages. Default percentages (10%, 25%, 50%, 75%, 90%) are placeholders. Replace them with your real conversion data after 6 months.

Variant — time-weighted forecast: Some teams add a time decay factor for deals that have been in the same stage beyond the median duration. A deal sitting in "Proposal" for 45 days when the median is 14 days gets a reduced probability.

Weighted forecast accuracy benchmarks

How weighted forecast accuracy varies by company maturity and data quality. Accuracy measured as actual closed revenue / weighted forecast.

Segment	Good Accuracy	Average	Below average	Action if below benchmark
SaaS with 12+ months CRM data	85-95% (±10%)	75-85%	<75%	Recalibrate stage probabilities from actual close rates
SaaS with 6-12 months CRM data	75-90%	65-75%	<65%	Supplement with rep commit data; blend both methods
SaaS with <6 months CRM data	60-80%	50-60%	<50%	Use commit forecast as primary; weighted as secondary
Companies with long sales cycles (6+ months)	70-85%	60-70%	<60%	Add time-decay factor; recalibrate quarterly

Sources: SaaStr 2025 Forecast Accuracy Report, Pavilion COO Survey 2025, industry-observed ranges from operator benchmarks.

Common mistakes when building a weighted forecast

1. Using default CRM stage probabilities instead of actual close rates

HubSpot and Salesforce ship with placeholder probabilities (10%, 25%, 50%, 75%, 90%). These are generic. Your actual close rate from "Proposal" might be 35%, not 50%. After 6 months of data, replace every default with your real stage-to-close conversion rate.

2. Not updating deal values as they progress

A deal enters the pipeline at $120K. During negotiation, scope changes reduce it to $85K. If the deal value isn't updated, the weighted forecast carries an extra $35K in phantom revenue. Require reps to update deal amounts when scope changes — not just at close.

3. Treating all stages as independent

Stage probabilities assume a deal that reaches "Proposal" has the probability assigned to that stage. But deals that skip stages (jumping from discovery to proposal) or that have been pushed back from a later stage have different close rates. Track stage progression quality, not just stage position.

4. Ignoring deal age within a stage

A deal that has been in "Negotiation" for 8 days is different from one that has been there for 60 days. The second deal is stalling. Apply a time-decay factor to deals that exceed the median stage duration by more than 50%. This prevents stale deals from inflating the forecast.

5. Not reconciling weighted forecast to actual results monthly

The only way to know if your probabilities are accurate is to compare the forecast to reality. Every month, calculate: weighted forecast at month start vs. actual closed revenue. If the gap exceeds 20% for three consecutive months, recalibrate your stage probabilities.

How Fairview tracks weighted forecast automatically

Fairview's Forecast Confidence Engine connects to your CRM (HubSpot, Salesforce, Pipedrive) and calculates a weighted forecast using your actual historical close rates — not default CRM percentages.

The Pipeline Health Monitor tracks deal progression and flags deals that have stalled beyond the median stage duration. These deals are automatically flagged with reduced confidence in the weighted view, preventing stale pipeline from inflating the number.

The Operating Dashboard shows the weighted forecast alongside the raw pipeline total and the commit forecast, so operators can compare mathematical probability against rep judgment in a single view. When the gap between weighted and commit exceeds a configurable threshold, Fairview surfaces the specific deals causing the divergence.

→ See how the Forecast Confidence Engine works

Weighted forecast vs commit forecast

Operators often debate which forecasting method to trust. Both are useful. They answer different questions.

	Weighted Forecast	Commit Forecast
What drives it	Mathematical probability based on stage and historical data	Rep and manager judgment on specific deals
Removes bias?	Yes — stage probabilities override rep optimism	No — relies on rep confidence, which is often inflated
Captures deal context?	No — treats all deals at the same stage equally	Yes — reps know which champion left, which budget shifted
Best accuracy when	6+ months of historical data, stable sales process	Experienced reps, consistent commit definitions
Risk	Stale probabilities; doesn't detect deal-specific risk	Rep sandbagging or overcommitting

The most accurate approach is blending both. Use the weighted forecast as the mathematical baseline. Layer in commit data to adjust for deal-specific context. When the two numbers diverge significantly, the deals causing the gap deserve immediate review.

FAQ

What is a weighted forecast in simple terms?

A weighted forecast multiplies each deal in your pipeline by its probability of closing based on its current stage. A $100K deal with a 40% close probability contributes $40K to the forecast. The total gives you a probability-adjusted revenue projection that is more realistic than adding up raw pipeline values.

What is a good accuracy rate for a weighted forecast?

Companies with 12+ months of CRM data and calibrated stage probabilities typically achieve 85-95% accuracy — meaning actual closed revenue lands within 10-15% of the weighted forecast. Below 75% accuracy usually means stage probabilities don't reflect real close rates and need recalibration.

How do you calculate a weighted forecast?

Multiply each open deal's value by its stage probability, then sum the results. If you have 5 deals worth $415K total and the probability-weighted values sum to $214K, your weighted forecast is $214K. Use your actual historical close rates for each stage, not default CRM percentages.

What is the difference between a weighted and commit forecast?

A weighted forecast uses mathematical probabilities assigned to pipeline stages. A commit forecast uses rep and manager judgment about which specific deals will close. Weighted forecasts remove human bias. Commit forecasts capture deal-specific context that math alone misses.

How often should you update a weighted forecast?

Weekly for operational planning and deal review meetings. Monthly for board and investor reporting. Recalibrate the underlying stage probabilities quarterly using your last 6-12 months of actual close data. After any major change in sales process or team composition, recalibrate immediately.

How do you improve weighted forecast accuracy?

Replace default CRM stage probabilities with your actual historical close rates. Require reps to update deal values when scope changes. Add a time-decay factor for deals stalling beyond median stage duration. Reconcile forecast to actuals monthly and recalibrate when accuracy drops below 80%.

Related terms

Sales Forecast — Broader category of revenue projection methods, including weighted, commit, and historical approaches
Pipeline Coverage Ratio — Total pipeline value relative to quota or target; measures whether enough pipeline exists
Forecast Confidence — A score reflecting how likely the current forecast is to be accurate
Bottom-Up Forecast — A forecast built from individual deal and rep data rather than top-down targets
Win Rate — The percentage of deals that close; the foundation of stage probability assignments

Fairview is an operating intelligence platform that generates weighted forecasts from your actual CRM data alongside pipeline coverage and forecast confidence. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built the Forecast Confidence Engine after watching operators rely on pipeline totals that looked healthy at 3x coverage but produced forecast misses of 30% or more every quarter.

Weighted Forecast