SaaS explainer video: the script, the length and the structure

A SaaS explainer video answers one question for someone who has never used your product: what is this and why would I want it? It is the video behind the "how it works" link on your homepage. Done well, it is the shortest path from a stranger to someone who understands your product. This guide covers the script, the length and the structure, and how to produce one from your site.

Explainer, demo or launch video?

These three get mixed up, and the mix-up wastes the video. They differ in the question they answer and in the person who watches:

• Explainer: "What is this?" For a cold visitor. About 30 to 60 seconds, mostly about the problem and the idea.
• Demo: "Show me it working." For someone who is considering. Mostly interface, one task, about 30 seconds.
• Launch video: "Why now?" For a feed or a launch page. Hook, reveal, three beats and a close, about 30 seconds.

Most early-stage products need one 30-second film that does a bit of all three. If you have to choose, make the explainer first, because your homepage gets visitors every day and a launch gets them once.

A six-beat script

You do not need a screenwriter. A short script of six beats covers almost every SaaS. Write one sentence per beat before you think about visuals:

1. The situation: who is doing what, in the viewer's words.
2. The friction: what goes wrong or takes too long.
3. The idea: the one thing your product does about it, in a single line.
4. How it works: two or three concrete steps, each on a piece of your real interface.
5. The proof: one fact you can state today, such as an integration, a number you publish or a platform badge.
6. The next step: where to start, with the address on screen.

The product launch video template turns the same beats into a shot list with timings, if you prefer to work from a table.

How long should it be?

Aim for about 30 seconds. At that length each of the six beats gets four to six seconds, which is enough to read one line of on-screen text twice. If your product genuinely needs 60 seconds, it usually means two ideas have been squeezed into one, and two 30-second films will do better than one long one.

Five mistakes that make explainers weak

• Starting with the company: viewers care about their problem for the first five seconds, not your history.
• Describing features in the abstract: show the feature on a real screen with one caption.
• Too many claims: three things people remember, ten things they do not.
• Invented screens: anything that is not in your product makes the real product look untrustworthy.
• No sound-off version: most plays start muted, so the captions have to carry the film.

Making one from your URL

LaunchReel AI writes this structure for you from the address of your site. It reads the home page and up to three inner pages, answers six questions about the product with sources, and drafts the brief and the storyboard. Then a code-based engine draws a film of about 30 seconds from your real colours, type and logo, with your interface elements rebuilt for the frame. Every claim in the film has to come from your pages.

From there you edit by chat: pin a shot, ask for a change, and only that shot is redrawn. That is how you try a different first line or reorder the three steps without starting again. The SaaS explainer video page and the page for SaaS founders show the flow end to end.

An example script for a scheduling tool

Here is the six-beat script for an imaginary scheduling tool, to show how little text it takes. Situation: "You are booking a call with four people in three time zones." Friction: "Twelve emails later, nobody has agreed on a time." Idea: "One link that shows everyone the times that work." How it works: "Paste your calendar, share the link, pick a slot." Proof: "Works with the calendars your team already uses." Next step: the address.

Each line fits on one shot, and each shot has one picture of the product doing what the line says. That is the whole explainer. Everything you might add beyond it, such as the story of the company or a list of every integration, belongs on your own pages.

Notice also what the script leaves out. There is no feature list, no pricing and no logo wall. Those answer different questions, for people further along, and they live on other pages of your site. The explainer's job ends when the viewer thinks "I get it" and knows where to click next.

How to know it is working

Watch the first ten seconds with the sound off and ask a colleague who has never seen the product what it does. If they can answer in a sentence, the explainer works. If they ask a question that the film should have answered, that question is the next line to add or the next shot to change, which is exactly the kind of edit that costs one shot and not a new film.

Where an explainer lives

Put the 16:9 film in the hero of your homepage or directly under the headline, and again on your pricing page where doubt is highest. Cut a 9:16 or 1:1 version of 5 to 10 seconds for social posts, and link the full one from your onboarding emails. Captions are burned in and an .srt file comes with each clean export, so the film also works with the sound off. For other product types, see the use-case pages.