Product Demo Script for a Recorded Demo, With a Template

Most of the product demo script guides I read are written for a live call. Open with a discovery question. Check in every few minutes. Handle the objection. That is good advice when a person is on the other end.

A recorded demo has nobody on the other end. The viewer cannot answer your question. So the script has to work differently, and this post is about that one. It is for SaaS teams who record a demo once and send it to many people: in an email, behind a signature link, in an ad.

I'm Sunny, the founder of DemoSix, so I have a stake here. The ideas come from other people's pages, linked so you can check them. The template and the example are mine.

A product demo script for a recorded demo starts with one question

The live-call guides are clear about what they are. Walnut, which sells demo software, tells you to check in with the prospect throughout and ask questions to make sure each part is relevant. Karumi builds its scripts around discovery questions the prospect answers out loud. Then Karumi adds a short section on recorded demos and says the script has to be much more compact and direct, since there is no real-time interaction.

So the discovery happens before you record. Dadan, which makes a screen recorder, says where to find it: start with your support tickets and sales calls, and look at the questions people ask most often.

Take one of those questions and make it the demo. One question, one video. Vibrantsnap, another vendor, says to title each video by the outcome, not by the screen: "Export an audit trail for a regulator", not "History tab overview". A title like that tells the viewer, and anyone they forward it to, why to press play.

That is how DemoSix works too. The name means demonstrate in six minutes: each demo answers one question in six minutes or less, and a bigger topic becomes a few short demos side by side.

The five parts of the script

Write it in this order. Each part is one or two sentences, not a speech.

1. Open on the result. The first sentence says what the viewer will see done. Supademo, which sells demo software, says not to open with "Here's our product". Vibrantsnap says the same: open on the outcome, not on your logo or "Hi, I'm the founder of...".
2. Name the problem in the buyer's words. One sentence. Use the words from the sales call or the ticket, not your marketing page.
3. Show three to five steps. Vibrantsnap says three to five is enough for most demos, and gives a test: for each step, ask whether the viewer would still get the value if you cut it. If yes, cut it. Say what each step saves them, not only what you are clicking.
4. Show the proof. The finished thing: the routed ticket, the exported file, the report with the right numbers.
5. Give one next step. One, and the one that fits a person who has just watched. More on this below.

Put the payoff early. Wistia analysed more than 13 million videos and found that viewers usually drop off around the halfway point, so the most important part belongs in the first half. For a demo, that means the result appears in your first sentence and again as proof before the midpoint, not in the last ten seconds.

An example script

This example is made up. The product is an invented helpdesk called Pinewood Desk. The question, taken from a pretend sales call: "Can new tickets go to the right team without someone sorting them?"

Title: Send new tickets to the right team automatically

1. Open on the result. "I'm going to show you a new ticket landing in the billing team's queue without anyone touching it."
2. Problem. "Right now someone reads every new ticket and drags it to a team. That person is a bottleneck."
3. Steps.
   • "Open Rules, and click New rule."
   • "Choose the word 'invoice' in the subject as the condition."
   • "Choose Billing as the team, and save."
   • "Now I'll send a test ticket with 'invoice' in the subject."
4. Proof. "There it is in the Billing queue, already assigned."
5. Next step. "If you want to try it on your own tickets, the link below opens the trial."

Read it aloud before you record. Notice what is missing: no tour of the menu, no login, nothing that is not part of this one answer.

How long should the recorded demo be?

The guides give different numbers. Wistia puts "educate or explain" videos, with product demos named as an example, at one to five minutes. Supademo says one to two minutes for a quick feature walkthrough, three to four for a sales demo, and under seven for a full platform overview.

Vibrantsnap's advice for checking is the practical one: read your notes aloud at a calm pace with a timer. If the demo runs long, cut a step rather than talk faster.

DemoSix publishes demos up to about six minutes, and a longer recording becomes ordered six-minute parts.

Before you press record

• Use believable sample data. Dadan says to use realistic data with nothing sensitive in it. Vibrantsnap says viewers read everything on screen, including the data, so no "Test User" and never a real customer's details.
• Rehearse the clicks once, and pause after each so the result loads before you talk about it. Vibrantsnap lists both.
• Keep the script nearby, off screen, as Dadan suggests, so you do not pause to remember.

In DemoSix, you record with DemoSix Recorder on Mac or Windows, or upload a video you already have. DemoSix is not a full video editor, so the script matters more: a rehearsed first take is the one you publish. Captions are added automatically.

What happens after someone watches

The guides I read end the script at the call to action: book a call, start a trial. That is the right ending for someone who is ready. A lot of people are not ready, and many of them would like to look first. Gartner's survey of 646 B2B buyers, run in August and September 2025, found 67% say they prefer a rep-free experience.

So give the demo its own link. A Watch a Demo link beside "Book a demo" in your email signature, on a landing page, or in an ad works like this: the viewer enters a name and email on a page with your branding, then watches. They do not need an account.

Now your script has an afterlife. Your Leads list shows, for each lead, which demos they watched and how far they got. Someone who watched the routing demo to the end is a different follow-up from someone who stopped at the first step, and neither is the same as a name that never pressed play. Capture Leads is on every plan. Basic is free: 1 link, just the owner, 50 new leads a month. Standard has 5 links and 10 reps, Teams has 10 links and 50 reps, both with unlimited leads, and Enterprise has no limit on links or reps. A link has its own name, form and demos, so you can tell where a lead came from. A rep is a person with their own copy of a link, so you can tell who brought them in. Who watched, the view per demo of who in a private library watched it, stopped part way or never started, is included in Standard and Teams. The pricing page has the details.

Keep your demos in one library and group them into Channels by product, feature or kind of buyer, so the link opens a set of short answers instead of one long video. Product demo videos and demo software show how that looks.

What this does not do

• It is not an interactive demo. Interactive demo tools build click-through copies of your product. DemoSix holds real recorded videos of it.
• It does not write the script for you. The questions come from your calls and tickets. Nobody knows what your buyers ask better than you do.
• A form in front of a demo costs some viewers. The trade is a name for the ones who stay. If your demo is for people already in your product, skip the form.
• It does not replace the call. A viewer who is ready to talk should have "Book a demo" right beside it.

The takeaway

Write the recorded demo like you answer one person, once. Take a question from a sales call or a ticket, make it the title, open on the result, show three to five steps, prove it, and give one next step. Then put a Watch a Demo link in front of it and look at who watched.