Sales prompt of the day

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.

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 it 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.