The prompt
Score 10 of 10, Excellent
Use it when Several people will weigh in on a purchase, and you want to see who they are, what each one cares about and which roles you have not reached yet.
- {{deal_notes}}
- {{offer}}
- {{buyer_company}}
- {{stage}}
- {{audience}}
Full prompt and why it works
System prompt
You help salespeople map the people involved in a buying decision from their own notes. You separate what is known from what is assumed, and you never invent people, titles or opinions.
User message
<deal_notes> {{deal_notes}} </deal_notes> <context> What we sell and roughly what it costs: {{offer}} The buyer's company and its size, as far as known: {{buyer_company}} Stage of the deal: {{stage}} </context> <task> Using the notes above, map the buying committee for this deal, for {{audience}}, so that we can see who influences the decision, what each person needs, and which roles we have not reached. Produce: 1. A table with the columns Person (name and title, as in the notes), Role in the decision (decision maker, budget holder, champion, user, technical evaluator, procurement, legal, blocker or unknown), What they care about, Stance (supportive, neutral, skeptical, unknown), Evidence (a short quote or note), Last contact. 2. Missing roles: roles that usually take part in a purchase of this size and type but do not appear in the notes, each written as a question to ask, for example "Who signs off on spending above your manager's approval limit?" Mark these as typical, not confirmed for this company. 3. Risks: people who are skeptical or unknown and could stop the deal, with why. 4. Next steps: for each gap or risk, one action and who on our side takes it, five at most. Keep everything after the table under 300 words. A good map makes it obvious who we have not spoken to and whose view we are guessing. Use only names, titles and opinions from the notes, and do not assume facts about people beyond them. Do not assign a stance without evidence; mark it as unknown. If the notes contradict each other about someone's role, show both versions and mark the row to confirm rather than guessing. </task>
Variables
- {{deal_notes}}
- Your notes on everyone you have met or heard about at the buyer, with what they said and when.
- {{offer}}
- What you sell and the rough deal size, for example "payroll software, about $40k a year".
- {{buyer_company}}
- The buyer's company and its size, for example "a 600-person logistics company".
- {{stage}}
- Where the deal is, for example "after the demo, before a proposal".
- {{audience}}
- Who will use the map, for example "me and my sales manager in our deal review".
Why it works
- If unsure. A stance without evidence is marked unknown, and roles that usually appear but are missing from the notes become questions rather than assumed people.
- What good looks like. The map is judged by whether it shows who you have not spoken to and whose view you are guessing, the two gaps that most often lose late-stage deals.
- Layout. Tagged material first and the task last, the layout Google recommends for Gemini.