Three rules
- One persona, one path. Pick the single journey that ends in your "magic moment" and cut everything else.
- Show, then tell. Each claim should land on screen within seconds of you saying it.
- Rehearse with a timer. Three minutes means three minutes. Most first drafts run six.
The script, second by second
0:00–0:20 Hook: the problem as a moment
Make them picture one person at one painful moment, with one number.
- Say
- It's 6 pm. [Persona] has just finished [situation] and now has to [painful task] — [number] minutes, every day.
- Show
- Nothing yet, or the "before" screen: the messy doc, the empty CRM, the spreadsheet.
- Example
- "It's 6 pm. Maya, an account executive, just finished her sixth sales call today. Now she has to type all six into HubSpot — 40 minutes she doesn't have. So she skips it, and her manager forecasts on stale data."
0:20–0:40 Who and why now
Size the pain and explain why this is possible or urgent now, not five years ago.
- Say
- [Number] people do this. It costs them [money/time]. Until [shift], it couldn't be automated reliably — now it can.
- Show
- Still the "before" screen, or one simple slide with two numbers.
- Example
- "Every B2B sales team has this problem — our design partners measured about 6 hours a week of CRM admin per rep. Transcription is solved — but turning a conversation into trustworthy, structured CRM fields only became reliable and cheap this year."
0:40–2:10 Live demo: one path to the magic moment
Before → the AI doing visible work → the user in control → the result landing where they already work.
- Say
- Narrate what the user sees and decides, not what the system does internally. Name the magic moment out loud when it happens.
- Show
- Realistic input (not "test 123"). The AI working with visible progress. The user reviewing and approving. The result in the tool they already use.
- Example
- "Maya ends the call. Thirty seconds later, CallNote has a proposed update: next step, new close date, two objections — each with the exact quote from the call. She fixes one field, approves, and… here it is in HubSpot. That's the moment: the CRM is updated before she's even opened it."
2:10–2:35 Proof
Show it works outside your laptop: usage, retention, a quote, or an eval number.
- Say
- One or two hard numbers and who they come from.
- Show
- A single proof slide or an analytics screen.
- Example
- "Three design-partner teams, 31 reps, 4 weeks: 68% of calls updated within an hour, 82% of suggested fields approved without edits. Two teams asked to pay before we'd sent a price."
2:35–2:50 Business
Who pays, how much, and why the margin holds as usage grows.
- Say
- Buyer, price, cost to serve, expansion path.
- Show
- Pricing line or a one-line unit economics slide.
- Example
- "Sales managers buy it: $39 per rep per month. AI costs us about $4 per rep per month at current usage. We land with one team and expand across the sales org."
2:50–3:00 Ask and close
State what you want from this meeting and repeat the one-liner.
- Say
- We're raising [amount] to [milestone]. [One-sentence product line again.]
- Show
- Final slide: logo, one-liner, contact.
- Example
- "We're raising $1.5M to get to 50 paying teams in 12 months. CallNote: your CRM, updated before you open it."
Your script
| Time | Segment | What you say | What they see |
|---|---|---|---|
| 0:00–0:20 | Hook | ||
| 0:20–0:40 | Who and why now | ||
| 0:40–2:10 | Live demo | ||
| 2:10–2:35 | Proof | ||
| 2:35–2:50 | Business | ||
| 2:50–3:00 | Ask and close |
Prep checklist for a live AI demo
Questions investors ask about AI products — prepare one-sentence answers
- "What happens when OpenAI (or Google, or Microsoft) ships this?" — your answer is workflow, data, distribution or trust, not the model.
- "What does each task cost you, and what happens at 10× usage?" — cost per task, margin, and your plan to keep it.
- "How do you know the output is good?" — your eval set, acceptance rate and how a bad answer is caught.
- "Whose data is it, and can you use it?" — permissions, privacy posture, what improves over time.
- "Why you?" — the unfair insight or access your team has.
Common mistakes
- Touring every feature instead of finishing one path.
- Explaining the architecture, the model or the prompt before showing the result.
- Starting on a login screen, an empty dashboard or settings.
- Apologizing for the UI or saying "this part is still rough".
- Ending on a feature instead of the ask.
EngiBoard
Vigilo
AI Dent