AI Prompts for Sales Demo Storylines

A demo is an argument, not a tour. The storyline should start from the prospect's current state as they described it, show the smallest set of moments that prove the outcome they care about, and end with a proposed next step tied to their process. Feature-by-feature demos lose the room; demos that mirror discovery win it, because the prospect recognizes their own situation on screen.

This page keeps the original storyline prompt and adds two around it: structuring each moment as tell–show–tell so the point lands before and after the click, and preparing for the interruptions — the feature question, the 'can it do X', the skeptic — that pull demos off the storyline.

Before you use these

Have these ready to replace the highlighted [variables]:

• Discovery evidence: the problem in their words, the impact, the stakeholders
• What each attendee needs to see to say yes (and what would make them say no)
• The three capabilities that map to their outcome
• Time available and who is presenting

The prompts

• 1. Build the demo narrative
• 2. Structure each moment as tell–show–tell
• 3. Prepare for demo interruptions

1. Build the demo narrative

Build a demo narrative for [product] tailored to [prospect company] in [industry]. Structure: their current state (based on: [what I know]), cost of inaction with a rough calculation, 3 'wow moments' to show in order of impact, objections likely to come up at each moment with responses, and a closing slide that proposes concrete next steps with dates.

2. Structure each moment as tell–show–tell

Act as a demo coach structuring a demo for [prospect] using tell–show–tell.

Storyline: [the moments in order]
Discovery quotes: [what they said about the problem, impact, and what good looks like]
Attendees: [roles and what each cares about]
Time: [minutes]

For each moment:
1. Tell (before): one or two sentences that set up the moment in their words — the problem as they described it and what they said they wanted. Quote where possible.
2. Show: the shortest click path that proves the point — list the steps; cut anything that does not serve the outcome. Note the data or example to have loaded (their industry, their terms, their numbers).
3. Tell (after): the landing line — what just happened in terms of their outcome, and the number or consequence attached. Then the check question ('is that how it would work for you?').
4. Who it is for: the attendee whose concern this moment addresses, and how to direct it to them.
5. Transition to the next moment.

Then: total time by moment; the moment to cut if time runs short; the opening (two minutes on their situation, no company slide) and the close (proposed next step tied to their process, with dates). Flag any moment that is a feature tour rather than an outcome.

3. Prepare for demo interruptions

You are preparing an account executive for the interruptions that derail demos with [prospect].

Storyline: [moments]
Attendees: [roles, likely questions, the skeptic if known]
Known gaps: [things we cannot do or do less well]

Prepare the playbook:
1. Feature question off the storyline: the line that answers briefly and returns to the story, and the rule for when to detour instead (it maps to a stated need) versus park it.
2. 'Can it do X?': the three responses — yes (show it briefly or promise a follow-up demo), partially (honest description and the workaround), no (honest, and what we do instead) — with wording for each.
3. Known gaps: for each, the honest answer, the reframe to what they said mattered, and whether to raise it proactively.
4. The skeptic: how to engage them directly, the question to ask them, and the moment in the demo designed for them.
5. Parking lot: the mechanism to capture questions visibly and the promise made about them.
6. Recovery lines: when the demo breaks, when the room goes quiet, when someone leaves.
7. The rule for stopping the demo: if discovery turns out to be wrong in the room, the line that pauses and asks.

Write real sentences. Do not prepare evasions — a demo that dodges a gap loses more than one that names it.

Related prompts

• Discovery Call Analysis
• Sales Proposal Development
• Competitor Battlecards
• Objection Handling and Response Libraries
• Sales Business Cases and ROI
• Mutual Action Plans
• Board-ready strategy deck outline — Consulting
• Presentation Building prompts

Logical next step

After this, most sales teams move on to Discovery Call Analysis.

All Sales prompts · Search the full library