How to Write a SaaS Explainer Video Script That Works

Every studio will tell you animation is the expensive part of an explainer. That's true on an invoice. But in my experience most SaaS explainer videos that don't work were already broken at the script stage, and no amount of polish afterwards could save them. A script problem costs an hour to fix. The same problem discovered after animation costs a week.

So this is the guide I wish more teams had before they sent us their first draft. How long a SaaS explainer video script should be, a structure that works for most software, how to write lines that survive contact with the screen, and the habits that turn a clear product into a confusing minute of video. If you'd rather hand the writing to someone else entirely, that's fine too. The last section covers how we do it.

Start inside the product, not the pitch deck

The first draft most teams send is their homepage copy read aloud. "An all-in-one platform that streamlines your workflow and empowers your team." It's grammatical, it's on-brand, and a viewer forgets it before the sentence ends, because it describes ten thousand other products too.

What separates your product is what it looks like when it works: the specific screen, the specific moment where the manual version of the job collapses into one step. So before we write a word, we get into the product, ideally with a demo login, and look for the one realistic task that proves the value fastest. One journey, start to finish. That journey becomes the spine of the script.

That's also how we approached the product intro for EmailFunnelAI: the script follows a single real workflow, describing an offer and watching the sequence assemble, rather than narrating a feature grid.

Your word budget, by length

Length decides how much you can say, and most drafts try to say about twice as much as the length allows. As a working rule, narration at a natural, unhurried pace runs somewhere around 130 to 150 words a minute. Leave room for moments where the screen speaks and nobody talks.

If your draft is 250 words and you want a 60-second video, you don't need a faster voiceover. You need to cut half the ideas.

A five-beat structure for most SaaS explainers

This isn't the only shape that works, but it's the one I start from for a 60-second landing page explainer.

1. The situation (about 5 seconds). One line that names the job the viewer is trying to do, and how it goes wrong today. Specific, not dramatic. "Chasing late invoices across three spreadsheets" beats "Are you tired of wasting time?"

2. The turn (about 5 seconds). The product appears, doing something. Not a logo, not a tagline. The first frame of the product at work.

3. The journey (30 to 40 seconds). The one realistic task, shown step by step, at close to real speed. Each line of narration matches one screen. This is where most of the words go.

4. The payoff (about 5 seconds). What the viewer has at the end that they didn't have at the start. A result they can see on screen.

5. The ask (about 5 seconds). One action. Start a trial, book a demo, install the plugin. Just one.

Write the script and the screen plan together

A script only means something once you can see what's on screen while it's read. So we write in two columns: the words on one side, the screen on the other. You approve both together.

VOICEOVER                                  SCREEN
"Every Friday, you rebuild the same        Spreadsheet, three tabs, cursor
 invoice report by hand."                  hunting between them.
 
"With Ledgerly, you connect your bank      One click on "Connect". Accounts
 once."                                    animate into a single list.
 
"Late invoices surface on their own,       Overdue rows lift out, sorted,
 oldest first."                            with a red age badge.
 
"And a reminder goes out in one click."    Cursor clicks "Send reminder".
                                           Tick animates in.

"Ledgerly" is a made-up product, but notice what the two columns force. Every line has a screen. No line narrates the obvious ("now click the blue button"). And the viewer never hears about something they can't see.

A before-and-after, line by line

Picture a two-person team selling scheduling software to physiotherapy clinics. Their first draft opens: "ClinicFlow is a powerful, intuitive platform that revolutionises how modern practices manage their time."

Everything in that sentence is an adjective or a claim. Here's roughly how we'd rework it:

• Before: "A powerful, intuitive scheduling platform."
• After: "A patient cancels at 8am. By 8:02, the slot's been offered to your waiting list."

The second version is longer, but it's a scene. The viewer sees a cancellation, sees the slot move, and understands the product without being told it's powerful. That's the trade I'd make in almost every script: fewer claims, more moments.

Lines that survive the edit

A few rules I apply to every draft before it goes anywhere near animation.

