Product Demo Script & Talk Track
Structures a product demo with discovery recap, feature walkthrough tied to pain points, and a closing framework.
You are a solutions engineer who has delivered 1,000+ product demos in the [industry] sector. Create a demo script for [product name] being presented to [buyer persona] at [company type]. The target audience is the prospect's decision-making team, and the goal is to advance to a proposal stage. Demo length: 30 minutes. Format the output as structured sections with timing: (1) Recap & Agenda (3 min): summarise discovery findings, set expectations, ask 'Is there anything else you'd like to see today?', (2) 'Day in the Life' opening (2 min): paint a picture of their current painful workflow without your product, (3) Core Demo Flow (20 min): 3-4 features to demonstrate, each following the pattern: 'You told me [pain point] → Here's how [product] solves that → [live demo steps] → The result is [outcome/metric]'. For each feature, include: what to click/show, what to say, a transition sentence, and a trial-close question such as 'How does this compare to your current process?', (4) Summary & Next Steps (5 min): recap the 3 key values, address concerns, propose next steps with specific dates. You must ensure each feature ties back to a stated pain point. Avoid demoing features the prospect didn't ask about. Include: 3 landmine questions competitors might plant and how to handle them, a backup plan if the live demo breaks (screenshots/video), and post-demo follow-up email template.
Why this prompt works
The 'each feature ties back to a stated pain point' rule is what makes this output a demo, not a product tour. Most demos drift into showing every feature the rep is excited about, which is also why most demos lose deals. The pain-to-feature-to-result pattern enforces the buyer-centric structure throughout, and the trial-close question after each feature ('How does this compare to your current process?') keeps the buyer engaged rather than letting them go silent. The backup plan if the live demo breaks is the practical detail that distinguishes this prompt from a generic outline; demos do break, and having a screenshots-or-video fallback ready avoids the worst-case scenario.
When to reach for it
- You're a solutions engineer or AE preparing a demo and want a structured script that ties back to discovery.
- You're a new hire learning how to present and need a worked example showing the right pacing and structure.
- You're rolling out a methodology change ('demos must be discovery-anchored, not feature-led') and need a reference script for the team.
How to customise it
The discovery findings are the most important input. The demo script reflects whatever pain points you tell the model the prospect mentioned; if you say 'they care about reporting', the script ties features to reporting. Be specific: 'they spend 3 hours a week manually consolidating data from 4 tools' produces sharper output than 'they care about reporting'. The 'landmine questions competitors might plant' section needs to be customised to your real competitors; the generic version is a starting point only. For technical demos with deep configuration, ask the model to add 'when the prospect asks about integration / security / SSO, here's the talk track' subsections.
What good output looks like
A 30-minute script with timed sections (recap and agenda, day-in-the-life opening, core demo flow with 3 to 4 features, summary and next steps). Each feature uses the pain-feature-result pattern with a trial-close question. Three landmine-question handlers, a backup plan for technical failure, and a post-demo follow-up email template. Total length 2,000 to 3,500 words.
Watch out for
The 'live demo' assumption sometimes mismatches reality; if your demo is actually a recorded walkthrough or a sandbox prospects access themselves, ask the model to adjust the format. The trial-close questions can come across as canned if delivered too frequently; pace them to two or three across the demo, not after every feature. The post-demo follow-up email template is generic on first pass; reference specific things that came up in the actual call before sending.
Build a prompt like this for your task
Use the free guided prompt builder on the homepage: pick what you need, answer three quick questions, and get a high-scoring prompt of your own.
Open the prompt builder →More sales prompts
Cold Outreach Email Sequence
Creates a 5-email cold outreach sequence with personalisation, value hooks, and strategic follow-up timing.
Discovery Call Question Framework
Provides a structured discovery call script with open-ended questions, qualifying criteria, and next-step close.
Sales Objection Handling Playbook
Builds a playbook with word-for-word responses to the 10 most common sales objections using proven frameworks.