Skip to content
Sales Pitch

Sales forecasting that survives the quarter: a method built on inspection, not optimism

Most forecasts are a mood with a number attached. A repeatable process for calling the quarter: pipeline coverage, deal inspection, and a weekly cadence.

, 5 min read, Sales leadership

Also available in Français, Español

Share on LinkedIn, X, Facebook

Sales leader presenting pipeline data on a large screen
Photo Vitaly Gariev, Unsplash

Key takeaways

  • A forecast is only as good as the deal inspection behind it. Category labels without evidence are opinions.
  • Pipeline coverage of roughly three times the target is a starting heuristic, not a law. Calibrate it against your own historical win rate by stage.
  • Use a qualification framework consistently so that 'commit' means the same thing for every rep and every manager.
  • Review the forecast weekly, change it when the evidence changes, and record why. The history of your calls is how you learn to make better ones.

Every sales leader has sat in a forecast call where a rep says "commit" and everyone in the room quietly knows the deal is not real. The rep is not lying. They are hopeful, and the process gave them no reason to be anything else.

Forecasting is not prediction. It is the disciplined inspection of what you know about each deal, applied consistently, on a schedule. This article lays out a method that works for teams from five reps to fifty, and that gets more accurate every quarter you run it.

Start with coverage, but calibrate it

The classic heuristic says you need about three times your target in open pipeline at the start of a period. It is a decent default because many B2B teams win somewhere between a quarter and a third of their qualified opportunities. It is a poor rule if you apply it blindly.

Compute your own ratio. Take the last four quarters, and for each one look at the pipeline that was open on day one and how much of it closed by the end. That gives you a realised conversion rate per quarter. The inverse is the coverage you actually needed. If it is 2.4x, planning for 3x is conservative. If it is 4.1x, planning for 3x guarantees a miss.

Then do the same by stage. Pipeline sitting in early stages converts far less than pipeline in negotiation. Coverage that is 3x but concentrated in discovery is not the same as 3x with half of it in late stages.

Inspect deals with a framework, every time

The forecast is a sum of deal-level judgments. Making those judgments consistent is the whole game. A qualification framework is the tool for that; MEDDPICC is the most widely used in enterprise software, and the questions it asks are the ones that matter regardless of the acronym you prefer.

ElementThe question to answerEvidence, not opinion
MetricsWhat measurable result does the buyer expectA number the buyer has said out loud or written
Economic buyerWho can approve the spendYou have met them, or your champion has confirmed and named them
Decision criteriaHow will they compare optionsA written or explicitly stated list
Decision processWhat steps and who is involvedNamed steps with dates
Paper processLegal, procurement, security reviewSteps identified and started
Identify painWhy change, and why nowThe buyer's words about the cost of the status quo
ChampionWho sells for you internallySomeone with influence who has taken a visible action
CompetitionWho else, including doing nothingNamed alternatives and the buyer's view of them

The forecast call should not ask "is this deal going to close". It should ask "which of these elements do we have evidence for". A deal with metrics, an engaged economic buyer, a defined paper process and a champion is a commit. A deal where the rep has met one person who likes the demo is pipeline, whatever the close date says.

Define categories in writing

Most teams use some version of commit, best case and pipeline. The categories are useless unless they are defined by criteria a manager can check.

A workable set of definitions:

  • Commit: economic buyer engaged, decision process and paper process mapped with dates inside the period, champion confirmed, no unresolved competitive or technical blocker. The rep would be surprised if it slipped.
  • Best case: most of the above, with one or two identified gaps that have a plan and a date. Realistic upside, not a wish.
  • Pipeline: qualified opportunity with a real pain and a plausible close date, but material gaps in the framework.
  • Omitted: open in the CRM but not forecast for the period. Being honest here is what makes the other categories meaningful.

Publish these definitions. Hold reps to them. Hold managers to them too: a manager's roll-up that equals the sum of rep commits with no adjustment is not a forecast, it is a spreadsheet.

Run the cadence

Forecasting is a weekly habit, not a quarter-end scramble.

Weekly, per rep (30 minutes): review every commit and best-case deal against the framework. What changed since last week. What is the next step, who owns it, and when. Move deals between categories based on evidence. Record the reason.

Weekly, per manager (30 minutes): roll up the team, apply judgment, and submit a number. The manager's number may differ from the sum of the reps. That difference, and the reasoning behind it, is the most valuable information in the process.

Monthly: compare the calls made four weeks ago with what happened. Which deals slipped and why. Which category was most wrong. This is the feedback loop that improves accuracy, and most teams skip it.

The signals that a forecast is soft

Certain patterns show up before a miss, and they are visible weeks in advance if anyone is looking.

  • Close dates that move by exactly one quarter, repeatedly.
  • Commit deals where the rep has not spoken to anyone in the account for two weeks.
  • A large share of the number concentrated in one or two deals.
  • Deals with no next step scheduled in the calendar.
  • A "decision process" field that says "they will get back to us".
  • Paper process not started with fewer than three weeks in the period.

A forecast review that surfaces these each week turns them into actions. A review that only looks at the total turns them into surprises.

What accuracy looks like

A well-run team lands within roughly 10% of its commit number most quarters, and knows by the midpoint of the quarter whether it is on track. That is achievable for almost any team, and it has little to do with tooling. It comes from writing down what commit means, inspecting every deal against evidence, and having the discipline to move a deal out of commit when the evidence says so, even in week twelve.

Frequently asked questions

What is a good pipeline coverage ratio?
The often-quoted rule is three times the quota in open pipeline for the period. It is a reasonable place to start, but the right number depends on your win rate. A team that wins 40% of qualified deals needs less coverage than one that wins 20%. Compute it from your own stage-by-stage conversion data.
What is the difference between commit, best case and pipeline?
Commit is revenue the rep is confident will close in the period and would stake their credibility on. Best case is realistic upside that needs one or two things to go right. Pipeline is everything else that is open. The categories only work if the criteria for each are written down and enforced.
What is MEDDPICC?
A qualification framework: Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition. It is used to test how well a seller understands a deal and to expose gaps before they show up as a slipped close date.