Product Demo Recording Brief Template
Give a founder or creator a precise recording brief with real setup, screen sequence, proof points and claims to avoid.
Read this resource as Markdown
When to use this template
Use this when handing a demo to a founder, editor or creator and you need the recording to show the actual task instead of improvising unsupported product claims.
Choose another approach when: You expect the recorder to invent a personal testimonial, imitate another creator’s identity, or conceal that the example is staged demo data.
Gather these inputs
- The available product build and a safe demo account.
- The task, audience and approved claims.
- A list of private data and unverified features that must not appear.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
Illustrative brief for a shared client-review tool: Use the demo project “Cafe menu refresh” and synthetic client details. Record uploading one design version, requesting review and viewing the resulting approval record. The spoken line may say, “Here is where this version’s approval is stored,” if the screen demonstrates it. Do not say, “My clients approved projects twice as fast,” unless that is the recorder’s genuine, supportable experience and approved for use. Hide real notifications before recording. Keep the same design version visible throughout the cut and return the draft to the product owner for accuracy review.
How to use it
- Rehearse the task in the exact account and build the recorder will use.
- Match every proposed claim to visible or otherwise verifiable evidence.
- Review the edited recording for continuity, privacy and truthful availability before any publication.
Check before using it
- No personal experience or testimonial has been fabricated.
- The recording does not expose private account information.
- An editing cut has not made an unavailable automation appear real.
What to measure
Count whether the brief produced an accurate usable recording and record revision reasons. Later audience or acquisition results are separate evidence and should not be promised in the production handoff.
Research and sources
The cited platform guidance supports accurate interface demonstrations and fulfilling viewer expectations. The production handoff and claim controls are original editorial practice, not a platform endorsement.
- Apple: App Store Asset Best Practices — checked 2026-10-23. Show actual UI and sequence screenshots around useful features and an understandable story.
- YouTube: Understand your content performance — checked 2026-10-23. Align title, thumbnail, opening and delivered value; observe audience response.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.