Most revenue forecasts are arithmetic performed on invented numbers. The math is fine. The inputs came from a dropdown menu.
Open any CRM and follow the forecast back to its source. Each open deal carries a value and a stage. Each stage carries a probability. Multiply, sum, report to the board. The output looks like a measurement. What it actually reports is whatever the stage probabilities were set to, and in most firms nobody set them.
Your CRM shipped with probabilities from a template
HubSpot assigns close probabilities to deal stages out of the box. Pipedrive lets you switch stage probability on and pick a value per stage. Salesforce ships defaults tied to stage the same way. All of them are editable, and the defaults exist so the field is not blank on day one. None of them were ever a claim about your business.
So a firm running the template forecasts an 80 percent close on every deal sitting at Proposal Sent, because a product manager somewhere picked 80 as a sensible starting value. That firm’s real close rate from Proposal Sent, measured across its own last four quarters, is 31 percent. The forecast is wrong by a factor of two and a half at the exact stage holding the most dollars.
Nobody catches it, because the error is not in the arithmetic. Everything sums correctly.
The shape I keep finding, on illustrative numbers: 38 open deals, average value $46,000, weighted at template probabilities to $684,000 for the quarter. Actual bookings, $290,000. That firm did not miss by 58 percent because the team went soft. It missed because the number was never a forecast.
The coverage ratio you quote is folklore
“We need three times coverage” is the most repeated number in sales management and almost nobody can say where it came from. It is a fine rule if your win rate happens to be 33 percent. It is negligence if your win rate is 15.
Coverage is one divided by your win rate on qualified opportunities, then adjusted for the share of pipeline that will still be open when the period ends. A firm closing 15 percent needs something near seven times coverage to land its number. A firm closing 45 percent needs a little over two. Same rule, opposite operating conclusion. One of those firms is in a prospecting emergency and the other is burning capacity building pipeline it cannot service.
Run the division before you set the target. It takes four minutes and it separates a quota that can be hit from a quota that is a wish.
A deal that stops moving is not a sixty percent deal
Stage probability treats position as the only variable. A deal that entered Negotiation last Tuesday and a deal that has been parked in Negotiation since March carry identical weight in the forecast. Only one of them is alive.
Age is the cheapest signal in the pipeline and most forecasts throw it away. Pull the median days-in-stage for the deals you eventually won, stage by stage. Anything sitting past double that median is no longer a late-stage deal. It is a stalled deal wearing a late-stage label.
The fix is mechanical, and it belongs in the CRM rather than in a rep’s judgment. Past 1.5 times the median cycle time for a stage, the deal drops to the weight of the prior stage. Past 2 times, it leaves the forecast and moves to a nurture list. A deal does not have to be deleted to stop counting.
Rep confidence belongs outside the math
Commit, best case, pipeline. Three buckets, filled in by the person with the most invested in the answer. The bias there is not random noise that cancels out across a team. It runs in one direction, it grows with every meeting the rep has already spent, and it peaks in the last two weeks of the quarter, which is precisely when the forecast is being used to make decisions.
Replace the confidence question with evidence questions. Has the buyer named a decision date out loud. Has anyone in their legal or procurement function seen paperwork. Has a second person besides the champion spoken on a call. Those are binary, they are checkable by someone other than the rep, and a deal missing all three does not belong in Commit no matter how the last conversation felt.
That is also the difference between a stage and a status. A stage advances when the buyer does something observable, not when the seller feels good about the call. Probabilities are only stable if the stage means the same thing every time it is used.
Weighted pipeline hides the two numbers that matter
A weighted forecast collapses volume and conversion into a single figure, which is the wrong shape for a diagnosis. $684,000 weighted tells you nothing about whether you have a top-of-funnel problem or a closing problem.
Report the two separately. Deal count entering each stage, and stage-to-stage conversion. When the number misses, one of those two moved, and you will know which one inside a minute. Firms tracking only the weighted total spend the following quarter guessing, and the guess almost always lands on “we need more leads,” because that is the reflexive answer and it is the one that requires nobody in the room to change how they work.
Sometimes the volume really is the constraint, and the fix is upstream in who is on the list. More often the constraint is conversion, and the cause is everything the team refused to disqualify three stages ago.
Rebuild the forecast from your own closed deals
You already have the data. Export every deal closed in the last twelve months, won and lost. For each one, record the stage it occupied 90 days before its close date. Group by that stage, then compute the share that eventually closed won. That percentage is your real stage probability, derived from your buyers, your sales cycle, your pricing.
Two caveats worth stating. Below roughly 40 closed deals in a stage the result is noise, so pool adjacent stages or widen the window to 24 months. And if you moved your ICP or repriced during the period, split the sample at that change and use the recent half. A probability derived from a business you no longer run is worth no more than the template.
Then write those numbers into the CRM. Ten minutes of configuration in HubSpot. The forecast will drop, often by 30 to 50 percent, and the smaller number will be the first one that ever meant anything.
Real probabilities fix the debrief downstream too. You stop arguing about whether a deal should have closed and start measuring it against a base rate, which is the only way a win-loss review produces anything a team can act on.
The check you can run this week
Pull your last twelve months of closed deals. Compute the actual win rate from each stage. Set those numbers beside the probabilities your CRM is using right now. If any stage is off by more than ten points, every forecast you submitted this year was fiction with a decimal on it.
Most firms find the gap at Proposal. A few find it at Discovery, which is worse, because it means the qualification standard is broken and everything downstream inherits the error.
Florida Man Innovations builds revenue systems that report what is actually happening, and Farsight Intelligence handles the questions that come up when the counterparty is the thing you cannot verify. If your forecast and your bank statement have been telling different stories all year, the gap is structural. Fix what the system reports before you go after how the team works. More at brettfl.com, time at meet.brettfl.com, or write me directly at [email protected].
Use your own numbers.