Voiceover for Product Demos and Explainer Videos

A product demo is watched by somebody with a question: does this do what I need, and how hard is it? Everything in the video should answer that question as quickly and honestly as possible. The narration is where most demos go wrong, because the temptation is to describe features, when the viewer wants to see outcomes. A good demo narration is less about the product and more about the person using it.

Here is how to structure and script a demo or explainer, with the narration working for the viewer rather than for the product.

Start with the problem

Open with the situation the viewer is in, not the name of the product. Something like if you have ever lost an hour renaming files one at a time, you know the problem tells them within seconds whether the video is for them. Only then introduce the solution. A viewer who recognises their own problem in the first ten seconds is a viewer who keeps watching.

A reliable structure

Show outcomes, not features

A feature is something the product has. An outcome is something the user gets. A viewer cares about the second. Instead of this tool has batch processing, say you can process fifty files in the time it takes to make a coffee, if it is true. Always ask, of every line in the script, so what, until the answer is something a viewer would want.

Keep it honest

A demo is a promise. Overstating what a product does costs you a viewer who feels misled, and, if they buy on the strength of it, a customer who feels cheated. State what it does well and what it does not do. Viewers trust the honest limit, and it makes the rest of what you say more believable. If a step takes longer than it appears on screen, say so rather than hiding it with an edit.

Match the narration to the screen

• Say what the viewer is about to see, then show it.
• Use the exact labels that appear on screen.
• Slow down at the important moments, and let the screen carry the quick ones.
• Avoid narrating things that are obvious on screen, such as a button being pressed.
• Pause after each step, so the viewer can take it in.

Choose a voice that suits the product

For a business or technical product, a calm, clear, steady voice is the right choice, the same as for a tutorial. For a consumer product, a warmer and slightly brighter voice can suit better. In either case, the aim is to inspire confidence, and a consistent, unhurried voice does that more reliably than a lively one. Listen to a sample of your own script before you commit, because voices differ more on real text than on the demo sentence.

Keep it short

A demo that shows a single workflow in two minutes is more useful than one that shows everything in ten. People who want more will look for it, and a short video is far more likely to be watched through. If a product has many functions, make a short video for each, and link them, rather than a single long one.

Add a caption or subtitle track. Demos are frequently watched at a desk with the sound off, and a viewer who cannot hear the narration will otherwise leave in seconds.