The Sales Forecasting Reboot — 60-Min Training

Direct Answer

Sales forecasting accuracy is the single highest-leverage operating discipline a SaaS revenue team can install. Per Clari's 2025 State of Revenue report, the median enterprise forecast misses by 26%, and Jason Jordan's *Cracking the Sales Management Code* shows that only forecast objects (the deals themselves) — not activities — directly drive results.

This training rebuilds the muscle in one hour.

Pre-work (send 24 hours before): Each AE pulls their current quarter pipeline filtered to deals with close date in the next 90 days. Have CRO or RevOps pre-load last quarter's commit-vs-actual delta per rep.

Section 1 — Opening & The Accuracy Gap (5 min)

Manager script, verbatim: *"Last quarter we committed $X and closed $Y. The delta isn't a math problem — it's a language problem. Today we're going to agree on what 'Commit' actually means, and we're never going to use the word 'feels good' again."*

• Show the scoreboard. Put last quarter's commit vs. Closed-won on screen by rep. No shaming — frame as system failure, not rep failure.
• State the goal. Move team forecast accuracy from current baseline to 90% by end of next quarter (Clari benchmark for top-quartile SaaS teams).
• Name the enemy. Force Management calls it "qualified vs. Not qualified" — most slipped deals were never qualified to begin with.

Section 2 — The Three-Bucket Classification (15 min)

This is the Salesforce/Clari standard taxonomy. Every deal in the next 90 days lives in exactly one bucket.

Definitions to write on the whiteboard:

• Commit — *"I will bet my variable comp this deal closes this period."* Requires MEDDPICC fully scored, mutual close plan countersigned, redlines exchanged or none required, and verbal from Economic Buyer.
• Best Case — Real opportunity with a champion, but missing one of: signed MCP, EB verbal, or procurement engagement. Never roll Best Case into Commit math.
• Pipeline — Everything else with a future close date. Coaching target, not forecast input.

Drill (5 min): Each AE reads their top 5 deals out loud and assigns a bucket. Manager challenges every "Commit" with one question: *"What would have to be untrue for this to slip?"*

Section 3 — The "What Would Have to Be True" Test (10 min)

Borrowed from Roger Martin's strategic-choice framework and adapted by Force Management for deal inspection. Replaces gut feel with falsifiable conditions.

The protocol, for any Commit deal:

1. AE writes 3-5 conditions that must be true for the deal to close this period. Example: *"Legal returns redlines by Tuesday. CFO joins the 5/29 call. PO issued by 6/14."*
2. AE rates each 0-100% likelihood based on evidence, not optimism.
3. Multiply the probabilities. If three conditions sit at 80%, the deal is 51% — not Commit.
4. Manager asks: *"What's the proof point for each percentage?"* No proof = downgrade.

Coaching line: *"Hope is not a forecasting category. If you can't name the email, the meeting, or the artifact, the deal isn't where you think it is."*

**Mike Weinberg's rule from *Sales Management. Simplified.*:** A deal without a next scheduled meeting with the buyer is not a Commit. Period.

Section 4 — Slipped-Deal Taxonomy (10 min)

Every slip falls into one of four categories. Naming them stops the pattern.

• Slip Type 1 — Champion Failure. Internal champion lost authority, left, or was never actually a champion. *Fix:* multi-thread to a second stakeholder before forecasting Commit.
• Slip Type 2 — Process Surprise. Procurement, security review, or legal step the AE didn't know existed. *Fix:* ask "what's your buying process" in discovery, not week 11.
• Slip Type 3 — Priority Reshuffle. Budget reallocated to a higher-pain initiative. *Fix:* tie deal to a quantified business pain in MEDDPICC's "I" (Identified Pain).
• Slip Type 4 — Competitive Loss Masquerading as Slip. Deal didn't slip — you lost and the buyer is being polite. *Fix:* if no movement in 14 days post-"slip," call it lost.

Exercise: Each AE picks one slipped deal from last quarter and assigns a type. Manager logs counts. Whatever type wins the count is the team's coaching priority for the next 30 days.

Section 5 — Weighted Math & The 30/60/90 Cadence (15 min)

Unweighted forecast = sum of Commit ACV. Top-quartile SaaS teams use this as the primary number because the buckets already encode probability.

Weighted forecast (use as a sanity check, not the primary):

• Commit × 0.90
• Best Case × 0.50
• Pipeline × 0.10 (only deals with close date in period)

If unweighted Commit and weighted total diverge by more than 15%, the team is mis-classifying. Recalibrate the buckets, don't change the math.

The 30/60/90 rolling cadence:

• Monthly (first business day): 30-min team forecast call. Each AE reads Commit list. Manager challenges with the "what would have to be true" test. Lock the number.
• Quarterly (week 1): 90-min reset. Review last quarter's commit-vs-actual by rep, slip-type counts, and average sales cycle. Reset Commit thresholds if cycle drifted >10%.
• Weekly (15-min standup): Just the deltas — what moved in, out, or changed bucket. No re-litigating.

Force Management's rule: monthly forecasting beats quarterly for $25K-$150K ACV; quarterly is fine for $150K-$500K because cycles are longer than the period.

Section 6 — Commitments & Close (5 min)

Each AE writes on an index card:

1. *"My Commit number for this period is $___."*
2. *"My Best Case number is $___."*
3. *"The one deal I'm most worried about is ___ and the proof point I need by Friday is ___."*

Manager closes: *"We meet every Monday for 15 minutes. If a Commit deal moves to Best Case mid-cycle, you tell me the day it happens, not the day the forecast is due. Surprises are the only failure mode in this room."*

FAQ

Q: What if a deal closes that we had in Pipeline, not Commit? A: That's a sandbagging signal. Track Pipeline-to-closed conversions per rep — if >15%, the rep is hiding deals. Coach for transparency, don't punish the close.

Q: Should we use AI forecasting tools like Clari, Gong, or BoostUp? A: Yes — but only after the team agrees on the bucket definitions above. AI tools amplify whatever taxonomy you feed them; garbage in, confident garbage out.

Q: How do we forecast renewals and expansion? A: Separate forecast entirely. New logo, renewal, and expansion each need their own commit/best-case/pipeline view. Don't blend.

Q: What's the right number of deals per rep in Commit? A: Top-quartile AEs commit 3-7 deals per period. More than 10 usually means they don't believe any of them.

Q: How long until we see accuracy improvement? A: Two full cycles. First cycle exposes the mis-classification; second cycle is when reps internalize the buckets and the number tightens.

Sources

1. Clari, *2025 State of Revenue Report* — median enterprise forecast accuracy and top-quartile benchmarks.
2. Jordan, Jason. *Cracking the Sales Management Code* (McGraw-Hill, 2011) — forecast objects vs. Activities framework.
3. Weinberg, Mike. *Sales Management. Simplified.* (AMACOM, 2015) — next-meeting rule and pipeline hygiene.
4. Force Management, *Command of the Message / MEDDPICC* curriculum — qualified-vs-not-qualified deal inspection.
5. Salesforce, *Sales Cloud Forecasting Categories documentation* — Commit, Best Case, Pipeline, Omitted definitions.
6. Martin, Roger L. *Playing to Win* (HBR Press, 2013) — "what would have to be true" strategic test.
7. Gartner, *2024 B2B Buying Journey research* — average 11 stakeholders per enterprise SaaS purchase.
8. Harvard Business Review, "Why Sales Forecasts Are So Often Wrong" (Schoemaker & Krupp, 2021).