How to make a SaaS explainer video

These three get mixed up, and making the wrong one is the most expensive mistake you can make.

• An explainer is for people who do not know you yet. It answers what is this and why should I care. It spends real time on the problem, because the viewer has to recognize themselves before they will listen to the solution.
• A demo is for people who already understand the problem and want to see how your product handles it. It spends most of its time inside the interface.
• A launch video announces something new to an audience that is paying attention for a moment. It is about the news.

If homepage visitors keep asking what the product actually does, you need an explainer. If trials stall because people cannot picture the workflow, you need a demo. Many SaaS companies end up with all three, but the explainer usually comes first because it does the most work on the page that gets the most traffic.

1. Problem, about 20 percent. Describe the situation in the customer's words, specific enough that they nod. "Feedback is everywhere" is vague. "The same feature request shows up in support, sales calls and app reviews, and nobody connects them" is real.
2. Answer, about 15 percent. Name the product and show it for the first time, with one sentence on what it is.
3. How it works, about 45 percent. Two or three steps, each shown in the real interface. Pick the steps that make the outcome feel inevitable, not the ones with the most engineering behind them.
4. Outcome and call to action, about 20 percent. What work looks like afterwards, then one clear next step.

Word budgets keep you honest. At a natural pace of about 2.5 words per second, a 30-second explainer holds roughly 70 words, a 60-second one about 150 and a 90-second one about 220. Write the script first, cut every adjective that is not doing work, and drop category jargon your buyer would never use themselves.

Most explainer video makers and animation studios default to illustrated characters: a cartoon office worker buried in paperwork who ends up smiling at a laptop. That style works when the product is abstract or invisible, when it is aimed at consumers, and when you have the budget to keep the illustrations current.

For software, the product itself is usually the most convincing thing you can show. A product-led explainer animates your real interface instead: the problem is told with kinetic type and familiar app imagery, and the solution is shown in your real screens, with the camera moving to the parts that matter. It answers the question buyers are left with after a character explainer, which is what the product actually looks like.

The trade-offs are simple. Character animation can tell a human story but usually takes longer to make and to update. Product-led animation is faster to make and to refresh when your UI changes, but it cannot show people or places. Wevi makes product-led explainers only, so if your story depends on characters or live footage, an illustration studio or video team is the better fit.

The explainer belongs where new visitors first land: in the homepage hero or just below it, next to your main signup button. Reuse the same file on paid landing pages, in the first email of an outbound sequence, at the top of your YouTube channel and in your sales deck.

A few placement rules:

• Use a poster frame that shows your product, not a title card, so the video looks worth playing.
• Make sure the on-screen text carries the story when it autoplays muted.
• Never hide the signup button behind the video. Let people skip it.

Explainers go stale when the interface changes. Plan to refresh yours whenever the UI gets a visible redesign or your positioning shifts. When the video is built from captured UI, that means recapturing the new screens and rendering again rather than commissioning a new animation.