Sales pipeline forecasting from stage conversion rates

Forecasts are usually wrong for one of two boring reasons: the data is dirty, or the pipeline arrives in bursts.

The basic method

Take how many opportunities sit at each stage, apply the rate at which each stage historically converts to the next, and you have an expectation. That is the whole mechanism; the difficulty is entirely in the inputs.

What has to be true first

Three conditions, and forecasts fail when any is missing:

1. Stages mean something, and everyone applies them the same way.
2. Records are current, so the pipeline reflects reality.
3. Enough volume, that conversion rates are not noise.

A worked forecast

Numbers make the method obvious. Take a pipeline holding 60 discovery calls, 24 proposals and 9 deals in negotiation, with historical rates of 40% from discovery to proposal, 38% from proposal to negotiation and 55% from negotiation to closed won.

• Negotiation: 9 × 0.55 = about 5 deals.
• Proposal: 24 × 0.38 × 0.55 = about 5 deals.
• Discovery: 60 × 0.40 × 0.38 × 0.55 = about 5 deals.

Fifteen deals in total, which at an average value of €6,000 gives €90,000. The important part is what the split tells you: only a third of that revenue is close to landing. The discovery-stage third will close a quarter or two later, if the cycle length holds. A forecast that reports one figure and hides that timing is the most common way a number becomes useless.

Three forecasting methods, and when each fits

• Stage-weighted. The method above. Best when you have enough deals for the rates to mean something and a sales cycle that does not vary wildly.
• Run rate. Take what closed in the last three months and project it forward. Crude, but harder to fool yourself with, and often more accurate than a weighted model built on twelve deals.
• Rep commit. Each deal is marked commit, best case or pipeline by the person running it, with a written reason. Slow, subjective, and the most accurate method inside the current quarter, because a human knows things the CRM does not.

Most teams should run two: a stage-weighted number for the quarter after next, and a commit list for the current one. When the two disagree badly, the gap itself is worth a conversation.

Forecasting backwards from a revenue target

The same arithmetic works in reverse, and this is the version that actually changes behaviour. Start from the revenue you need, divide by average deal value to get the number of deals, then walk back up your conversion rates to the number of meetings, and from meetings to the number of prospects the top of the funnel has to carry.

Do that once and the forecasting problem usually turns out to be a prospecting problem. If a quarterly target needs 20 deals and your own history says meetings convert to deals somewhere between 10% and 20%, that is 100 to 200 meetings, which for most B2B offers means several thousand prospects contacted. Cold email reply rates on a clean list stay in low single digits, and only a share of those replies are positive, so the required volume climbs quickly. Realistic figures for each step are collected in outbound benchmarks, and the KPIs worth watching alongside the forecast are in the KPIs worth tracking.

Why forecasts swing

The usual culprit is a pipeline filled in bursts. A month of heavy prospecting followed by a month of none produces a forecast that lurches, and no amount of spreadsheet sophistication fixes it.

A steady flow of new conversations is what makes a forecast stable, which is the least exciting and most important part of the answer.

Stale deals distort everything

A deal sitting untouched in a late stage inflates the forecast while being, in practice, already lost. Regular cleanup is not tidiness, it is what stops the number from lying. This is where CRM hygiene pays for itself.

What a bad forecast tells you

If the number is consistently wrong in one direction, that is information. Consistently high usually means dead deals are not being closed out. Consistently low usually means stage criteria are too strict. Either way it points at the process rather than the spreadsheet.

Forecasting mistakes and their fixes

• One blended conversion rate for every deal type. Enterprise and small-business deals convert at different rates over different timescales, and averaging them produces a number that describes neither. Fix: forecast segments separately, along the lines set out in enterprise vs. SMB outbound.
• Letting stage definitions drift. If one person moves a deal to proposal when they send pricing and another when the buyer asks for it, the rates are meaningless. Fix: write one exit criterion per stage and review it quarterly. MQL and SQL explained covers the same problem at the top of the funnel.
• Close dates that never move backwards. A deal pushed from March to June to September is not a live deal. Fix: cap the number of times a close date can slip before the deal is reset or lost.
• Forecasting from a pipeline nobody has touched. An opportunity with no activity for six weeks should not carry weight. Fix: add a last-activity filter to the forecast view before anyone reads the number.
• Never checking the forecast against what happened. Fix: compare forecast to actual every quarter and note why the gap existed. Win-loss analysis turns that habit into something the whole team can use.

Forecasting pipeline that came from outbound

Outbound-sourced pipeline behaves differently from inbound, and mixing them in one model hides the difference. An inbound lead arrived because it had a problem today. An outbound prospect agreed to a meeting because the timing happened to suit, which means a larger share of those deals stall in the middle rather than losing outright.

Two practical adjustments. First, expect a lag: a new campaign takes weeks to produce meetings and a full sales cycle beyond that to produce revenue, so the first quarter of any outbound programme forecasts poorly by nature. Second, hold stalled outbound deals in a separate bucket rather than in the main forecast, and work them through a nurture track. They still close, just not on the timeline the model assumes.

If your deal count is small enough that percentages swing on a single win, do not build a weighted model at all. Forecast on run rate, track meetings booked per week as the leading indicator on your outbound reporting dashboard, and revisit stage rates once you have several months of consistent volume behind you. A steady top of funnel comes first, and every other part of forecasting depends on it.