Personalize one demo script for every stakeholder in the room
Maps every demo attendee to their silent question, their high-relevance moments with name-addressed talk lines, their skepticism trigger with a preemption, and the one sentence you want each repeating internally. Turns a single demo flow into a call where every stakeholder feels the demo was built for them.
You are a presales strategist who specializes in multi-stakeholder demos — the calls where an end user, their boss, and someone from IT or finance all watch the same screen and each silently asks a different question. End users ask 'will this make my day easier?', executives ask 'what does this do to my numbers?', and technical evaluators ask 'what will this break?'. A demo that answers only one of those loses the other two votes.
Take my demo plan and personalize it for each attendee. Output format — for EACH stakeholder:
1. THEIR SILENT QUESTION: the one thing they need answered to say yes, in one sentence.
2. THEIR MOMENTS: which 2-3 parts of my existing demo flow matter to them, and the exact line to say at each one that speaks to their silent question — addressed to them by name ('Maria, this is the part that changes your Monday').
3. THEIR LANDMINE: the moment in my demo most likely to trigger their skepticism, and the one-line preemption.
4. THEIR TAKEAWAY: the single sentence I want them repeating internally after the call.
Then give me a 60-second opening that acknowledges each person's stake so nobody spends the demo wondering why they're there. Rules: no stakeholder gets more than three moments — spreading attention thin serves no one. If two stakeholders conflict (e.g., automation that helps the boss but threatens the user), name the tension and give me a line that addresses it honestly rather than hoping nobody notices.
Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. Walk me through your current demo flow — the sections you plan to show, in order.
2. Who's attending? For each: name or role, what they own, and anything you know about their attitude toward this purchase.
3. What did discovery reveal about the problem, and who on the call felt it most?
4. Who do you believe actually decides, and who can veto?
Once you have my answers, produce the stakeholder map and personalized script notes. If I can't describe an attendee's attitude, ask me one probing question about them before writing their section.How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Answer question 2 thoroughly — attitude notes like 'the IT lead was burned by the last vendor' change everything.
- 3
Print or split-screen the per-stakeholder moments so the name-addressed lines are in front of you live.
- 4
Deliver the 60-second opening as written; acknowledging each stake early keeps quiet attendees engaged.
- 5
After the call, check which takeaway sentences actually landed and rerun the prompt before the follow-up meeting.
Best practices
The landmine preemptions are the highest-value output — saying 'you might be wondering what happens to your current setup' before IT asks it builds more trust than any feature.
If a named conflict exists between stakeholders, decide before the call how honest to be; the model gives you the line, but you choose to use it.
Address people by name at their moments — it's the cheapest, most underused attention device in group demos.
For calls with 5+ attendees, ask the model to cluster them into three archetypes instead of individually mapping everyone.
Example: what this looks like in practice
An AE at an expense-management platform has a demo with a controller (economic buyer), two accountants (daily users), and an IT manager. Discovery showed the accountants dread month-end close. The output flags a real tension: the automation that saves the controller headcount hours is the same feature the accountants may read as replacing them. The model supplies the honest line — 'this doesn't remove the review step, it removes the chasing' — and maps the IT manager's landmine to the SSO section. The AE opens with the 60-second stake acknowledgment. Afterward the controller emails asking for pricing, and one accountant replies separately: 'the chasing part is exactly our problem.' Two constituencies, both sold, one demo.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Map each attendee's silent question before the call — end users ask if it makes their day easier, executives ask what it does to their numbers, technical evaluators ask what it breaks. Then assign each person two or three named moments in your flow. This prompt builds that map and scripts the lines, so nobody in the room spends 40 minutes wondering why they were invited.
More discovery calls & demos prompts
Build a discovery question bank tailored to one persona
Generates a 15-question discovery bank built around one persona's actual responsibilities and failure modes, organized by call stage, with listening notes on what strong and weak answers sound like. Beats generic question lists because the interview forces your product, competitor, and deal-death context into every question.
Write a post-discovery summary email that mirrors their words
Produces a sub-180-word summary email built on the prospect's verbatim phrases, with impact-paired bullets, an invitation to correct you, and next steps with your commitments listed first. Mirroring their language proves you listened in a way no template can, and the email becomes the artifact your champion forwards internally.
Build a demo storyline from your discovery notes
Converts raw discovery notes or a transcript into a three-act demo storyline that opens on the prospect's problem in their own words, sequences scenes by deal importance, tells you what NOT to show, and scripts the close. It's the difference between a feature tour and a demo the champion replays internally.