Free guide
Fundraising kit, guide 3 of 6Your product demo is one flow in three minutes.
Nobody funds a feature tour. Show one real user doing one real job in your product, narrate why, and stop before the third minute. Six beats, recorded or live.
- Under three minutes
- Real product, real data
- No intro, no music
- One user, one job
At a glance
Six beats, one job done
In order: who it is for, where they start, what they do, the moment it pays off, the proof it is real, what happens next. Tap a beat to jump to it.
Beat by beat
What each beat must do
The question the viewer has at that moment, what to show, what to skip, and a test to check it passes.
The first ten seconds. One sentence: who the user is, the job they need done, and what your product gives them. Then the product is on screen. No logo animation, no company history.
Show
- One sentence: for whom, which job, what result
- Your name and the product's name, once
- The product on screen by second ten
Skip
- A title card, a logo reveal, music
- The founding story
- Describing the industry
Pass test: By second ten a stranger knows who this is for and the product is visible.
The real situation just before your product. The trigger, the mess they are in today, and the one thing they want. Use a real account with real data, never placeholder text.
Show
- A real user scenario with a name and a task
- The state before: the spreadsheet, the inbox, the manual step
- Real data, with anything sensitive replaced
Skip
- Login, sign-up and onboarding screens
- Empty states and test data
- Explaining every menu
Pass test: The viewer wants the problem solved before you touch a button.
The core action, start to finish, at the speed a real user works. One path, no detours. Narrate why the user does each step, not what the button is called.
Show
- One path from trigger to result
- Narration on the why: the decision at each step
- The two or three details that show craft
- Cursor movements a viewer can follow
Skip
- Every feature you built
- Settings, admin and edge cases
- Silence, or reading the interface aloud
Pass test: A viewer could repeat the flow from memory.
The result. The report generated, the deal matched, the hours saved, on screen and quantified. Slow down here. This is the moment the viewer remembers and the reason the flow existed.
Show
- The output, on screen, in full
- The number: how much faster, cheaper or better than the state before
- A beat of silence for the viewer to see it
Skip
- Cutting away before the result appears
- Explaining the result instead of showing it
- A second flow before the first has landed
Pass test: Pause the video here and the screen alone makes the case.
Evidence that this is a working product with real users, not a prototype. A live URL, usage numbers, a customer name, all dated.
Show
- The live URL or the app store listing, on screen
- Usage in one line: customers, weekly actives or revenue, with the date
- What is built versus what is coming, said plainly
Skip
- Mockups presented as product
- Numbers without dates
- Roadmap slides
Pass test: The viewer knows what exists today and what does not.
Ten seconds. What ships next, and where the viewer can try it themselves. End on the product, not on a slide.
Show
- The next milestone, dated
- Where to try it: the URL, an invite, a sandbox
- Your name and contact, spoken once
Skip
- A thank-you slide
- A recap of everything you showed
- Music or an outro animation
Pass test: The viewer can open the product the moment the video ends.
Example
Try it at app.example.com with the code DEMO. The mobile app ships next month. I am Sara, [email protected].
Make it yours
Recorded, live, or on stage
The default is a screen recording with your voice, the format most applications ask for. Three formats change the rules, and a few beats are optional.
Recorded video
When: An application or an investor asks for a link.
Change: Screen recording with your voice, one take if you can, under three minutes. Y Combinator caps it at three; aim for two. Unlisted link, no password.
Live in the room
When: You demo in a meeting or on a call.
Change: A staged account loaded with real-looking data, one path rehearsed ten times, and a recording as backup. Never build or fix anything live.
On the demo day stage
When: A pitch competition or a demo day gives you two minutes.
Change: Bigger type, slower cursor, the magic moment first. Cut context to one sentence and skip proof: the deck carries it.
Optional beats
- A second flow. One flow undersells the product and you still land under three minutes.
- Captions. The video will be watched on mute, as most application videos are.
- Before and after. The old way is so painful that seeing it makes the magic moment land harder.
- A sandbox login. Reviewers can try it themselves and the product survives a stranger's clicks.
- Mobile view. The product lives on a phone, or the buyer will judge it there.
Build it with AI
Hand this framework to your AI
Writing the demo script with ChatGPT, Claude or any AI? Point it at this guide so it scripts one flow instead of a feature tour. The whole method is published as two files, built from the same data as this page.
Or paste this prompt into your AI and describe your product and its user:
Act as a startup pitch coach and follow the MrAdib product demo framework at https://mradib.com/product-demo/llms.txt. Ask me who the user is, the one job the product does for them, and what I can show today, then script my demo beat by beat: what is on screen, what I say, and the seconds it takes. One flow, under three minutes, real data, no feature tour, no invented numbers.
Sources
Where this comes from
The beats distil what the programmes that watch the most demo videos ask for. Read them.
Questions founders ask
How long should a product demo video be?
Under three minutes, and two is better. Y Combinator asks for up to three. Reviewers watch dozens in a sitting; the shorter video with one clear flow beats the complete tour every time.
Do I need a voiceover?
Yes. The screen shows what happens; your voice explains why it matters. Record it in one take in a quiet room. A phone headset microphone is enough.
What if the product is not ready?
Show what works, and say what does not. A clickable prototype is fine if you call it one. Never present a mockup as a product; reviewers can tell, and it costs you trust.
Video or live demo?
Both, for different rooms. Applications and cold intros get the video. Meetings get the live demo, with the video as backup for when the wifi fails.
The fundraising kit
Six guides, one set of facts
The whole kit, in the order you build it. Every piece draws on the same facts, so none of them contradicts another.
Show the product. Say why.
Three minutes of one real user doing one real job beats any slide. Questions about your demo? Say hello.