# SaaS Explainer Video Script Template: Timed 30, 60 and 90-Second Versions

> Free SaaS explainer video script template with timed 30, 60 and 90-second versions, a filled-in example and a checklist you can copy for your launch.

Canonical: https://www.clickcast.tech/blog/saas-explainer-video-script-template
Last updated: 2026-10-24

By ClickCast Team · October 24, 2026 · 10 min read · Guides

A SaaS explainer video script template is a fill-in outline of six timed beats: hook, problem, product, workflow, proof and call to action. For a 60-second video, write about 150 words: roughly 12 for the hook, 25 for the problem, 18 to introduce the product, 55 for the workflow, 18 for proof and 20 for the call to action.

Below you get that template in three lengths, a filled-in example for a fictional SaaS product, a review checklist, and the mistakes that make founder-written scripts sound like a feature list. If you would rather skip the blank page, the free [SaaS demo video script generator](https://www.clickcast.tech/free-tools/saas-demo-video-script-generator) fills the template from three inputs.

## Key takeaways

- **Six beats, one story.** Hook, problem, product, workflow, proof, call to action. Each beat does one job.
- **The workflow beat is the longest.** Show your product doing one job, from start to result, in about 40% of the runtime.
- **Write to a word budget.** At 150 words per minute, 30 seconds holds about 75 words, 60 seconds about 150 and 90 seconds about 225.
- **One audience, one problem, one call to action.** A script that tries to speak to everyone or show every feature stops landing for anyone.
- **Write for the ear.** Short sentences, spoken numbers, and no words your customer wouldn't say out loud.

## What is a SaaS explainer video script?

A SaaS explainer video script is the narration and scene plan for a short video that tells a prospect what problem your software solves, shows it solving that problem, and asks them to take one next step. It usually runs 30-90 seconds and lives on a landing page, a launch page or a social post.

It is different from a sales demo script. Leadde's guide puts the distinction well: a demo [shows how the product works in detail](https://leadde.ai/blog/saas-explainer-video-script), while an explainer helps the viewer understand the product's value quickly. A good SaaS explainer contains a short demo, but only the part that proves the value.

## What structure should a SaaS explainer script follow?

Use the six-beat structure below. It is the same problem-to-solution arc most guides recommend, with two SaaS-specific changes: the product introduction is a single sentence, and the workflow gets the biggest share of the time because seeing the UI is what convinces a software buyer.

| Beat | Job | 60-second timing | Word budget at 150 WPM |
|---|---|---|---|
| 1. Hook | Name a pain the viewer already feels | 0:00-0:05 | ~12 words |
| 2. Problem | Show what the pain costs them today | 0:05-0:15 | ~25 words |
| 3. Product | Introduce your product in one sentence | 0:15-0:22 | ~18 words |
| 4. Workflow | Show the product doing one job, start to result | 0:22-0:45 | ~55 words |
| 5. Proof | One concrete reason to believe it | 0:45-0:52 | ~18 words |
| 6. Call to action | One next step | 0:52-1:00 | ~20 words |

The word budgets come from simple arithmetic: seconds × 150 ÷ 60. We explain the narration-pace math in [how many words fit in a 60-second SaaS demo video](https://www.clickcast.tech/blog/how-many-words-in-a-60-second-script).

## The SaaS explainer video script template (60 seconds)

Copy this, replace everything in square brackets, and keep each beat inside its word budget.

**Beat 1: Hook (0:00-0:05)**
> Still [doing the painful task] by hand every [day/week]?

*On screen: the messy "before": a spreadsheet, a stack of tabs, a manual process your buyer recognises.*

**Beat 2: Problem (0:05-0:15)**
> For [your customer], that means [concrete cost: hours lost, errors, missed revenue]. And every time [trigger], you start over.

*On screen: the cost made visible: a clock, a pile of tickets, a failed export.*

**Beat 3: Product (0:15-0:22)**
> [Product] is the [category] that [does the job] for [your customer].

*On screen: your logo, then your product's main screen.*

**Beat 4: Workflow (0:22-0:45)**
> [Step 1: connect / import / paste]. [Step 2: the key action]. [Step 3: the result appears]. That's it: [the outcome, in their words].

*On screen: three clean shots of your UI, one per step, zooming in on the part that matters.*

**Beat 5: Proof (0:45-0:52)**
> [One true proof point: a real customer number, a named integration, a free plan, or how long setup takes].

*On screen: the proof itself: a logo row, an integration badge, a result screen.*

**Beat 6: Call to action (0:52-1:00)**
> [Start free / Try it on your own data] at [yourdomain.com].

*On screen: the URL and one button. Nothing else.*

Only use proof you can back up. If you don't have customer numbers yet, a factual product claim works: "Set up in two minutes," "Works with Stripe and HubSpot," or "Free for your first 100 invoices," as long as it is true.

## How do you adapt the template for 30 and 90 seconds?

Keep the six beats and change how much each one gets. Shorter videos merge beats; longer ones add a second workflow step, never a second product.

| Beat | 30 seconds (~75 words) | 60 seconds (~150 words) | 90 seconds (~225 words) |
|---|---|---|---|
| Hook | 0:00-0:03, ~8 words | 0:00-0:05, ~12 words | 0:00-0:06, ~15 words |
| Problem | merged into the hook | 0:05-0:15, ~25 words | 0:06-0:20, ~35 words |
| Product | 0:03-0:08, ~12 words | 0:15-0:22, ~18 words | 0:20-0:28, ~20 words |
| Workflow | 0:08-0:22, ~35 words | 0:22-0:45, ~55 words | 0:28-1:10, ~105 words |
| Proof | skip or 3 words on screen | 0:45-0:52, ~18 words | 1:10-1:20, ~25 words |
| Call to action | 0:22-0:30, ~20 words | 0:52-1:00, ~20 words | 1:20-1:30, ~25 words |

Which length should you pick? Use 30 seconds for social teasers and paid ads, 60 seconds for a landing page hero, and 90 seconds for a Product Hunt gallery or a launch post where viewers have chosen to learn more. Our guide on [how long a SaaS demo video should be](https://www.clickcast.tech/blog/how-long-should-a-saas-demo-video-be) covers each placement with sources.

Shorter is a safe default for public pages. Wistia's [analysis of over 13 million videos](https://wistia.com/blog/optimal-video-length) found videos under one minute average a 52% engagement rate, and Nielsen Norman Group found that [users often leave web pages within 10-20 seconds](https://www.nngroup.com/articles/how-long-do-users-stay-on-web-pages/). That is why the hook and problem have to land in the first 15 seconds.

## Filled-in example: a 60-second script for a fictional SaaS

Here is the template filled in for "Ledgerly", a made-up invoicing tool for small agencies' finance leads. The product is fictional; the structure is the point.

> **Hook:** Still chasing late invoices by email every Friday?
>
> **Problem:** For a ten-person agency, that's hours a month spent writing the same polite reminder. And when one slips, you find out at payroll.
>
> **Product:** Ledgerly is the invoicing tool that follows up on unpaid invoices for you.
>
> **Workflow:** Connect your accounting software. Pick a reminder schedule: three days before due, on the day, a week after. Ledgerly sends each reminder from your own address, with a pay-now link. When the client pays, the invoice marks itself paid and the reminders stop. That's it: you stop chasing, and you still sound like you.
>
> **Proof:** It works with the accounting tool you already use, and setup takes one afternoon.
>
> **Call to action:** Start your free trial at ledgerly.example and send your first automatic reminder today.

That script is 125 words, which runs about 50 seconds at 150 words per minute and leaves roughly ten seconds of breathing room for on-screen moments and the closing URL. Paste your own draft into the [SaaS demo video script timer](https://www.clickcast.tech/free-tools/script-duration-calculator) to check yours.

Notice what it leaves out: no feature list, no company history, no "revolutionary" or "all-in-one". Every sentence moves the viewer from "that's my problem" to "I can see it working" to "I'll try it".

Want to see your script as a finished video before you spend a weekend recording? **[Paste your website URL into ClickCast](https://www.clickcast.tech/url-to-video)**: it writes a script from your site, captures your product and adds a natural AI voiceover, so you can compare its draft against yours.

## How do you write each beat so it sounds natural?

Write the way your customer talks about the problem, not the way your homepage describes the product. Read every line aloud; if you run out of breath or stumble, the sentence is too long.

### The hook: start with their pain, not your name

The first five seconds decide whether anyone hears the rest. Open with a question or statement your buyer would nod at: "Still copying Stripe data into a spreadsheet?" beats "Introducing Ledgerly". Never open with your logo or a greeting.

### The problem: make the cost concrete

Name the time, money or risk the problem costs. "Hours a month" or "you find out at payroll" works because the viewer can picture it. Only use numbers you can source; a vivid situation beats an invented statistic.

### The product line: one sentence, plain category

Use the formula "[Product] is the [category] that [job] for [customer]." If a stranger couldn't repeat it back after one listen, simplify it. Save clever taglines for your headline.

### The workflow: three steps, one job

Pick the single job that makes new users stay, then show it in three steps: setup, the key action, the result. Show only the screens that move the story forward, and end on the result screen, not on a settings page.

### The proof: one thing, and true

One proof point is stronger than four weak ones. Good options for an early-stage SaaS: a named integration, a free plan, setup time, or a real number from a real customer who agreed to be quoted. Never invent testimonials or user counts.

### The call to action: one verb, one place

"Start free at yourdomain.com" is enough. Pointing viewers to a trial, a waitlist and a demo call at once splits attention. Match the call to action to the page: "Start free" on a landing page, "Upvote and try it" on a launch post, "Join the waitlist" before launch.

## Explainer script vs demo script vs launch script: which do you need?

Most SaaS founders need all three eventually, and the six-beat template adapts to each by changing the balance between story and product.

| Script type | Where it plays | Typical length | What changes in the template |
|---|---|---|---|
| Explainer | Landing page hero, ads | 30-60 sec | Full hook and problem; short workflow |
| Product demo | Onboarding, sales follow-up | 60-180 sec | Short hook; long workflow with several jobs |
| Launch video | Product Hunt, launch posts, AppSumo | 60-90 sec | Hook names what's new; proof can be "launching today" plus an offer |
| Feature announcement | Changelog, in-app, email | 20-45 sec | Skip the problem; show the new feature's workflow only |

For launch day specifics, see our [Product Hunt launch guide](https://www.clickcast.tech/blog/product-hunt-launch-guide-tips). For release videos, the [SaaS feature announcement video guide](https://www.clickcast.tech/blog/saas-feature-announcement-video) has a shorter variant of this structure. More examples of finished videos live on our [SaaS explainer videos](https://www.clickcast.tech/saas-explainer-videos) page.

## What are the most common SaaS script mistakes?

The most common mistake is listing features instead of showing one job done well. These are the others we see most often in founder-written scripts:

1. **Opening with the company name.** Viewers don't care who you are until they know you solve their problem.
2. **Describing the product in internal language.** "Unified workspace orchestration" means nothing to a buyer. Use the words from your support tickets and sales calls.
3. **Writing too many words.** A 60-second video with 200 words forces a rushed voiceover. Stay inside the budget.
4. **Narrating every pixel.** Let the UI breathe. If a result animates on screen, a two-second silence is fine.
5. **Unsupported claims.** "Trusted by thousands" without proof hurts trust. Use one true proof point instead.
6. **Several calls to action.** Pick the one next step that matters for that page.
7. **Writing numbers the way they're typed.** Write "forty-nine dollars a month", not "$49/mo", so the voiceover reads it correctly.

## Script review checklist

Run your draft through these eight checks before you record or generate the video:

1. The first sentence names a pain your buyer already feels.
2. Your product is described in one sentence a stranger could repeat.
3. The workflow shows one job in three steps, ending on a result.
4. The word count fits your length at about 150 words per minute.
5. Every claim and number is true and can be backed up.
6. There is exactly one call to action, matched to the page.
7. Read aloud with a timer, it lands within five seconds of the target.
8. It still makes sense with the sound off, using on-screen text.

## Frequently Asked Questions

### What is the best structure for a SaaS explainer video script?
Six beats in this order: a hook that names the customer's pain, the problem and what it costs them, your product in one sentence, a short workflow showing the product solving it, one piece of proof, and one call to action. Spend most of the time on the workflow.

### How many words should a 60-second SaaS explainer script have?
About 150 words at a natural narration pace of 150 words per minute. Write closer to 135-140 words so the video has room for on-screen moments without narration. A 30-second script holds about 75 words and a 90-second script about 225.

### What is the difference between an explainer script and a demo script?
An explainer script sells the idea: why the problem matters and what changes when it is solved, with a short look at the product. A demo script walks through the product itself in more detail. For a landing page hero or a launch, most SaaS founders need an explainer that includes a short demo section.

### Should a SaaS explainer video mention pricing?
Only if price is a reason to buy, for example a free plan or a much lower price than the tool your buyer uses today. Otherwise leave it out and point the call to action at a free trial or signup, where your pricing page does the job.

### Can I generate a SaaS explainer script for free?
Yes. ClickCast's free SaaS Demo Video Script Generator fills this template from your product name, your customer and the problem you solve, and gives you a timed script for 30, 60 or 90 seconds. It runs in your browser and needs no signup.

## Turn your script into a video

A good script is most of a good explainer video. Fill in the six beats, cut to your word budget, and run the checklist. Then let ClickCast do the production: it turns your website URL into a narrated SaaS explainer video in minutes, so your launch page has a video before launch day.

**[Create your SaaS explainer video free →](https://www.clickcast.tech/url-to-video)**

Tags: SaaS Explainer Video, Video Script, Product Demo, SaaS Marketing

## Related

- [All ClickCast blog posts](https://www.clickcast.tech/blog)
