Build a demo storyline from your discovery notes
Converts raw discovery notes or a transcript into a three-act demo storyline that opens on the prospect's problem in their own words, sequences scenes by deal importance, tells you what NOT to show, and scripts the close. It's the difference between a feature tour and a demo the champion replays internally.
You are a demo architect who has rebuilt demo programs at multiple B2B software companies. Your rule: a demo is a story about the prospect's future, told in their words, with the product as supporting evidence. The moment a demo becomes a feature tour — 'and over here you can also...' — you've lost the room. You structure demos so the biggest moment lands in the first ten minutes, because attendance and attention decay from there. Turn my discovery notes into a demo storyline. Output format: 1. THE COLD OPEN: The first two minutes, scripted. Restate their problem in their exact words from discovery, state what we'll prove today, and confirm nothing has changed. No company slide, no agenda slide, no 'a little about us'. 2. THREE ACTS, each: the pain (their words) → the scene to show (which workflow, with what data on screen) → the payoff line connecting it to the impact they quantified → a check-in question. Order acts by deal-winning importance, not by product menu order. 3. FEATURES TO DELIBERATELY SKIP: what I must not show, and the one-line deferral if they ask. 4. THE LANDING: last five minutes — recap the three payoffs, then the specific next-step ask. Rules: every act must trace to something said in discovery. If my notes support fewer than three acts, tell me what discovery gap to close first instead of inventing pain. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. Paste your discovery notes or call transcript — messy is fine. 2. Who will be in the demo, and were any of them absent from discovery? 3. What does your product actually do, in a few sentences? 4. What next step do you want to walk out with? Once you have my answers, build the storyline. If the notes are thin on quantified impact, ask me one follow-up before writing act structure.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Paste your rawest material for question 1 — a Gong or Fireflies transcript beats cleaned-up notes because it preserves their exact words.
- 3
Flag any demo attendee who missed discovery; the model will adjust the cold open to re-anchor them.
- 4
Rehearse the cold open verbatim once — it's the two minutes that set the whole call.
- 5
If an act feels feature-heavy, reply 'act 2 reads like a tour, tighten it to the payoff' and regenerate.
Best practices
The skip list is as valuable as the acts — showing less, better, is the highest-leverage demo change most reps can make.
Use their vocabulary everywhere: if they say 'handoffs', never say 'workflow orchestration'.
Put your strongest act first, not last; decision-makers often drop off after 20 minutes.
Pair with the demo story data prompt in this category so the data on screen matches the storyline.
Example: what this looks like in practice
An SE at a field-service software company gets a transcript from the AE's discovery call with an HVAC firm: the ops director said scheduling conflicts cost them 'probably six jobs a week' and dispatchers 'live in three tabs'. The storyline opens with exactly those phrases, act one shows conflict detection with a six-job week on screen, act two shows the single-pane dispatch view, act three shows the owner's revenue dashboard — because the owner, absent from discovery, will attend. The skip list says: do not show the inventory module, defer with 'that's a phase-two conversation.' The demo runs 35 minutes instead of the usual 55, and the ops director asks to bring in their lead dispatcher — the exact next step the AE wanted.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
As a story, not a tour: open on the prospect's problem in their exact words, show three scenes ordered by importance to the deal, connect each to the impact they quantified in discovery, and land on a specific next step. Skip the company slide entirely. This prompt builds that structure directly from your discovery notes so every minute traces to something they said.
More discovery calls & demos prompts
Build a discovery question bank tailored to one persona
Generates a 15-question discovery bank built around one persona's actual responsibilities and failure modes, organized by call stage, with listening notes on what strong and weak answers sound like. Beats generic question lists because the interview forces your product, competitor, and deal-death context into every question.
Write a post-discovery summary email that mirrors their words
Produces a sub-180-word summary email built on the prospect's verbatim phrases, with impact-paired bullets, an invitation to correct you, and next steps with your commitments listed first. Mirroring their language proves you listened in a way no template can, and the email becomes the artifact your champion forwards internally.
Build a multi-threading plan for a stalled single-threaded deal
Diagnoses why your single-threaded deal stalled, maps the three or four other roles you need relationships with, and writes both paths in: language that gets your contact to introduce you, and direct outreach that references the live evaluation without burning the relationship. Turns 'my contact went dark' from a dead deal into a workable plan.