PromptSharp › Prompt Library › Sales › Pipeline scrub: commit-call interrogation for every late-stage deal
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.
The prompt — copy and run it
You are a RevOps analyst running a pipeline scrub before the forecast call. I will paste the late-stage deal list. Produce: A) SCRUB TABLE — columns: deal ID, red flags (stalled age vs stage norm, past-due next step, single-threaded, close date pushed more than once), and a risk-adjusted category (commit / best case / pipeline / remove) with a one-line justification. B) INTERROGATION QUESTIONS — for each deal you kept in commit, the 3 questions a CRO would ask the owner, specific to that deal's flags. C) ROLL-UP SUMMARY — count and value by category, plus the single biggest risk to the number. Data: [PASTE DEAL LIST: STAGE, AGE, AMOUNT, CLOSE DATE, NEXT STEP, LAST ACTIVITY, CONTACTS THREADED] My stage norms: [OPTIONAL: AVERAGE DAYS PER STAGE, HISTORICAL STAGE WIN RATES] Rules: Do not invent deal facts or probabilities — categorize only from the fields provided and write "insufficient data" where a row is thin. Flag every recategorization for the deal owner to verify before the call. Use internal deal IDs, never customer names, and never include confidential pricing.
Why this prompt works
Forecast misses come from unexamined commit deals, not bad math. Turning each red flag into a deal-specific interrogation question converts the scrub from bookkeeping into the actual forecast-call agenda — and 'insufficient data' rows expose your CRM hygiene problem for free.
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?
Forecast call is tomorrow. Pressure-test the commit list so the number you roll up is the number that closes.
Why does this prompt work?
Forecast misses come from unexamined commit deals, not bad math. Turning each red flag into a deal-specific interrogation question converts the scrub from bookkeeping into the actual forecast-call agenda — and 'insufficient data' rows expose your CRM hygiene problem for free.
What mistake does this prompt help you avoid?
{'code': 'PF07', 'note': "Unexamined commit deals rolling into the number — each red flag becomes a deal-specific interrogation question; 'insufficient data' is a legal verdict."}
Related Sales prompts
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.…
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…
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