How to Make a Product Demo Video (Script Template + Examples)

Most teams know how to make a product demo video in theory: open the app, hit record, click around. The result is usually four minutes of wandering cursor that nobody finishes. A good demo is closer to a short film than a screen recording. It has one viewer in mind, one job to do, and a script that decides what to show before anyone touches the record button.

This guide walks through the process we recommend for SaaS teams: pick the use case, write the script, plan the shots, produce it (by recording, motion design or both), and ship versions for each channel. There is a copy-paste demo script template in the middle, plus length guidance for landing pages, sales follow-ups and app stores.

What is a product demo video?

A product demo video shows your software doing the job a customer cares about. It is different from an explainer, which sells the idea and the problem, and from a tutorial, which teaches someone who has already signed up. A demo sits in between: it proves the product works and makes the outcome feel close.

How do you make a product demo video, step by step?

1. Pick one use case and one viewer. A landing page visitor, a prospect after a sales call and an app store browser need different videos.
2. Choose the single workflow to show. The one that produces the clearest before-and-after for that viewer.
3. Write the script before you record. Words first, then the screens that prove each line.
4. Prepare a clean demo account. Realistic data, no test names, no notification badges, browser chrome hidden.
5. Capture the screens. Either a screen recording or high-resolution screenshots of each step.
6. Produce the video. Edit the recording, or animate the screenshots with motion design, then add captions and audio.
7. Export versions per channel. 16:9 for the site and YouTube, 1:1 or 9:16 for social and mobile.
8. Review it on mute, on a phone. If the story does not land without sound on a small screen, it is not finished.

1. Start from the viewer, not the feature list

Write one sentence before anything else: who is watching, and what should they believe at the end? For example: a head of support at a 50-person SaaS company should believe they can answer repetitive tickets without hiring. That sentence decides which workflow you show and which features you leave out. If a feature does not serve that belief, it belongs in a different video.

2. Pick the workflow with the clearest payoff

Look for the moment in your product where the user gets something they could not easily get before: a report that builds itself, a bug that gets triaged automatically, a page that publishes in one click. Work backwards from that moment. The demo is the shortest path from a recognisable problem to that payoff.

3. Script it like a short story

A demo script has five parts: a hook, the problem, the walkthrough, the payoff and a call to action. Keep sentences short enough to read as on-screen captions, because many people will watch without sound. Every line of the script should map to a specific screen. If you cannot point to the screen that proves a line, cut the line.

4. Prepare a demo environment that looks real

Fake data is where most demos lose credibility. Use plausible company names, real-looking numbers and filled states rather than empty ones. Clear notifications, hide internal admin menus and set the browser to a consistent window size. If you will zoom into details later, capture at a higher resolution than the final video so text stays sharp.

5. Produce, then cut harder than feels comfortable

Whatever method you use, the first cut will be too long. Remove loading states, typing that goes on for more than a second or two, and any step the viewer can infer. Speed up or skip anything that is not part of the story. The goal is a video where every second is either setting up the payoff or delivering it.

What should a product demo script include?

Here is a product demo script template you can copy. Timings assume a 60 to 90 second demo for a landing page or sales follow-up; compress each section proportionally for shorter cuts.

PRODUCT DEMO SCRIPT
Product: [name]
Viewer: [role, company type]
The viewer should believe: [one sentence]
Target length: [30 / 60 / 90 seconds]

1. HOOK (0:00-0:05)
On screen: [the end result, shown first]
Line: "[Outcome] in [time or effort]."

2. PROBLEM (0:05-0:15)
On screen: [the old way: spreadsheet, manual steps, messy inbox]
Line: "Today, [role] spends [time / effort] doing [painful task]."

3. WALKTHROUGH (0:15-0:60)
Step 1 on screen: [first action]
Line: "Connect [source] / Start with [input]."
Step 2 on screen: [key moment, zoom into the detail]
Line: "[Product] [does the hard part] automatically."
Step 3 on screen: [result forming]
Line: "Review, tweak, and [ship / send / publish]."

