SaaS
SaaS Explainer Video Production
SaaS explainer video production is the work of making software obvious in 30–90 seconds — who it is for, what is broken, what changes — without dumping every feature. It is not a screen recording. We write the script from the real product, then animate: UI when the interface is the proof, metaphor when it is the confusion. Most films deliver within 3 days once the brief is clear.
By Jonathan Maynard, Knowlify Studio
Updated August 26, 2026 · 7 min read
What a SaaS explainer has to do
It has to make a complex product feel obvious in under 90 seconds without becoming a feature dump. The viewer should leave knowing who it is for and what changes if they switch.
A SaaS explainer is a short animated film for software — usually 30–90 seconds — built for people who have not sat a demo. It is not a tour of the app. It is the argument: this is the job, this is what is broken today, this is the change, this is the next step.
That is a narrower job than SaaS video production as a whole. Production can also mean demos, feature launches, and onboarding. The explainer is the homepage film. If you only make one this quarter, make this one.
Feature lists belong in the page body. The film has to survive without them. If you mute it and still cannot tell who it is for, the script is not done.
SaaS explainer vs screen recording
A screen recording shows the product to someone who already cares. A SaaS explainer has to create that care first. Cold homepage traffic rarely has the patience for a raw click-through.
Recordings are useful. They are the wrong first hire when the visitor does not yet know why the product exists. They also date the minute you ship a UI change, and they hide the story behind whoever happened to click.
An animated explainer can still show the real interface — we do this when the UI is the proof, as with Jude’s workflow from prompt to document. The difference is direction. The pictures are chosen to carry the claim. The recording is not the claim.
Use a recording later, for people who asked to see it. Use the explainer on the page that has to do the convincing.
UI story vs metaphor
Some products need to see the actual interface. Others need a simple metaphor first. We pick based on whether the UI is the proof or the confusion.
If the product looks like the value — a document appearing, a credential issuing, a workflow completing — show the UI. Hide chrome that does not help the sentence. Accuracy still matters. Fake screens that do not match the app train distrust.
If the product is infrastructure, API, or a category the buyer cannot picture yet, start with a metaphor, then land on one real moment of the product. Metaphor-only films feel clever and still leave people unable to describe what you sell.
| Approach | Use when | Our example |
|---|---|---|
| UI story | The interface is the proof — a document appearing, a credential issuing | Jude — prompt to finished document |
| Metaphor first | The product is infrastructure or a category the buyer cannot picture yet | Land on one real product moment after the metaphor |
We decide this in the script, not in a style moodboard. Style follows the claim.
How long a SaaS explainer should be
Most SaaS explainers we produce land in 30–90 seconds. That is enough for the problem, the change, and one ask. A two-minute “everything the platform can do” is usually two films.
Spoken English is roughly 130–150 words a minute. A 60-second explainer is a 130–150 word script. If product wants every module named, cut the film in half: homepage for the job, a second film for the module that actually needs a launch. Wyzowl 2026 reports 71% of marketers prefer 30 seconds–2 minutes; we produce most SaaS explainers in the 30–90 second slice of that.
Feature launches can be shorter. AccessGrid’s credential-pools film is 31 seconds — one capability, one reason it exists. That is still explainer work. It is not the homepage story.
Jude · 1:48Conference explainerA full product story that walks a legal-tech workflow from prompt to finished document. AccessGrid · 0:31Credential Pools launchShort launch film for AccessGrid’s credential-pool feature — how newly issued passes get credentials automatically.
How we produce a SaaS explainer
Script first, then direction, then animation and voice — from the real product. Most films deliver within 3 days once the brief is clear. You own the files.
We need access to the product or a tight walkthrough, the page the film will live on, and the one action. We write the script, lock it, then animate. Revisions stay cheap while it is still words.
Humans direct and finish every video. The quote covers script, design, animation, voiceover, music, revisions, and delivery — not a teaser price for “animation” with the rest as extras. We do not publish a rate card; the film you need is the quote.
Book a free 15-minute Video Strategy Audit if you want to know whether you need a SaaS explainer, a demo, or a feature cut first.
Frequently asked questions
What is SaaS explainer video production?
- Writing and animating a short film that makes software make sense to a first-time viewer — usually 30–90 seconds — for a homepage, launch, or sales loop. Script, direction, animation, voiceover, and revisions.
How is a SaaS explainer different from a product demo?
- The explainer is the reason to care. The demo shows the product in use. Homepage first, demo second — once someone is already considering a trial.
Should we show our real UI?
- Yes, when the interface is the proof. Use a metaphor first when the UI would confuse a stranger. Fake screens that do not match the product train distrust.
How long should a SaaS explainer be?
- Most of ours land in 30–90 seconds. Feature launches can be shorter. If the script wants two minutes of modules, you probably need two films.
How do we start?
- Book a free 15-minute Video Strategy Audit. We will tell you whether you need an explainer, a demo, or a feature cut first — then quote one done-for-you film.