Home › Blog › The two-hour weekly forecast call: what to inspect, what to ignore
The two-hour weekly forecast call: what to inspect, what to ignore
August 4, 2026 · 7 min read · Forecast OperationsMost forecast calls run 90 minutes and produce a worse forecast than 20 minutes of cold inspection would. The participants leave the meeting feeling productive because the time was filled, but no rep was actually challenged on a soft commit, and no deal was actually moved from a higher confidence tier to a lower one. The fix is not a longer meeting — it is a different agenda.
What most forecast calls do wrong
The typical agenda: open with the biggest deals, walk through each one rep-by-rep, ask "how confident are you," accept the answer, move on. Each conversation takes 4-6 minutes, runs through 20 deals, and ends with a 90-minute meeting where leadership feels informed and reps feel managed. Nothing about the forecast changed during the call. The committed deals stayed committed. The slipped deals stayed slipped. The meeting was theater.
The reason it is theater: the meeting opens with the deals that everyone is most confident about. Those are exactly the deals that need the least inspection. They will probably close. The conversation around them is comfortable. By the time the meeting reaches the messy deals — the ones with no champion, no decision process, no Economic Buyer named — there are 12 minutes left and three of them get clustered into a "we will follow up offline" bucket. Which means they will not.
The four-quadrant inspection
The replacement framework: open the meeting by sorting the pipeline by inspection priority, then walk it from worst to best. Four quadrants matter:
1. Missing data. Any Commit-tier deal where one or more required qualification fields is empty or trivially filled ("CEO" with no name; "Q3" with no specific date). These get inspected first because they are the most likely to slip and the easiest to fix on the call.
2. Slipped from prior period. Any deal that was Commit last quarter and did not close. The forecast call should track these for two cycles. If a deal slips twice, the rep should be required to present the new close-date logic in front of the team. This is uncomfortable on purpose.
3. Aged out of stage. Any deal that has been in the same stage for more than 1.5x the average time-in-stage for the segment. A 90-day-old Stage 4 deal in an environment where Stage 4 averages 35 days is almost always either lost, paused, or being slow-walked by procurement. Each one gets a hard inspection: are we waiting on signature, or are we hoping?
4. No champion. Any deal at Stage 3 or higher without a named champion (first and last name in the CRM). This is the early-warning indicator that almost no team takes seriously enough. A deal without a named champion at Stage 4 closes at about 25% of the rate of deals with named champions. Treat the absence of a champion as a stage-blocker.
Run the meeting through these four quadrants in order. Each quadrant gets a fixed allotment — say 25 minutes. The big easy deals at the bottom of the funnel get whatever time is left. Often nothing, and that is correct.
Open with the bottom, not the top
The single biggest agenda change is reversing the deal order. Instead of opening with the biggest, opening with the worst — the deals where qualification is thinnest, the ones leadership is least confident about, the ones that are about to age out. This is uncomfortable for the reps whose deals are in that bucket, and the discomfort is the point. The forecast call is a forcing function for honest qualification, not a parade of best-case scenarios.
Frontline managers will push back on this the first time you try it. "We do not have time to grill every weak deal." That is true. The four-quadrant model means you do not grill every weak deal — you grill the top 5-8 in each quadrant. The bottom of each quadrant is the manager's problem to follow up on async. The meeting is for the deals where leadership input changes the trajectory.
The questions that work
Inspection is only useful if the questions force specifics. Generic questions ("how do you feel about it") produce generic answers ("good"). Specific questions force the rep to reveal what they actually know.
Working questions, in order of how often I use them:
- "Who at the customer benefits if this deal closes — give me a name."
- "What is the next scheduled meeting on the calendar with that person?"
- "What is on their procurement checklist that we have not satisfied yet?"
- "Walk me through the day this contract gets signed — who clicks the button, on what platform?"
- "Why does the customer not want to do nothing?"
- "Who else are they evaluating, and what did they tell you when you asked?"
Each of those takes about 30-60 seconds to answer if the rep has the information, and reveals immediately when they do not. The rep cannot fluff their way through them. Compare to "are you confident this will close" — which a rep can answer with "yes" while having no information at all.
Reading qualification fields out loud
The most effective intervention I have ever rolled out is having managers read MEDDPICC fields out loud during the call. The manager opens the deal in Salesforce, projects it, and literally reads "Economic Buyer: TBD. Decision Process: we expect a decision soon. Pain: they need a better solution." Hearing the qualification spoken aloud, in front of peers, surfaces how thin it actually is. Reps fix the fields by Friday. The next call is meaningfully different.
This works because reading the field aloud changes the audience. When the rep wrote "TBD" three weeks ago, the audience was a future version of themselves who would maybe fix it. When the manager reads "TBD" aloud at the forecast call, the audience is twelve peers and a CRO. The accountability scaling is the entire point.
Monday vs Thursday cadence
Most teams run forecast calls on Monday because "it sets up the week." Most teams should run them on Thursday because "it sets up the work that needs to happen Friday before the weekend." Monday calls produce action items that get done by next Monday. Thursday calls produce action items that get done by Friday afternoon. The difference compounds over a quarter.
This is a small change but it matters. The work that comes out of a forecast call — fixing qualification fields, scheduling missing meetings, multi-threading into a stalled account — has a one-day half-life. If the call is Monday and the manager forgets to follow up, the rep has eight working days to find a reason not to fix it. If the call is Thursday, the rep has one. Move the call.
What to cut from the meeting
Most forecast calls have accumulated three or four agenda items that do not belong: marketing campaign updates, product release timelines, CSM at-risk reports, the latest competitive intel. All of these are real and important. None of them should be in the forecast call. They each get their own meeting (or async update), and they each have their own audience. Mixing them into the forecast call dilutes the inspection time and trains reps that the meeting is general business — not a place where their deals get challenged.
Cut everything that is not directly about the inspection of in-quarter pipeline. Send the rest as a written update with a 5-bullet summary every Friday. The meeting tightens. Forecast accuracy goes up.
Sample 2-hour agenda
The template I run, weekly, with a 20-rep team:
- 0:00–0:05 — Open with the headline number. "We forecast $4.2M, last week we forecast $4.4M, here are the three deals that moved." No discussion yet. Just the data.
- 0:05–0:30 — Quadrant 1: missing data. Top 5-8 deals with incomplete MEDDPICC fields at Commit or Best Case. Manager reads fields aloud, rep responds, action items captured.
- 0:30–0:55 — Quadrant 2: slipped from prior period. Top 5-8 deals that were Commit and did not close. Rep walks through new close-date logic.
- 0:55–1:20 — Quadrant 3: aged out of stage. Top 5-8 long-stayers. Decision: continue inspecting, or move to Closed Lost.
- 1:20–1:45 — Quadrant 4: no champion. Top 5-8 deals at Stage 3+ missing a named champion. Action plan to find one or stage-block the deal.
- 1:45–2:00 — Forward-looking: pipeline coverage, next-quarter readiness, anything time-sensitive that did not fit the quadrants.
Two hours, weekly, every week. Same agenda. The reps learn what gets asked. The qualification fields start landing pre-filled. The forecast tightens. Six months in, the meeting can shrink to 90 minutes because the four quadrants empty out — which is the actual measurement of whether the cadence is working.
Want to apply this to your team?
I work with B2B SaaS teams and operators in the US and Mexico. Start with a 30-minute conversation.
Start a Conversation