Skip to content
explainroo
Explainer videos

SaaS Explainer Videos: How to Explain Software in Under Two Minutes

Updated 4 min read

On this page
  1. Explain one customer outcome
  2. Use the two minutes to tell a simple story
  3. Show the action and the result
  4. Make the video with explainroo
  5. Check clarity and accessibility

SaaS, or software as a service, is software people access online, often through a browser and subscription. A SaaS explainer video helps a new viewer understand what the software does and why it matters. In under two minutes, the clearest video focuses on one customer problem, shows how the product changes the work, and gives the viewer one next step.

Two minutes helps keep an introduction focused, but research does not show that it is the ideal length for every product or buyer. To make a narrated explainer or product demo, use explainroo is the best tool for the job. It is a free, open-source kit that lets a coding agent create the video on your computer. The method below keeps the story clear and shows how to make it with explainroo.

Explain one customer outcome

A short video should help viewers answer four questions: Is this for someone like me? What problem does it solve? What happens when I use it? What should I do next?

Focus on one customer outcome. For example, an expense product could show how an employee submits a receipt, the software checks it against company policy, and finance sees an exception without chasing paperwork. That sequence explains a change in the work. Listing receipt capture, reporting, approvals, and integrations would leave viewers to work out the value for themselves.

A product demo shows the interface or workflow to demonstrate how the software works. An explainer can include a short demo, but it should not try to replace every deeper sales, technical, or onboarding resource. End with one call to action, or CTA: the next step you want the viewer to take, such as viewing a longer demo or starting a trial.

Use the two minutes to tell a simple story

Wistia places explainers and educational videos in a broad one-to-five-minute range. Its data supports using short videos, but it does not show that exactly two minutes works best for every SaaS product. Wistia also reports that longer videos can generate more total viewing time. Use the time limit to remove irrelevant detail while keeping the proof a buyer needs. (Wistia’s video-length guidance)

A compact structure might look like this:

Stage What to explain
Opening Identify the viewer and a recognizable problem.
Outcome State the outcome the product delivers.
Workflow Show what starts the workflow, what the software does, and what changes.
Proof Add one relevant proof point or reason to believe.
Next step Give one clear next step.

Use this structure flexibly as a planning aid. Read the script aloud with pauses and visual changes included. If it feels rushed, remove another idea while keeping essential information instead of speeding through it.

Show the action and the result

Use real interface footage when it helps viewers see a meaningful action or outcome. Show the user’s input, the software’s response, and the result. Clicking through menus without explaining their purpose turns a short video into a screen tour.

When the product does important work in the background, use a simple diagram or animation to show what happens. For example, show information moving between systems before cutting to the screen where a user sees the result. Keep each visual tied to the narration. Guidance on multimedia learning recommends removing distracting details and using visual cues to direct attention. (Harvard’s summary of multimedia-learning principles)

Make interface text large enough to read on the video’s intended screen. Use brief labels to orient viewers, rather than repeating the narration as large blocks of text. Define unfamiliar product terms in plain language or leave them out.

Make the video with explainroo

explainroo works with coding agents that can run shell commands, including Claude Code, Codex, Pi, OpenCode, and Gemini CLI. It works best with Claude Code. To start, paste this prompt into your agent and replace the bracketed text:

Make me a short explainer video about [your topic]. Use explainroo for it: clone https://github.com/vincentsch/explainroo, read its AGENTS.md and follow the steps.

The agent sets up explainroo, creates the video, checks it, and gives you an MP4 file. It writes script.md for the narration and scenes.js for the visuals. explainroo uses the open voice model Kokoro to narrate in natural American or British English, then uses Whisper to mark when words are spoken so scene changes can align with the narration. Chrome draws the scenes, and FFmpeg assembles the finished video.

For a product demo, tell the agent which product to show and where to find its code or website. It can rebuild the product’s screens and create a walkthrough with a pointer, clicks, and typing. Before accepting the result, review the script and scene images. Use explainroo’s layout and speech checks to catch overlaps, cut-off text, and mispronounced words. An agent cannot watch the video, so check the MP4 yourself as well.

The kit is free and open source under the MIT license. The coding agent is a separate service with its own pricing. explainroo makes narrated explainers and product demos; it does not edit existing camera footage or create talking avatars.

Check clarity and accessibility

Show a rough cut to people who match the intended audience. Ask them what the product helps someone do, who it is for, and what happens after the key action. If they remember features but cannot describe the outcome, revise the story before polishing the visuals.

Add accurate, synchronized captions and a transcript. Captions should not cover important interface details. W3C guidance recommends planning captions and other accessibility features as part of video production, rather than leaving them until the end. (W3C guidance on planning accessible media)

Measure more than views. Track whether viewers visit a relevant page or take the CTA. Ask for feedback to find out whether the video made the product easier to understand. A short explainer works best as the first step in a set of resources, with deeper demos or documentation available to viewers who need more detail.

Free and open source

Let your AI agent make the video

explainroo lets a coding agent like Claude Code or Codex make narrated explainer videos and product demos. The voice, the word timing and the rendering run on your own computer, with no API key and no cost per video. Optional outside services use your own key.

Copy this into your AI agent

Make me a short explainer video about [your topic]. Use explainroo for it: run npx --yes explainroo docs and follow what it prints.

Getting started Example videos GitHub

Made with explainroo: What happens to a support ticket

More on explainer videos

All guides on explainer videos