The forecast number nobody would bet on

11 people. 90 minutes. 3 slides. The number on the last slide is the number everyone walks out believing.

It's also the number nobody in the room would stake their own money on.

That gap is the forecast meeting in one sentence. The CRO presents a pipeline coverage ratio, the CFO presents a finance-adjusted version, sales ops presents a variance-corrected blend. Each version is internally consistent. None of them is the version a rep would write down if you handed them a sheet of paper and asked them to commit, alone, in pen.

I've run versions of this meeting in five companies. The math is always theater. Reps inflate, because the forecast is the metric, not the close. Ops compresses, because they got burned the last quarter the number went out wrong. Finance averages, because finance is graded on variance to plan, not variance to truth. The three pressures don't cancel. They layer. By the time the slide is built, the number is the artifact of three incentives politely shaking hands, and it reads a lot like the projections startups miss and can't explain afterward.

Those layered incentives produce a number that survives the meeting and almost never survives the quarter. The CRO's version is calibrated for team morale and board appetite. The ops version is calibrated against last quarter's overcommit. Finance's version is calibrated against a plan that's already been promised. Each calibration is sensible on its own. The aggregate has been bent in three directions and arrives at the slide as the convex hull of three different stories.

Better software isn't the answer. Salesforce has been here for twenty years. Clari, Gong, BoostUp, every one of them sells a story about how the platform finds the real number. It doesn't find the real number. It finds a number that's defensible inside the existing meeting. The meeting is the problem.

One thing changes the math. Ask each rep, in writing, before the meeting, what they'd personally stake five hundred dollars of their own money on for each commit-stage deal. Not what they want to commit. What they'd bet cash on. Collect the sheets. Compare them to the CRM.

The gap is the forecast.

The first time I ran this, the gap was forty-two percent. Forty-two percent of commit pipeline was deals reps wouldn't stake a dollar of their own money on. They'd marked them commit because commit was the stage that made the manager's coverage look healthy. The deals weren't closing. Everyone in the room except the CRO had known it for weeks.

The second time was a different company, different stack, different industry. The gap was thirty-eight percent. The third was thirty-one. The pattern held across geographies, deal sizes, and sales cycles. It holds because the underlying mechanism holds: reps grade their own pipeline against the metric they're paid on, which is commit attainment, not closure. The metric they're paid on is the metric they game, in the direction of the game.

The exercise is uncomfortable. Reps don't want to put cash behind a number they'd been treating as a stage label. The CRO doesn't want to walk into the board with a pipeline that shrank by a third overnight. The CFO loves it, briefly, until it's clear the new number means re-baselining the quarter. The board, when it sees the rebaselined number, asks why last quarter's was different. The conversation is uncomfortable for two cycles and clarifying after that.

Everyone hates the new number for the first month. Then it starts landing within five percent of actual, two quarters running, and the room stops fighting. The team operating against the honest number starts forecasting well, because forecasting well is now the job. The metric matches the operational truth, and the reps' calibration converges toward honesty within about two quarters.

A forecast is a personal commitment dressed in spreadsheet clothes. Strip the spreadsheet and ask for the commitment. The number that survives is the number worth budgeting against. The number on the slide is the number worth ignoring.

The exercise also surfaces the comp problem the meeting was hiding. Reps grade pipeline against commit because commit is what their manager grades them on. The manager grades the rep because the CRO grades the manager. The CRO is graded by the CEO on whether the number hit. The CEO is graded by the board on whether the company hit plan. At each layer, the metric passed up is the metric optimized below, and every layer optimizes in the direction of inflation. The five-hundred-dollar question is the only check in the system that interrupts it, which is the same reason a comp band only means what its exception process enforces.

Before your next forecast review, ask which commit deal you personally wouldn't stake five hundred dollars on, whose bonus moves if the forecast comes in five percent low and whether that person is the one building it, what you'd have to cut at eighty percent of plan and who decides, and when the forecast was last right within ten percent and what that meeting looked like. If you can't remember the last accurate one, the forecast isn't a forecast. It's a meeting that happens on Thursdays.