SaaS explainer video: which format your page actually needs

Three different films get ordered under the same word. Picking the wrong one is why a video costs a quarter of the marketing budget and moves nothing.

August 16, 2026 · 7 min read

A marketing lead asks for an explainer video. The studio quotes an explainer video. Everyone agrees on the word, nobody agrees on the film. Six weeks later there is a 90 second animated piece with a voice-over sitting above the fold, where visitors wanted to see the product, and a launch two weeks away with no asset that works in a feed.

The word covers at least three deliverables that share almost no craft decisions. Different lengths, different audiences, different first frames, different budgets. Ordering one and needing another is the most expensive mistake in SaaS video, and it happens before anyone opens a project file.

So the first job is not writing a script. It is deciding which of the three you are buying.

The three films that get called an explainer

They answer different questions. A viewer arrives with one of them already in their head, and the film either matches it or gets closed.

The pattern to notice: only the explainer assumes attention. The other three have to earn it or already have it for other reasons. That single difference sets length, pacing, sound design and whether the first frame can afford to be abstract.

When an explainer is the right buy

An explainer earns its cost when the product cannot be understood from a screenshot. That is a narrower case than most teams assume.

• The category is new. If you have to define the problem before you can sell the solution, prose on a page loses people and a film does not.
• The value is invisible before signup. Infrastructure, security, data plumbing, anything whose benefit is an absence of pain.
• A human explains it on every call. If your founder gives the same five minute explanation to every prospect, that explanation is the script and it is already validated.
• The buying committee includes someone who never opens the app. A finance or legal stakeholder needs the mechanism, not the interface.

And when it is the wrong buy: the product is self evident in one screenshot, the real objection is pricing rather than comprehension, or the actual need is something that survives two seconds in a feed. In that last case you want a teaser, and calling it an explainer will get you 90 seconds of animation that nobody on social will ever finish.

The placement sets the length, not the ambition

Length is not a taste question. It is a function of where the video sits and what the viewer was doing one second before it started.

The above the fold row is where most SaaS explainers die. A film built for a dedicated page gets dropped into the hero, where it opens on a logo animation and a slow abstract shape, and the visitor leaves before the product appears. Same file, wrong slot, wasted spend.

What the first ten seconds have to contain

Every explainer that works front loads the same four things. Every one that fails saves them for later, in the belief that setup buys patience. It does not.

1. 01The problem, stated as a situation the viewer recognizes, not as a category noun.
2. 02The product, on screen, doing something. Real interface, not a floating rectangle standing in for one.
3. 03The one claim you want repeated, written on screen so it survives the sound being off.
4. 04A reason to keep watching, usually the part of the mechanism that is not obvious.

Notice that three of the four are visual. An explainer that only works with the voice-over playing is a podcast with pictures, and it will be watched muted more often than not, even on a page where someone chose to press play.

Build one system, cut every format from it

The reason teams end up with the wrong format is sequencing. They commission a single film, discover the gaps at launch, and then commission more films from scratch, each with its own look. Three productions, three visual languages, one incoherent brand.

The cheaper order is to build the visual system first: type, motion behavior, color, how the interface is framed, how numbers appear. Once that exists, the explainer, the product film and the feed cuts are recuts of one build rather than three separate jobs. This is the same logic behind the four decisions in our post on the product launch video, and it is how our Launch Sprint is sequenced: narrative and visual micro system first, assets after.

If what you need this week is only the feed cut, there is a faster route and we should be clear that it is ours: ShipTeaser is a product built by the same founder as this studio. You paste a product URL and it returns a 15 second 1080p motion graphics teaser designed for muted feeds, with an optional music bed and the first video free without a card. It is deliberately not an explainer: there is no voice-over, no screen recording, no timeline to edit, and it will not give you a visual system your other pages can inherit. For a teaser you need on Thursday it is the right tool. For the film that has to make a new category understandable, it is not.

The one page brief that prevents the rework

Before you talk to any studio, freelancer or internal designer, write these five lines. They take twenty minutes and they settle every argument that would otherwise happen during revisions, when changes are expensive.

• Format, named: explainer, product film, teaser or brand film. One of them.
• Placement, named: the exact page or feed, with the length that placement allows.
• One claim, written as a single checkable sentence a viewer could repeat.
• The mechanism, in three steps maximum. If it needs five, the film is too early.
• The action at the end, and where it leads.

A studio that gets that page back writes a script that is close on the first pass. A studio that gets "we need an explainer, here is our deck" writes three scripts, and you pay for the two you throw away.