The motion graphics techniques that cut cognitive load in a SaaS explainer are: one idea per scene, rebuilding the UI instead of screen recording it, using motion to point at what matters, putting keywords on screen instead of sentences, turning invisible processes into visible objects, keeping one consistent visual grammar, and pacing the edit so each idea has a beat to land. Together they let a buyer understand a complex product in 60 to 90 seconds without a salesperson in the room.
Who this is for
SaaS teams briefing an explainer, and anyone reviewing a storyboard who senses it is too much but cannot say why. Use this as the checklist.
Your Explainer Sells Without You in the Room
Gartner's research on the B2B buying journey found buyers spend only 17 percent of their buying time meeting potential suppliers, and that is all suppliers combined. Far more time goes to researching on their own.
How B2B Buyers Spend Their Buying Time (Gartner)
So the explainer on your homepage is the version of your pitch most buyers actually get, usually watched alone, often muted, and then forwarded to a committee. It has to be followable on the first watch by someone who has never heard of you. The theory behind why is in our companion piece, How Motion Graphics Explainer Videos Reduce Cognitive Load for Software Buyers. This post is the practice.
The 7 Techniques
1. One idea per scene
Working memory holds about four chunks at once, per psychologist Nelson Cowan's research. So every scene earns exactly one idea, and the next scene builds on it. If a storyboard frame needs two sentences of narration to justify it, split it.
- Test: describe each scene in five words or fewer
- Replaces: the montage of six features in eight seconds
2. Rebuild the UI, do not record it
A screen recording shows everything: nav bars, test data, toasts, a cursor hunting for a button. Mayer's coherence principle found people learn better when extraneous material is removed, with a median effect of 0.86 across 18 of 19 tests in his research based principles. Rebuild the interface from your Figma files and keep only the elements the scene is about.
- Keep: the one panel, the one button, realistic data
- Cut: sidebars, settings, notification badges, browser chrome
3. Point with motion
Signaling, cues that tell people where to look, carries a median learning effect of 0.70 in Mayer's work, and visual cues such as arrows, spotlighting, and pointing worked in 11 of 12 tests. In motion graphics the cues are free: push in on the field that matters, dim the rest of the screen to 30 percent, draw a highlight as the narrator says the word. The viewer never has to search.
- Zoom to the element, then hold
- Dim everything else
- Time the highlight to the spoken word, not before it
4. Keywords on screen, not sentences
When the narration says it, the screen should not repeat it word for word. Mayer's research finds that adding the full printed text on top of narration does not help, and can hurt. Put the two or three word anchor on screen, like 2 hours saved, and let the voice carry the rest. For muted autoplay on a landing page, captions do the voice's job, so build a muted cut where on screen type carries the story alone.
5. Make the invisible visible
The hardest part of software to explain is the part nobody can see: a sync, a trigger, a permission check, a model scoring leads overnight. Draw it. Data becomes a moving line between two logos. Automation becomes a queue that empties itself. Infrastructure becomes a 3D system modelled in Blender. A visible mechanism costs the buyer nothing to imagine.
6. One visual grammar, held all the way through
If blue means your product in scene two, it means your product in scene nine. Same icon for the same concept. Same direction for the same flow, usually left to right. Every time a rule changes, the buyer spends working memory relearning the code instead of following the story.
- One colour per meaning
- One icon per concept
- One direction for flow and progress
- One type style for claims, another for UI labels
7. Pace for understanding, then leave a beat
Fast cuts feel energetic in an ad. In an explainer they stack ideas faster than they can settle. Conversational narration runs at around 150 words a minute, so a 60 second script lands near 130 to 150 words once you leave a short beat after each key claim, where the visual holds and the music breathes. Silence is where the idea gets filed.
A Low Load 60 Second Structure
Five beats, one idea each. This is the skeleton most of our SaaS explainers start from.
- 0 to 8 seconds, the problem: one familiar pain, shown not described
- 8 to 18 seconds, the cost: what that pain is doing to the team, as one number
- 18 to 42 seconds, the product: three beats, one per core job, rebuilt UI
- 42 to 52 seconds, the proof: one result or one recognisable customer
- 52 to 60 seconds, the action: one call to action, nothing else on screen
Mistakes That Quietly Add Load
- The feature tour: every feature gets two seconds, so none of them stick
- Real time screen recording: the buyer watches loading spinners and cursor travel
- Internal language: your team's names for features mean nothing to a stranger
- Wall of text: full sentences on screen while the narrator reads them out
- Shifting style: illustration, then 3D, then stock footage, then UI
- Loud music under a dense voiceover
- Three calls to action at the end instead of one
Storyboard Review Checklist
Scenes
- One idea each
- Five word test
- No montage
- Problem first
Screen
- Rebuilt UI
- Clutter cut
- Keywords only
- Realistic data
Motion
- Zoom and dim
- Timed highlights
- Visible mechanisms
- Consistent flow
Sound
- Unhurried narration
- Beats after claims
- Music under voice
- Muted cut
"If a scene needs a second sentence to make sense, it is two scenes."
- Holly Films
How Holly Films Puts This Into Production
Holly Films is a motion graphics studio that makes explainer videos for SaaS companies, including PostHog, Attio, Chili Piper, Happeo, and Userflow. The seven techniques are not a style. They are built into how every project runs.
- A 30 minute call and a demo login. We find the one action the video has to drive.
- Script and storyboard, one idea per scene, approved by you before any animation starts.
- UI rebuilt from your Figma files, stripped to what each scene needs.
- Animation in After Effects, 3D in Blender, finishing and grade in DaVinci Resolve.
- Delivered as a landing page cut, a muted autoplay cut, and cuts for your deck and paid channels.
- Built in layers, so when your UI changes next sprint, one screen is swapped instead of the whole video rebuilt.
Common Questions
What makes a SaaS explainer video easy to understand?
One idea per scene, a clean rebuilt interface instead of a raw recording, motion cues that point at the right element, short keywords on screen rather than sentences, and a pace that leaves a beat after each claim. These choices keep the number of new ideas inside working memory limits, which sit at about four chunks for most adults.
Should a SaaS explainer use a screen recording or animated UI?
Animated UI for anything a prospect sees first. A screen recording includes every element on screen and runs at real time speed, which adds load the buyer did not ask for. Rebuilding the interface as motion graphics keeps only what the scene is about and lets you zoom, dim, and highlight. Screen recordings are fine for detailed help centre tutorials, where the viewer is already a user.
How much text should be on screen in an explainer video?
Two to four words at a time when there is narration: the claim, the number, or the label. Full sentences on screen while a narrator reads them split the viewer's attention. The exception is a muted cut for autoplay, where captions and on screen type carry the story because there is no voice.
How many words should a 60 second explainer script have?
Roughly 130 to 150 words. That pace leaves space for the visuals to land and for short pauses after key claims. Conversational narration runs at around 150 words a minute. Push much past that and the edit has to rush, and rushed edits stack ideas faster than buyers can absorb them.
Can an explainer video replace a sales demo?
Not entirely, but it changes what the demo is for. With buyers spending only 17 percent of their buying time with vendors, according to Gartner, the explainer reaches far more of the buying group than any call. Prospects who have watched it arrive at the demo already holding the core mental model, so the call goes to their specific questions instead of the basics.
How long does Holly Films take to make a SaaS explainer?
Most product explainers and animated demos are delivered in 7 to 12 days, with shorter feature and onboarding videos in 5 to 10 days. The script is approved before animation begins, so changes happen early, when they are cheap. Details are on the SaaS page.
The Bottom Line
Every technique here does the same thing: it moves effort from the buyer to the designer. The buyer should never have to search the screen, decode a label, or hold five ideas at once. That work belongs in the storyboard. For what it costs to get it done properly, see How Much Does an Explainer Video Cost in 2026, and for why we only do this for software, read Why Holly Films Specializes in SaaS Video Production.
Get a storyboard built for the buyer
Holly Films makes motion graphics explainers, animated demos, and launch videos for SaaS teams worldwide. One idea per scene, real UI rebuilt, most delivered in 7 to 12 days. Book a free 30 minute call at hollyfilms.com/book-call.