You can know your product inside out and still struggle to explain it in a minute. A recording of every menu usually makes that harder. The viewer needs to understand one useful thing they could accomplish, then see the product doing it.
This guide uses a fictional project-management app called Relay to work through a 60-second demo. The product and script are examples, not a customer story or a claim about results. Replace them with a workflow your own software genuinely supports.
You can use the structure in any editor. In Vidmoat, the Startup Launch Kit opens a prepared brief in the dashboard so you can attach your recording, explain your audience and review an editable draft.
01 / FIELD NOTESChoose the job before the footage
Write a sentence with a person, a task and an outcome: “A team lead can turn a meeting’s action items into assigned tasks.” That is a more useful brief than “Make our app look exciting.” It tells you which interaction must survive the edit.
Choose the next step too. Someone on your homepage might be ready to try the product. Someone watching a feature update might already be a customer and only need to know where to find it. A tutorial should help the viewer finish a task rather than repeatedly asking them to buy.
For the Relay example, our audience is a small team lead, the task is assigning follow-up work, and the invitation is to try the task board. We do not need to show billing, settings or the entire navigation.
02 / FIELD NOTESA 60-second script with room to understand
Treat these timings as a starting structure. A complicated action needs more time than a title. If the viewer cannot follow the demonstration, shorten the introduction before speeding up the product interaction.
- 0–5 seconds — Name the problem. Example: “The meeting ends. The follow-up work gets lost.” Show a short, readable title instead of a long logo animation.
- 5–12 seconds — Introduce the outcome. “Give each action item an owner and a place to live.” Show the real task board with prepared sample data.
- 12–35 seconds — Demonstrate one workflow. Create a task, assign it and add its due date. Hold the important controls long enough to read. Cut repeated navigation and unrelated waiting.
- 35–48 seconds — Show the result. Return to the board and show the assigned task. Describe only what the recording demonstrates; do not attach an invented time-saving percentage.
- 48–60 seconds — Give one next step. “Try Relay with your team.” End with a readable product name and the actual destination you want viewers to visit.
03 / FIELD NOTESRecord source material that is easy to edit
Use a clean demonstration account with sample data. Hide notifications, close unrelated tabs and check names, addresses, API keys and customer information before recording. It is easier to avoid capturing a secret than to remember every frame that needs a blur.
Record one complete workflow, including its initial and finished states. Leave a little stillness before and after each important action. If you narrate, explain the viewer’s goal and the effect of the action rather than reading every button label.
Make interface text comfortable to read before recording. Keep browser zoom consistent. A higher-resolution source can leave more room for a crop, but the real test is whether the exported video is readable on the device where people will watch it.
Keep your source files. Add the logo and any screenshots as separate assets so the editor can position them cleanly. If you supply a video as a style reference, say whether it is inspiration only or footage you have permission to include.
04 / FIELD NOTESGive the AI a useful editing brief
Attach the actual recording before asking the agent to make content-dependent edits. Include the audience, demonstrated feature, desired length, aspect ratio, brand direction and CTA. Separate facts about your product from suggestions about style.
Ask for one draft first. Reviewing a single clear sequence is easier than reviewing several versions with the same unresolved story problem. You can ask for alternate hooks and formats after the main edit works.
Make a 45–60 second product demo from my attached screen recording.
Product: [name and what it does]
Audience: [specific person and task]
Demonstrate: [one real workflow]
CTA: [one next step]
Use the real interface. Do not invent product features, testimonials or results.
Structure: problem → demonstration → outcome → CTA.
Keep controls readable. Use restrained zooms and concise brand-coloured callouts.
Caption supplied speech accurately. Ask before paid generation.
If footage or key details are missing, ask me for them.
Keep the timeline editable and let me review the draft before export.05 / FIELD NOTESPolish the parts that carry the explanation
Use a zoom to direct attention, then give the viewer a moment to orient themselves. If every click gets a camera move, the video can become harder to follow. Keep related steps visually connected and check that callouts do not cover the control they describe.
If narration is present, listen through the whole edit and keep any music underneath it. If there is no narration, write on-screen text that explains the action without filling the frame. Captions should reflect the supplied speech; a visual analysis of a screen recording cannot establish what was said.
Review the opening, the most detailed interaction and the end card at phone size. Then watch the entire exported file. An editor preview can help catch mistakes, but it does not replace checking the actual delivery.
06 / FIELD NOTESAdapt the approved story for each channel
A website demo can explain the workflow with some breathing room. A short social cut needs a tighter promise and one visible proof. A customer tutorial may need more steps and less introductory branding. Use the purpose of the version to decide what stays.
For a vertical cut, crop around the important action and reposition supporting text. Shrinking a full desktop screen into a tall frame can make everything unreadable. Check platform interface overlays and preview captions at a realistic viewing size.
In Vidmoat, request each adaptation as a follow-up edit and review it before exporting. The Startup Launch Kit is a set of guided briefs, not an automatic multi-video delivery service. AI work, generation and export allowances depend on the current plan.
07 / FIELD NOTESKnow when a human finish is worth it
If this is the video visitors see first on your homepage, you may want an experienced editor to review pacing, typography and the story. Give them the source assets, the current draft and a precise list of what needs improving.
Vidmoat Community Editing supports requests for paid help. Agree the scope, quote, revision expectations and delivery timing before work starts. An editor is not automatically included in a software subscription, and availability varies.
08 / FIELD NOTESMeasure the next step, not just the play count
Decide what the video should lead to: a product visit, a trial, a demo booking or a completed onboarding task. Tag shared links consistently and compare the relevant outcome, not only views.
For an initial test, keep the main demonstration the same and change the opening promise. Use the same audience and destination where possible. Small samples can be useful feedback, but they are not proof that a winning headline will work everywhere.
Keep a simple production record as well: time spent recording, AI usage, editor assistance and revisions. A repeatable feature-announcement workflow can matter more to a small team than a one-off video that takes too much work to reproduce.
Common questions
How long should a SaaS product demo be?
For an introductory demo, 45–60 seconds is a useful starting constraint. It is not a universal rule. A detailed tutorial or sales walkthrough needs enough time for the viewer to follow the task.
Can I make a product video from screenshots?
Screenshots can explain an interface or result, but they cannot prove an interaction happened. Use a real recording when the workflow itself is the selling point, and avoid presenting animated mockups as a working product demonstration.
Do I need AI-generated video?
A clear software demonstration can use screen recordings, titles and supplied audio. Generated footage is optional. Keep the real product visible and check availability and cost before generating extra media.
