Skip to main content

Product demo script: word-for-word samples for live and video demos

By Alan Magliocca

Quick answer: A strong product demo script writes the opening, transitions, check-in questions and close word for word, and leaves the middle as short cues tied to clicks. Start with the buyer's problem, show one workflow from trigger to result, stop to ask questions, and end on a scripted next step. For a demo video, script every word and reuse it as the caption file.

KEY TAKEAWAYS
  • Write the opening, transitions and close in full; use short cues for the clicks in between.
  • Prepare exact lines for features you don't have, roadmap items and pricing questions.
  • A 90-second demo video script runs before screen, trigger, workflow, result, then where to see more.
  • Scripted lines that make claims need proof before they run, and caveats don't fix misleading ones.
  • A full video script doubles as the transcript for captions.

Script the words around the clicks

Nobody forgets which button to press in their own product. What goes wrong is the talking: the opening that wanders for four minutes, the transition that turns into a feature list, the close that ends with "so, yeah." A good product demo script writes those parts out in full and leaves the middle as short cues tied to clicks. Below are two samples you can copy: a 30-minute live demo and a 90-second demo video. Replace anything in square brackets.

Sample script: 30-minute live product demo

Opening (minute 0 to 2, word for word)

"Thanks for joining. In the next thirty minutes you'll watch [product] do one job from start to finish: [the job, in the buyer's words]. I'll stop three times to ask how you handle this today, so keep the chat open. Put questions in the Q&A box and I'll answer them from minute twenty. If you have to leave early, the recording goes out tomorrow."

The problem (minute 2 to 5)

"Here's what [the job] looks like for most [audience] right now." Cue: show the before screen, such as the spreadsheet or the paper form. "Every [week], someone spends [the step that hurts] doing this by hand. Keep that in mind, because it's the part we're about to remove."

Workflow, step one (minute 5 to 11)

Cue: start from the trigger, such as a new order or a new hire. Say each click before you make it.

Transition line: "That's the part most people do by hand. Watch what happens next."

Check-in line: "Quick one for the chat: type 1 if this is how you do it today, 2 if you do it differently. I'll read a few out."

Workflow, step two (minute 11 to 17)

Cue: the step that saves the most time. Pause on the result screen for a full five seconds without talking.

Transition line: "So far we've [what step one did] and [what step two did]. The last piece is what you see at the end of the [week or month]."

The result (minute 17 to 20)

"This is the screen you'll actually look at on [day]." Cue: show the report or finished output. "Everything on it came from the two steps you just watched. Nobody retyped anything."

Questions (minute 20 to 27)

Opening line: "Let's go to your questions, starting with the most upvoted."

For a feature you don't have: "Not today. Here's what customers do instead." Then show it.

For a roadmap item: "We're building that. I won't show it until it ships, because I'd rather you see the real thing."

For pricing: "[How pricing is structured, in one sentence]. I'll put the pricing page link in the chat."

Close (minute 27 to 30, word for word)

"Here's what happens next. Within an hour you'll get the recording with chapters, so you can jump to any part. If you want to see this with your own [data type], reply to that email with your [one detail] and we'll set up a short call. Thanks for spending thirty minutes with us."

Sample script: 90-second product demo video

Each line is the time, then what's on screen, then the voice-over.

  • 0:00 to 0:08. On screen: the before screen. Voice: "If [job] still means [painful step], this is for you."
  • 0:08 to 0:20. On screen: the trigger arriving. Voice: "A [new order] comes in. Here's what happens."
  • 0:20 to 0:55. On screen: the workflow, no cutaways. Voice: describe each step in under ten words as it happens.
  • 0:55 to 1:15. On screen: the finished result. Voice: "That's [the result]. No retyping, no [painful step]."
  • 1:15 to 1:30. On screen: the product name and where the longer demo lives. Voice: one sentence telling viewers where to see the full walkthrough.

Script every word for video. The script then doubles as your caption file: YouTube can auto-sync a transcript you upload, as long as it's in the language spoken in the video, though Google doesn't recommend this for videos over an hour (YouTube Help).

Lines that need extra care

