How to Write a 60-Second SaaS Explainer Video Script (Template, 2026)

A good explainer video script is one audience, one problem and one promise, told in about 130 words. Most founders' first drafts try to cover every feature and end up explaining nothing. This post gives you a second-by-second structure, word counts for each part, a shot list format and a fill-in template, so you can write the script yourself in an afternoon. It is the same script stage that comes first in App369's fixed-price SaaS Launch Video, and you can use it whether or not you ever hire anyone.

Start with three decisions

Before writing a word, answer these in one sentence each:

1. Who is this for? "Freelance designers who send their own invoices", not "businesses". If you have two audiences, you have two videos.
2. What problem do they already feel? Use their words, from support tickets and sales calls, not yours.
3. What is the one promise? What changes for them after they use the product? Everything in the script either supports that promise or gets cut.

If you can't finish those sentences, the video isn't ready to script. Fix that first.

The 60-second structure

Spoken English in a product video usually runs somewhere around 130 to 160 words per minute. That is a guideline, not a rule: slower, clearer delivery suits a software demo, and you need gaps for animation and music. Plan on 120 to 140 words for a full minute and you will have room to breathe.

Hook. Open on the pain or the outcome, never on your logo or "Hi, we're...". "Chasing a client for payment again?" works because the viewer recognizes themselves in four words.

Problem. Two or three sentences describing how people cope today: the spreadsheet, the five tabs, the copy-paste. Don't mock the old way; describe it accurately.

Product in action. This is half the video. Show three steps at most, each tied to the promise. Describe outcomes, not feature names: "Clients get a reminder before the invoice is late" beats "automated notification engine". Every sentence should match something visible on screen at that moment.

Honest proof. Skip invented numbers and logos you don't have. Proof can be a real, specific capability ("every invoice links to a payment page"), a real integration, a free trial that exists, or who built it and why. If you have genuine customer results you can show and verify, use them; if not, don't hint at them.

Call to action. One action, identical to the one on the page where the video lives. "Start your free trial at example.com", said and shown on screen.

On-screen text vs voiceover

Decide early whether the video is voiceover-led or captions-only, because it changes how you write.

• Voiceover carries the explanation. On-screen text should be short labels and key phrases (three to six words), not a transcript. If the screen shows the same sentence the narrator says, viewers read faster than you speak and tune out.
• Captions-only means the on-screen text is the script. Aim for fewer words overall, because people read more slowly than they listen, and give each line a second or two longer on screen than feels natural.

Either way, write so the video works muted. Many people watch on phones without sound, and burned-in captions make that painless. YouTube also accepts uploaded caption files, which helps accessibility and search; see YouTube's help page on adding subtitles and captions.

Read the script aloud while you write it. If you stumble over a sentence, the narrator will too.

The shot list: one row per screen

Once the words work, turn them into a shot list. A simple table is enough, one row per change of screen:

Rules that keep this honest:

• Use real screens from your product with realistic test data, never real customer data.
• One idea per screen. If a row needs two sentences of explanation, split it.
• Mark the cursor path for any click you need to show, so the recording is clean on the first take.
• Cap the number of rows at about 12 to 15 for a minute. More than that and the video will feel frantic.

Fill-in-the-blanks template

Copy this into a doc and fill every bracket. If a bracket stays empty, that's your next research question.

AUDIENCE: [who]
PROBLEM (their words): [quote]
PROMISE: [after using it, they can ___ without ___]

0-5s HOOK (8-12 words)
"[Question or result that names the problem.]"

5-15s PROBLEM (20-30 words)
"[How people cope today.] [What it costs them: time, errors, stress.]"

15-45s PRODUCT IN ACTION (60-70 words)
"[Product name] [does step 1 as an outcome]."
"[Step 2 as an outcome.]"
"[Step 3 as an outcome.]"

45-52s PROOF (12-18 words)
"[One true, specific thing: capability, integration, free trial, or who built it.]"

52-60s CALL TO ACTION (10-15 words)
"[Single action] at [URL]."

Cut it to 15 seconds and vertical

Write the 60-second version first; the shorter cuts come from it. A 15-second cut keeps only the hook, one product moment and the call to action: roughly 30 to 40 words. Pick the single most visual step from the middle, not a rushed summary of all three.

For vertical, don't crop the 16:9 master. Re-lay out each screen for a 9:16 frame (1080×1920), enlarge the UI so text is readable on a phone, and keep key content away from the bottom and sides where apps overlay buttons. YouTube treats videos with a square or vertical aspect ratio, up to three minutes long, as Shorts, so a vertical cut can double as one. For more on that side of things, read how to make a SaaS launch video from your real product screens.

When to get help

You can write and produce all of this yourself. If you'd rather hand it over, App369's SaaS Launch Video is $1,500 and takes 10 business days. The script, with on-screen copy, is approved by you before anything is animated. You receive a 60-second 1080p master, a 15-second cut, a vertical 9:16 cut with burned-in captions and an SRT file, with two revision rounds. Simon makes the product videos and Shorts for his own SaaS, Workspace369, the same way. No one can honestly promise views or sign-ups from a video, and the offer doesn't.

Frequently Asked Questions

How many words should a 60-second explainer video script be?

Roughly 120 to 140 words. Normal speaking pace is often cited around 130 to 160 words per minute, but a product video needs pauses for animation and music, so aim a little under the top of that range.

How long should a SaaS explainer video be?

Sixty seconds is enough to state one problem, show the product doing one valuable thing and give a next step. If the product needs a walkthrough, make a separate, longer demo instead of stretching the explainer.

What is the best structure for an explainer video script?

Hook, problem, product in action, honest proof, call to action. Spend about half the time on the product in action, and keep a single audience and a single promise throughout.

Should I use voiceover or only on-screen text?

Either works, as long as the video also works muted. Voiceover suits longer explanations; captions-only suits short, punchy cuts. Don't repeat the full voiceover as on-screen text.

How do I make an explainer video without customer results to show?

Use honest proof you do have: what the product really does, a real integration, a free trial, or who built it and why. Leave out invented numbers and implied testimonials.