DEMOVELA FIELD GUIDE
How-to guides
Explore how-to guides for product demos and marketing videos, with specific examples, production decisions and useful next steps.
23 resources
how to
Turn a product URL into a demo ↗Begin with a supported product URL and a clear task. A URL identifies the site; it does not establish which account or workflow is appropriate.
how to
Write a six-scene demo brief ↗Six scenes can cover a useful workflow when each changes what the viewer understands. Start by listing proof moments rather than navigation destinations.
how to
Remove login from a marketing edit ↗Authentication establishes access but rarely belongs in the finished promotion. Preserve the source while choosing export windows after the product is ready.
how to
Record a responsive mobile workflow ↗Use a mobile browser context and navigate the actual phone interface. A phone-shaped border around desktop footage is a different deliverable.
how to
Choose the first frame of a demo ↗The opening frame should orient a viewer immediately. Prefer useful product evidence over a blank transition or a long logo reveal.
how to
Write a product video hook ↗A useful hook names a situation the audience recognises and makes a promise the footage can support. Avoid opening with a generic productivity claim.
how to
Add a call to action to a demo ↗The closing action should continue the video's story. Match the destination to what the viewer has just learned.
how to
Review a demo without sound ↗Muting the export reveals whether the interface and captions carry the story. Use a viewer who has not memorised the script if possible.
how to
Turn a walkthrough into a teaser ↗A walkthrough teaches a sequence; a teaser motivates another action. Select its proof moments rather than compressing every step equally.
how to
Create three different video hooks ↗Keep the underlying product proof stable while varying the opening angle. This makes each version recognisably different without inventing features.
how to
Build a demo scene index ↗A scene index makes source footage searchable and keeps edits tied to evidence. Record meaning as well as timestamps.
how to
Remove loading scenes from an edit ↗Waiting can be part of the source without being part of the finished story. Preserve cause and effect while removing dead time.
how to
Capture menus without hiding the page ↗Navigation is useful context but an open drawer can obscure the proof. Decide whether a shot demonstrates navigation or the destination.
how to
Choose music for a software video ↗Music should support pacing without masking speech or making a straightforward workflow feel frantic. Confirm usage rights for the intended distribution.
how to
Write captions for interface actions ↗Caption the meaning of the action while leaving the interface room to speak. Keep product terms consistent with the visible labels.
how to
Make a demo thumbnail ↗A thumbnail should set an accurate expectation about the video. Use a legible product state and one clear topic.
how to
Embed a demo on a landing page ↗Place the video where it answers the page's main buying question. Provide controls and enough surrounding text to explain what will play.
how to
Make a video watch page ↗A dedicated watch page gives one video a clear home. The page should be useful even before playback.
how to
Audit a final MP4 ↗Treat export validation as a separate check from editing. Inspect the actual file that viewers will receive.
how to
Refresh a demo after a UI change ↗A small interface change may only require a few new scenes. First identify which claims or controls became inaccurate.
how to
Collect useful video feedback ↗Good feedback identifies an observable problem and a proposed outcome. Timestamped notes are easier to act on than broad reactions.
how to
Create a product demo transcript ↗A transcript should describe meaningful speech and enough visual context to understand the workflow. It should not invent narration for a silent export.
how to
Recover a failed recording session ↗Recovery should use the assets already saved before repeating expensive work. First identify whether capture, planning, rendering or saving failed.