By Harpal Singh · · 8 min read
You recorded a product demo video, put it on the site, and nothing changed. People press play, watch a login screen and a settings page, and leave before the part that would have sold them. The product is good. The video is a tour of the interface, and nobody buys software because they were shown where the menus are.
A demo that converts is not a better-looking tour. It is a short argument: here is your problem, here it is being solved, here is what to do next. This guide is about building that argument — who it is for, what it shows, what you say and how long it runs. The mechanics of the recording itself, from the microphone to the export, are in the step-by-step guide to how to record a software demo.
Why do most product demo videos fail to convert?
The usual failure is structural, not visual. Three patterns account for most of it:
- It starts with the product, not the problem. The viewer has no reason to care about your dashboard until they recognise their own situation.
- It shows everything. Six features at equal volume means none of them lands.
- Nobody can see what happened. A full 4K display squeezed into a small player turns every button into a smudge, and a viewer who loses the thread does not rewind. They close the tab. The fixes in why viewers can't see what you click apply directly.
Step 1: Choose one viewer and one outcome
Write one sentence before you open any software: "After watching, a [specific person] will believe they can [specific outcome] with this product."
| Weak | Strong |
|---|---|
| An overview of our platform | A finance lead sees the month closed without a spreadsheet |
| Our new dashboard | A support manager sees which tickets will miss their deadline today |
| Everything the integrations can do | An operations lead sees orders arrive from the shop without a manual export |
The strong versions name a person and a result they would pay for. If you have three audiences, you have three short demos, and each will do better than one long one.
Then decide the single action you want afterwards: book a call, start a purchase, reply to the email. One demo, one next step.
Step 2: Script five beats, not every word
You do not need a word-for-word script. You need five beats in a fixed order, and a click path that carries the viewer through them. Here they are for an invoicing product, in a demo of about two minutes:
| Beat | On screen | What you say |
|---|---|---|
| 1. Hook, 5–10 s | The painful starting state | "If you still chase late invoices by hand, this is for you." |
| 2. Problem, 10–20 s | The overdue list, fourteen rows long | "Fourteen invoices, all more than thirty days late. Normally that is an afternoon of emails." |
| 3. Path, 45–75 s | The shortest route through the product | "Select them, send reminders — each one already has the customer's name and amount." |
| 4. Proof, 10–20 s | The result, held still | "Every reminder is out, and you can see which ones have been opened." |
| 5. Next step, 5–10 s | Where to click, or what to reply | "Book a call from the link below and we'll set it up with your data." |
Write the hook and the next step word for word; they are the two lines people remember. Everything in between can be a numbered list of clicks with a few anchor sentences, which sounds far more natural than a script read aloud.
Two rules keep the beats honest. The proof must be something the viewer can read in one glance — a number, a status, an empty queue — not a claim you make about it. And the path must be the real path. If the demo skips a step the customer will have to do, they find out on day one — and a buyer who churns in the first week was never really converted.
Rehearse the path twice. Most stumbles come from hunting for the next click, not from forgetting words.
Step 3: Stage demo data that tells the story
The data on screen does half the persuading, so set it up the way a set designer would.
- Make the starting state look like the problem. Fourteen overdue invoices is a problem; two is a curiosity. Put enough rows in the "before" view that the viewer feels the pain before you solve it.
- Make the proof unmissable. Arrange the data so the result is one number or one state change, large enough to read in a small player.
- Be believable, never real. Real-looking names, plausible amounts, a few weeks of history — and never a real customer's data. Sign in beforehand so no password prompt appears on screen.
- Remove everything that competes. Close other tabs and apps, silence notifications, and size the window sensibly rather than full-width on an ultrawide display.
In ReScreen, record the "Window" or "Application" rather than the whole display, so a second monitor or a stray notification never enters the take. Because recording, editing and export are all local, a demo account with customer-like data never leaves your Mac.
Step 4: Record it, then direct the viewer's eye
Record with settings built for demos. ReScreen ships with a preset called "Product Demo" that sets 4K at 60 FPS, so interface motion looks smooth and the footage still holds up when a zoom magnifies part of it. The full recording checklist — microphone, permissions, capture source and a thirty-second test take — is in how to record a software demo.
A converting demo directs attention: the viewer always knows where to look, and especially during the proof beat. Done by hand, that means keyframing every click, which is why most teams skip it. Smart Zoom builds those zooms from your recorded clicks, drags and scrolls; the mechanics are covered in the guide to the auto zoom screen recorder for Mac. For a demo, these are the settings worth touching:
| Setting | Suggested starting point | Why |
|---|---|---|
| "Zoom amount" | 1.4–1.6× | Enough to read a button without hiding the layout around it |
| "Animation" | Snappy, or Smooth for a slower sales walkthrough | Brisk motion keeps a short demo moving; calmer motion suits a longer conversation |
| "Combine nearby clicks" | On, "Combine within" about 2 s | A form with five fields becomes one held zoom, not five lurches |
| "Stay zoomed" | Around 1.5 s, longer if you explain each click | Long enough to read the label you are talking about |
If you change these after recording, press "Regenerate Automatic Zooms" to rebuild the blocks; any manual zoom you added is kept. Delete any zoom that points at something unimportant. On the proof screen, add a manual zoom and click the preview to set its focus on the number that proves your point.
Step 5: Edit for pace, then stop editing
The edit for a demo is mostly removal. In the timeline editor, set in and out points around each stumble and use "Remove Range" to ripple-delete it. Select any loading or processing section and run it at 2–4× so waiting costs the viewer a second instead of ten.
Then watch it once with the sound off, on your phone. If you cannot follow the five beats from the picture alone, a zoom or a click effect is missing. Then stop editing.
ReScreen does not add titles, captions, music or annotations. If the demo needs an opening card or subtitles, add them in another editor or use the captioning on the platform where the video will live.
How long should a product demo video be?
One to three minutes for most demos: long enough to show one complete outcome, short enough to watch between two meetings. The right length depends on where it plays and how much the viewer already wants to know.
| Where it plays | Length | Why |
|---|---|---|
| Landing page hero, silent loop | 15–30 seconds | Visitors are deciding whether to keep reading |
| Click-to-play explainer on your site | About 60 seconds | Shows the core outcome before attention drifts |
| Launch post in a social feed | 45–90 seconds | Has to earn attention before it can explain anything |
| Cold sales outreach | About a minute, one problem | Watched between meetings by someone who did not ask for it |
| Website or email demo for an interested buyer | One to three minutes | Time for all five beats without padding |
| Walkthrough for a buyer already evaluating you | As long as their questions need | Every minute should answer something they asked |
The shorter formats have their own playbooks: landing-page product videos, the SaaS launch video and sales demo videos for outbound.
Where should the finished demo go?
Export once with the YouTube or LinkedIn preset for a landscape 16:9 MP4 in H.264, which plays everywhere. ReScreen does not host video or collect viewer analytics, so upload the file to your own site, YouTube or a video host.
One recording can then be reused:
- A tighter cut of the problem and proof beats works as a landing-page hero clip.
- The proof moment is the core of a launch video.
- A version with your camera on and the prospect's name in the hook becomes a personalised sales follow-up.
How to make a demo video for software: the short version
If you want the process before the strategy, here it is in six steps. One: choose the single task the viewer wants done. Two: write the beats, using a product demo script template. Three: prepare the account so every click lands on something sensible. Four: record the real product at 4K and 60 FPS, narrating the reason for each click. Five: cut the stumbles and speed up the waits. Six: export, and put the video on the page where the question is asked.
That is the whole creation process in short, and how to create a demo video for software without a production budget, and how to record a software demo is the detailed version of step four. SaaS demo best practices lists the rules that make the result convert, and the product demo video page covers the recording setup.
Next step: script one demo this week
Pick the viewer, write the one-sentence outcome, fill in the five beats, and record it with the "Product Demo" preset. Expect the second take to be the keeper.
ReScreen puts the recording, the zooms and the edit in one app; the product demo video page shows how they fit together. It runs on macOS 13 Ventura or later, on Apple Silicon and Intel. Every plan includes every feature with no watermark and no time limits; compare the monthly, yearly and lifetime options on the pricing page, then download ReScreen and record it.
Filed under
