Before trusting any detailed forecast, revenue leaders run one simple check: pipeline coverage ratio — total open pipeline value divided by the revenue target for the period. If coverage is too low, no amount of forecasting sophistication fixes the underlying problem, because there simply isn't enough open pipeline in the system to produce the target even at a strong win rate. Coverage is a volume check that has to pass before a win-rate-weighted forecast is worth building at all.

The coverage ratio formula and typical targets

Coverage Ratio = Total Open Pipeline Value ÷ Revenue Target

Most B2B sales organizations target somewhere between 3x and 5x coverage, and the right multiple for a given team depends directly on its historical win rate: a team with a 33% win rate needs roughly 3x coverage just to hit target on average (since two out of three dollars of pipeline won't close), while a team with a 15% win rate needs closer to 6-7x. Copying a generic '3x coverage' target without checking it against your own win rate produces a forecast that looks healthy on a dashboard and misses in reality.

coverage_ratio_example.txt

text

Quarterly revenue target:        $1,000,000
Current open pipeline value:     $3,200,000
Coverage ratio = 3,200,000 / 1,000,000 = 3.2x

Historical win rate for this team: 28%
Implied "required" coverage at this win rate ~ 1 / 0.28 = 3.6x

READ: 3.2x coverage is slightly BELOW what this team's own
win rate requires (3.6x) to reliably hit $1M — a gap worth
flagging even though 3.2x looks fine against a generic "3x" rule.

Forecast categories and what each one assumes

Forecast category	What it includes	Confidence assumption
Commit	Deals the rep is confident will close this period	Near-certain — reps should rarely miss their own commit
Best case	Commit deals + upside deals that could close with favorable movement	Possible but not expected — the optimistic ceiling
Pipeline (weighted)	All open deals, each weighted by stage-based win probability	Probabilistic — a statistical estimate, not a prediction
Worst case	Only deals considered essentially guaranteed, no judgment calls	Conservative floor — what happens if nothing goes right

Weighted pipeline vs. commit/best-case/worst-case

Weighted pipeline forecasting multiplies each open deal's amount by a probability tied to its current stage (a deal in late-stage negotiation might carry 80% weight, a deal still in discovery might carry 10%), then sums the results into a single statistical expected value. This works well in aggregate across a large number of deals but can be misleading applied to a small number of large deals, since a single big deal's actual binary outcome (closes or doesn't) gets smoothed into a fractional number that no individual deal will actually produce. Commit/best-case/worst-case forecasting instead asks reps to make an explicit human judgment call on each deal's bucket, which captures context a stage-probability model can't see (a champion just left the company, a competitor just undercut on price) but is vulnerable to individual rep optimism or sandbagging bias.

weighted_vs_judgment_forecast.txt

text

WEIGHTED PIPELINE (stage-probability model)
  Deal A: $200,000 @ stage weight 80%  = $160,000
  Deal B: $150,000 @ stage weight 40%  = $60,000
  Deal C: $300,000 @ stage weight 20%  = $60,000
  Weighted forecast total:               $280,000

REP JUDGMENT (commit / best-case / worst-case)
  Commit:      Deal A only              = $200,000
  Best case:   Deal A + Deal B          = $350,000
  Worst case:  none fully guaranteed    = $0

READ: The weighted model ($280K) sits between the rep's worst
case ($0) and best case ($350K) — useful as a cross-check, but
the rep's commit number is what management should hold them to.

The best forecasting process triangulates, rather than trusting one method

Mature forecasting compares the weighted-pipeline number, the rolled-up rep commit number, and the coverage ratio against each other every cycle. When all three roughly agree, confidence in the forecast is high. When they diverge significantly — commit is high but coverage is thin, or weighted pipeline is strong but no individual rep will commit to it — that divergence itself is the signal worth investigating before the number goes to the board.

Stage-based weighting breaks down if stage definitions aren't enforced

Weighted pipeline forecasting assumes a deal's CRM stage accurately reflects its real progress — but reps under pressure routinely advance deals to later stages to make personal pipeline look healthier, which inflates the weighted forecast without any real change in likelihood of closing. This is the same data-integrity discipline from CRM data modeling and lifecycle stage governance, applied to the Deal object instead of the Contact object: stage changes need enforced criteria, not manual rep discretion alone.

What's next

Forecasting accuracy, like every other metric in this track, depends on a clean, consistently defined data model underneath it — revisit CRM Data Modeling if stage or object definitions are the weak link in your own forecast.

Next: CRM Data Modeling →

I build these systems professionally.

Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.

Work With Me →

Need production AI or MarTech expertise? I build custom LLM workflows, server-side GTM tagging, and analytics infrastructures professionally.

Need custom AI or MarTech setup? Let's build together.

Let's talk →