Guide
How to make a SaaS demo video
A SaaS demo video shows your product doing its job well enough that a viewer can picture themselves using it. That's the whole assignment — and it's why demo videos fail in predictable ways: they show features without a story, they run twice as long as anyone watches, or they were accurate three releases ago. This guide walks the traditional workflow first (script → capture → voiceover → edit), because understanding it is how you judge shortcuts. Then it shows the generated workflow, where most of those steps collapse into one. Budget expectations up front: the manual route costs a full day for a first video and a half-day for each revision; an agency costs $3k–$15k and weeks; generation costs minutes and low single-digit dollars per draft.
- 1
Decide the one job of the video
Pick a single audience and a single outcome before writing anything: 'convince trial signups to connect their data' is a demo video; 'show everything we do' is a screensaver. Length follows from the job — top-of-funnel demos should land at 60–120 seconds, feature-specific onboarding clips at 30–90.
If you can't finish the sentence 'after watching, the viewer will ___', you're not ready to record or generate anything.
- 2
Write the script before touching any video tool
Structure that survives contact with real viewers: a 3-second hook stating the problem or boldest claim, then 3–5 scenes that each show one capability while the narration says why it matters (not what the button is called), then one call to action. Write narration conversationally — read it aloud; anywhere you stumble, a viewer tunes out.
At a natural speaking pace, narration runs ~150 words per minute. A 90-second demo is roughly 220 words — shorter than this step's text.
- 3
Capture the product
Manual route: screen-record at 1080p or higher in a clean browser profile (no bookmarks bar, no notifications), move the cursor slowly and deliberately, and expect several takes per scene. Generated route: point the AI at your site and it captures the rendered pages directly — no cursor, no takes, no compression blur. Either way, capture per scene, not in one heroic take.
Shortcut: generate it from your URL
- 4
Record or generate the voiceover
Manual: record in a quiet room, one scene at a time, and accept that syncing audio to footage is where your afternoon goes. Generated: the voiceover is produced from the script and timed to each scene automatically, in your choice of voice and language. If you're manual-recording, sync narration to actions with the action landing a beat after the words announce it.
- 5
Edit, caption, and export
Trim dead time aggressively — demo videos die in the gaps between actions. Add captions (most viewers are muted), keep transitions simple, export 1080p MP4. Generated videos come with timed captions and scene transitions already applied, plus separable tracks (clean video, voiceover, SFX, SRT/VTT) if you want a final polish pass in your own editor.
- 6
Put it where it works, and plan for staleness
Landing page hero, pricing page, onboarding emails, sales outreach, help center. Then set a rule for updates: a demo showing an old UI quietly damages trust. Manual videos need a re-record calendar; generated videos get regenerated as a release-checklist item.
What not to do
- Don't tour the navigation. Nobody buys a navbar — show outcomes, not menus.
- Don't record the voiceover as one continuous take over finished footage; per-scene audio is the only way sync stays manageable.
- Don't exceed two minutes for a top-of-funnel demo. Watch-time cliffs are real and steep.
- Don't ship without captions — feeds, offices, and store listings all default to muted.
- Don't let the video outlive the UI it shows. Stale demos read as neglect.