Forecasting revenue from pipeline, honestly

An honest revenue forecast multiplies each open deal's value by the measured conversion rate of its pipeline stage — not by a percentage anyone feels — and reports the result as a range, not a number. Built this way, a forecast for a 5–50-staff service firm fits in one CRM report and gets more accurate every quarter, because each quarter's outcomes recalibrate the weights. Everything else about forecasting is discipline around close dates and stage definitions.

Why are most small-firm forecasts fiction?

Because they are built from confidence, and confidence is not data. The standard method — ask each salesperson how likely each deal is, multiply, add up — inherits every human bias in the room: optimism about pet deals, sandbagging before target reviews, and the universal reluctance to admit a deal has died. The result swings with mood, and nobody can say afterwards why it was wrong, because the inputs were never measurable in the first place.

The honest alternative uses the pipeline's own history. If deals that reach proposal stage have gone on to close roughly a third of the time over the past year, then a proposal-stage deal is worth roughly a third of its value in the forecast — regardless of how anyone feels about it. The number belongs on the same self-compiling instrument panel described in The MD Dashboard Blueprint: read, not negotiated.

What do you need before forecasting is even possible?

Three preconditions, all upstream of any formula:

1. Stages defined as verifiable events. When "Qualified" means whatever each rep wants, conversion rates from Qualified are noise. Event-based stage design — covered in pipeline stages that mean something — is the foundation.
2. A pipeline purged of dead deals. Immortal deals inflate every stage's value and quietly rot the historical conversion rates too.
3. Enough history to measure. Two to four quarters of closed outcomes is a workable start. With less, use conservative placeholder weights, label them as placeholders, and let the data replace them.

Skip these and the forecast automates fiction — faster fiction, with more decimal places.

How does the mechanism work?

Five steps, all repeatable monthly:

1. Measure stage-to-close conversion. When a deal entered proposal stage during the look-back window, then record whether it eventually closed won. Do this for every stage; the resulting percentages are your weights.
2. Weight the open pipeline. When a deal sits in a stage, then its forecast contribution is deal value × that stage's measured rate. Sum by expected close month.
3. Report a range. When the weights are applied, then publish the weighted total flanked by a plausible band — commonly the weighted figure, a floor of deals in the final stage only, and a ceiling adding late-stage deals at full value. A single-point forecast invites false precision; a range invites planning.
4. Time-decay the strays. When a deal's close date has been rolled forward more than twice, then its weight is cut or the deal is flagged for a close-or-kill decision. Serial re-daters are the forecast's biggest single error source.
5. Recalibrate quarterly. When the quarter closes, then compare forecast to actual, recompute the stage weights, and write down the miss. The forecast's error history is itself a management number.

When the weights come from measured history and the pipeline is clean, then the forecast stops being a debate and becomes arithmetic — arguable only at the level of its inputs, which is exactly where argument is useful.

How accurate can a small firm expect this to be?

Honestly: modestly, and that is still transformative. With a few dozen deals a quarter, sample sizes are small and one large deal can swing the outcome, which is precisely why the range matters more than the midpoint. What the method reliably delivers is not clairvoyance but early warning — a weighted pipeline that sags below the run-rate needed for next quarter's payroll is visible months before the revenue misses. The response is then mechanical: open more deals or convert better. Which lever to pull is a constraint question — find the narrowest point in the machine, as set out in the theory of constraints applied to a service firm, rather than pushing everywhere at once.

Two companion numbers sharpen the forecast considerably. Win rate — measured properly, segmented, and watched over time, as covered in win rate: the number that sets your prices — is the forecast's most sensitive input. And pipeline velocity tells you when the weighted value will land, not just whether.

What does this look like in practice?

A single saved report: open deals, stage, value, weighted value, expected month — totalled into a three-line summary of floor, likely and ceiling. It lives beside the other dozen management numbers, refreshes itself, and takes a minute to read. No spreadsheet gymnastics, no BI project — the reporting layer from dashboards without the BI project carries it comfortably. The MD stops asking "how does the quarter look?" because the answer is already on the wall, with its error bars showing.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks, including whether your pipeline can support an honest forecast, and what to build first.