ChatGPT Prompts for Demo Prep: Run Demos That Close Deals
ChatGPT prompts for sales demo preparation. Personalized demo scripts, discovery-to-demo bridges, and objection handling for software and services demos.
The Prompt
Act as a demo coach who has trained SaaS sales teams to close at 35%+ from demo.
Build a demo preparation plan for:
Product: {product name and core capability}
Prospect: {company, decision-maker, industry, company size}
Discovery findings: {what you learned in discovery — their pain points, priorities, success metrics}
Demo duration: {30 / 45 / 60 minutes}
Decision-maker profile: {technical / business / executive — what they care about}
Competitors being considered: {what else is on their shortlist}
Output:
1. Demo opening (how to open: recap discovery insights, confirm agenda, establish evaluation criteria)
2. Demo narrative arc (the story structure — problem → current state pain → your solution → future state)
3. Personalized demo flow (in order of prospect's stated priorities — not your standard product tour):
- Feature A: why this matters to THIS prospect specifically
- Feature B: why this matters to THIS prospect specifically
- Feature C: (if applicable)
4. "So what" bridges (transition lines that connect each feature to the prospect's stated business outcome)
5. Handling live objections (2 scenarios: "We can do that ourselves" and "Your competitor does this too")
6. Mutual action plan (end of demo — 3-step next steps with owners and dates)
Constraints:
- Demo flow must be ordered by prospect priority, not product default
- Every feature shown must connect to a pain point from discovery — don't demo features they didn't ask about
- "So what" bridges must reference the prospect's specific language from discovery
- Mutual action plan must include something they agree to do, not just things you agree to do
Variables to fill in
-
{product}Product name and what it does -
{prospect details}Company, decision-maker name and role, industry, size -
{discovery findings}What you learned in discovery — critical input for personalization -
{decision-maker profile}Technical, business, or executive — affects demo depth and focus -
{competitors being considered}What else is on their shortlist
How to use this prompt
- Fill in the discovery findings field immediately after your discovery call — don't wait
- Use the narrative arc as your demo script structure — tell a story, not a feature tour
- Practice the 'so what' bridges until they feel natural — they're the hardest part to improvise
- Present the mutual action plan as a slide or document — not just a verbal agreement
Order by their priorities, not yours
The standard product demo — Feature 1, Feature 2, Feature 3 in onboarding order — is designed for your team, not for prospects. A prospect who told you in discovery that their biggest pain is reporting should see the reporting module first, not fifth. This prompt reorders the demo flow around the discovery findings — which is the single biggest driver of demo win rate improvement.
The ‘so what’ bridge is the most important sentence in your demo
Showing a feature without connecting it to the prospect’s stated problem is a feature tour, not a demo. ‘So what that means for your team specifically, based on what you told me earlier…’ is the sentence that turns a product demonstration into a business case. The prompt generates these bridges for each feature shown.
Mutual action plans create accountability — and filter out tire-kickers
A prospect who agrees to a specific next step at the end of a demo is more likely to show up for that next step than one who says ‘sounds great, I’ll get back to you.’ Asking them to do something (loop in their CTO, send you a data file to analyze, share the demo recording with their team) separates genuinely engaged buyers from polite ones.
Related free tools
- Free AI Prompt Generator — build structured prompts instantly
- AI Token Counter — estimate API costs
- AI ROI Calculator — calculate the business value of AI adoption