How to Make a Product Demo Video in 15 Minutes
The product demo video you keep postponing does not require an editor, a subscription to three tools, or an afternoon. The recipe below reliably produces a demo you'd put on a landing page, in a launch tweet, or in a sales email — in about fifteen minutes, most of which is the recording itself. It's the process indie founders and PMs actually use, minus the parts that don't survive contact with a deadline.
Minute 0–3: script the beats, not the words
Don't write sentences — you'll sound like you're reading them. Write five to seven beats: the state you start in, each action you'll show, the payoff. Example for a feature demo:
- Dashboard, the problem visible
- Open the new feature
- Configure it (the impressive part — slow down here)
- Show the result
- One-line recap
Prepare the tab: demo data that looks real, notifications off, and nothing sensitive on screen (close the Slack window). A 90–120 second video is the sweet spot; if your beats add up to five minutes, cut beats, not pace.
Minute 3–8: record once, tolerantly
Open DemoReel in your browser (nothing to install), enable your mic — camera too if you want a human in the corner — and hit Record. Then perform the beats and keep going when you stumble: pauses, re-dos and "wait, let me do that again" get cut in the edit for free. Restarting the take for every flub is the classic time sink; one tolerant take beats five perfect attempts.
Narration tip: describe outcomes, not clicks. "Now billing reconciles itself every night" beats "now I click the settings icon."
Minute 8–14: the polish pass
This is where a raw capture becomes a demo, and each step is a minute or two:
- Trim and cut. Chop the start fumble and the end dangle, then remove the mid-take stumbles — in DemoReel, park the playhead and "Remove section", then drag the edges to fit.
- Zooms. Run auto-zoom for a first pass, then re-aim or add the one or two zooms that matter most. This is the single edit that most changes how professional the result feels.
- Scene. Put a background behind the recording, a little padding, rounded corners, a shadow. Instantly reads as "made on purpose."
- Captions. One click generates them on-device; fix any name it misheard in the transcript panel. Most feed viewers watch muted — captions are how your narration survives.
- Music, quietly. A track at 30–40% volume with fade in/out closes the "polished" gap. Skip it for sales emails; use it for launch posts.
Minute 14–15: export for the destination
| Destination | Canvas | Notes |
|---|---|---|
| Landing page, YouTube, X | 16:9, 1080p | The default; 4K if the UI is dense |
| Reels / TikTok / Shorts | 9:16 | Same project, switch the canvas — zooms matter double here |
| In-app or docs embed | Fit (recording's own shape) | No background padding |
The export is a standard MP4 encoded on your machine — nothing was uploaded at any point, which also means this whole workflow is safe for unreleased features.
The three mistakes that sink demos
- Showing everything. A demo is an argument, not a tour. One feature, one payoff.
- Full-screen from arm's length. Without zooms, the viewer watches a postage stamp of your UI and reads none of it.
- Restart-itis. The edit exists so the take doesn't have to be perfect. Record once, cut twice.