Product demo script
script template

Most demos fail the same way. The seller knows the product, so they show all of it, and the buyer sees a tour of a building they have no reason to enter. A demo that works shows one person doing one job, arrives where that person wanted to get to, and then stops. This is that structure, live and recorded, including what to say when it breaks.

256 words as written 43 places to fill in 3 versions

Opens the free teleprompter with the script already loaded. Nothing is uploaded, and your camera never leaves your device.

THE LIVE DEMO ON A CALL, ABOUT TEN MINUTES

Before I share anything, let me check I have this right.You said [THEIR PROBLEM, IN THEIR OWN WORDS], and that it costs you [THE NUMBER THEY GAVE YOU]. Is that still where you are?Good. I am going to show you three things: [THING ONE], [THING TWO] and [THING THREE]. That is all. If anything else comes up, stop me.[SHARE THE SCREEN ON THE FINISHED RESULT, NOT ON THE LOGIN PAGE.]This is where we end up. [THE FINISHED OUTPUT, DESCRIBED IN THEIR LANGUAGE.] Today that takes you [THEIR CURRENT PROCESS AND TIME].Let me show you how it gets made.[SECTION ONE.] Now I am going to [THE ACTION]. [THE RESULT.] For you, this is the part that replaces [THE THING IT REPLACES].Does that match how your team would use it, or would it be [THE OTHER LIKELY WAY]?[SECTION TWO.] Same idea here. [THE ACTION.] [THE RESULT.]The reason that matters for [THEIR SITUATION] is [ONE SENTENCE].Anything you would want different about that?[SECTION THREE.] And this is where [THE PERSON WHO WILL ACTUALLY USE IT] would spend their day.[PAUSE AND LET THEM LOOK.]So that is [THE PROMISE], done in [TIME]. Against [THEIR CURRENT PROCESS], the difference is [THE SPECIFIC SAVING].What have I not shown you that you need to see?Here is what I suggest. [THE SPECIFIC NEXT STEP, WITH WHO DOES WHAT.] I can do [DAY] or [DAY]. Which is easier?

THE RECORDED DEMO YOU SEND, UNDER THREE MINUTES

[NAME], this is [NUMBER] minutes on [THE ONE THING YOU ASKED ABOUT]. No pitch in it.Here is the end result first. [THE FINISHED OUTPUT.]Three steps to get there.One, [THE ACTION]. Two, [THE ACTION]. Three, [THE ACTION].That took [TIME]. The manual version you described takes [THEIR TIME].One thing I should flag: [THE HONEST LIMITATION FOR THEIR CASE].If that is useful, [THE NEXT STEP]. If it is not, tell me and I will leave you alone.

WHEN SOMETHING BREAKS

That is not meant to do that.[SAY WHAT SHOULD HAVE HAPPENED, IN ONE SENTENCE.]I will [FIX IT NOW / SEND YOU A TWO MINUTE RECORDING OF IT WORKING THIS AFTERNOON]. While that reloads, let me tell you [THE THING YOU WERE GOING TO SAY NEXT].[IF IT IS STILL BROKEN AFTER TWENTY SECONDS, MOVE ON. DO NOT DEBUG ON THE CALL.]

Why it is built this way

Open in their words, before you share your screen

Repeat back the problem they described on the previous call and check it is still true. That one move frames the demo as an answer to something rather than a walkthrough of something.

Show the end state first

Start on the finished report, the completed workflow, the result. People need to see where this ends before they will pay attention to how it gets there. A tour with no destination is where demos die.

One persona, one job, one path

Every extra role and edge case you demonstrate makes it harder for the person watching to see themselves. Pick the buyer in the room and show the path they would take on an ordinary Tuesday.

Narrate the click a half-second before you make it

Saying "now I open the report" just ahead of the cursor keeps their eyes with you. Silent clicking makes people watch your mouse instead of listening to you.

Stop and check after each section

A demo is not a presentation. One question after each part turns it into a conversation and surfaces the objection while you still have time to answer it.

Do not demo what does not exist yet

The moment you say "we are building that", everything you have shown becomes a roadmap and stops being a product. Note it, move on, and follow up in writing.

Close on a named next step with a date

A demo that ends on "any questions" simply ends. Say what happens next, who does it, and when.

Delivering it

·Build a demo account that looks like their business: their sector, plausible names, realistic volumes. Demo data called Test Test 123 undoes ten minutes of good work.
·Close every other tab and turn off notifications before you share. It is the most avoidable way to lose a room.
·Rehearse the recorded demo once against the prompter and keep the second take. First takes contain every apology you did not need to make.
·Never say "as you can see". If they could see it, you would not be pointing at it.
·Write down the three things you will show and stop after the third, even when it is going well. Overrunning a good demo is how the next step gets postponed.

Frequently asked questions

How long should a product demo be?

Ten to fifteen minutes live, under three minutes recorded. The limit is not attention span, it is the number of things a buyer can hold at once, which is about three.

What should you show first in a demo?

The finished result. Start on the output the buyer wants and work backwards to how it is produced, rather than starting at the login screen and hoping they stay for the payoff.

Should a product demo be scripted?

The path and the checkpoints should be. Write the opening, the three sections and the close, then leave room for their questions in between. A demo read start to finish is a webinar with one attendee.

What do you do if the demo breaks?

Say what should have happened, offer a recording, and move on inside about twenty seconds. Debugging live turns a product problem into a competence problem.

More scripts

Sales call script

Business and creator · 310 words

→

Webinar opening script

Business and creator · 229 words

→

Elevator pitch

Business and creator · 198 words

→

Tutorial video script

Business and creator · 185 words