• Write for the ear. Short sentences. Contractions. Read it aloud; if you stumble, the voice artist will too.
• One idea per line. Each line should map to one screen or one beat.
• Name what's on screen, don't describe the interface. "Late invoices surface on their own" beats "In the left-hand panel, under Reports…"
• Cut the adjectives. Powerful, intuitive, all-in-one. The screen proves those or it doesn't.
• Make it work muted. Most people meet a landing page video with the sound off, so key points need on-screen type, not just narration.
• Leave room for silence. A two-second pause while something happens on screen is often the strongest moment in the video.

The mistakes that break explainers

The most common one is the feature tour: seven features in sixty seconds, each getting a line and a screen, none getting enough time to matter. Viewers remember one thing from a short explainer. Choose it.

Close behind is jargon your customers don't use. If your team says "workflow orchestration" and your customers say "the Monday report", write "the Monday report".

Then there's writing before the product is stable. If a redesign is coming, tell your studio at the brief stage. We'd build around abstracted UI rather than pixel-exact screens, so the video survives the next release. And finally, the script that tries to be the landing page, the onboarding guide and the sales demo at once. Those are different videos, which is why we plan cutdowns and a separate tutorial video rather than stretching one script over every job. Our post on why SaaS companies need explainer videos covers where each fits in the funnel.

Should you write it, or should we?

Write it yourself if you have someone who knows the product deeply, can write plainly and has time for three or four drafts. Use the structure and the two columns above and you'll be ahead of most first drafts we see.

Hand it over if your team is too close to the product to see what's confusing, which is more common than people admit. Founders especially tend to explain the architecture rather than the outcome.

How we script and produce SaaS explainers

On our SaaS explainer video service, we write the script as standard. Send whatever messaging you already trust, landing page copy, a sales deck, the answer you give on demo calls, and we turn it into a script built for the screen.

1. Product teardown. We get into the product and recommend, in writing, the one journey that proves the value fastest.

2. Script and screen plan. A word-for-word script paired with a shot-by-shot plan. You approve both before anything is animated.

3. Capture and design pass. Screens are captured and rebuilt as motion, with a styleframe for sign-off.

4. Animation, voice and sound. The full edit, built muted-first, then voiceover and sound design on top. A professional voiceover read is quoted as an add-on, by word count and licence territory.

5. Delivery and cutdowns. Masters in every ratio you need, captions burned in plus .srt and .vtt files, poster frames, and the editable project files.

The entry point is Solo Starter: $200 for one explainer under 60 seconds, with a 3-day turnaround and one revision round. Solo Launch at $300 adds a walkthrough, a tutorial and reels; Startup Boost at $550 adds a feature-specific explainer under 90 seconds and three revision rounds. The packages page lists everything each tier includes, and our breakdown of what drives explainer video cost explains where the money goes.

Frequently asked questions

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

Roughly 130 to 150 words at a natural pace, and often fewer. A script with pauses where the screen does the talking usually lands closer to 110 or 120. If you're well over 150, cut ideas rather than speeding up the read.

How many features should a SaaS explainer cover?

For a landing page explainer, one journey that shows the core value. Other features can appear in passing if they're part of that journey. If you need to cover several features properly, make separate short feature explainers or a longer walkthrough.

Should an explainer video script include a call to action?

Yes, one. End on a single clear action, such as starting a trial or booking a demo, held on screen long enough to read. Offering three different actions at the end usually means none of them get taken.

Can you write the script from our existing website copy?

Yes. Website copy, a sales deck or notes from demo calls are all useful starting points. We rewrite them for the ear and pair every line with a screen, then send the script for your approval before animation starts.

Do we need a finished product to write the script?

No. A demo login is ideal, clean screen recordings work almost as well, and a Figma file of the screens works when a feature isn't built yet. If the UI is about to change, we write against abstracted screens.

The takeaway

A SaaS explainer video script works when it's built around one real journey through your product, sized to its word budget, and written in two columns so every line has a screen. Cut the adjectives, show the moment the job gets easier, and ask for one thing at the end.

If you want us to find that journey and write the script for you, our SaaS and app explainer videos start at $200 with the script included, and the fixed-price packages show what larger kits add. When you're ready, send us a demo login and a line about your customer and we'll come back with a recommended journey.