Who this is for: Product marketers, founders and motion producers planning a software launch.
What to prepare
- Verified product behavior
- Approved example screens
- A list of claims the team can support
- Known limitations
Choose the evidence you actually have
A new product can explain its value without pretending that customers have validated every promise. A clear demonstration lets the viewer inspect a useful action. A limitation helps them decide whether that action fits their situation.
Consider an illustrative note-review tool. The team can show a supplied note receiving a tag and a follow-up owner. It has no approved customer quote or measured adoption result. The launch should use the note workflow as evidence and leave outcome claims unmade.
Build an evidence ladder
Order the available material by what it can establish. Moving up the ladder requires new evidence, not more confident copy.
- Product identity: an approved name and interface show what is being introduced, but not that anyone achieved a result.
- Observable behavior: matching states show the defined action and outcome for the example.
- Illustrative scenario: a clearly fictional situation explains when the behavior could be useful, without pretending it happened to a customer.
- Verified first-party measurement: if later supplied, report its actual method and limits rather than turning one observation into a universal claim.
- Approved customer evidence: if later available, retain the genuine wording, permission and relevant context. Do not invent this layer for the launch.
Write a demonstration-led story
A usable opening for the fictional tool is “Decide what happens next to a collected note.” Show the note, tag it, assign a follow-up owner and hold on the result. Label example data where needed. The story remains concrete without claiming increased productivity.
Replace trust-shaped decoration with explanation. A strip of invented company logos creates a false endorsement. A made-up usage counter implies adoption. Neither is necessary to show why a task might matter.
A founder's genuine motivation can add context, but do not fabricate a quote in their voice. Ask for approved wording or use a neutral statement about the task. Similarly, an illustrative persona should remain visibly fictional rather than acquiring a company name and performance result.
Before publishing, list what the viewer could reasonably infer. If the images suggest real customer success while the fine print says illustration, revise the images. Honesty belongs in the main presentation, not only in a disclaimer.
Review checklist
- Examples are explicitly illustrative where appropriate.
- No invented endorsement, customer identity or usage metric appears.
- The promise is supported by observable behavior.
- The film's visual implications agree with its written boundaries.