Igniva / Blog / How to Write a SaaS Demo Video Script Th...

How to write a SaaS demo video script

Updated November 7, 2026 · 7 min read

Start with the questions, not the features

Most demo scripts begin with a feature list. The team picks what they are proudest of and walks through it in menu order. The result is accurate, but it rarely matches what a buyer is wondering in the first ten seconds.

Flip it. Before you write a single line, collect the questions buyers actually ask. The best source is your recorded sales calls. Listen for the questions that come up again and again: does it work with our tools, how long does setup take, can my team use it without training, what happens when we grow. Those questions are your outline.

Pick three to five questions

A 60 second video has room for about three to five real ideas. More than that and every scene feels rushed. Rank the questions by how often they come up and how much they matter to the buying decision, then keep the top few.

If two questions overlap, merge them. If a question needs a long answer, it probably belongs in a follow up conversation or an interactive demo, not the video.

Give every scene one job

Structure the script as a series of scenes, each answering one question. A simple shape that works for most SaaS products:

• Hook (5 to 8 seconds): name the problem in the buyer's words.
• Promise (5 seconds): one line on what your product does about it.
• Answers (30 to 60 seconds): one scene per buyer question, each showing the real screen that answers it.
• Proof (5 seconds): a concrete result, number or customer line if you have one you can stand behind.
• Next step (5 seconds): one clear action, such as try the demo or book a call.

Write for the sound off

Most people watch website and social videos without sound. Write the script as on-screen text first. Keep each line to about eight words, use the words buyers use, and let the screen do the explaining. If a line needs a second sentence, the scene is doing too much.

Read the script out loud at a normal pace. If you run out of time before the scene ends, cut words, not scenes.

Show the real product

Mockups and abstract animations look polished but leave buyers wondering what the product actually looks like. Use real screens, cropped and zoomed so the answer to each question is obvious. Real screens also mean the demo stays honest as the product changes.

A sample 60 second outline

Here is how the questions from a typical CRM sales call might turn into a script:

• Scene 1: "Your reps live in spreadsheets." Show a messy shared sheet.
• Scene 2: "One pipeline your whole team can see." Show the board.
• Scene 3: "Bring your old deals with you." Show the import screen.
• Scene 4: "Know who to call next." Show the ranked call list.
• Scene 5: "Set up in an afternoon." Show the onboarding checklist.
• Scene 6: "Try it yourself." End card with the next step.

Common mistakes

A few patterns sink otherwise good demo videos: opening with the logo for five seconds, explaining the company before the problem, cramming in every feature, and ending without a next step. Each one spends the viewer's attention on something they did not come for.

How Igniva helps

Igniva does the first half of this work for you. It reads up to five of your sales calls, finds the questions buyers ask most, and drafts the scenes around them using your real screens and brand. You then edit the words, order and timing on a timeline. See demo videos or how it works.

Frequently asked questions

More guides