How to Create a SaaS Demo Video: Step-by-Step Guide for Founders
How to create a SaaS demo video is a five-step process: plan your script, record your screen, structure the script in an editor, add context scenes, and export. Most founders skip step one -- they hit record, capture ten minutes of wandering clicks, then wonder why the output looks rough and takes hours to fix. This guide covers each step with specific actions, including the sub-steps where founders most often lose time. For a faster overview, see how to make a SaaS product demo video in under 30 minutes.
What you need before you start
You need three things before touching the recorder: your product open in a browser tab at 1920x1080 resolution, one or two specific workflows you want to show (not the full feature list), and a target viewer in mind. If you can write a single sentence -- "I want a developer signing up for the first time to see how to connect their first API key in under 90 seconds" -- the whole demo writes itself from that constraint. If you cannot write that sentence, the demo scope is too broad. Narrow it before recording.
You also need to decide the output destination before you start. A landing-page demo, a Product Hunt video, and a sales-call clip have different ideal lengths and pacing. Landing page: 60-90 seconds, tight and auto-playing. Product Hunt: 90 seconds maximum, must work without sound. Sales call: up to 3 minutes, can assume more viewer context. This guide targets the landing-page case, which is the most constrained and the most commonly needed.
Step 1: Plan your script in three sentences
Write three sentences before recording anything: (1) the problem your product solves and for whom; (2) the one core workflow that proves it; (3) the action you want the viewer to take after watching. Example: "Founders spend hours editing screen recordings to look polished. SlickVid adds auto-zoom, animated scenes, and title cards automatically from a plain-text script. Try it free at slickvid.com." If you cannot write all three sentences in under five minutes, your scope is still too broad -- keep narrowing until you can.
These three sentences become the skeleton of your script: sentence one is your opening title card, sentence two is your recording clip, sentence three is your closing CTA card. Every scene you add in step four should support sentence two and nothing else.
Step 2: Record your screen
Record only the core workflow from your three-sentence plan -- not a product tour. Use SlickVid's built-in recorder: every click auto-zooms during the recording so the raw footage already looks edited when you drop it into the editor. Record at 1920x1080. Click deliberately: one action per click, with a half-second pause after each so the zoom has time to settle before the next action. Avoid keyboard shortcuts during recording -- keyboard actions do not produce click events, so the zoom does not trigger and the viewer cannot see what changed.
Aim for under three minutes of raw footage. A 90-second demo needs roughly 60 seconds of product clip after trimming the start and end pauses. If your recording runs longer than three minutes, stop, go back to step one, and cut a workflow step.
Record free in your browser -- no app install
Step 3: Structure your script in the editor
Paste your recording into SlickVid's markdown editor as a --- video --- scene. Above it, add a --- text --- scene for the opening title card using your sentence one. Below the recording, add a closing --- text --- scene with your CTA from sentence three. At this point you have a three-scene script that maps directly to your plan.
Each scene defaults to 6 seconds. Add duration: 8s on the video scene if the clip needs more time, or trim the recording down. Preview the composition in the right pane before adding anything else -- if the three-scene version does not tell the story, more scenes will not fix it. Fix the recording first.
Step 4: Add context scenes around the recording
Context scenes turn a raw recording into a story. The most effective additions for a SaaS demo are a --- panel --- stats scene showing one key metric (saves 4 hours per week, 98% uptime, 2x faster), a --- text --- scene with variant: typewriter to introduce a feature before showing it, or a --- notifications --- scene to simulate the product doing something useful in the background. Pick one, not all three.
Do not add more than two context scenes to a 60-second demo. Each scene adds 6 seconds and the best landing-page demos stay under 90 seconds total. Add one context scene, preview the result, and only add a second if the story genuinely needs it. The most common mistake is over-producing a demo that was already clear at three scenes.
Step 5: Style, export, and publish
Set a background in the stage block at the top of your script with background: /your-image.jpg -- a dark abstract texture works for most SaaS products and gives the title card scenes something to sit against. Add transition-in: zoom-in to any scene that feels abrupt. Background music is optional for a landing-page embed where autoplay is muted by default; skip it unless you specifically need it for a social post.
Hit Render. SlickVid generates a 1080p MP4 in under a minute. Download it and embed the file directly on your landing page using a native <video> element with autoplay muted loop playsinline -- this plays immediately on page load without requiring the visitor to click. If you need a hosted player link for Product Hunt or social, upload the MP4 to a CDN or use the SlickVid share URL from the render history.
Common mistakes that add time
Starting with the UI instead of the problem. The first five seconds should state what the product does for the viewer, not show a login screen or a dashboard. Put a --- text --- scene first, always.
Recording the full product tour. A demo that touches eight features convinces no one of any of them. Pick one complete workflow and show it end to end. Viewers who want more will sign up -- that is the CTA's job.
No zoom on clicks. A flat recording where the cursor is a moving dot loses viewers in seconds. SlickVid auto-zooms every click -- but if you are using a different recorder, manually add zoom to every significant interaction before exporting.
Ending without a CTA. The last scene should always be a text card with a single action. "Try it free at slickvid.com" is better than letting the video loop back to the beginning. If you only fix one thing from this list, fix this one -- the CTA scene takes 30 seconds to add and directly affects conversion.
The five steps above complete in under 30 minutes on a first demo and under 10 on every subsequent one. The only step that cannot be rushed is step one: a vague three-sentence plan produces a vague recording, and no amount of context scenes or styling fixes a demo that tries to show everything at once.