SaaS Explainer Videos: What Actually Drives Sign-Ups
Most explainer videos describe the product. The ones that convert describe the problem for long enough that the viewer recognises themselves in it.
The average SaaS explainer video opens with a logo, a swelling track and a sentence about how the modern workplace is changing. By the time it reaches the product, most of the audience has gone.
We build these and we measure them. Here is what the retention data consistently says.
The First Eight Seconds Decide Everything
On a product page, a viewer who presses play has already given you intent. What they have not given you is patience. The drop between second three and second eight is the largest single fall in almost every explainer we have measured.
What survives that window is a specific problem stated in the viewer's own words. What does not survive it is a company introduction, a mission statement, or an animated logo.
The Structure That Converts
0 to 8 seconds: the problem, named specifically
Not "managing data is hard" but the actual moment of friction: the spreadsheet that three people are editing, the report that takes a day to assemble. The viewer should recognise themselves before they hear your product name.
8 to 20 seconds: the shift
What becomes true once this is solved. Still not the product. The outcome, stated as a change rather than a feature.
20 to 60 seconds: the product doing the thing
Real interface, real data, one path through it. Not a feature tour. One job, done start to finish, so the viewer can imagine themselves doing it.
60 to 80 seconds: proof
A number, a customer, an integration they already use. One is enough.
80 to 90 seconds: one action
One call to action, matching the button next to the video. Two calls to action is a choice, and a choice is a delay.
Ninety seconds is the ceiling for a page-level explainer. Anything you cannot fit belongs in a second, longer video for people who have already decided they are interested.
Where The Video Should Sit
- Above the fold, but not auto-playing with sound. Autoplay with sound loses more than it gains on a product page.
- Next to the sign-up action, not replacing it. The video is a support for the decision, not a gate in front of it.
- With a real thumbnail. A frame from the interface outperforms a stylised title card, because it previews what the viewer is about to get.
- Captioned by default. A large share of first views happen with the sound off, and a video that is unusable silently is a video most people never really watch.
What We Measure Afterwards
Play rate, which tells you whether the thumbnail and placement work. Average view duration, which tells you whether the script works. The retention curve, which tells you exactly where it stops working. And sign-up rate for viewers versus non-viewers on the same page, which is the only number that answers whether the video was worth making.
That last one is the one almost nobody instruments, and it is the one that decides whether you make a second video. We publish our own retention numbers in the retention data nobody publishes.
We build product and SaaS explainers as a studio that runs its own channels, which means you get the retention numbers with the invoice rather than a vague sense that it went well.
See The ServiceOne Video Or Several?
Most teams commission one explainer and expect it to work on the homepage, the pricing page, in a sales email and at the top of a paid campaign. It will underperform in at least three of those, because the viewer arrives with a different amount of context each time.
A more useful split, and usually not much more expensive if it is scoped together from the start:
- A sixty second product page video. The problem, the shift, one job done end to end. This is the one most teams already have.
- A twenty second paid social cut, from the same material, opening on the sharpest moment rather than the setup. Different audience, no context, no patience.
- A three to five minute walkthrough for people who have already booked a demo or started a trial. Nobody watches this cold, and everybody watches it once they have decided to care.
Shot and produced together, the second and third are largely edits of the first. Commissioned separately six months apart, they are three projects. This is the clearest example of why deliverables belong in the original brief, which we cover in how to brief a production company.
Three Things To Stop Doing
- The feature tour. Seven features at ten seconds each is a video that shows everything and communicates nothing. Pick one job.
- The generic animated character. The abstract figure walking past floating icons has been in every explainer for a decade and it tells a viewer nothing about your product.
- The mission statement ending. The last eight seconds are the most valuable in the film. Do not spend them on a slogan when they could carry an action.
Common questions
- How long should a SaaS explainer video be?
- Ninety seconds is the ceiling for a product page. Sixty is usually better. Anything longer belongs in a second video for people who are already interested.
- Animated or screen recording?
- Real interface wherever the interface is presentable. Animation is for what a screen cannot show, such as what happens between systems.
- Should the video autoplay?
- Muted autoplay is usually fine. Autoplay with sound on a product page loses more visitors than it converts.