Some lines in a demo script are claims, and claims have rules. The FTC's guide for small businesses says advertisers need proof for express and implied claims before the ad runs, that a line like "Your results may vary" is not enough to fix a misleading claim, and that customer endorsements must reflect the typical experience of people who use the product (FTC). In practice:

  • Replace "you'll save ten hours a week" with what the product does: "it fills the order sheet from your sales, so nobody types it."
  • Quote customers on what they do with the product, not on unusual results.
  • If a recording is sped up, say so on screen.

Check claims in regulated industries with a lawyer before the script is final.

Worked example: an inventory app for independent restaurants

Parcount is a made-up inventory app for independent restaurants with one to three locations. Its weekly live demo runs on Monday at 3 pm, the quiet window between lunch and dinner service. Here's how the team filled in the brackets.

  • The job: "Counting your walk-in and building Thursday's order without a clipboard."
  • The before screen: a photo of a stained count sheet taped to a cooler door.
  • Step one: a cook counts the walk-in shelf by shelf on a phone, with items in the order they sit on the shelves.
  • Step two: the app compares the count with par levels and drafts the produce and dairy order.
  • The result: a food cost view for the week, by category.
  • Check-in question: "Who does your count now, and what day? Type it in the chat."
  • Close detail: "Reply with a photo of your current count sheet and we'll show you the walk-in set up your way."

After each session, owners who sent a count sheet got a recorded walkthrough of their own layout, made with the screen recorder. On Loom's free Starter plan recordings stop at five minutes (Loom Help Center), so the team scripts those clips to cover one shelf layout and one order each.

How long a demo script takes

  • First live script: about three to four hours to write, then two read-throughs with the product open.
  • 90-second video script: about an hour, plus another for timing it against the screen recording.
  • Updates: about 30 minutes whenever a screen in the workflow changes.
  • With BrightStage AI: the video creator builds a script and slides with AI presenters, and "Suggest" buttons fill event fields with AI for 1 credit per click.

Script mistakes to avoid

  • Writing the middle word for word. Reading while clicking sounds like reading. Use cues there.
  • A transition that lists features. Each transition should name what just happened and what comes next.
  • No line for "we don't do that." Without one, presenters improvise and over-promise.
  • Ending on questions. Always end on the scripted close, even if questions run long.

For the delivery habits that make a script land, see product demo best practices. The questions to plant at each check-in are in product demo engagement and questions. If the demo is part of a launch event, adapt the opening from the product launch script.

Where BrightStage AI fits

BrightStage AI, an AI webinar and live-event platform from Podavinci LLC, can run this script live or as an automated (evergreen) event on a schedule. Its video creator drafts a script and slides with AI presenters, which gives you a first version to edit against your own product. During the event a chat assistant answers attendees in the event chat, review cards collect testimonials, and sale announcements show only real purchases. The replay is called "Encore." BrightStage AI won't know your product's screens, so the click cues are yours to write. For tools that help with the video version, compare the best AI video script tools.

Sources

AIVX LABS ACCOUNT VERIFICATION
Get AIVX Labs verified for $1: RICO, your AI operator, and 35+ AI tools, with 7 days of full access.
Get AIVX Labs Verified for $1 →

Frequently asked questions

Is there a product demo script sample I can copy?

Yes. A copyable 30-minute script has six parts: a word-for-word opening, the problem, two workflow steps with transition lines, questions, and a word-for-word close. Fill the bracketed parts with your product and audience.

How do you write a product demo video script?

Plan it in beats: the before screen, the trigger, the workflow, the result and one line on where to see more. Keep each voice-over line short enough to match what's on screen.

Should a live product demo be fully scripted?

Only the edges. Scripting the opening and close keeps them tight, while cues for the middle let you talk naturally as you click.

What should a demo script say when the product can't do something?

Say so plainly and show the workaround current customers use. It keeps trust and stops presenters from promising features that don't exist.

Related playbooks

Written by Alan Magliocca, founder of BrightStage AI and AIVX Labs (Podavinci LLC). Written with AI assistance and checked against the linked sources. Follow along: LinkedIn · YouTube · TikTok · X · Facebook · Instagram · Skool community