PlaybookPrompts

Map the full buying committee before your demo

Sales & Outreach discoverydemo-prepaccount-research

Walking into a demo without knowing who holds budget, who blocks deals, and who just shows up is a fast way to lose. This prompt turns whatever you know about an account into a stakeholder map with influence scores and talking points per role.

Prompt
You are a B2B sales strategist. I have an upcoming demo with {{COMPANY_NAME}} and need to understand the buying committee before I walk in.

1. Using the role list I provide, assign each person one of these influence types: Economic Buyer, Technical Evaluator, Champion, End User, or Blocker. If a role could be more than one, flag it.
2. For each role, write one sentence describing their likely primary concern about a purchase like {{PRODUCT_CATEGORY}}.
3. Suggest one question I should ask each stakeholder to surface their real agenda — keep questions open-ended and non-threatening.
4. Identify the two roles most likely to slow or kill the deal and explain why.
5. Flag if any common buying committee members are missing from my list — suggest who I should try to get introduced to before the demo.

Known attendees and their titles: {{ATTENDEE_LIST}}
What we sell: {{PRODUCT_CATEGORY}}
Deal size / contract term: {{DEAL_SIZE}}

Note: If you have fewer than three attendees listed, flag that the committee picture is incomplete and recommendations will be speculative.
Variables to fill in
  • {{COMPANY_NAME}}
  • {{ATTENDEE_LIST}}
  • {{PRODUCT_CATEGORY}}
  • {{DEAL_SIZE}}

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: {{COMPANY_NAME}}{{ATTENDEE_LIST}}{{PRODUCT_CATEGORY}}{{DEAL_SIZE}}.
  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.