Why it matters
Supporting footage should add meaning rather than conceal missing evidence. A generic dashboard pan cannot prove a specific automation, and stock footage of a happy person does not establish that a customer used the product.
Apply the idea to product footage
- Identify what the main explanation needs the viewer to see at each moment. Select supporting footage that clarifies that idea.
- Capture clean holds and detail views during the source session so the editor has relevant material for transitions and narration.
- Label the footage by what it actually shows, including product version and any synthetic data. Keep conceptual or stock material distinguishable from recorded product evidence.
A concrete example
An illustrative founder-led demo can cut from the presenter to a close view of the actual task queue while the founder explains prioritisation. The queue footage supports the explanation; a later recorded status change supplies the proof of the action.
Limits and checks
B-roll is not permission to imply a result that was never demonstrated. Check rights for stock footage and avoid presenting actors or fictional accounts as real customers.
Your next step
Add two or three relevant supporting shots to the shot list, each tied to a specific line or transition.
References and scope
Examples are illustrative production guidance, not measured customer results. General workflows are not promises of product compatibility. Read our editorial approach and current Demovela scope.