Verified against ChatGPT · 2026-08-01
Build a demo agenda around what discovery actually revealed, not a default feature tour
Turns discovery findings into a time-boxed live demo agenda ordered by buyer priority rather than product logic, with a named counter for a known skeptic in the room.
The prompt
Ready to copy — highlighted parts are example details you can swap.
I have a live demo coming up with Aldergate Health Network and want an agenda built around what discovery actually revealed, not our default feature-tour order. Who's attending: the Director of Clinical Ops (business buyer), and their IT Security lead. What discovery revealed about priorities and pain: clinical ops is drowning in manual scheduling conflicts; IT security's main concern is data residency for patient records. Features or workflows that must be shown, non-negotiably, regardless of ordering: the audit-log export, since it came up as a compliance requirement. Time allotted: 40 minutes including Q&A. A known skeptic in the room, if there is one, and why: the IT Security lead was burned by a previous vendor over a data residency issue. AGENDA ORDER Order the demo by what clinical ops is drowning in manual scheduling conflicts; IT security's main concern is data residency for patient records showed actually matters to this specific audience, not by the logical order features would be introduced to someone learning the product from zero. If the thing that matters most to this buyer happens to be the fifth feature in a typical default demo flow, it goes first here anyway, since a demo that opens with fifteen minutes of context-setting before reaching the one thing the buyer actually came to see risks losing their attention before the payoff arrives. FOR EACH AGENDA SEGMENT Give me: the time allotted, the specific discovery finding it's directly answering (not a generic "shows value" label), the one thing to say while showing it that ties back to that finding in the buyer's own language, and one likely question this segment will provoke from this specific audience, with a one-line answer ready for it. MULTI-ATTENDEE HANDLING If the Director of Clinical Ops (business buyer), and their IT Security lead includes more than one role, name which segment of the agenda is primarily for which attendee, and flag any point where two attendees in the room are likely to want to see genuinely different things at the same moment — a technical lead wanting to see the API and a business buyer wanting to see the ROI dashboard rarely want the same five minutes of screen time, and the agenda should either sequence around that or explicitly call out the segment as one where the other attendee should be told up front that their part is coming shortly. HANDLING the IT Security lead was burned by a previous vendor over a data residency issue If a known skeptic is named, identify the specific point in the agenda where their skepticism is most likely to surface as a question or pushback, and build in one line addressing it proactively before they have to ask — not by naming them directly as a target, but by simply making sure the segment doesn't leave an obvious opening for the exact objection they're likely to raise. TIME DISCIPLINE If the sum of segment times exceeds 40 minutes including Q&A, cut something and say plainly what got cut and why it was the lowest-priority item relative to clinical ops is drowning in manual scheduling conflicts; IT security's main concern is data residency for patient records — never silently overrun the agenda and hope the call runs long; a demo that hasn't reached its most important point when time runs out is a demo that failed regardless of how good the earlier segments were. CLOSE End the agenda with a specific next-step ask tied to what was just shown, not a generic "any questions?" close — the ask should name a concrete next action and, if possible, a date.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Ordering the demo by buyer priority rather than product logic directly targets the most common self-inflicted failure of live demos: a rep who defaults to the product's natural onboarding order — the sequence a new user would learn features in — ends up spending the first several minutes on context the buyer doesn't need, and if the meeting runs long or gets interrupted, the segment that actually mattered most to the buyer is the one most likely to get cut or rushed, precisely because it was scheduled last by habit rather than by relevance. Requiring each segment to name the specific discovery finding it answers, rather than a generic value label, forces the same discipline the proposal-tailoring prompt applies to written material onto a live, real-time format — a demo segment justified only as 'shows value' could be shown to any prospect regardless of what discovery revealed, which is the live-call equivalent of a proposal that never actually engages with what the buyer said. Explicitly handling multiple attendees with different priorities addresses a structural reality of enterprise demos that a single-audience script ignores: a business buyer and a technical evaluator in the same room frequently want to see different things in the same five minutes, and a demo agenda that doesn't plan for that divergence either bores one attendee while satisfying the other, or worse, never actually reaches the specific proof point the skeptical technical evaluator needed to see, leaving their concern unaddressed and unspoken until after the call. The time-discipline instruction — cut something and say what, rather than silently overrunning — matters because an agenda that's allowed to overrun in practice always overruns on the earlier, easier segments and squeezes whatever was scheduled last, so forcing an explicit pre-planned cut ensures that if something has to go, it's a deliberate, lowest-priority choice made in advance rather than an accidental one made under live time pressure.
Verified against
ChatGPT GPT-5.1 · 2026-08-01
Claude Sonnet 4.5 · 2026-08-02
Changelog
- 2026-08-02 — Initial publish, verified against ChatGPT (GPT-5.1) and Claude (Sonnet 4.5).
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
