PromptSharp › Prompt Library › Sales › Deal inspection: pressure-test your commit before you call it to the boss
Deal inspection: pressure-test your commit before you call it to the boss
You're about to commit a number. Inspect each deal cold so your forecast is defensible, not hopeful.
The prompt — copy and run it
You are a sales-ops analyst running a skeptical deal inspection before I submit my forecast. Produce: A) DEAL TABLE — each deal I paste: stage, amount, close date, and a REALITY score (committed / best-case / omit) based ONLY on evidence I provided, with the single missing proof that would upgrade it. B) SLIP RISK — the 2 deals most likely to slip the quarter and why, from the signals in my notes. C) GAP MATH — my committed total vs quota, the exact dollar gap, and which best-case deals would need to convert to close it. D) NEXT ACTIONS — the one highest-leverage action per at-risk deal this week. Inputs: [DEAL LIST: NAME, AMOUNT, STAGE, CLOSE DATE] · [EVIDENCE PER DEAL] · [MY QUOTA] · [WHAT'S WORRYING ME] Rules: Do not upgrade a deal's confidence beyond what my evidence supports, and do not invent amounts or dates. Keep confidential pipeline data out of consumer AI tools. This inspects the pipeline; the forecast call stays yours. Verify anything uncertain against the source before relying on it.
Why this prompt works
Forecasts inflate because reps score deals on hope; anchoring every REALITY score to evidence-provided-only and demanding the specific missing proof to upgrade a deal produces a commit number that survives scrutiny — and the gap math makes the shortfall undeniable instead of something to explain away later.
Want the daily version?
The PromptSharp Sales Brief delivers prompts like this every day. Honest status: sample stage — 50 waitlist signups start the free daily, and waitlist members see every issue first.
Frequently asked
When should I use this prompt?
You're about to commit a number. Inspect each deal cold so your forecast is defensible, not hopeful.
Why does this prompt work?
Forecasts inflate because reps score deals on hope; anchoring every REALITY score to evidence-provided-only and demanding the specific missing proof to upgrade a deal produces a commit number that survives scrutiny — and the gap math makes the shortfall undeniable instead of something to explain away later.
What mistake does this prompt help you avoid?
{'code': 'PF02', 'note': "Inflated forecasts — REALITY scores are evidence-gated and require a named missing proof to upgrade, so hope can't be committed as pipeline."}
Related Sales prompts
Coverage check: is there really enough pipeline to hit the number?
You're building next quarter's forecast. Pressure-test whether current pipeline actually covers the goal, and quantify the build g…
Pipeline scrub: commit-call interrogation for every late-stage deal
Forecast call is tomorrow. Pressure-test the commit list so the number you roll up is the number that closes.…
Account research brief: from raw filings to a first-touch angle
You have 30 target accounts and one hour. Turn one account's public footprint into a brief you can actually open a conversation wi…
All Sales free prompts
The PromptSharp Sales Brief page — five full free prompts plus the ladder status.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. See what each vertical is like before you commit to one.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Home · Prompt Library · Pricing · Archive · Privacy · Terms · Refunds
Finance · CPG · Marketing · Sales · Consulting & Strategy · Product Management · Dev & Engineering · C-suite · Law · Personal Finance · Career & Job Search · Focus & Productivity · Learning · Health & Fitness · Parenting