What you'll get
- 6 copy-ready blocks
- 5 min read
A sales demo script usually follows the product: login, dashboard, features, questions. A buying committee does not watch it that way. The problem owner wants their Tuesday fixed, the budget holder wants the cost of the problem, the evaluator wants to know what breaks and the user wants to know what changes. This script runs scenes, one per role, so everyone hears their question answered in front of the others.
Before the first scene
Know who is in the room and what each owns; that is the buying committee roles cheat sheet's job, and the setup checks are the demo prep checklist. If you cannot name the roles attending, the demo is not ready to book.
The opening (2 minutes)
"Thanks all. Rather than a tour, I will show how [their problem, their
words] gets handled, start to finish. [Problem owner name], interrupt
me where this is not how it really works. At the end I want ten
minutes of your questions more than my slides."The invitation to interrupt is load-bearing: it converts the problem owner from spectator to referee, and a referee is invested.
Scene 1: The problem owner (8 minutes)
Show their worst recurring moment, end to end, using their words from discovery.
"You said the day gets planned at 6 and replanned by 9. Here is the 9am
replan, done in [the product]."
[Show exactly that path. Their data shape, their terminology, nothing else.]
"Is that the real shape of it, or did I make it too easy?"The closing question matters: a yes is public validation in front of the budget holder, and a no is discovery you needed.
Scene 2: The budget holder (5 minutes)
Do not show features; show consequence.
"[Budget holder name], the bit that concerns your side: that replan
currently takes [their number]. This way it is [the change]. Over a
quarter that is [the arithmetic, from their own figures]."
"What would you need to see measured in a pilot for that to be credible?"The question hands them the pilot's success criteria, which means the pilot is now partly theirs.
Scene 3: The evaluator (5 minutes)
"[Evaluator name], your part: how it connects and what breaks. It talks
to [their systems, from discovery] like this. The honest limits: [one
or two, stated plainly]."
"What did I skip that you would test first?"Volunteering a limit before they find one is the cheapest credibility in the meeting. An evaluator who catches you hiding something owns the room from that moment.
Scene 4: The user (5 minutes)
"[User name or role], your Tuesday: here is the same task, your side."
[Hand over control if the format allows. Let them click.]
"What would annoy you about this by week three?"Users asked for annoyances give real answers, and a user who has driven the product argues for it later in rooms you are not in.
Scene 5: The close (5 minutes)
"Three things I heard: [problem owner]'s point about [x], [evaluator]'s
question on [y], [budget holder]'s measure of [z]. Proposed next step:
[a scoped pilot or working session] that answers all three by [date].
Who else should be in that conversation?"The recap proves the scenes were listening, not theatre, and the "who else" keeps the map growing. Then the account's forwardable recap goes to your champion within 24 hours.
Worked example (illustrative, not a real company)
Tessaro Analytics demos to four people at Northfield Logistics. Scene 1 replans the 9am schedule with depot names from discovery; the operations director interrupts twice, both corrections minor, both public proof she is engaged. Scene 2 turns her overtime number into a quarterly figure and the finance lead names his pilot measure. Scene 3 volunteers an integration limit; the IT manager relaxes visibly. Scene 4 hands the mouse to a dispatcher. The close books a pilot scoping call with all four plus procurement. All names are invented.
Five mistakes to avoid
- Running feature order to a mixed room. Every minute on a feature nobody owns loses one role; forty minutes loses four.
- Playing the scenes to the wrong faces. Cost to the evaluator and plumbing to the budget holder is the same content wasted twice. Name the person each scene is for, out loud.
- Hiding the limits. Scene 3 exists because the evaluator will find them anyway; the only choice is whether you look honest or caught.
- Demoing with generic data. Lorem-ipsum customers and round numbers tell the room this performance runs unchanged for everyone. Their terminology is the cheapest personalisation that exists.
- Ending at questions. "Any questions?" is not a close. The recap-plus-next-step script in scene 5 is; use it even when the demo went badly, especially then.
Why this works on named accounts
Common questions
How do you structure a sales demo for multiple stakeholders?
In scenes by role, not features by menu: the problem owner's worst moment first, then consequence for the budget holder, plumbing and limits for the evaluator, hands-on for the user, and a close that recaps what each said and books the next step. Each scene is addressed to its person by name.
How long should a software demo be?
About thirty minutes of showing across the scenes, held inside a 45-minute meeting so questions have room. Past that, attention and honesty both decay. If the product needs an hour to make sense, the demo is carrying work discovery should have done.
What should you say at the end of a demo?
Recap one thing each role said during the demo, propose a scoped next step with a date that answers the open points, and ask who else belongs in it. The close is the demo's whole purpose; the scenes exist so that it lands.
More from the Academy
Buying Committee Roles Cheat Sheet
For sellers and SDRs working deals where more than one person decides.
You leave with the six roles on one page, what each cares about, what to send each one, how to spot them by job title and the cost of ignoring each.
Demo Prep Checklist
For anyone who has watched a demo die from an unshared screen or an unknown audience.
You leave with a three-part checklist: the account facts to hold, the setup checks and the first-minute questions.
Buying Committee Map
For sellers working a large account through a single contact.
You leave with nine roles to look for, a map you can paste into a spreadsheet, a brief for each person and a coverage check that shows where the account is exposed.
Buying Committee Mapper
Map the people behind a decision by role, stance and influence, and see who to approach next. Runs in your browser.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.