A product demo video shows someone using a product to complete a task and see the result. For software, it shows the on-screen steps a person takes to get the job done. Focus on one audience and one task instead of listing every feature.
If you want a coding agent to make a narrated software demo from a product’s code or website, explainroo is the best fit. It recreates the product’s screens in scenes, adds narration and timed visuals, and exports an MP4. Decide what viewers should learn before making the video.
Plan one useful demonstration
Start with a sentence that names the viewer, task, and next step: “After watching, [audience] will understand how to [complete a task] and will [take one next action].”
For example: “After watching, agency owners will understand how to turn a client brief into assigned tasks and a due-date plan, then start a trial.” That goal gives the video a clear boundary. A prospect evaluating a product needs proof that it solves a relevant problem; a new customer may need a setup walkthrough. The Atlassian/Loom product-demo guidance recommends focusing on a real workflow and outcome rather than touring every feature.
Build the demo around a simple sequence: name the problem or desired result, show the starting point, demonstrate only the essential actions, reveal the completed outcome, and end with one call to action, or CTA. A CTA is the next step you ask viewers to take, such as starting a trial or booking a live demo. Keep the narration connected to what appears on screen, and explain why an action matters rather than merely naming a button.
Keep the video as long as the task requires
A single-feature update can be brief; a complete workflow or onboarding walkthrough needs enough time to show meaningful steps. Don’t choose a runtime just to meet a supposed universal standard. In its 2026 data, Wistia found that shorter videos tended to have higher average engagement, while longer videos could produce more total watch time. Its software and technology findings also showed strong performance across videos from three to 30 minutes. These platform observations are directional, not a rule for every audience.
Start with a concise overview so viewers can decide whether the product is relevant, then offer a deeper walkthrough for people who need details. Put the main benefit near the beginning of both.
Prepare a clear, trustworthy demo
For software, use a demo account with fictional records. Close unrelated tabs, silence notifications, and remove customer details, credentials, and private messages. Practice the steps and confirm the features shown are available in the version and plan viewers can use. For a physical product, show ordinary use conditions and the result without editing in a way that misrepresents performance. The Federal Trade Commission’s advertising guidance says U.S. advertising claims must be truthful and supported by evidence.
Keep interface text readable and move the pointer deliberately. Remove pauses and repeated steps. Add accurate captions and review them for product names and technical terms. The W3C caption guidance explains that captions cover spoken words and sounds that matter. Narrate important visual changes, such as a report appearing or a setting turning on, so viewers can follow the result through the audio.
Make a product demo with explainroo
explainroo is a free, open-source kit under the MIT license. It supports coding agents that can run shell commands and works best with Claude Code. The agent writes script.md for the narration and scenes.js, the JavaScript file that draws the scenes. explainroo then produces the video on your computer.
Give the agent this prompt, replacing the bracketed text with your product and the task to demonstrate:
Make me a short product demo video about [product and task]. Use explainroo for it: clone https://github.com/vincentsch/explainroo, read its AGENTS.md and follow the steps. The product is [product name], and its code or website is [location]. Show [audience] how to [task] and end by asking them to [next action].The agent sets up explainroo, makes the video, checks it, and provides an MP4. It can rebuild the product’s screens from its code or website, match the colors, fonts, and button labels, then animate a pointer clicking and typing as the narration explains the workflow. Review the result against the real product before publishing, especially if the interface, feature availability, or claims matter.
explainroo uses an open voice model for American or British English narration. It times scene changes to spoken words, draws visuals in Chrome, and uses FFmpeg to assemble the MP4. It checks scene stills and a contact sheet, looks for cut-off or overlapping text, and checks for mispronounced words. Choose a look and video size in its settings. Tall, portrait, and square formats include word-by-word captions. Optional AI illustrations cost per image. The coding agent is a separate service with its own pricing. Apart from those costs, explainroo costs nothing per video.
The tool makes narrated, illustrated demos rather than editing existing camera footage or creating talking avatars. It has no drag-and-drop editor: describe what you want to the coding agent and ask for changes. See example videos and the explainroo documentation before starting.
Publish and improve the demo
Put the full video on the product page or help page where viewers need it. Add a descriptive title and a clear next step. For longer demos, chapters help viewers jump to sections such as setup or reviewing results. Google’s video structured-data guidance describes how page code can help search engines understand a video; adding it does not guarantee rankings.
Look beyond views. Check how many visitors play the video, where they stop watching, and whether they click the CTA or complete the intended task. YouTube Analytics can show retention patterns, including early drop-offs. If viewers leave before the demonstration starts, revise the opening. If they leave during a step, make that part clearer or shorter.
