Product Demo Script: A Template, an Example and How to Review It
A two-column product demo script template, a filled-in example and the review checks to run before production starts.

Quick answer: A product demo script names one buyer, opens on their problem, walks through two or three workflows and ends with a next step. Write it in two columns, what the viewer hears and what they see, and plan about 140 to 160 spoken words per minute. The template below is the structure we use on software demos.
Most demo videos are decided at the script stage. If the script tries to cover every feature, no edit will save it. If it's built around one buyer and a few workflows, the rest of production gets easier.
This guide gives you a product demo script template, a filled-in example and the review steps we use before anything gets animated or recorded. It's written for product marketers and founders who are writing the script themselves or reviewing one from a vendor. If you'd rather have a team handle it, see our product demo video production.
What should a product demo script include?
- The viewer: One role, such as "operations manager at a mid-size logistics company". Write it at the top of the script.
- The problem: The pain that viewer feels today, in their words.
- Two or three workflows: The ones that make buyers lean in on sales calls.
- The result: What the viewer has at the end, such as a report, an approval or time saved.
- Proof: A customer name, a quote or a number you can back up.
- The next step: One call to action, such as booking a demo or starting a trial.
Product demo script template
Use two columns. The left column is what the viewer hears. The right column is what they see. Writing both at once keeps you from describing a screen that doesn't exist.
- 0:00 to 0:10, the hook. Hear: the problem in one sentence. See: the old way, such as spreadsheets, email threads or a cluttered dashboard.
- 0:10 to 0:20, the promise. Hear: what changes with your product. See: the product's main screen, simplified.
- 0:20 to 1:10, workflows one to three. Hear: what the user does and why it matters, one workflow at a time. See: the exact screens, zoomed or rebuilt so they're readable.
- 1:10 to 1:25, the result and proof. Hear: the outcome and a customer proof point. See: the finished output and a logo or quote.
- 1:25 to 1:30, the next step. Hear: one clear action. See: the URL or button.
At about 150 spoken words per minute, that's roughly 200 to 230 words of voiceover for a 90-second demo. If your draft is longer, cut features, not pauses. Viewers need a beat to read each screen.
Created by Levitate. Propel Software: a 2D animated product video explaining product lifecycle management and cloud software.
A filled-in example
Here is the opening of a demo script for a fictional expense approval tool, so you can see how the two columns work together.
- Hear: "Approving expenses shouldn't take three emails and a spreadsheet." See: An inbox filling with receipts and reply-all threads.
- Hear: "With Approvely, every request lands in one queue with the receipt attached." See: A clean queue screen with three requests.
- Hear: "Approve in one click, or send it back with a note." See: A cursor clicks Approve. A green check appears.
- Hear: "Finance sees it the moment it clears." See: The finance view updates with the approved total.
Notice that each line of voiceover matches one screen. If a line needs two screens, it's usually two lines.
Need help with a demo script? Our product demo team writes and reviews scripts as part of every project.
How do you review a demo script before production?
Script changes are cheap. Animation changes are not. These are the checks we run before anything moves into design.
- Check every line against the real product. Each button, label and menu the script names should exist in the current build.
- Get current screens. Ask for screenshots or design files from the latest release, not the deck from last quarter.
- Put screenshots in the script. Many reviewers can't picture a demo from text alone.
- Collect feedback in one document. One consolidated round beats five separate email threads.
- Get the senior technical reviewer early. Their changes are the most expensive to make late.
From our production notes: On a recent AI document-processing demo, the client gathered feedback from many people into one updated script, then had their senior AI leader add a short list of what the demo had to cover. That list became the test for every scene. If a scene didn't serve one of those points, it was cut. For more on demoing AI products, see our guide to AI product demo videos.
On another AI platform video, the client's reviewers struggled to picture the finished video from the script alone, so we added storyboard screenshots to the script document. That gave everyone the same picture to react to before any design work started.
Created by Levitate. Egnyte: one of a series of animated videos explaining data security and content collaboration.
Common demo script mistakes
- Starting with the logo and company history. Viewers want their problem first.
- Naming features instead of results. "Automated workflows" means less than "approvals in one click".
- Writing for internal reviewers. Product teams want every feature in. Buyers want the ones that matter to them.
- No room to breathe. If the voiceover never pauses, viewers can't read the screens.
- Two calls to action. Pick one.
Should you script a demo differently for sales and for onboarding?
Yes. A sales demo persuades a buyer that the product is worth a call, so it stays high level and outcome-focused. An onboarding video assumes they already bought it and shows the exact steps. Our guide to SaaS onboarding videos covers the post-sale side. For examples of finished sales demos, see our product demo video examples. If the demo is part of a release, plan it alongside your product launch videos.
Clients often mention how the team handles reviews. Brandon M., an enterprise reviewer on G2, described the team as "incredibly professional, skilled in media production, and organized." On demo projects with many reviewers, that organization is what keeps the script on schedule.
Write the script around one buyer
Pick the buyer, pick the workflows that close deals, and write both columns together. Then check every line against the current product before anyone starts animating. Typical demo budgets at Levitate run from $5,000 to $25,000+, and the video pricing calculator gives a quick estimate.
Want a second set of eyes on your demo script? Contact Levitate for Tech. New clients can get up to $1,000 toward a first video project, and you can plan now and produce in 2027.
Frequently Asked Questions
How do you write a product demo script?
Name one buyer, open on their problem, walk through two or three workflows, show the result and end with one call to action. Write it in two columns, what the viewer hears and what they see, so every line matches a real screen.
How long should a product demo script be?
At about 150 spoken words per minute, a 90-second demo needs roughly 200 to 230 words of voiceover. Leave pauses so viewers can read the screens.
What is the best structure for a SaaS demo video?
Hook with the problem, state the promise, show two or three workflows, show the result with proof, then give one next step. That structure works for most SaaS demos between 60 and 120 seconds.
Who should review a demo script?
A product owner to check accuracy against the current build, a sales lead to check it answers buyer questions, and the most senior technical reviewer early, because their changes are the most costly later. Collect feedback in one document. If reps will send the demo to buyers, plan it as part of your sales enablement videos.
Can Levitate write the demo script for us?
Yes. Script writing and review are part of our product demo video production projects, which typically range from $5,000 to $25,000+.
What Do Your Buyers Need to Understand?
Tell us what you are explaining, demonstrating, proving or launching. We'll help determine the smartest video approach, relevant examples and a realistic budget range.
Get PricingWhat Do Your Buyers Need to Understand?.
Tell us what you are explaining, demonstrating, proving or launching. We’ll help determine the smartest video approach, relevant examples and a realistic budget range.




