Weighted Pipeline: Useful as an Indicator, Dangerous as a Forecast

Weighted pipeline is what you get when every open deal is multiplied by a probability attached to its stage and the results are added up. A deal worth ten lakh at a stage that historically converts at three in ten contributes three lakh rather than ten. The purpose is to make two pipelines of the same size comparable when their composition differs, because a large pipeline of early-stage deals is worth far less than a smaller one sitting mostly at negotiation. It is a useful indicator of shape and coverage, and it is routinely misused as a revenue forecast, which it cannot be.

Weighted pipeline equals the sum, across all open opportunities, of deal value multiplied by the probability assigned to that deal's stage.

The only difficult input

The arithmetic is trivial and the probabilities are not. A stage probability should be the observed proportion of opportunities that reached that stage and eventually closed won, calculated from your own history over a period long enough to contain a reasonable number of outcomes, and calculated separately for each distinct sales motion. Default percentages supplied with software are round numbers chosen for tidiness, and a weighted total built on them is arithmetic performed on fiction.

A worked example (illustrative figures)

Four open deals. Deal A, ₹10,00,000, at qualification, historic conversion 10%, contributes ₹1,00,000. Deal B, ₹6,00,000, at discovery, 25%, contributes ₹1,50,000. Deal C, ₹8,00,000, at proposal, 50%, contributes ₹4,00,000. Deal D, ₹4,00,000, at negotiation, 75%, contributes ₹3,00,000. Raw pipeline is ₹28,00,000. Weighted pipeline is ₹9,50,000. Now consider a second team with the same ₹28,00,000 raw total, but with ₹20,00,000 of it at negotiation. Their weighted figure would be far higher, and the two teams are in genuinely different positions despite identical headline pipelines. That comparison is the thing weighting is good for.

It answers a coverage question: given what is open and where it sits, is there plausibly enough to hit the number? Comparing weighted pipeline against the revenue still required gives a far better sense of that than the raw total, which treats a deal created yesterday as equivalent to one in contract review.

It is also useful over time. Tracking the weighted figure week by week shows whether the pipeline is maturing or merely accumulating. A raw total that grows while the weighted total stays flat means new deals are arriving at the front and nothing is progressing, which is a pattern worth catching early and easy to miss in a headline number.

Small numbers

Expected value is a statement about many trials. With eight open deals, the weighted figure describes an average of outcomes that will not occur; the actual result will be some subset of whole deals closing, and it will rarely land near the weighted number. The fewer and larger the deals, the less the calculation means, and businesses selling a handful of large contracts a quarter get almost nothing from it.

Correlated outcomes

Weighting assumes deals succeed or fail independently, and they often do not. A budget freeze, a seasonal slowdown or a competitor's aggressive quarter moves many deals in the same direction at once. When that happens the weighted figure is wrong for every deal simultaneously rather than averaging out, which is precisely when an accurate forecast would have been most valuable.

Stale values and dates

Two unglamorous problems do more damage than any modelling issue. Deal values entered at creation and never revised drift away from reality, and deals with optimistic or missing close dates get weighted into a period they cannot land in. Both are data hygiene rather than method, and both are usually larger than the error introduced by imperfect probabilities.

Always show it next to the raw total and the deal count. The relationship between the three is the information: a weighted figure far below the raw total means an early-stage pipeline, and a small deal count means the weighted number should be treated as a rough indication rather than a projection.

Then check aging. Stage probability is an average across deals that reached that stage, most of which moved through it at normal speed. A deal that has been at proposal for four months converts far below the stage average, and no weighting scheme knows that unless you filter for it. Between the two adjustments, close date and aging, most of the practical inaccuracy in a weighted total can be removed without touching the probabilities at all.

These four are frequently confused with each other and answer different questions.

The most common mistake is to apply weighting on top of a judgement-based forecast, discounting deals that a salesperson has already discounted in deciding to commit them. That double-counting produces a figure that is pessimistic for no principled reason. Pick one method for the period forecast and use the other as a check.

Weighting is only as good as the stage discipline underneath it. Start with what a CRM is, then look at sales automation for keeping deals moving, AI CRM for surfacing stalled opportunities, lead management software, CRM versus Excel for why stage history matters, and sales use cases.