PlaybookPrompts

Diagnose why deals stall at a specific pipeline stage

Business Strategy salespipelinerevenue

A win-rate problem often hides inside one broken pipeline stage. This prompt turns your deal data and rep observations into a short, testable diagnosis rather than a vague 'sales process needs work' conclusion.

Prompt 
You are a sales strategy consultant. My company sells {{PRODUCT_OR_SERVICE_DESCRIPTION}} at an average deal size of {{AVERAGE_DEAL_SIZE}}. Deals are stalling most often at the {{STALL_STAGE}} stage of our pipeline. Here is what we observe: {{OBSERVED_SYMPTOMS_AND_DATA}}.

1. Generate five distinct hypotheses for why deals stall at this specific stage. For each hypothesis, explain the mechanism (i.e., what is actually happening in the buyer's mind or process).
2. For each hypothesis, name one piece of evidence that would confirm it and one that would rule it out. Keep evidence-gathering practical—assume I can review CRM notes and run three rep interviews.
3. Rank the hypotheses by likelihood given what I have already described.
4. For the top two hypotheses, propose a targeted fix that could be tested in the next 30 days without a full process overhaul.
5. Write three discovery questions I can add to rep call reviews to gather the evidence needed to confirm or rule out each hypothesis.

If my symptom data is too thin to diagnose confidently, tell me exactly what data I should collect first.
Variables to fill in
  • {{PRODUCT_OR_SERVICE_DESCRIPTION}}
  • {{AVERAGE_DEAL_SIZE}}
  • {{STALL_STAGE}}
  • {{OBSERVED_SYMPTOMS_AND_DATA}}

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: {{PRODUCT_OR_SERVICE_DESCRIPTION}}{{AVERAGE_DEAL_SIZE}}{{STALL_STAGE}}{{OBSERVED_SYMPTOMS_AND_DATA}}.
  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

Notion AI

$8/user/mo add-on

AI baked into the docs/wiki/projects tool you already use.

Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.

productivitywriting

Perplexity

$0/mo (Pro at $20)

AI search engine with citations.

Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.

learningdata

Claude (Anthropic)

$0/mo (Pro at $20)

Frontier model with long context and strong reasoning.

Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.

writingcodinglearning

ChatGPT (OpenAI)

$0/mo (Plus at $20)

The category-defining general-purpose AI assistant.

ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.

writingcodinglearning

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.