Map the Buying Committee and Multithread a Single-Threaded B2B Deal

Returns a ranked stakeholder table, a short outreach message per person, a script to ask your champion for the economic buyer, and a 14-day multithreading plan.

You getStakeholder table, outreach message per person and script for asking the champion for the economic buyer…

Prompt

Prompt
Act as a B2B sales coach who specializes in enterprise deal strategy. Your job: help me map the buying committee on a deal where I have only one contact, and plan how to reach the others, especially the economic buyer, through my champion instead of around them.

First, ask me these questions in one message and wait for my answers:
1. What do you sell, what is the deal size, and what stage is it in?
2. Who is your one contact (title, what they care about, how engaged they are)?
3. Which other people or roles do you know or suspect are involved?
4. What is the decision date or trigger, and is there a competitor?

Rules:
- Include the usual roles for this kind of purchase (economic buyer, technical evaluator, end-user lead, finance, procurement or legal) even if I named no one; mark unknown names as "Unknown, ask champion".
- Rank stakeholders by risk to the deal if left unengaged.
- Every outreach message is under 60 words, gives one concrete reason that person would care, and says whether it goes via the champion or direct with the champion's knowledge.
- Never suggest contacting anyone above the champion without asking the champion first.

Output format:
1. Stakeholder table: Person or role | Likely priority | Current access (None, Indirect, Direct) | Risk if unengaged | Next action
2. Outreach message per person
3. Script for asking the champion for the economic buyer introduction
4. 14-day plan as dated steps

End with the main assumptions you made and what to verify on the next call.

Example output

At a glance14-day multithreading plan for Harlow MechanicalSeven milestones to widen access beyond Dana
  1. Send summary and champion askDay 1Three-slide summary to Dana
  2. Confirm VP Ops and IT namesDay 3Get the unknown stakeholders named
  3. Rosa runs sandbox testDay 5End-user lead tests the product
  4. Joint call with VP OpsDay 7Dana leads the conversation
  5. IT integration callDay 9Cover ERP and access controls
  6. ROI review with CFODay 11Walk through payback assumptions
  7. Agree mutual close planDay 14With Dana and VP Ops

Example for: a rep selling field-service scheduling software to Harlow Mechanical (fictional), $85k ARR deal in evaluation, single-threaded through the operations manager, decision targeted for end of quarter, competing with a spreadsheet status quo.

1. Stakeholder Table

Person or roleLikely priorityCurrent accessRisk if unengagedNext action
VP Operations (Unknown, ask champion) – economic buyerCut overtime and missed appointmentsNoneHighAsk Dana for intro this week
CFO, Mark EllisonPayback under 12 months, no surprise costsNoneHighSend ROI one-pager via Dana
IT Manager (Unknown, ask champion) – technical evaluatorIntegration with existing ERP, security reviewNoneMediumOffer 30-min integration call
Dispatch Lead, Rosa Kim – end-user leadFewer manual reschedules, easy for techsIndirectMediumInvite to sandbox demo
ProcurementStandard contract terms, vendor onboardingNoneLowAsk Dana about their process and timing
Dana Patel, Ops Manager – championLook good for solving scheduling chaosDirect—Prep her for internal pitch

2. Outreach Messages

VP Operations (via Dana): "Dana shared that missed appointments hit 9% last quarter. I'd value 20 minutes to show how two similar contractors cut that by half, and hear what you'd need to see before approving."

CFO Mark Ellison (via Dana): "Attached is a one-page payback estimate built on Harlow's overtime numbers Dana provided. Happy to walk through the assumptions in 15 minutes."

IT Manager (direct, Dana copied): "Before anything moves forward, I want your team to see how we connect to your ERP and handle access controls. Would a 30-minute technical call next week work?"

Rosa Kim (direct, Dana copied): "Dana mentioned your dispatchers handle most reschedules by phone. Could you test the sandbox with two real jobs? Your feedback shapes the rollout plan."

3. Champion Script

"Dana, you've built a strong case. In my experience, deals like this stall when the VP first hears about it at budget review. Would you be open to a joint call where you lead and I handle the technical questions? I can send you a three-slide summary to use first."

4. 14-Day Plan

  • Day 1: Send Dana the three-slide summary and the champion ask.
  • Day 3: Confirm names for VP Ops and IT Manager.
  • Day 5: Rosa runs sandbox test.
  • Day 7: Joint call with VP Ops, Dana leading.
  • Day 9: IT integration call.
  • Day 11: ROI review with CFO.
  • Day 14: Agree on mutual close plan with Dana and VP Ops.

Assumptions to verify: that the VP Ops signs at $85k, that IT has veto power, and that procurement needs under two weeks.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Forcing standard roles into the table exposes stakeholders you haven't met instead of only mapping the names you already know.
  • The champion-first rule protects your main relationship while still getting you to the economic buyer.
  • Ranking by risk if unengaged tells you which contact to chase this week, not just who exists.

Use when a deal rests on one contact and the close date is getting closer. Have the deal size, stage, your contact's title and any names you've heard ready. Works in ChatGPT, Claude or Gemini.

Common edits

  • Shorten the plan to 7 days for deals closing this month.
  • Ask for a MEDDICC-style gap list alongside the stakeholder table.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Sales