SaaS Demo Video: What to Show in 60 Seconds, With a Shot List
How to plan a SaaS demo video that converts: pick one workflow, follow a 60-second shot list, show the UI clearly, and cut shorter versions for social and sales.
September 2026
A SaaS demo video has a simpler job than it seems: prove that the product does what the landing page claims. Not every feature, not the roadmap, not the integrations page. One workflow, from the moment a user starts to the moment they get the result they came for. Viewers who see that are ready to try it. Viewers who see a feature tour are ready to close the tab.
This guide gives you a 60-second shot list, the rules for showing interface clearly, and the mistakes that make most demos feel longer than they are.
Demo, explainer, or launch video?
| Video | Answers | Shows |
|---|---|---|
| Demo video | “Does it actually work?” | The product doing its core job, on screen |
| Explainer video | “What is this and why should I care?” | The problem and the idea, often more than the interface. See our explainer guide. |
| Launch video | “What's new, and should I look?” | A fast announcement built for attention. See our launch video guide. |
If your video spends more time on the problem than on the product, it is an explainer. If it spends more time on the product, it is a demo. Both are useful; just don't make a demo that forgets to show the product.
Pick the one workflow
The hardest part of a demo is choosing what to leave out. Pick the single workflow that best answers why someone would pay for your product, the one a new user should complete in their first session. Ask:
- What is the first thing a new customer does after signing up that makes them stay?
- Which result would a buyer screenshot and send to their boss?
- Which workflow can be shown in three steps without skipping anything important?
Everything else goes in a different video: a walkthrough per feature, a docs page, or a sales call.
The 60-second shot list
| Time | Scene | What to show | On-screen text |
|---|---|---|---|
| 0 to 5s | Outcome hook | The end result, first: the finished report, the closed ticket, the published page | What the viewer gets, in under 8 words |
| 5 to 15s | Starting point | Where the user begins: an empty state, a messy inbox, a blank dashboard | The problem in the user's words |
| 15 to 40s | The workflow | Three steps, one action per scene: type, click, see it happen | One verb-first caption per step |
| 40 to 50s | The result | The finished outcome again, now earned, ideally with one number | The number and what it means |
| 50 to 60s | Close | Your logo and one call to action | The exact words on the button |
Opening on the outcome is the move most demos skip. Viewers decide in the first few seconds whether the rest is worth watching, and “here is what you'll have at the end” is a better reason to keep watching than a login screen.
Showing the interface clearly
Demos fail on legibility more than on content. A full-screen dashboard shrunk into a video player becomes a gray blur. These rules keep the UI readable, even on a phone:
- Show less screen. Capture the part of the interface that matters, not the whole window. A cropped panel at full size beats a whole app at a quarter size.
- Frame it. A screenshot or recording inside a browser window frame reads as software someone is using; the same image dropped straight onto the canvas reads as a picture.
- One action per scene. A click, a typed query, a result appearing. Two actions at once means the viewer misses one.
- Captions start with a verb. “Connect your calendar”, “Pick a template”, “Share the link”. The caption names the action the viewer is watching.
- Capture at export size. Screenshots and recordings at least 1920 pixels wide stay sharp in a 1080p video.
- Use fake but realistic data. Real-looking names and numbers make the demo believable; real customer data makes it a liability.
Screenshots, recordings, or animated components?
| Option | Best for | Trade-off |
|---|---|---|
| Screenshots | Showing a state: a dashboard, a result, a settings page | Needs motion around it to avoid a slideshow feel |
| Short screen recordings | Showing an action that only makes sense in motion | Keep each clip to one action; long recordings drag |
| Animated UI components | Typing, clicking, notifications, and numbers, shown cleanly | Stylized rather than your exact UI, which is often clearer |
The best demos mix all three. In Demogent that means a Browser Window holding your screenshot or recording for the product scenes, plus components for the moments that don't need your exact interface: a Search Field or Query Submit for a typed question, Button Click for the key action, Mobile Notifications for results arriving, and a Progress Ring for the number in the result scene. A CTA Outro closes it.
Build a 60-second demo on a timeline
Drop your screenshots and recordings into browser and device frames, add the UI moments as ready-made components, and export from your browser.
Cut three lengths from one demo
| Version | Length | Where it goes | What to keep |
|---|---|---|---|
| Social cut | 15 to 20 seconds | X, LinkedIn, community posts | Outcome hook, the single most visual step, close |
| Landing page demo | 45 to 60 seconds | Homepage, product page, launch posts | The full shot list |
| Sales version | 60 to 90 seconds | Follow-up emails, sales decks | The full shot list plus one objection answered |
Demogent timelines run up to 60 seconds, which covers the social cut and the landing page demo. For anything longer, split the content into a short series rather than one long video; viewers finish three 40-second videos more often than one two-minute one.
Common SaaS demo video mistakes
- Starting with a login screen. Nobody needs to see you sign in.
- Touring every feature. A tour answers “what does it have?”. A demo answers “does it work?”. Buyers care about the second.
- Showing the whole screen, all the time. Crop to what matters.
- Relying on voiceover. Most demos autoplay muted. Put the message in on-screen text.
- Ending without a next step. Close with one clear action and the exact words on the button.
Frequently asked questions
How long should a SaaS demo video be?
About 60 seconds for a landing page demo, and 15 to 20 seconds for a social cut. Longer sales demos work in one-to-one follow-ups, but for public pages shorter wins.
What should a SaaS demo video include?
An outcome hook, the starting point, one core workflow shown in about three steps, the result with a number if you have one, and a single call to action.
Should I use a screen recording or screenshots?
Both. Use screenshots for states, like a finished dashboard, and short recordings for actions that only make sense in motion. Frame either in a browser window so it reads as live software.
Can I make a SaaS demo video without a video editor?
Yes. A template-driven motion editor like Demogent lets you build the demo from screenshots, recordings, and ready-made components on a simple timeline, with no traditional editing skills.
Make your next product video in Demogent
Start from a finished launch template or a blank timeline, drop in your screenshots and logo, and export in your browser. Free to start, with no editing experience needed.