4. PAYOFF (0:60-0:75)
On screen: [finished result, real-looking data]
Line: "[Concrete outcome the viewer cares about]."

5. CALL TO ACTION (0:75-0:90)
On screen: [logo, URL, button]
Line: "[Start free / Book a demo] at [url]."

CHECKS
- Every line maps to a screen
- Story works on mute with captions
- One call to action only

Open with the result, not the login screen: showing the payoff first gives the viewer a reason to watch the steps. And write walkthrough lines as verbs (connect, generate, publish), which keep the pace up and work as captions.

How long should a software demo video be?

There is no single right length. It depends on where the video lives and how much attention the viewer has already given you. Use this as a starting point:

App stores set their own technical requirements for preview videos (length, resolution, what can be shown), and they change, so check Apple's and Google's current documentation before you export. For landing pages specifically, our guide to landing page videos goes deeper on autoplay, placement and loops.

Should you screen-record or use motion design?

There are two broad ways to produce a software demo video, and many teams end up using both for different jobs.

Screen recording is honest and quick. It is the right call when the viewer wants to see the real product in real time, such as a prospect who asked how a specific integration works. The risk is pacing: real software has loading spinners, typing and scrolling that feel slow on video.

Motion-designed demos treat screenshots as layers that can be zoomed, blurred, rearranged and animated. You control exactly where the eye goes, so you can show a complex workflow in a fraction of the time. This used to mean hiring an agency or learning After Effects. Tools like Videly now generate a motion-designed video from your screenshots or product URL plus a short script, show you a storyboard to approve before rendering, and export 16:9, 1:1 and 9:16 versions with your brand kit and auto captions.

Product demo video examples: three structures that work

Rather than point at other companies' videos, here are three example structures you can adapt directly. Each one uses the script template above, just weighted differently.

Example 1: the 20-second landing page loop

No voice-over and no sound needed. Open on the finished result for two seconds, cut back to the input (a blank form, a raw data source), then show three quick beats as the product transforms it, each with a short caption: Connect, Generate, Publish. End on the result again so the loop feels seamless. This works well above the fold because it answers what the product does before the visitor reads a word.

Example 2: the 75-second app demo video for a feature page

Use the full five-part script. Spend about ten seconds on a problem the viewer will recognise, ideally shown visually (a cluttered spreadsheet, a pile of tickets). Then walk through one workflow in three steps, zooming into the detail that makes your product different. Finish with the outcome stated in the viewer's terms and a single call to action. Voice-over is optional; captions are not.

Example 3: the three-minute sales follow-up

After a discovery call, record a short demo that uses the prospect's own words for their problem. Open with a recap of what they told you, then show the two or three workflows they asked about, in the order they matter to them. A real screen recording is often the right choice here, because the prospect wants to see the actual product. Keep it under a few minutes so it can be forwarded to a decision-maker who was not on the call.

What are the most common demo video mistakes?

• Starting at the login screen. Open with the outcome. Nobody needs to watch you sign in.
• Showing every feature. A demo that tries to cover everything proves nothing. One workflow, one payoff.
• Unreadable UI. Full-screen captures shrunk into a small video player make text illegible. Zoom into the part that matters.
• Cursor wandering. If you record, plan every movement. If you animate, the cursor should move with purpose or not appear at all.
• Empty or obviously fake data. Test User 1 and lorem ipsum undercut the whole video.
• No captions. Many viewers watch on mute, especially on social and in autoplay placements.
• Multiple calls to action. Pick one: start free, book a demo, or join the waitlist.
• Letting it go stale. When the UI changes, an outdated demo confuses new users. Plan how you will update it.

How do you keep a demo video up to date?

SaaS products change every few weeks, and demo videos age quickly. A few habits help. Keep the script and the source screenshots or recordings in one shared folder, labelled by step. Build the video in sections so you can replace one step without redoing the rest. And add a demo review to your release checklist: when a release changes a screen shown in the demo, flag the video for an update.

For new features, a short standalone clip is often more useful than re-cutting the full demo. See feature announcement videos and our release notes template for pairing the two.