Product demo scripts

What a product demo script is

A product demo script is the spoken text for a video that shows a product doing its job, written alongside the exact click path that produces what the viewer sees. It is ordered around the questions a buyer has, in the order they have them, and timed so the finished recording runs to a length somebody will actually watch.

It is not a tour of the interface, and that distinction is why this page exists separately from a general video script. It is also not an explainer, which is for a viewer who does not yet understand the offer. A demo is for a viewer who understands it, half believes it, and wants to see the thing work before booking a call.

When you need one

You need a demo script when prospects keep asking to see it. That request is a good sign and an expensive one, because it usually means somebody gives the same live demonstration four times a week and gives it differently each time. A script makes the recorded version consistent, and the live version better.

The second case is a product that is hard to picture from a page. Scheduling, dispatch, inventory, anything with a workflow inside it: no amount of feature page writing shows a buyer what Tuesday morning looks like, and screen recording does.

You do not need one if the product is simple enough that stills and captions carry it, or if what you actually need is instructions for people who have already bought. That is user guides and manuals, a different job with a different reader. A demo persuades. A guide instructs.

What goes in it

The running order is the work. Almost no buyer cares about your product in the order the menu is laid out in, yet almost every demo made in-house follows that menu, because it is the order the person demonstrating knows. So the video opens with settings and arrives at the thing the buyer came for at minute nine, by which time they have gone.

The script is built instead from the three or four things a buyer has to be satisfied about before they will take a call. Those come out of the objections your sales conversations already produce, and they set the order.

• The starting position. One sentence saying whose screen this is and what they are trying to get done, so the viewer has somebody to stand behind.
• The buyer's questions, in order. Each becomes a section. Can it handle our volume. Does it talk to the accounting package. What happens when a job changes at eight in the morning.
• The click path. A second column giving the exact route through the product for each spoken line, and the sample data to have loaded, so the recording matches the words on the first take.
• The result at each step. Every step shows a result, not a click. Nobody needs to watch a cursor find a menu; they need to see the invoice appear, the route redraw, the alert reach the phone.
• The honest limit. One line naming something the product does not do. It costs thirty seconds and buys more trust than the rest of the video combined.

What you get

The script. A two-column document formatted for reading aloud: spoken text on the left with a running time at each section, the click path and screen notes on the right. Every draft is read aloud against a stopwatch first, because writing for the ear is not writing for the page, and a web page read aloud sounds wrong within a sentence or two.

The recording plan. The sample data to set up first, the window size, what must be blurred, and the order to record sections in so a mistake at minute five does not cost you minutes one to four.

A chaptered version. Where the demo runs past four minutes, sections are marked with timings, so a viewer can jump to the part they care about and a salesperson can send one chapter rather than the whole thing.

The on-screen text list. Labels, callouts and section titles in order, since a screen recording without them is hard to follow.

A worked example

An illustration, not a client. A Kitchener company sells scheduling software to heating and plumbing contractors. Their demo video runs fourteen minutes. It starts with account setup, spends two minutes on user permissions, and reaches the dispatch board at minute nine. Most prospects stop replying after it is sent.

The rewrite starts from the three questions those contractors actually ask: whether a job can be moved when a van breaks down, whether the technician sees the change on the phone without ringing the office, and whether the hours land in payroll without being retyped. Those become the running order, each shown as a result rather than a sequence of clicks. Setup and permissions come out entirely, into a separate two-minute video for customers who have already signed. The demo lands at six minutes and ten seconds with three chapter markers, and a salesperson can now send the ninety-second dispatch section on its own.

How it runs

1. A half-hour call. What the product is, who buys it, and the questions that come up in every sales conversation. No charge.
2. A fixed price in writing. Run time, one demo or a set of short ones, and whether a recording plan is needed, agreed before anything starts.
3. Access. I need to use the product myself, on a demonstration account with realistic data. Watching somebody else drive it is not enough to write an accurate click path.
4. The draft. Five to seven working days for a single demo, longer for a set. Every path in it is walked through in the product first.
5. Your read-through. Whoever will record it reads it aloud with the product open and follows the click path. Anything that does not match is corrected.
6. The final. Script, recording plan, chapter markers and on-screen text list, in one folder.

What it costs

A demo script is quoted as a fixed price in CAD after the half-hour call. The size varies more here than for other scripts, because the writing includes learning the product properly, and a workflow tool takes longer to learn than a single-purpose one. The pricing page explains how fixed pricing works, and the number is settled in writing before any work begins.

What happens next

Three things typically follow. The recording gets proper captions taken from the script, which matters more here than elsewhere because product names and field labels are exactly what automatic captioning gets wrong. The chapters usually become short clips a salesperson sends one at a time, which is short-form cutting. And the questions that set the running order are the ones the site should be answering in writing, so they often end up as FAQ pages in the same month. None of it is assumed. The demo script is complete on its own, and you can record it and leave it there.