PlaybookPrompts

Audit a stalled deal and surface your next move

Sales & Outreach deal-managementpipelinecoaching

Deals stall when a rep stops diagnosing and starts hoping. This prompt takes everything you know about a stuck opportunity and returns an honest diagnosis plus a ranked list of concrete actions to unstick it.

Prompt
You are a senior sales coach reviewing a stalled deal. Analyze the deal I describe and give me a clear-eyed diagnosis and action plan.

1. Based on the deal notes I provide, identify the most likely root cause of the stall. Give me your top two hypotheses ranked by probability and explain the evidence for each.
2. List three warning signs in my notes that I may have glossed over — things that suggested a problem earlier than the stall became obvious.
3. Recommend three specific actions I can take in the next 5 business days to test whether the deal is still alive. Each action must be concrete (who I contact, what I ask, what I'm looking for in the response).
4. Write a one-paragraph internal deal note I can paste into my CRM that accurately reflects the deal status — no spin, just facts and the path forward.
5. Give me a go/no-go signal: based on what I've shared, is this deal worth the next 30 days of effort? State your reasoning plainly.

Deal background and notes: {{DEAL_NOTES}}
Last meaningful interaction: {{LAST_INTERACTION}}
Estimated close date originally set: {{ORIGINAL_CLOSE_DATE}}
Deal value: {{DEAL_VALUE}}

This prompt works best when you've had at least two discovery conversations. For deals still in the first meeting stage, the diagnosis will be limited.
Variables to fill in
  • {{DEAL_NOTES}}
  • {{LAST_INTERACTION}}
  • {{ORIGINAL_CLOSE_DATE}}
  • {{DEAL_VALUE}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{DEAL_NOTES}}{{LAST_INTERACTION}}{{ORIGINAL_CLOSE_DATE}}{{DEAL_VALUE}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.