A product demo video answers one question: "how does it work, and will it fit what I need?" It is for people who already understand the problem and are deciding whether to trust your product. If they do not understand the problem yet, make an explainer first.
1. Pick one task and one viewer
A demo that shows everything shows nothing. Choose the single task a prospect most wants to see done, such as importing data or sending a first report, and the one person who will watch it. Write both in a sentence before you record anything.
2. Script it in five parts
- The situation the viewer is in
- The task they want to do
- The steps, shown on screen
- The result
- The next step
Keep narration to what the screen cannot say by itself.
3. Record a clean run
- Use a demo account with believable sample data, never real customer data.
- Close notifications and unrelated tabs, and fix the window size.
- Rehearse once, then record slowly. Mistakes are easier to cut than to hide.
4. Polish it in the edit
Raw recordings show cursor wobble, loading screens and small text. Zoom into the part that matters, add short callouts and captions, cut the waiting time and keep the pace steady. If the real interface is cluttered or still changing, UI animation can replace the recording and keep the screens sharp and on brand.
5. Match the length to the job
A feature clip can be under a minute. A task walkthrough usually runs one to three minutes. A longer product tour works better with chapters. These are starting points, so test what your viewers actually finish.
Common mistakes
- Showing every feature instead of one task
- Narrating what is obvious on screen
- Leaving in loading time and typos
- No captions, so it fails with the sound off
- No next step at the end
I wrote a longer version with a table of demo types and FAQs here: https://vaghelabhavesh.com/blog/saas-product-demo-video-how-to-make-one.html
I'm Bhavesh, a freelance motion designer and video editor. My portfolio is at https://vaghelabhavesh.com
Top comments (3)
Picking one task and one viewer before you open the recorder is the line that saves most demo videos. A clip that shows the whole product usually shows none of it well, because the viewer never gets a finished job. Writing the five parts of the script first also keeps narration from explaining what the screen already makes obvious. I'd add one more gate before the polish pass: play the cut for someone who knows the problem but not your UI, and ask only whether they could repeat the task afterward. If they can't, zoom and captions will not fix it. A ninety second homepage demo and a twenty second feature clip should not share the same outline.
The "could they repeat the task afterward" test is a better gate than anything I had in the checklist, thanks. I'll add it before the polish pass. It also settles the outline question: if the tester can't repeat the task, the problem is the script, not the edit.
Glad that gate landed. Putting it before polish also saves you from polishing a script that still fails the task. When you run that stranger test, do you give them one watch only, or do you let them pause and rewatch once before you ask whether they could repeat it?