Product demo playbook
How to record a product demo people can follow
A strong product demo is not a tour of every feature. It is a short argument: the viewer has a problem, your product changes something, and the screen proves it. Use this workflow to make that proof easy to follow.
In short: Write one outcome, script the visible actions, prepare clean demo data, record in short sections, and edit for attention. Every zoom, cut and caption should help the viewer understand the product—not advertise the editing.
Choose one outcome before you record
Finish this sentence: “After this video, the viewer should understand that…” If the answer contains “and,” the demo probably needs to be split.
A launch demo might prove that a task now takes one minute. A sales demo might show how a role gets visibility. A tutorial might help a customer complete one workflow. Keep the outcome narrow enough that every click supports it.
Write a screen-first script
Use a two-column outline: what the viewer sees and what they hear. This catches a common problem—narration that moves ahead of the cursor or describes something that is not yet visible.
| On screen | Narration |
|---|---|
| Open the crowded task list | “The launch plan is spread across six owners.” |
| Choose the launch view | “This view brings every blocked task into one place.” |
| Assign the missing owner | “Now the handoff has an owner and a date.” |
| Show the resolved state | “The team can act without another status meeting.” |
Say less than feels natural. The screen is already carrying information. Short sentences leave room for the viewer to look.
Prepare a believable, private demo environment
- Use realistic names and data, but never real customer or employee information.
- Turn off notifications and close unrelated tabs, chats and password managers.
- Increase text size enough to survive the final viewing size.
- Put the app in a stable state and preload slow pages before recording.
- Choose a clean desktop and remove visual noise from the menu bar when possible.
- Decide whether the webcam helps. A face builds connection; it can also compete with a dense interface.
Record in sections, not from memory
Record one idea at a time. Leave a quiet second between sections, and repeat a sentence after a mistake instead of apologizing on camera. Those gaps create obvious edit points.
Move the cursor with intention. Park it away from important text while you speak, then move directly to the next action. Avoid circling an element while searching for words. If your recorder tracks interaction data, deliberate motion also produces better automatic focus.
Capture screen, system audio and microphone separately when the tool allows it. Use headphones, record a ten-second test and listen before committing to the full demo.
Edit for attention, not decoration
- Cut delay first. Remove setup, loading, mistakes and pauses that do not help comprehension.
- Use speed selectively. Compress repetitive work, but return to normal speed before the important result.
- Zoom with a reason. Focus on the control being used or the outcome being revealed. Ease back out when context matters again.
- Keep the cursor calm. Smooth jitter and hide idle wandering.
- Add readable captions. Break lines by meaning, not at arbitrary character counts, and keep them away from the UI you are explaining.
- Watch once with no sound. The sequence should still make sense. Then listen without looking; the narration should still form a coherent argument.
Adapt one demo to where it will live
- Website hero: lead with the result, keep it brief and assume the first view may be muted.
- Sales follow-up: name the prospect's problem and show only the workflow discussed.
- Help center: optimize for completeness and clear step boundaries, not drama.
- Social feed: front-load the visible change, use a larger crop and test captions on a phone.
- Internal update: preserve context and decisions; polish only enough to prevent misunderstanding.
Turn the recording into the finished story
Cadre records your Mac and gives you an editable cinematic timeline—automatic zooms, local captions, cuts, styling and an AI agent that can follow your direction.
Record, edit and preview free · Cadre Pro required to export · Apple Silicon · macOS 13+
Frequently asked questions
How long should a product demo video be?
Make it as short as the promised outcome allows. A single-feature website or social demo may be under two minutes; a tutorial can be longer when each step earns its place. Remove anything that does not change what the viewer understands.
Should a product demo include a webcam?
Use a webcam when trust, personality or explanation matters more than screen space. Skip it for dense interfaces or small mobile formats where the face would cover important product details.
What should I say at the start of a product demo?
State the problem and the visible outcome, then show the product quickly. Avoid a long company introduction before the viewer understands why the workflow matters.
Can an AI edit a product demo?
Yes, when the editor exposes precise, non-destructive controls. Cadre lets an AI agent inspect the timeline and apply cuts, zooms, captions, styling and export while preserving undo history and the same validation used by manual edits.