Audit an Open B2B Deal Against Ten Risk Signals Before Your Forecast Call

Get a red-yellow-green audit of one open deal, a Commit, Best Case or Pipeline call backed by evidence from your notes, and the top actions to firm it up.

You getVerdict, table and top 3 actions to move the deal up one category

Prompt

Prompt
Act as a sales forecasting manager who reviews deals before the weekly forecast call. I will paste my notes on one open opportunity right after this prompt (CRM fields, call notes, emails, close plan).

Audit the deal against ten risk signals: 1) single-threaded, 2) no confirmed economic buyer or budget owner, 3) close date has slipped, 4) no next step with a date, 5) no mutual close plan, 6) pain not quantified, 7) competitor or status quo not addressed, 8) legal, security or procurement not started, 9) champion untested, 10) no buyer activity in 14 days.

Rules:
- Mark each signal Red, Yellow or Green and cite the exact note that supports it.
- If my notes are silent on a signal, mark it Unknown and count it as Yellow, never Green.
- Category: Commit = 0-1 Red and none on signals 2 or 3; Best Case = 2-3 Red; Pipeline = 4+ Red or no economic buyer.
- Every action has an owner and a deadline before the close date.

Output format:
1. Verdict: category and one-sentence reason
2. Table: Signal | Status | Evidence
3. Top 3 actions to move the deal up one category
4. What to say on the forecast call (2-3 sentences)

End with one line naming the missing information that would most likely change the verdict.

Example output

At a glanceDeal risk signals by status (10 signals)Northwind Freight, $84,000 ARR: verdict Best Case
  • Red: 2
  • Yellow: 4
  • Green: 4

Example for: an AE at a SaaS vendor reviewing a $84,000 ARR deal with Northwind Freight, close date June 28.

1. Verdict: Best Case

Strong champion and quantified pain, but the CFO has never been on a call and the close date has already slipped once, so this cannot be called Commit.

2. Signal Audit

SignalStatusEvidence
1. Single-threadedYellowTwo contacts engaged (Dana Ruiz, Ops Director; Mark Chen, IT Lead), but all scheduling goes through Dana
2. Economic buyerRed"CFO Priya Nair signs over $50k" - no meeting with her logged
3. Close date slippedRedMoved from May 31 to June 28 on May 14
4. Next step with dateGreenSecurity review call booked June 6
5. Mutual close planYellowClose plan drafted, not yet confirmed by Dana
6. Pain quantifiedGreen"Losing ~$12k/month on manual dispatch errors" (May 2 call)
7. Competitor / status quoYellowDana mentioned "looking at one other tool," not named
8. Legal / security / procurementYellowSecurity review starts June 6; legal not started
9. Champion testedGreenDana got IT to attend the demo and shared internal budget slide
10. Activity in 14 daysGreenEmail reply from Dana on May 29

Count: 2 Red, 4 Yellow, 4 Green.

3. Top 3 Actions to Move to Commit

  1. Get 30 minutes with Priya Nair - Owner: you, via Dana. Deadline: June 7. Bring the $12k/month cost figure as a one-page ROI summary.
  2. Get the close plan signed off - Owner: you and Dana. Deadline: June 10. Include legal redlines, security sign-off and signature date.
  3. Send contract to Northwind legal now - Owner: your deal desk. Deadline: June 5. Running legal alongside security saves about a week.

4. What to Say on the Forecast Call

"Northwind is Best Case at $84k for June 28. Pain is quantified at $12k a month and Dana has proven she can move people internally, but we have not met the CFO and the date slipped once. I have asked for a CFO meeting by June 7; if it happens and the close plan is confirmed, I will move it to Commit."

Missing information: whether Priya Nair has already approved this budget line, and the name of the competing vendor.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Ten named signals with fixed scoring thresholds make the Commit, Best Case or Pipeline call consistent and hard to argue with.
  • Treating silent signals as Yellow stops the model from assuming good news the notes do not support.
  • Requiring cited evidence and dated actions turns the audit into something you can defend and act on.

Use the day before a forecast or pipeline review. Paste the deal's CRM fields, recent call notes and emails into ChatGPT, Claude or Gemini right after the prompt. More detail gives a sharper call.

Common edits

  • Swap the ten signals for your team's MEDDPICC or BANT fields so the audit matches your CRM.
  • Paste several deals at once and ask for a one-row-per-deal summary table ranked by risk.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Sales