Most explainer videos fail the same way: they spend 90 seconds describing what a product does, then drop a logo at the end and call it done. The viewer learned something, but they didn’t do anything. The gap between informed and convinced is where most explainers die.
Start With the Gap, Not the Features
An explainer video has one job: close a specific gap in the viewer’s understanding that is stopping them from taking the next step. That job is almost never “explain the product.” It’s more often “make the product feel worth the risk” or “help the viewer see themselves in the outcome.”
The distinction changes everything you put in the video. A demo fills in feature gaps. A testimonial fills in credibility gaps. An explainer fills in the understanding gap. Before scripting a single line, name the gap. A viewer who lands on your site knowing nothing is a different brief from a viewer who has already read the pricing page and is still stalling.
Who you are writing for
Most explainer briefs describe a market segment: “B2B SaaS companies” or “first-time homeowners.” That is a sales definition, not a writing brief. For the video to work, you need a person: someone with a specific problem, a specific level of awareness, and a specific objection they are walking in with. The narrower the person, the cleaner the script.
Script First, Visuals Second
The most common production mistake is running the script and visual direction in parallel, or worse, designing the storyboard before the words are locked. Visuals built to fit a locked script will always be sharper than visuals conceived independently and then asked to match a voiceover.
A good explainer script reads at 130–160 words per minute at a natural pace. A 60-second video is roughly 150 words. A 90-second video is around 210. That constraint is useful: it forces you to cut the parts that feel important but aren’t. Most first drafts are about 40% longer than they need to be. If you are starting from scratch, read how to write a video script before you open any animation software.
The script is the product. The visuals are delivery.
The structure that reliably works: open with the problem, not the solution. Spend the first third on the tension the viewer already recognises. Introduce the solution in the middle, anchored to the emotional shift, not the feature list. Close with what happens next and a clear, specific action.
Animation Style Is Not a Taste Decision
The visual style of an explainer carries meaning independent of its content. Flat 2D motion graphics read as scalable, clean, slightly corporate. Character-driven animation reads as approachable and consumer-facing. Kinetic typography reads as urgent and editorial. None of these is the right choice in isolation; the right choice is the one that fits the audience’s expectations and the brand’s register.
A mismatch between style and audience destroys credibility before the viewer has processed a single word. A playful, bouncy animation on a security software product tells the viewer, at a visual level, that this company does not understand them. The opposite problem is rarer but real: a clinical motion style on a product built for creative professionals signals that the team behind it has never tried to use it.
Choosing style should happen in pre-production, after the script is locked and the audience is clearly defined. It should not happen in a mood board meeting held before either of those things is done. For a deeper look at how motion choices carry brand meaning frame by frame, see Purposeful Motion Design.
Length and the Patience Threshold
The received wisdom is that 60–90 seconds is the sweet spot for explainer videos. That is roughly right for a cold audience on a product page. But length should be derived from content, not convention.
A single-feature product with one clear problem-solution story can work in 45 seconds. A multi-stakeholder enterprise product with several distinct buyer concerns might need two minutes. What doesn’t work: padding a 45-second idea to 90 seconds because you’ve seen that length recommended, or cramming a complex story into 60 seconds and leaving viewers more confused than when they arrived.
The real constraint is not absolute length. It’s whether every 10-second segment of the video is earning its place. An 80-second video where every segment advances the story is better than a 60-second video with 20 seconds of filler. Approach each segment the same way you’d cut a paragraph: if removing it changes nothing, remove it.
See Video Content for Brands for a broader look at how explainers fit into a content strategy alongside longer-form and social-native formats.
The Conversion Layer
The ending of an explainer video is where most of the conversion work happens, and most videos treat it as an afterthought. A logo animation and a domain name is not a call to action.
The closing sequence should name the next step specifically. Not “learn more” but “start your free trial” or “see how it works for teams like yours.” The ask should match where the viewer sits in their decision. Someone watching an explainer on a product page is warmer than someone encountering the same video on a social feed. The same video will behave differently across those placements, which is why the closing CTA sometimes needs to be adapted for context rather than fixed in the original master.
Captions and subtitles matter here too. A significant share of video views happen with sound off, and if your CTA lives only in the voiceover, those viewers never see it. Make the final frame readable without audio.
One trade-off worth naming: a hard, direct CTA converts better with warm audiences and worse with cold ones. If your video lives primarily at the top of the funnel, a softer next step (“see how it works”) will likely outperform a direct trial ask. Match the ask to the moment.
How Strynal Approaches Explainer Video
We start with the gap audit, not the brief. Before writing a word of script, we identify what the viewer believes when they arrive and what they need to believe to act. That gap defines the length, the tone, the structure, and the ending.
Scripts get written, reviewed, and locked before any visual direction is developed. The visual direction is then built to serve the script, not to be interesting on its own.
Our motion and content work covers the full production path: scripting, storyboard, motion design, and post. We do not hand briefs off between teams; the people who understood the brief are the people who finish the work.
If you have an explainer that isn’t converting, or a product that needs one built from scratch, start a conversation and we’ll tell you where the gap is.