By Touchbase Technologies · Published
Product demo video for SaaS: show one real task
A useful product demo answers a practical question: what does this product let me do, and what would using it involve? Choose one task a viewer recognizes, show the real starting point, carry out the important steps and leave the finished result on screen long enough to inspect.
There is no universal length that makes a demo persuasive. A short overview may help a new visitor understand the product; a longer walkthrough may be necessary to explain setup, a review decision or an integration. Make the length follow the task. This guide uses an illustrative three-minute recording plan that you can shorten or expand without inventing results.

Decide who is watching and what they need to learn
Write the viewer’s situation in one sentence. For example: “An operations manager needs to see how appointment changes move from the office to a field technician.” That is more useful than a list of every feature in the application.
Then write the decision the video should support. Is the viewer deciding whether to explore the product, whether a specific workflow fits their team or how to complete a task after buying? Different decisions need different detail. A buyer evaluating an integration may need to see its configuration and limitations; an existing user may need the exact recovery step after an error.
Keep a note of what the video will not establish. A recording can show a task succeeding with your chosen sample. It does not prove that every customer will have the same result or that a connected service will always be available.
Choose a task you can actually demonstrate
Use a start state, an action and a visible end state. For an appointment workflow, that could mean opening a fictional customer request, selecting an available slot, reviewing the details and seeing the confirmed appointment in the correct place.
Avoid switching between unrelated features simply because they are available. Each extra task creates another explanation the viewer has to hold in mind. If a second feature matters, explain the handoff between the tasks or record a separate walkthrough and link to it.
A storyboard can be a short table rather than a production document:
| Moment | What the viewer sees | What the narration explains |
|---|---|---|
| Starting point | A fictional appointment request | Who needs the task completed and what information is available |
| Review | The relevant request details | What the operator must verify before proceeding |
| Action | The real scheduling controls | The choices that affect the result |
| Result | The confirmed sample appointment | Where the outcome appears and what still needs human attention |
| Next step | One appropriate destination | What the viewer can do after watching |
Prepare a safe demonstration workspace
Use a demo account with fictional people, reserved example addresses and files created for the recording. Remove private customer records, personal notifications, access tokens and unrelated browser tabs from view. A product demonstration does not need access to a real person’s inbox to explain the workflow.
Check what the recording can capture. MDN’s Screen Capture API guide explains browser-based screen capture and its security controls. A browser may offer a tab, window or screen choice; available audio capture and behavior vary by browser and system. Confirm the actual selection with a short test rather than assuming your microphone or application audio is included.
Complete the task once before recording. Note required permissions, loading time, plan restrictions and any external service involved. If a feature is unavailable in your account, do not substitute an animation and present it as a successful live demonstration.
Use a script that names the actions
Write what you will say next to what you will show. The narration should explain the reason for a decision rather than read every label on the screen. A natural opening could be: “Here is a fictional appointment request. I’ll check the details, choose a slot and show where the confirmation appears.”
For the scheduling example, this proposed three-minute outline allocates time to the task. It is an editing plan, not an optimal-length claim or a performance benchmark.
| Time | Screen action | Narration purpose |
|---|---|---|
| 0:00–0:20 | Show the sample request and intended outcome | Establish the situation and say that the data is fictional |
| 0:20–0:50 | Review the information needed to proceed | Explain the checks the operator makes |
| 0:50–1:50 | Carry out the important steps | Name the decisions and show the controls that matter |
| 1:50–2:30 | Inspect the resulting appointment | Confirm what changed and where it can be found |
| 2:30–2:50 | Explain one relevant limitation or follow-up | Clarify what the recording does not automate or prove |
| 2:50–3:00 | Show one next step | Give a destination that fits the viewer’s decision |
If your task takes longer, keep the explanation accurate. You can separate the overview from a detailed walkthrough. Do not remove a required review step merely to meet an arbitrary duration.
Record real screens and label illustrative material
A screen recording can demonstrate the actual interface and its current behavior. An animation can explain a concept or show a situation that is difficult to film. Both can be useful, but tell the viewer which they are seeing. See the separate whiteboard explainer versus screen demo guide when choosing the format.
If a process includes waiting, you may trim or speed up the interval and label that edit. Keep the order of important steps understandable. Do not join an action from one account to an unrelated result from another and imply they are one continuous successful run.
Keep the pointer visible when it helps locate the control. Pause after an important change so the result can be read. If the original capture is very wide, reframe the relevant area carefully instead of shrinking an entire desktop into an unreadable phone-sized video.
Explain results without inventing proof
Describe the result you can show: a sample record was created, a draft appeared, an appointment was confirmed or a file was generated. Do not turn that observation into a claim about revenue, saved hours or guaranteed customer outcomes unless you have appropriate evidence for that separate claim.
For example, “The sample appointment now appears here” is supported by the recording. “Teams save two hours every week” would require a separate basis, including what was measured, whose experience it describes and the limitations. A script should not fill an empty proof section with a plausible-sounding number.
If you include customer material, obtain the permission needed to use it and preserve its context. A customer quote about one feature should not appear to endorse an unrelated workflow.
Check the captions and the viewing experience
W3C’s caption guidance explains that automatically generated captions need accuracy checks and correction. Review product names, negatives, technical terms and timing against the actual audio. A missed word can change the meaning of a step.
Test the video with sound off and on a phone. Check that the essential action remains visible, captions do not cover the control being used and links can be followed. Provide a transcript or written steps where useful so viewers can review the process without replaying the whole recording.
Ask someone unfamiliar with the product to watch once. Have them describe the starting situation, the action taken, the result and what they would do next. Their answer is a concrete editing signal: if the task is unclear, revise the explanation before adding more effects.
Choose one next step that matches the video
An overview might lead to account creation or a product page. A detailed buyer walkthrough might lead to a question about fit. A support demonstration should lead to the written instructions or the next task. Use a destination that exists and check it from a signed-out browser when it is intended for new visitors.
Label a trial, free account, paid feature or sales meeting accurately. The video should not offer a free workflow that immediately requires payment without explanation. When using Touchbase, review the current plans and allowances before describing what the viewer can access.
Questions
How long should a SaaS product demo be?
Long enough to demonstrate the selected task clearly. Use a brief overview for initial orientation and a separate detailed walkthrough when setup or evaluation needs more explanation. The three-minute outline above is an example, not a universal rule.
Can I use AI voice or animation?
Yes, when the result is accurate and understandable. Review the narration, captions and visual claims. Label explanatory animation and do not present generated screens as proof of a working feature.
What if the feature fails during the recording?
Fix and verify the workflow before presenting a successful demonstration. If the video is about troubleshooting, show the failure and recovery accurately. Do not edit an unresolved failure into an apparent success.
Published by the Touchbase editorial team. The illustration explains a recording process; it is not a screenshot or evidence of a customer result.
Prepared with AI assistance and checked against the sources linked in this guide.
Your next step
Get started with Touchbase
Find relevant customers, prepare outreach for review and keep contacts, replies and follow-up connected.
Start for freeStart with a Free account. Upgrade or add credits when you need more capacity. Compare plans