Product demo video script: what to show in 30, 60 and 120 seconds
A launch video announces a product; a demo video shows how it works. That difference changes the script, because a demo is judged on whether the viewer can picture themselves using the product afterwards, and that needs a real workflow rather than a montage.
Step 1: Choose one person and one job
Write down who is watching and the single job they hire your product for, like "a freelance designer sending this month's invoices". Every screen in the demo should serve that job, and anything that doesn't belongs in a different video.
Step 2: List the clicks, then cut to three moments
Do the job in your product and write down every step. Then circle the three moments where the value is obvious: usually the starting point, the moment the product does the hard part, and the result. Those three moments are your demo, and the steps between them can be cut or skipped with a transition.
Step 3: Put the most important part first
Wistia's data shows viewers of longer educational videos typically drop off around the halfway mark, so it recommends putting the most important or compelling information in the first half (Wistia). In a demo, that means showing the result early, then showing how you got there.
Templates
| Length | Use | Structure |
|---|---|---|
| 30 seconds | Landing page, social, launch post | Result (0 to 5s), three moments (5 to 25s), name and address (25 to 30s) |
| 60 seconds | Landing page with a play button, sales emails | Who it's for and the result (0 to 10s), three moments with a line each (10 to 45s), what makes it different (45 to 52s), call to action (52 to 60s) |
| Two minutes | Help centre, onboarding, hackathon and accelerator applications | The problem (0 to 15s), the full workflow at real speed with narration (15 to 100s), one advanced feature (100 to 110s), where to start (110 to 120s) |
Step 4: Write the voiceover in the second person
"You pick a client, and Ledgerly fills in last month's hours" is easier to follow than "The user selects a client entity". Describe what the viewer would do, keep sentences short, and never narrate what's already obvious on screen. If the video will mostly play muted, move the key phrases into on-screen text instead.
Step 5: Cut the tour
The most common demo mistake is the feature tour: every menu, every setting, in order. It feels thorough to the team and loses everyone else. In Wyzowl's 2026 survey, 63% of people said they'd most like to learn about a product from a short video (Wyzowl), and short means choosing.
Making it
The two-minute walkthrough is best recorded from the real product; here's how to record it cleanly, and for a hackathon or accelerator, recording is the expected format (Devpost). For the 30-second overview, Teasr can make a motion version from your website in about 10 minutes, from €19.50, which many teams put above the recorded walkthrough on the same page. See also how to make a SaaS demo video and the product demo video page.