Forecast Calls May 13, 2026 · 9 min read

How to Run a Weekly Forecast Call as an Enterprise AE

Most closers walk into forecast calls with vague pipeline updates and get torched. The VP asks one pointed question — "why are you committing Acme?" — and the answer is opinions, not evidence. Here's how to change that.

What a forecast call actually evaluates

Your VP isn't running a status update meeting. They're evaluating three things for every deal you put in commit: confidence level, supporting evidence, and next steps with real dates.

Confidence without evidence is a guess. Evidence without next steps is history. Both get your number rewritten.

The AEs who come out of forecast reviews with their number intact share one habit: they show up with a documented position, not an oral argument. They have specifics — who said what, what was confirmed, what's still assumed, what happens next and by when.

The real question in every forecast call

Your VP is asking: "Do I trust this number enough to put my name on it?" Your job is to give them a reason to say yes — or to surface the risk so the rewrite is yours, not theirs.

The 5-part structure for every deal you bring

For every deal in your commit column, you need five things documented before you open your mouth on the call. Not all at once — this is a cadence you build through the week.

1. Snapshot

Account name, ARR, close date, stage. One line. Your VP has 8 deals to review in 30 minutes — don't make them ask for basics.

2. Evidence

What is confirmed (buyer said it or did it, on record), what is assumed (you believe it but no one has explicitly confirmed it), and what is at risk (a known threat with no mitigation yet). If you don't know the difference between what you've confirmed and what you're assuming, your evidence score is a 3 out of 10.

A $180K deal example: see how Acme Q3 gets structured with evidence tags →

3. Stakeholders

Champion, economic buyer, blockers. For each: confirmed access or assumed access? Have you spoken to the economic buyer directly, or are you relying on your champion's read of the room? This one question kills more deals than any other.

4. Risks

Top two or three risks, each with an owner and a mitigation. Not "procurement might be slow" — that's not a risk, that's a concern. A risk has a name: "Legal review at GlobalBank took 6 weeks last quarter; our close date assumes 2. Owner: me. Mitigation: legal kickoff meeting scheduled for Thursday."

5. Next proof points

What does the buyer have to do next, by what date, that would move this deal forward? If there's no buyer action with a date attached, it's not in commit. It's in best case.

What to say when asked "why are you committing this?"

This is the moment most AEs fumble. The wrong answer is a narrative: "I feel really good about this one, Sarah's been super engaged, we had a great call last week…"

The right answer is evidence-first:

Evidence-first answer pattern

"Economic buyer confirmed budget verbally on March 12th. Champion mapped the full procurement timeline and says legal takes two weeks — we've built that in. Security review is our one open item; kickoff is Thursday. If that slips, the close date moves. I'm committing at $180K with that as the known risk."

That answer does three things. It shows you know what's confirmed. It shows you know what's at risk. And it puts the risk on the table before your VP finds it themselves — which means the rewrite, if it happens, is surgical, not a gut-shot to your number.

The enterprise deal review template structures all of this into a one-page artifact you can read verbatim or hand to your VP. It's what makes the evidence-first answer repeatable across every deal in your pipeline.

Red flags that get deals pulled out of commit

These are the patterns VPs recognize immediately. If any of these describe your deal, it needs to move to best case before the call — not during it.

Pattern What your VP hears Move to
"We have strong executive alignment" No one has talked to the economic buyer Best case
"They're 100% going with us" Competing vendor not formally ruled out Best case
"Close date is end of quarter" No buyer-committed milestone to drive urgency Best case
"Legal is a formality" Legal has not been engaged and timeline is unknown Best case
"Champion is fully bought in" Champion has not shown willingness to push internally Best case
Deal dark for 10+ days No buyer engagement, no urgency mechanism Pipeline

None of these are fatal — but they belong in best case, with a clear story for what has to happen to promote the deal to commit next week. That's not weakness; that's the kind of forecast hygiene that earns VP trust over time.

A repeatable weekly cadence

The AEs who consistently defend their numbers don't scramble before the Friday call. They build the artifact through the week.

Friday (after last call)

Update your evidence log for every deal in commit or best case. What changed this week? What moved from assumed to confirmed — or from confirmed to at risk? Tag it. Five minutes per deal.

Monday (before the call)

Review your Deal Review Pack for each deal. Is the snapshot accurate? Are the risks current? Do you have next proof points with dates? If any deal can't answer yes to all three, it's not ready to commit.

This is the moment to read your pack out loud — to yourself or a colleague. If you can't explain why a deal is in commit in two sentences backed by evidence, your VP will find that out in real time.

Tuesday (after the call)

Update your pack based on VP feedback. Every rewrite, every question, every "I'm not sure about that one" — document it. What did they push back on? What evidence were they asking for that you didn't have? That's your prep list for next week.

The compounding effect

AEs who track commit vs. actual over time get better at forecasting — not because of intuition, but because they have data. You start to see patterns: deals where economic buyer access was assumed almost never close on the original date. Deals with security reviews always add 10 days. That calibration is what makes your number trustworthy at the VP and CRO level — and it's what earns you quota relief when something legitimately slips.

The bottom line

A weekly forecast call is not a narrative exercise. It's an evidence review. The AEs who come out with their number intact are the ones who did the work before the call — tagging evidence, documenting risks, building a position they can defend in one sentence.

The fastest way to build that habit is a structured deal review for every deal you bring to commit. Not a CRM note. An artifact with a defined format, evidence tags, and specific next steps. That's what turns "I feel good about this" into "here's what I know, here's what I'm watching, and here's why I'm committing."

Stop preparing for forecast calls in your head.

The Deal Review Template turns your pipeline into evidence-backed positions your VP can trust — and gives you the artifact to read verbatim on the call.

Download the Free Template → Or start a free trial and generate your first pack in 90 seconds →