Most sales forecasts are wrong for a simple, structural reason: they multiply a deal's value by a stage probability that someone invented. A deal in "Proposal" gets 60%. A deal in "Negotiation" gets 80%. Neither number is based on anything real.
The result is a forecast that feels precise — it has decimal points — but is essentially fiction.
The problem with stage-probability forecasting
Stage probabilities are averages at best. At worst, they're numbers someone typed into a CRM configuration screen five years ago and nobody has touched since.
Your 60% Proposal stage might include deals that are genuinely 80% likely to close and deals that are 10% likely. Averaged together you get 60%, which tells you nothing useful about either deal.
Multiply by deal value and you've built a mathematical structure on top of a guess.
The four-bucket framework
Target → Secured → Commit → Gap is built on a different principle: instead of asking "what stage is this deal in?", it asks "what can we count on?".
Target is the revenue number you've committed to the business for the quarter. It doesn't change week to week. It's your accountability baseline.
Secured is revenue you've already recognised — closed deals, signed contracts, activated subscriptions. This is the most conservative number. If everything else fell apart, this is what you have.
Commit is revenue your reps are personally committing will close this quarter. Not "probably." Not "likely." Committing. If a rep puts a deal in Commit and it slips, that's a conversation.
Gap is the arithmetic: Target minus Secured. Every Monday morning your whole team is working to close the Gap.
Why this works
The framework works because it changes the psychology of forecasting. Stage probability is passive — deals accumulate probability by moving through stages. Commit is active — a rep is making a personal commitment.
When a deal moves into Commit, the rep is saying: "I will close this." That changes how they manage it, what they prioritise, and how transparent they are about risk.
Implementing it in OrgAxis
In OrgAxis, every deal has a forecast bucket field: Best Case, Commit, or Secured. Reps assign their own buckets — managers don't assign them. This is intentional.
The Target/Secured/Commit/Gap dashboard updates live as deals move. When you open OrgAxis on Monday morning, the Gap is already calculated. The review can be about closing the Gap, not calculating what it is.
The Attention Zone then flags Commit deals that show risk signals — no recent activity, close date approaching, champion contact gone quiet. The system catches deals that might slip before they do.
The objection
"Our team won't accurately self-report." This is the most common pushback, and it's valid for CRMs where self-reporting has no consequence.
When Commit is tied to accountability — when a rep's Commit number is visible to the manager, when slippage is tracked — accuracy improves. Not because you're punishing people, but because Commit means something. It's not a field in a form; it's a commitment.
Start with weekly review where the manager goes through each rep's Commit deals. After 4–6 weeks of that visibility, accuracy improves significantly.