How to make a product demo video

Buyers watch a demo to answer one question: can I do my job with this? So the best demos follow a single workflow the way a customer would live it, not a tour of every menu.

Pick the job most of your buyers came for, then write it in three parts:

• The trigger: what happens in the customer's day that sends them to your product. A request comes in, a deadline lands, a report is due.
• The steps: the three to five actions in your product that handle it. Leave out settings, setup and anything people only do once.
• The result: the finished thing on screen, such as the schedule published, the invoice paid or the report sent.

If you sell to several audiences, make one short demo per audience rather than one long demo for everyone. A finance lead and an engineer want to see different workflows, and a 40-second demo of the right one does more than a five-minute demo of all of them.

There are two ways to put your product on video, and they suit different jobs.

A screen recording captures exactly what happens on screen, click by click. It is the right choice for tutorials, onboarding and sales walkthroughs where the viewer needs to copy the steps. The downsides show up in marketing: text is tiny on a phone, the cursor wanders, loading states eat seconds, and every redesign makes it look dated.

An animated product demo uses the same real interface but directs it. The camera pushes in on the button that matters, components lift off the page so they can be read, waiting is cut to a single moment, and each scene lasts exactly as long as it needs to. It reads well on a phone and holds attention on a homepage.

A good rule: if the viewer needs to follow along, record the screen. If the viewer needs to understand the value and want to try it, animate it. Many teams use both, with a 30 to 60 second animated demo on the website linking to a longer recorded walkthrough in the help center.

Write the narration before you choose any visuals, then build the scenes to match it.

1. Open on the situation, not the logo. One line the viewer recognizes from their own week.
2. One sentence per scene. Each scene shows one step, and the narration says why that step matters.
3. Do not narrate the cursor. "Now I click the Publish button" spends words on what the viewer can already see. Say what it gets them: "Publish, and the week is set."
4. Use real numbers or none. "Confirmations roll in" is fine. "Saves 10 hours a week" needs to be true and provable.
5. Budget the words. Narrators read about 2.5 words per second, so a 30-second demo holds about 70 words and a 60-second demo about 150.

Then read the script out loud with a timer. Wherever you stumble, the viewer will too, so rewrite those lines until they are easy to say.

The interface is the star of a demo, so stage it like a set:

• Use a demo account with realistic data. Plausible names, amounts and dates make the product feel lived in. Empty states and "Test User 1" make it feel unfinished.
• Remove anything private. No real customer names, emails or figures unless you have permission to show them.
• Clear the clutter. Close cookie banners, chat widgets, onboarding tips and notification toasts before you capture.
• Zoom the browser in. Larger components on screen give sharper results when the camera moves in close.
• Set the right state. If a scene shows a menu choice, open the menu first. If it shows a filled form, fill it first.

Capture from the live product or a staging copy that matches it, so the demo shows exactly what customers will get after they sign up.