ThinkWithPrompt by SynotticThinkWithPrompt

Inspect a deal to find the real risk before I commit it

A structured deal inspection that tests evidence behind each qualification element and tells you whether the deal belongs in commit.

SalesRTFStandardFill-in Template

The prompt

Help me inspect one deal before I put it in my commit forecast. Deal: [ACCOUNT, amount, product, current stage, close date] Qualification method we use: [e.g. MEDDICC, BANT, SPICED, or "none"] What the rep has told me: [paste notes, CRM fields, or call summary] Buyer activity so far: [meetings held, who attended, last contact date, next step booked] Paper process: [legal, security, procurement status] Close date history: [how many times it has moved] For each element of my qualification method (if I said "none", use metrics, economic buyer, decision criteria, decision process, paper process, pain, champion, competition): 1. Rate the evidence: Verified (buyer said or did it), Claimed (rep belief), or Unknown. 2. Quote or point to the evidence I gave you. If there is none, mark it Unknown. Do not fill gaps with assumptions. Then check for common commit traps: no meeting with the economic buyer, no agreed next step with a date, close date moved 2+ times, procurement not started within 30 days of close, single-threaded with one contact, and a close date driven by our quarter rather than the buyer's event. Return: - A table: Element | Evidence | Rating | Gap. - A verdict: Commit / Best case / Pipeline, with a one-paragraph reason. - The 5 questions I should ask the rep in our next conversation. - 3 actions that would most raise confidence this week, each with an owner.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Sales prompts

What to fill in

  • ACCOUNT, amount, product, current stage, close date
  • e.g. MEDDICC, BANT, SPICED, or "none"
  • paste notes, CRM fields, or call summary
  • legal, security, procurement status
  • how many times it has moved

How this prompt is built

This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.

Related prompts

Find more prompts like this