Verified against ChatGPT · 2026-08-11
Build a product demo script ordered by the prospect's stated priorities, not your feature list
Structures a sales demo around the specific outcomes a prospect said they care about, mapping each feature shown back to one of their stated priorities, and cutting anything that doesn't connect to something they actually mentioned.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Help me structure a product demo. I don't want a walkthrough of everything the product does in the order features exist in the UI — I want the demo ordered by what THIS prospect actually said they care about, with everything else cut or deprioritized. PRODUCT FEATURES AVAILABLE TO SHOW Automated invoice matching, custom approval workflows, real-time spend dashboards, multi-currency support, Slack notifications. WHAT THE PROSPECT SAID THEY CARE ABOUT (FROM DISCOVERY) "Our biggest headache is invoices sitting for approval for two weeks with no visibility into where they're stuck." WHO'S IN THE DEMO The AP manager who did discovery, plus her director who's seeing this for the first time. DEMO LENGTH 25 minutes. For each stated priority, map it to the specific feature that most directly addresses it, and order the demo so the highest-stated priority is shown first, not last — a demo that saves the most relevant thing for the end risks running out of time before it gets there. For each feature you include, write one sentence connecting it explicitly back to the prospect's own words from discovery, so the transition sounds like "you mentioned X, here's how that works" rather than a feature tour that happens to include something relevant. Explicitly list which available features you are cutting from this demo and why — anything that doesn't map to a stated priority should be left out entirely rather than squeezed in for completeness, even if it's a feature I'm personally proud of. If multiple attendees are in the room with different priorities, note where the demo should pause and briefly check whether it's still landing for both, rather than optimizing only for whichever attendee spoke most during discovery. Do not claim the product does something not in the feature list I gave you. Output format: an ordered list of demo segments (Segment, Feature Shown, Connects To Which Stated Priority, Talking Point Sentence), followed by a "Cut from this demo" list with a one-line reason for each cut.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The core mechanism here is inverting the model's default demo structure: asked for a generic "demo script," GPT-5.1 tends to organize output around the product's own feature architecture — the order features exist in a UI or a marketing one-pager — because that's the most available organizing structure in the absence of other instructions, and that order has no necessary relationship to what any specific prospect cares about. Forcing every included feature to map explicitly back to the prospect's own discovery language is what prevents the demo from drifting into a generic capability tour; a feature shown without that connecting sentence gets presented as inherently impressive, while the same feature introduced as a direct answer to something the prospect said unprompted carries far more weight because it demonstrates the rep was listening, not reciting. The explicit "cut from this demo" list matters more than it looks — it's a deliberate check against the instinct to include a feature the rep is personally proud of or that showcases technical depth, even when it wasn't asked for; naming and justifying every cut forces the discipline that a demo's value comes from relevance, not comprehensiveness, and most demos fail by trying to be comprehensive. Ordering by the prospect's highest-stated priority first, rather than saving the strongest material for a big finish, directly addresses the real risk of a demo running over time and never reaching the part that actually mattered — a risk a model won't account for unless explicitly told to front-load rather than build to a climax.
What you get back
Segment 1: Automated invoice matching. Connects to: "invoices sitting for two weeks with no visibility." Talking point: "You mentioned invoices getting stuck for two weeks with no clear owner — here's what happens the moment one lands in the system." Cut from this demo: multi-currency support — nothing in discovery indicated cross-border operations, so this would be a tangent rather than a relevant capability.
Verified against
ChatGPT GPT-5.1 · 2026-08-11
Changelog
- 2026-08-11 — Initial publish, verified against ChatGPT GPT-5.1.
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
