Product Demo Video Script: A Template and Examples for SaaS

A product demo video script is the written plan for a demo video: what the viewer sees on screen, what the voice-over or captions say, and how long each scene lasts. Writing it first is the single biggest thing you can do to make a good demo, because most weak demos fail on structure, not on production quality. This guide gives you a template you can copy, word counts for each video length, a worked example for a fictional SaaS product, and the mistakes that most often sink a script.

What a demo video script is (and is not)

A sales demo script is a talk track for a live call. A demo video script is different. The viewer cannot interrupt, ask questions or skip ahead with you, so the script has to carry the whole argument in a fixed amount of time. It also has two columns that a call script does not need: what is on screen, and what is said or written.

Keep the scope tight. A demo video script covers one audience and one outcome. If you try to cover every feature, you get a feature tour that nobody finishes. For the broader production process, see our guide on how to make a product demo video.

How long should the script be?

Spoken English runs at roughly 130 to 160 words per minute. Plan for the lower end, because the viewer needs a beat to take in each screen. The table gives working targets, not rules.

If the script does not fit the word count, cut scenes rather than speeding up the narration. Fewer scenes shown clearly beat more scenes shown fast.

The structure of a good demo script

Almost every effective short demo follows the same five-part arc. You can stretch or compress each part, but keep the order.

1. Hook. State the outcome or the problem in one line. Do not open with your company name or a logo animation.
2. Context. One sentence on who it is for and what they struggle with today. Skip it in videos under 30 seconds.
3. Walkthrough. Show two to four steps in the real interface, in the order a user would do them. Each step is one action and one result.
4. Proof. Show the finished result with realistic data. Use only numbers that are true; leave invented statistics out entirely.
5. Call to action. One next step, named exactly: 'Start free at your-app.com', not 'Learn more'.

Write the hook last

The hook is the line most worth rewriting, so draft it after the rest of the script is done. Once you know what the walkthrough actually proves, the sharpest opening is usually the result of that walkthrough, stated plainly: 'Send a client report in two minutes' beats 'Introducing Acme, the all-in-one reporting platform'.

Product demo video script template

Copy this into a document and fill in the brackets. The two-column layout (on screen, said) forces you to check that every line has something to show.

PRODUCT DEMO VIDEO SCRIPT
Product: [name]
Viewer: [role and company type]
Outcome: [what they can do after watching]
One action: [start free / book a demo / join waitlist]
Target length: [60 s] | Target words: [130-150]

SCENE 1: HOOK (0:00-0:05)
On screen: [the finished result or the pain point]
Said / caption: "[Outcome] in [time or effort]."

SCENE 2: CONTEXT (0:05-0:12)
On screen: [the old way: spreadsheet, tabs, manual steps]
Said / caption: "[Role] spend [time] on [task] every [period]."

SCENE 3: STEP 1 (0:12-0:24)
On screen: [first action in the product, zoomed to the relevant area]
Said / caption: "[Verb] your [thing]."

SCENE 4: STEP 2 (0:24-0:36)
On screen: [key feature at work]
Said / caption: "[Product] [does what], so you [benefit]."

SCENE 5: STEP 3 (0:36-0:48)
On screen: [result appears]
Said / caption: "[Verb] it to [destination]."

SCENE 6: PROOF (0:48-0:55)
On screen: [finished result with realistic data]
Said / caption: "[One true, specific benefit]."

SCENE 7: CALL TO ACTION (0:55-1:00)
On screen: [logo, URL, button text]
Said / caption: "[Action] at [url]."

CHECKS
- Works with the sound off (captions carry every key line)
- Every line maps to a visible screen
- No jargon the viewer has not met yet
- One call to action only

Worked example: a 30-second script

Here is the template applied to a fictional product, 'Tallyboard', an invoice-tracking tool for freelancers. The product and numbers are made up for illustration.

Notice what the script leaves out: pricing tiers, integrations lists, the team page. Each of those is a separate video or a section of your site. This example is about 70 words, which leaves room to breathe at a natural pace.

Writing rules that make scripts better

• Write for the ear. Read every line aloud. If you stumble, rewrite it.
• One idea per sentence. Short sentences are easier to caption and easier to follow with the sound off.
• Name the outcome, not the feature. 'Reports build themselves' tells a viewer more than 'automated report generation engine'.
• Use the product's own words. If the button says 'Send reminder', the script should say 'send reminder', not 'trigger a notification workflow'.
• Match the narration to the screen. Say the thing at the moment it appears, not before or after.
• Show, then tell. Let the screen change first and the line land a half-second later.
• Cut adjectives. 'Powerful', 'seamless' and 'revolutionary' add words and no information.

Adapting one script for different uses

You rarely need a brand-new script for each channel. Start with the 60-second version and cut down or add to it.

• Landing page: use the 30-second cut and make sure it works silently, since many visitors will not turn on sound. See our notes on landing page video.
• Launch day: use the full 60 seconds, with a stronger hook tied to the announcement. The product launch checklist shows where the video fits.
• Social: cut to 15 to 20 seconds, keep the hook and the proof, and drop the context scene.
• Sales follow-up: extend to 90 seconds and add a scene on the specific problem the prospect raised.
• Non-English audiences: translate the captions and voice-over lines, then check that the translated text still fits the scene length, since some languages run longer than English.

Common script mistakes

• Opening with the company. Viewers care about their problem first. Your name can come at the end.
• Writing a feature list. If the script reads like a changelog, restructure it around one task.
• No visual plan. A line with nothing to show gets filled with a generic stock clip or a static screen.
• Too many calls to action. 'Sign up, follow us, read the docs and book a demo' is four asks and zero actions.
• Scripting for a 3-minute video, then cutting. Start from the target length so the structure fits from the beginning.
• Skipping the read-aloud test. Text that looks fine on paper often sounds stiff.

If your demo doubles as a longer explainer, the examples in our SaaS explainer video examples show how different companies structure the opening.