Weighted Pipeline

A weighted pipeline is a business development forecasting metric that multiplies each opportunity's total contract value by its estimated win probability to produce an aggregate expected value that more accurately reflects the revenue a company is likely to win from its current pursuit portfolio.

What is a Weighted Pipeline?

Raw pipeline value sums all opportunities regardless of likelihood of winning, making it an optimistic ceiling rather than a realistic forecast. The weighted pipeline corrects for this by applying a probability-of-win (Pwin) estimate to each opportunity before summing, producing an expected revenue figure analogous to expected value in probability theory.

For example, a company with three opportunities, a $10M pursuit at 70% Pwin, a $5M pursuit at 30% Pwin, and a $20M pursuit at 20% Pwin, has a raw pipeline of $35M but a weighted pipeline of ($10M × 0.70) + ($5M × 0.30) + ($20M × 0.20) = $7M + $1.5M + $4M = $12.5M. Leadership can compare this $12.5M expected value against its $10M revenue target to assess coverage adequacy.

Win probabilities in the weighted pipeline are not static. They change as capture matures: an opportunity at Gate 0 might carry a 15% baseline Pwin, which rises to 40% when the RFP drops with no surprises, and to 65% after a successful proposal submission where the company is confident in its competitive position. Many GovCon BD systems use stage-based default Pwin percentages (e.g., 10% at identification, 25% at qualification, 50% at active capture, 70% at proposal submission) combined with judgment-based adjustments for incumbency advantage, competitive field size, and customer relationship strength.

Why weighted pipeline matters for government contractors

Raw pipeline value is easy to inflate by adding marginal opportunities. Weighted pipeline forces honest probability assessment, making it a more reliable revenue planning tool. Companies whose weighted pipeline significantly undercovers their revenue target need to add opportunities or re-evaluate pursuit investments, not simply add more long-shot bids to inflate the raw metric.

Example

A government IT firm's pipeline contains 15 opportunities totaling $200M in raw value. Applying stage-based and judgment-adjusted Pwin estimates produces a weighted pipeline of $52M. Against a $30M new business target, this represents 1.7x weighted coverage, below the company's minimum 2x weighted coverage standard. The BD team identifies three additional $8M opportunities to add to the pipeline, bringing weighted coverage to 2.1x, within acceptable range.

Frequently Asked Questions

How should win probabilities be assigned in a weighted pipeline?

The most common approach is to combine stage-based default probabilities with judgment factors. A capture manager might start with a 25% default at the proposal stage and then add 10 points for incumbent status, subtract 10 points for a large competitive field, and add 5 points for a strong known customer relationship. The final probability should represent the team's honest assessment of win likelihood given all available intelligence.

Should lost bids remain in the weighted pipeline?

Lost bids should be removed from the pipeline immediately upon notification and the accurate outcome recorded in the company's win/loss database. Keeping losses in the pipeline inflates the metric and distorts forecasting. Prompt removal also triggers a lessons learned review.

What weighted pipeline multiple should a company maintain?

A weighted pipeline of 1.5x to 2x the new revenue target is typically sufficient for companies with consistent win rates. Companies in new markets, competing outside their core competency, or with lower historical win rates should maintain higher multiples (2x to 3x) to account for greater uncertainty in their Pwin estimates.

How does weighted pipeline differ from a sales funnel in commercial businesses?

The concept is similar, applying probability to deal value at different stages, but GovCon pipelines have longer cycles (18-36 months is common for major programs), fewer deals with much larger individual values, and probability estimates influenced by public procurement data rather than private sales relationships. The weighted pipeline methodology is the same; the data inputs and timescales differ.