The 90-Second Explainer Script Structure That Converts
A line-by-line script template — problem, stakes, mechanism, proof, action — with word counts, pacing rules and the mistakes that kill comprehension.
An explainer video has one job: make a stranger understand and want your product in under two minutes. Most fail because they were written like a feature tour.
This is the structure I use — with word counts, because pacing is a maths problem before it's a creative one.
Table of contents
1. The maths of 90 seconds
Comfortable narration runs about 140–150 words per minute. Ninety seconds gives you roughly 210 words.
That's it. Write your first draft freely, then cut to 210 and watch how quickly the non-essential claims fall away.
Every word you keep should earn its place against a clear alternative.
2. Seconds 0–10: the problem in their words
Open on the frustration, phrased exactly as your customer would say it in a meeting. No brand name yet, no product.
Roughly 25 words. If the viewer nods here, they'll stay for the rest; if they don't recognise themselves, nothing later matters.
3. Seconds 10–25: the stakes
What the problem costs, made concrete. Hours, revenue, risk, credibility.
About 35 words. This is the section teams most often skip, and skipping it is why so many explainers feel informative but not persuasive.
4. Seconds 25–60: the mechanism
Now introduce the product and show how it works in three steps, not eleven features. Around 85 words, with the animation carrying the specifics your narration doesn't have room for.
Visual and voice should never say the same thing at the same time — that redundancy wastes your scarcest resource.
5. Seconds 60–80: proof
One number, one customer type, one outcome. Roughly 35 words.
'). Placing it earlier tends to be forgotten.
6. Seconds 80–90: one action
One CTA, spoken and on screen for at least two seconds, phrased as a low-risk next step. About 20 words.
Never end an explainer with three options; the viewer's decision energy is already spent.
Explainers convert when they respect the clock and the viewer's scepticism. Problem, stakes, mechanism, proof, action — 210 words, one idea per beat.
Write to the structure and the animation gets easier too.
Key takeaways
- Comfortable narration runs about 140–150 words per minute.
- Open on the frustration, phrased exactly as your customer would say it in a meeting.
- What the problem costs, made concrete.
- Now introduce the product and show how it works in three steps, not eleven features.
- One number, one customer type, one outcome.
- One CTA, spoken and on screen for at least two seconds, phrased as a low-risk next step.
Frequently asked questions
Who is this explainer videos guide for?+
Founders, marketers and creative leads who want a practical, no-fluff playbook on explainer video. If you own a growth or brand outcome and need something you can act on this week, you're in the right place.
How long does it take to see results?+
Most teams start seeing early signal within 2–4 weeks of applying the ideas here. Compounding results — the kind that change your unit economics — usually show up between weeks 8 and 12 once the loops are running consistently.
Do I need a big budget to implement this?+
No. Everything in this article is designed to work with the resources you already have. Bigger budgets can accelerate outcomes, but the frameworks themselves compound on discipline, not spend.
Where should I start if I only have one hour?+
Read the Key Takeaways at the bottom, pick the single item that maps to your biggest bottleneck this quarter, and ship one small change before the end of the day. Momentum beats perfection.
Want a system like this built for your brand?
I help ambitious teams turn scattered marketing into a predictable growth engine — SEO, paid, brand video, AI and CRO working together.
Book a strategy call