How to write a product demo video script

Start from the viewer's question

People do not watch a demo to learn your navigation. They watch to answer "is this for me, and what would it change?" So before writing any lines, write down three things:

1. Who is watching, in one phrase: "operations leads at small logistics companies", "freelance designers", "anyone who files expenses".
2. The problem they have today, in their words, not yours.
3. The one thing you want them to do afterwards: start a trial, book a call, install the app.

If the draft script ever drifts into features that do not serve those three lines, that is where to cut.

The structure

Most good demo scripts follow the same shape, whatever the product.

1. The hook, one line. Name the problem or the result. "Month-end close in an afternoon, not a week." Put the product on screen while it is said.
2. The product in action, three to five moments. One screen and one line each. Show outcomes: the report that exists, the message that was sent, the chart that answers the question.
3. The reason to believe, optional. One line of proof, if you have honest proof: a number from real customers, a notable user, a certification. Skip it rather than invent it.
4. The call to action, one line. One action, said plainly, with where to do it. "Start free at example dot com."

That is five to eight lines for a sixty- to ninety-second video. The structure is deliberately plain. The creativity goes into choosing the moments and phrasing each line, not into the shape.

How many words you can afford

A calm narration runs at about 150 words per minute, or two and a half words a second. That gives a hard budget:

Each screen should stay up long enough for the viewer to find what the line mentions, usually four to seven seconds. That is why a line of eight to fifteen words per screen feels right: long enough to say something, short enough that the picture changes before attention drifts.

Write for the ear

A script is heard once, at the speaker's pace, with no way to scroll back. Sentences that read well on a page often sound dense out loud.

• One idea per sentence. "Invoices go out on time. Payments match themselves." beats one long sentence joined with "and".
• Verbs over nouns. "You see every late payment" is easier to follow than "visibility into payment delays".
• Say numbers the way people say them. "About two hundred" is easier to hear than "198".
• Spell names for the voice, not the eye. An acronym, a product name or a domain may need writing out, like "O-I Data" or "shot demo dot com", so a synthetic voice says it right. Good tools keep a pronunciation list so the captions can keep the real spelling.
• Avoid lists of three features in one line. The viewer remembers one; show the others on their own screens.
• Read it aloud, with a timer. Anything you stumble on, the voice will too.

Captions are not the voice

On-screen captions and the spoken line do different jobs. The spoken line is a full sentence. The caption is a headline of three to eight words that still makes sense with the sound off: "Reports that write themselves". Viewers in a muted feed read the captions first, so each caption should carry the point of its screen on its own.

A separate subtitle file, which repeats every spoken word, is what people who turn on captions in a player expect. The example video on this page has both: a short caption on every screen, and a subtitle track of the whole script.

A fill-in template

Copy this and replace the brackets. Keep each line to one breath.

Hook (product on screen): [The result, or the problem], in [the time or effort it takes with you].

Moment 1 (the result screen): Here is [the outcome] for [who], [how it is different from today].

Moment 2 (how you get there): [Action in plain words], and [product] [does the tedious part].

Moment 3 (the feature that sets you apart): [What it does], so you [benefit].

Moment 4, optional: When [common situation], [what the product does].

Proof, optional: [An honest number or name], [what it means].

Call to action (closing card): [One action] at [address].

And the caption for each screen: the same idea in three to eight words.

A real script, line by line

The OIData example above is a dense analytics product, so its script is a good model for making numbers-heavy screens understandable. Its opening line says what the whole product is for in two short sentences: "Open interest shows where traders are positioned. OIData reads it for you." The first sentence names the thing the audience already cares about; the second says what the product does with it.

Each following line describes one screen by what the viewer gets from it, and several stay under ten words: "See the street's fear and greed as one number." The closing line gives one action and one address. Two techniques are worth copying: one line that covers two related screens, which saves words without rushing, and a single montage line, "Plus futures OI, strike history, seasonals...", that shows breadth in a few seconds instead of a sentence per page. The full script is on the OIData example page.

Common mistakes

• Opening with a welcome. "Hi, and welcome to our product demo" spends three seconds saying nothing. Open with the result.
• Narrating clicks. "Now I click the settings icon" describes the screen instead of the benefit.
• Jargon from inside the company. Internal names for features mean nothing to a stranger.
• Claims you cannot back. "The fastest", "the only", "trusted by thousands" invite doubt unless they are true and checkable. Plain, specific statements are more convincing.
• Two calls to action. "Start a trial or book a demo or follow us" leaves the viewer with no clear next step.
• Writing the script after recording. Then the words have to fit the footage, and the video ends up long.

If an AI writes the first draft

AI writers are good at producing a structured first draft quickly, especially from your website's own words. Treat that draft like one from a new colleague: check every claim against what your product and your site actually say, cut anything general, and read it aloud. On the SignValid example, the AI wrote the whole script from the website and a person rewrote two lines so each said only what the site says. It took minutes, and it is the step that keeps a product video honest.

Once the script is done, the rest is production. Our guide to making a SaaS demo video covers the steps that follow.