The Best Forecasts Are Built Deal by Deal.
Ask a CRO how confident they are in the forecast, and the answer usually depends on how far they can trace the number back to individual deals. A commit forecast of $4.2M sounds precise. But if nobody reviewed the deals that make up that number — if it’s just a rollup of whatever’s sitting in the Commit category in Salesforce — it’s precision without accuracy.
The gap between a forecast and a good forecast is deal-level judgment.
The problem with top-down forecasting
Most forecast processes work from the top down. The number rolls up from Salesforce. A manager looks at the total. Maybe they adjust it by a percentage based on gut feel. The result is a forecast built on aggregates — directionally useful, but impossible to defend when someone asks “which deals are driving that number?”
This is how forecast calls turn into status meetings. Instead of discussing deals, teams discuss numbers. Instead of applying judgment, they apply math.
What deal-level forecasting looks like
Deal-level forecasting flips the process. Instead of starting with the number, you start with the deals.
You see every opportunity laid out by period and forecast category. You review each one: Is this deal really closing this month, or should it move to next month? Is this Best Case deal actually a Commit? Is that $500K deal still real, or has it gone quiet?
Then you make adjustments — not to the aggregate number, but to individual deals. You move a deal from May to June because the procurement process is taking longer than expected. You promote a Best Case to Commit because the verbal came in yesterday. You reduce a deal’s forecast amount because the scope narrowed during negotiations.
Each adjustment is tracked. Each one changes the numbers in real time. And when you’re done, you submit with comments explaining what you changed and why.
The audit trail changes everything
The magic isn’t in the drag-and-drop. It’s in what happens after.
Every adjustment you make during a deal-based submission is recorded. When you submit, an AI-generated digest captures the full story: which deals you moved, how the adjustments affected quota attainment, and what the overall impact was on the forecast.
Your manager reads the digest instead of asking you to walk through your forecast on a call. The CRO reviews the aggregate of everyone’s submissions instead of relying on a single RevOps-compiled spreadsheet. The story behind the number is always available.
Why this matters for managers
Managers benefit even more than reps. During a deal-based submission, the side panel gives you everything about a deal without leaving the forecast page: AI insights, activity timeline, stage history (including how many times it’s been pushed), and sales methodology scoring. You can assess a deal’s real health and adjust accordingly — all in one session.
This is how you go from “I think we’ll hit $4.2M” to “here are the 15 deals that make up $4.2M, here’s what I adjusted and why, and here’s the AI summary that documents it.” One is an opinion. The other is a forecast.
See deal-based submissions in action: Deal-Based Submissions. Or schedule a demo to walk through it with your pipeline.
