Forecasting

For eleven weeks of one quarter I watched the forecast track above target and felt good about it. Every Monday I rebuilt the executive call from Clari, and every Monday the net number sat comfortably north of the goal. Then the quarter closed roughly $1.8M under the committed call. Nothing exotic happened. A single large MOU slipped its close date one month into the next quarter, and three dozen new-business deals that had all been sitting on the last day of the quarter quietly moved. Churn came in almost exactly where we had modeled it. The miss was entirely a bookings-slippage miss, and it was invisible to a forecast that read pipeline value and stage labels, because those are the last things to move.

That quarter is why this chapter exists. The previous chapter, Pipeline Management and Deal Velocity, taught you to run a pipeline on observable exit criteria and to kill zombie deals before they rot the quarter. This chapter is what you do with that clean pipeline: turn it into a number leadership can bet on. The rule that survived my bad quarter is simple. The forecast is an output of inspection, not a substitute for it, and coverage is a capacity question, not a forecast.

Coverage tells you capacity, not this quarter

The first habit to break is treating 3x pipeline coverage as a forecast signal. Coverage answers “is there theoretically enough pipeline to hit the number,” which is a planning question about capacity. It does not answer “will we hit,” which is a this-quarter question about specific deals. The right coverage number is not a folk constant. It falls straight out of the metrics spine: coverage is 1 divided by your win rate, CR4 from the metrics spine. At a 50% win rate you need 2x. At 25% you need 4x. At 20% you need 5x.

That matters more than it used to, because the denominator moved. The math chapter showed why a win is a product of every conversion in the funnel, so a few points shaved off each stage collapses the win rate faster than any single dashboard shows (The Mathematical Model). Industry win rates have fallen into the 19 to 21% band, down from roughly 29% two years earlier (Ebsta/Pavilion 2025). A team still quoting itself 3x coverage at a 20% win rate is carrying about 60% of the pipeline it actually needs and does not know it.

Read coverage at the start of a period, not the end. In week 1 a thin ratio is still fixable: you can source net-new pipeline that matures in time. In week 10 the same reading is an autopsy, because all you can do is protect close dates on deals that already exist. Coverage sets the table for the quarter. It never calls the number. The two do different jobs, and confusing them is how a room talks itself into confidence it has not earned.

The five inputs that actually predict

Weighted pipeline (deal amount times a stage probability) is where most forecasts start and where too many stop. The trouble is that the CRM knows only one of the five things that predict an outcome, and it is the weakest one. A calibrated call combines five inputs, weighted by what has predicted wins in your own closed-deal history rather than by a pick-list probability someone typed three years ago.

• Stage-transition probability, built from a cohort of your own recently closed deals, not the CRM’s default percentage. The CRM number is a wish; the cohort number is what happened.
• Velocity versus baseline. A deal moving slower than the segment median is slipping whether or not the rep has admitted it. This is the deal-velocity read you built in the last chapter, now pointed at the forecast.
• Engagement and multi-thread depth. Contact activity and the number of stakeholders in the deal catch a slip 30 to 45 days before the close date moves. A single-threaded deal is a risk the stage label will never show you, in a world where multi-threading lifts win rate sharply on larger deals (Ebsta/Pavilion 2025).
• Qualification completeness. A confirmed economic buyer and a documented decision process, straight from the D in SPICED (SPICED and the Buying Center). Deals die on procurement and approval, not on whether the rep quantified the pain on call one.
• Rep conviction, calibrated to history. A rep who calls Commit and lands 90% of them gets weighted differently from one who lands 55%. Uncalibrated conviction is optimism with a job title.

Naming them is enough for the arc. The weighted model that combines them, the SQL to build the stage-transition cohort, and the maturity ladder for choosing a combine method all live in the forecasting reference, which is the deep build this chapter sits on top of. The short version of that ladder: under about 200 closed deals, run a simple weighted-score model you can explain; around 500, build cohort-baseline transition probabilities, which is where most teams should live; past 5,000, layer machine scoring on top of clean cohorts, and not one deal before. Jumping to a black box early just gives you a confident guess trained on nothing.

Whose number is the company number

Here is the part the tooling hides. Once every rep and manager has a call, you have to decide which number is the number, and the naive answers are both wrong. Summing every entry in the system double counts, because a manager’s roll-up already contains their reps. Summing only the leaf reps drops every override a manager made on purpose, and in my own weekly scorecard that leaf sum ran close to 2x the eventual actual and read like a fantasy. The company call is the value at the root of the forecast hierarchy: in our case the node owned by the chief revenue officer, the one person accountable for the whole tree. Every layer below is an input to it, not a copy of it.

Feeding that root number is a category discipline, enforced org-wide or the roll-up is fiction. On the bookings side we carry three: Commit, Most Likely, and Upside. On the renewal side, a worst case and a best case for churn. The one rule that keeps them honest is the close date. A deal a rep loves with a close date in the next quarter is pipeline, not Commit, no matter how badly they want it in this period’s roll-up. Write the definitions once, publish them, and hold reps to them, exactly the way the metrics spine governs a stage definition. The forecasting reference has the enforced category sheet you can adopt directly.

The cadence, and the diff that saves the quarter

A forecast is a process, not a spreadsheet, and the process is a weekly rhythm sitting on a daily job. The daily job is the one that pays for everything else: snapshot the open pipeline every morning and diff it against yesterday. I run that against a Salesforce daily snapshot in the warehouse (roughly 30,000 open opportunities a day at our scale), comparing today against seven days ago on amount, stage, close date, and next step. Drift shows up on a Tuesday instead of in week 11. Had that diff been feeding an exception review the quarter I missed, the three dozen deals sliding toward quarter-end would have been a flagged list in week 4, not a postmortem in week 13.

The payoff is not a prettier deck. It is a shorter meeting and a truer number. Replace the 90-minute call where reps read their pipeline out loud with a 30-minute exception review that only touches the deals the diff and the signal model flagged, and you recover most of a room’s week while the deals that need a decision get one. The best teams hold forecast variance under 5% (RevOps Masters 2026), and they get there in the second full quarter after a rebuild like this, not the first, because the conviction weighting needs a quarter of scored history before it earns its place.

Handing off

You can now stand up a forecast leadership will trust: coverage read early as a capacity gate at 1 over your win rate, a calibrated call built from five inputs instead of one, enforced categories rolling up to a single accountable number, and a weekly cadence on a daily diff that catches drift while there is still time to act. For the full build, the weighted model, the cohort SQL, and the category sheet, work through the forecasting reference.

Notice what coverage kept pointing back to. “How much pipeline, at what win rate, to hit what number” is a capacity equation, and this chapter only read it for one quarter at a time. Set that capacity for a whole year, across a team of reps and a map of accounts, and you are no longer forecasting. You are designing. That is Territory and Quota Design, and it is next.