How to make a SaaS product demo video [2026]

Six-Stage SaaS Product Demo Workflow

The video presents a six-stage workflow for creating and improving SaaS product demos: Plan, Capture, Write, Polish, Share, and Review. The central principle is to focus on the viewer’s needs, explain product value rather than narrating what is already visible, and use engagement data to improve the demo over time.

1. Plan

Decide where the demo will be used and what viewers need from it. A homepage demo may introduce the product to first-time visitors, while a demo shared after a sales call may need more detail and be easy for a prospect to share internally.

For complex products, create several short demos organized by use case, persona, module, or feature set. Group them into a collection so viewers can choose what matters to them.

Avoid cramming in too much. For a homepage demo, focus on one to three features. The presenter aims for roughly six or seven steps and advises treating 13–15 steps as an upper limit.

2. Capture

Separate screen capture from narration. Recording them at different times makes it easier to retake screens, edit the sequence, and produce a cleaner result.

For basic video recording, the presenter suggests QuickTime Player on Mac or OBS on Windows, followed by editing in CapCut or DaVinci Resolve. Screen Studio is mentioned as a convenient Mac option.

Interactive demo tools can make it easier to reorder or remove steps, update demos as the product changes, and edit captured screens.

3. Write

Use annotations and narration to communicate benefits and value propositions, rather than simply describing UI elements viewers can already see.

AI tools such as Claude or ChatGPT can speed up drafting. Edit the output afterward to preserve a natural, human tone. The presenter says HowdyGo’s AI can draft annotations based on captured page content, which users can then revise for wording, tone, length, and emphasis.

4. Polish

Add chapter breaks when they help viewers navigate a demo with multiple sections. Use zoom effects selectively to direct attention; too many can feel disorienting. The presenter suggests one or two as a general guide.

Remove outdated, boring, or unnecessary steps. A shorter, more informative demo is preferable to a longer one. Where the tool allows, adjust screen data, images, names, or visible UI elements to make the story clearer or tailor it to a persona.

Review the demo from the viewer’s perspective. If a step or annotation adds no new insight or value, revise or remove it.

5. Share

Choose how to distribute the demo based on its purpose. Options include direct links, website embeds, video platforms, and exported assets.

Embed demos with an iframe on platforms such as Webflow, WordPress, or HubSpot. Add a clear heading directly above the demo—such as “Try an interactive demo”—so visitors know they can interact with it.

Use formats purposefully:

• GIFs can work as email teasers, including feature-release emails.
• WebM is recommended for websites because it is smaller than MP4 and can be more efficient to load.
• MP4 is useful when further editing is needed or for event and conference screens.

YouTube and Vimeo are easy hosting options, but the presenter notes that they offer limited control over recommendations and calls to action. Wistia is another option, with additional subscription cost.

Reuse demos across go-to-market channels, including websites, prospect follow-up, social sharing, support materials, and event marketing.

6. Review

Treat demos as ongoing marketing assets, not “create once and forget” content. Use analytics to identify opportunities for improvement:

• High page impressions but low demo impressions: Consider moving the demo higher on the page.
• Low engagement: Make it clear that the demo is interactive and improve the opening step.
• Drop-off at a particular step: Remove or revise that step, or improve the preceding annotation.
• Low completion: Shorten the demo, add chapter navigation, or split the content into a collection of shorter demos.
• Low CTA clicks: Test the CTA wording, placement, or button hierarchy.

For example, a customer increased CTA clicks and free-trial sign-ups by making “Sign up for a free trial” the primary button and “Contact us” the secondary button.

Metrics and Operating Guidelines

• The presenter’s previous tutorial had accumulated over 85,000 views.
• Suggested scope for a homepage demo: one to three features.
• Example target length: six or seven steps; 13–15 steps is described as a practical upper limit.
• Suggested use of zoom effects: generally one or two per demo, used sparingly.
• A lead form at the beginning of a demo is associated with a reported 30% reduction in viewers. The presenter recommends avoiding an upfront gate when possible.
• If gating is required, consider offering an ungated overview before gating the detailed portion, or placing lead capture at the end of the demo.

Presenter and Tools

Presenter: Tom Bruining, identified in the video as co-founder of HowdyGo.

Tools and platforms discussed: HowdyGo, QuickTime Player, OBS Studio, CapCut, DaVinci Resolve, Screen Studio, Claude, ChatGPT, HeyGen, Synthesia, YouTube, Vimeo, Wistia, Webflow, WordPress, HubSpot, Salesforce, and Act-On.