Revenue Forecasting That Your Board Can Trust

Most $10M-$100M companies miss their revenue forecast by 15-25%. I've audited forecasting processes at nine companies in that range since 2021, and the gap is almost never the CRM or the tool. It's the process: inconsistent stage definitions, no historical conversion data, and a forecast built on rep confidence instead of pipeline math. A board-ready forecast takes about 90 days to install. The math is simpler than most teams expect.

What Is a Board-Ready Revenue Forecast?

A board-ready revenue forecast is a quarterly projection built on weighted pipeline, historical stage conversion rates, and a coverage ratio target. It's not a sales team's gut feel rolled up into a spreadsheet.

The distinction matters because boards lose trust fast. A $45M logistics company I worked with in 2023 missed their forecast by 22% two quarters in a row. The board stopped trusting the number entirely and started discounting every projection by 20% in their own models. Rebuilding that trust took three quarters of accurate calls.

Why Do Most Revenue Forecasts Miss?

Most B2B revenue forecasts miss because they're built on opinion, not math. Reps call a deal "likely to close" based on the last conversation, not based on how deals at that stage have historically converted.

I've seen this at seven of nine companies I've audited. The average forecast variance was 18% on the high side. Stage definitions were vague ("qualified" meant something different to every rep), historical conversion rates didn't exist, and nobody reviewed the forecast against actuals weekly.

The cost is concrete. A $62M PE-backed company I worked with in 2024 missed Q2 by $1.4M. The board had already committed that number to their LPs. The operating partner called it an execution risk problem. It was a measurement problem: the revenue engine was performing fine, but the forecast was reading the wrong signals.

How Do You Build a Forecast the Board Trusts?

Building a trustworthy forecast takes about 90 days in three phases: clean the pipeline stages, install the math, then run the weekly review cadence.

Step 1: Redefine pipeline stages with exit criteria

Every stage needs a clear, objective exit criterion. Not "the prospect is interested." Specific: "Budget confirmed in writing." "Decision-maker identified and engaged." "Technical evaluation complete with positive outcome."

At the $45M logistics company, I found six stages with no documented criteria. Reps moved deals based on feel. We cut to five stages and wrote one-sentence exit criteria for each. Stuck deals dropped 35% in the first quarter.

Step 2: Calculate historical conversion rates by stage

Pull 12-18 months of closed-won and closed-lost data. Calculate the conversion rate between each stage. Stage 1 to Stage 2: what percentage advance? Run the math all the way to closed-won.

If Stage 3 historically converts at 40% and you have $5M there, your weighted contribution is $2M. Multiply across all stages for the bottom-up forecast. At the $62M company, this exercise revealed Stage 2 converted at 12%, not the 30% the team assumed. One data point changed the entire forecast.

Step 3: Set a pipeline coverage ratio target

Coverage ratio is total qualified pipeline divided by revenue target. For most B2B companies with 90-day sales cycles, 3-4x is the baseline. Need $3M this quarter? You need $9-12M in qualified pipeline.

Longer cycles require more coverage. A $28M enterprise software company I worked with needed 5x to hit consistently because their average sales cycle ran seven months. I've measured this across six engagements: companies below 3x coverage miss their forecast more than 70% of the time.

Step 4: Install a weekly forecast review

The forecast isn't quarterly. It's weekly. Every Monday, the sales leader reviews the pipeline stage by stage. Deals that advanced get validated against exit criteria. Deals stalled 14+ days get flagged. Commit and best-case numbers get updated.

At the $45M company, this weekly rhythm cut forecast variance from 22% to under 8% within two quarters. This is where The KPI Tree Framework connects the pipeline to the board number. Revenue at the top, coverage and conversion as the branches, deal velocity and win rate as the leaves. Each node has a number and an owner.

How Do You Separate Commit from Best Case?

The commit number includes deals with 80%+ probability based on historical conversion data, not rep optimism. The best case adds upside deals in late stages with real momentum but unconfirmed outcomes.

Boards need both, presented cleanly. "Our commit is $3.2M. Our best case is $3.8M. The $600K delta is three deals in Stage 4 with verbal agreements but unsigned contracts." That precision builds trust.

What Went Wrong at My First Forecast Rebuild?

At a $34M SaaS company in 2022, I installed the weekly review and conversion math but skipped the stage redefinition. The historical data was built on old, vague stages. Conversion rates looked reasonable, but they measured the wrong thing. "Stage 3" at that company could mean a first discovery call or a signed LOI.

The forecast came in accurate for Q1 by luck, not process. Q2 missed by 11%. I went back, redefined stages, and recalculated 18 months of conversion data against the new definitions. That rebuild added six weeks. The lesson: stage definitions come first. You can't course-correct math built on bad inputs.

What to Do This Week

Pull your last four quarters of forecast vs. actual results. Calculate the average variance. If it's above 10%, ask three reps what each pipeline stage means. Three different answers means that's your first fix.

Then calculate your current pipeline coverage ratio. If it's below 3x, you have a pipeline generation problem, not a forecasting problem.

If you want help building the math and installing the weekly review cadence, book a diagnostic.

Frequently Asked Questions

What is a good pipeline coverage ratio for B2B forecasting?

For most B2B companies with sales cycles under 120 days, 3-4x pipeline coverage is the target. That means $3-4M in qualified pipeline for every $1M in quarterly revenue target. Companies with longer enterprise sales cycles need 4-6x coverage. I've tracked this across six companies: below 3x, forecast misses exceed 15% in more than 70% of quarters.

How often should you review your revenue forecast?

Weekly for operating purposes, monthly for board prep. The weekly review catches stalled deals, validates stage movements, and updates the commit and best-case numbers. The monthly review rolls the weekly data into the board-ready format with actuals vs. plan, variance explanations, and next-month projections.

What is the difference between a commit forecast and a best-case forecast?

The commit forecast includes only deals with 80%+ close probability based on historical conversion data and verified stage criteria. The best-case forecast adds upside deals in late stages with strong signals but unconfirmed outcomes. Healthy companies keep the delta under 20% of the commit number.

Who should own the revenue forecast?

The CRO or VP of Sales owns the number and presents the forecast in the weekly review. The CFO validates the math against financial models. The CEO presents the number to the board. Ownership splits create forecast drift: when nobody owns the number, the number drifts.

Why do most B2B revenue forecasts miss?

Three reasons account for 80%+ of forecast misses I've seen. Vague pipeline stage definitions lead to inconsistent deal classification. Teams don't track historical conversion rates by stage, so weighted pipeline is based on guesses. The forecast gets built quarterly instead of reviewed weekly, so problems surface too late to correct.

Related

• Board Reporting for Growth-Stage Companies - where the forecast becomes a board conversation
• Run a Quarterly Business Review That Drives Action - the quarterly rhythm that validates forecast assumptions
• Pipeline Velocity - the math behind deal movement through the funnel
• The Weekly Revenue Standup - the Monday meeting where forecast accuracy lives