A SaaS explainer works when it makes one specific claim about your product and proves it on screen with your real UI in 60 to 90 seconds. Which claim depends on where the video will live, because a homepage viewer, an onboarding viewer, and a sales-thread viewer are three different people. So the placement decision comes before the script.
Picture a CRM: a pipeline board of deals, each with a stage, an owner, and a next step. Any workflow SaaS has this board's two problems: dense screens, and an automation layer you cannot see.
Most SaaS teams skip the placement decision. They script one general-purpose piece, put it on the homepage, reuse it in onboarding emails, and attach it to sales follow-ups. Aimed at everyone, it convinces no one. Our best-graded videos start from a single question: when the video ends, what must this specific viewer be able to think?
Decide where the video lives before anyone writes a script
- The homepage viewer is mid-evaluation and probably muted. They have competitor tabs open and give you a few seconds. Put the real pipeline board on screen with a deal visibly moving; the opening seconds carry the whole video.
- The onboarding viewer already bought, so teach instead of re-selling. They opened the app and met stages, filters, and fields they cannot read yet. Give them a mental model, one concept per video, at a calm pace — the exit state every onboarding video targets.
- The sales-thread viewer never saw your demo. B2B deals get decided by people who skipped the call: the CFO, the security reviewer, the engineer who has to live with the tool. A 90-second video in the follow-up email is the only demo that person receives, so it stands alone, with no "as we discussed."
Whichever placement you choose, give the video one energy. A concept video is calm, because teaching needs pauses. A showcase video is excited, because the machine running end to end should feel like an outcome. A video that tries both does neither.
The three beliefs a SaaS viewer has to leave with
- "I can see my problem in this." Carry one worked example through: a lead arrives, gets qualified, becomes a deal, moves through the stages, closes. A feature tour fails here — eight features in ninety seconds is eight things half-seen and no problem solved. So does repetition: one deal shown moving three ways beats three separate deals, because viewers give a system's first run full attention and its fifth almost none.
- "This is the actual product." A SaaS viewer is minutes from a free trial. They will open the app and look for the pipeline board from the video, and if it is not there, they file the video as a lie. Build every frame from real components, real field names, real output; the review history behind this rule is in show the real product.
- "I can see where the value shows up." Abstract benefit claims do not survive video, but a surface visibly filling does: a stage column populating, a task list draining, a closed-won count climbing. When nothing accumulates, the viewer finishes unable to say what a month of use would get them — usually why a technically fine video produces no signups.
B2B adds a fourth job. Your champion has to convince four other people, and a 90-second artifact that survives forwarding is the cheapest tool you can hand them. A video that assumes homepage context, or needs sound, forwards badly.
Dense screens: staging without faking
The honest screen of a workflow product is dense. A real CRM record page holds an activity timeline, a contact panel, a dozen custom fields, and a filter bar — illegible in a homepage embed, hopeless on a phone.
The tempting fix is a simplified, prettier fake of the UI. That fix dies in review, because users notice the screen is not real and prospects sense brochure even when they cannot say why; the verdict it earned in ours is quoted in show the real product. Stage instead of simplifying:
- Port real components onto a clean canvas. Your actual pipeline board, deal card, and activity feed, rebuilt faithfully with room to breathe. Composition is the only invented layer.
- Keep one element focal and dim the rest to about a third. A dense frame becomes readable the moment the film points at something.
- Push the camera in for the payoff. A deal card flipping to closed has to be big enough to see; the size floor comes from a rejected build in why explainer videos look cheap.
Timing makes the automation layer visible
In a workflow product, the value is causality, and causality does not appear in a screenshot. A lead comes in, scoring runs, a deal is created, a follow-up task lands on the right rep's list. That chain is the product, and no single frame contains it.
Viewers decide what caused what by watching when things happen. When the scoring step finishes and the new deal card lands a beat later, the viewer files the card as a consequence — no arrow, no caption. Cause should lead effect by a beat rather than firing simultaneously; the tuned offset is in what makes a good explainer video. We once let related events fire on independent schedules, and the connection the scene existed to teach never landed.
- Never let the frame freeze while the voice keeps talking. Boards look "done" the moment they settle, and a static screen under running narration reads as a slideshow. Keep something alive in every hold; the measured case is in animation timing and easing.
- Layer long workflows instead of panning along them. A seven-stage pipeline in one line outgrows the frame, and a camera cannot fix a staging error. Stack the layout and move the camera between ideas, not along a conveyor belt.
Realistic outcomes
- A video cannot rescue unclear positioning. The script starts from one thesis sentence the whole video argues — for the CRM, "your pipeline updates itself, so reps only touch deals that need a human." If you cannot write that sentence, the gap is positioning, and no animation fills it.
- Plan for partial viewing. The strongest proof belongs in the first third, and for most SaaS products 60 to 90 seconds serves better than three loose minutes.
- Budget for revision, or gate it out early. Roughly half of all production effort in our records came after review started; the counts are in how long an explainer video takes. The cheapest lever a buyer has is to ask for still frames before anything animates — one look catches wrong screens and invented UI at a small fraction of a finished video's cost, a gate described in how to make an animated explainer video.
- Expect real but unglamorous effects. A good SaaS explainer shortens the "what even is this" phase, gives your champion a forwardable artifact, and shows the product working to the person who never saw the demo. We do not promise conversion numbers before seeing a page, and a vendor who does is quoting a guess.
FAQ
Should the homepage video autoplay muted? If it does, the picture carries the whole argument: state shown visually, cause and effect carried by timing. A well-built explainer survives muting because the narration was written to the picture, never the reverse. Test yours muted before you embed it.
One workflow or a feature tour? One workflow, end to end, with the viewer's problem recognizable in it. Features earn a mention only as the worked example passes through them. If a second feature needs its own video, make a second video.
Our UI is ugly. Should we animate or record? Animate the concept from your real components — staged, composed, still true — and record the live product for the "click run and watch" beat. A real screen staged with care beats a beautiful fake your users will never find.
Where does the same video get reused? A homepage explainer usually survives in sales threads and paid-social cutdowns. It usually fails as onboarding, because it was built to convince and onboarding viewers need to be taught. Plan the placement first; treat reuse as a bonus.
If you want this done for your product, start with the URL. We come back with twenty short candidates and you pick from the board.