One Month Left. Where Will the Quarter Land?
It’s late August. For most sales teams that’s two-thirds of the way through Q3, with roughly a month left to close it. Every forecast call between now and the end of September circles the same question: where will we land?
There are plenty of ways to answer it, and most teams use some combination of three.
Gut feel. Fast, occasionally right, impossible to defend when someone asks why.
Weighted pipeline. A number nobody set carefully multiplied by a probability nobody measured. The Probability field on an opportunity is usually a stage default that no one has revisited since it was configured.
A full forecast scrub. Every deal gets a call, every manager gets a spreadsheet, and two weeks later you have a real answer — one that was assembled by hand, is already partly stale, and will have to be assembled again next month.
Rev Intel answers the question two other ways, both computed from your own data, and it’s worth understanding why there are two.
1. Quarterly Shape
Bookings don’t arrive evenly across a quarter, and they don’t arrive randomly either. Most teams have a pattern. New business is end-loaded — the hockey stick is real, and it’s usually the same hockey stick every quarter. Renewals land steadily month over month. A team with a heavy enterprise mix looks different from one selling into SMB.
That pattern is measurable. Rev Intel stores what the quarter looked like on every single day — not just where quarters finished — so it can measure the shape of how your bookings accumulate, day by day, across your closed history.
Apply that shape to where you stand right now and you have a projection. On day 58 of a 92-day quarter, with this much won, teams that look like this at day 58 finish here.
It’s an at-a-glance read on the trajectory, and it holds up because it’s built on your own closing rhythm rather than a generic curve. What it doesn’t do is look at a single deal. It knows the pace. It doesn’t know whether there’s anything behind it.
2. Deal Simulation
In enterprise selling it always comes back to the individual deals. So the second projection starts with the pipeline you actually have and plays each deal forward:
- How often deals at each stage actually close. Measured reach-through from your closed history — what fraction of deals that reached Proposal became Closed Won — not the Probability field.
- How far close dates push. How many deals slip at all, and by how much when they do.
- How both of those change near the end of a quarter. Deals behave differently in the last three weeks than they do in the first six. A projection that ignores that will be wrong in a predictable direction.
- How much arrives from deals that don’t exist yet. Some meaningful share of every quarter is created and closed inside the same quarter. Ignoring it systematically understates the finish.
The part that makes this accurate rather than merely plausible is that none of those benchmarks are org-wide averages. They’re resolved per segment, per rep, and per team — because a blended close rate applied to an enterprise deal is just a different flavor of guessing.
This projection inspects the deals. Its limitation is the mirror image of the first one: it’s only as good as your pipeline hygiene. Stale close dates and deals parked in a stage they left months ago degrade it.
Which is why both are shown, side by side
Neither method is a correction of the other. They’re independent reads with different blind spots, and the relationship between them is the actual signal:
They agree. Two methods with different failure modes arrived at the same place. Be confident in the number.
Shape is higher than simulation. Your closing pace is normal for this point in the quarter, but the pipeline may be thin. The rhythm says you’ll get there; the deals on the board don’t add up to it yet.
Simulation is higher than shape. Your pipeline is stronger than a typical quarter at this stage. Either you’re ahead, or the pipeline needs a hygiene pass before you believe it.
That last read is the one worth sitting with. A gap between the two projections isn’t an error to resolve — it’s a question that tells you where to look. Coverage problem, or hygiene problem?
Nobody has to assemble any of it
This is the part that changes whether the analysis happens at all.
There’s no data scrub. No exports, no pivot tables, no request sitting in an analyst’s queue for a week. Both projections are computed from your own closed history and your own live pipeline, and they’re there in real time at every level of the org — company, team, territory, segment, rep.
That matters more than it sounds. The reason most teams answer “where will we land?” with gut feel isn’t that they prefer gut feel. It’s that the good answer takes two weeks to produce, so it gets produced once a quarter, at the moment it’s least useful — after the decisions have already been made.
When the projection is standing there on a Monday morning, it becomes part of the weekly rhythm instead of a quarterly fire drill. You see the gap open in week four rather than week eleven, when there’s still time to do something about it.
One more thing worth saying plainly: none of this is generated by AI. These are measured statistics computed from your own Salesforce history — the same calculation, run the same way, every night. You can trace any number back to the deals underneath it.
The shift
From one number that gets argued about to two independent reads whose agreement — or disagreement — tells you something you didn’t know before you looked.
Rev Intel computes both projections from your own history and your own pipeline, live, at every level of the hierarchy. If you want to see what your quarter looks like through both, book a demo and we’ll run it on your data.
