What makes a useful breakdown
A useful breakdown identifies the exact hook, the first product frame and the visible action that answers the opening. Use a complete video you own or have permission to analyze and share. A list of hooks cannot show whether the later product view actually proves the opening.
Illustrative shot plan
For a fictional notes app, a planning sequence might be: reaction with “the next steps are right here”; a project screen; a call note opening; and a held view of a next-step section. This is a written example, not a real clip, a customer story or an observed result. Confirm that your real app supports the same behavior before using it.
| Shot | Question | Evidence |
|---|---|---|
| Hook | What does the opening promise? | Exact words and timing |
| Demo | Which product action is visible? | Permissioned screen recording |
| Handoff | Does the screen answer the hook? | Actual frames and review notes |
Annotate an actual asset
For each shot record its start and end time, the exact text, the screen action and why it follows the previous shot. Capture a readable frame only when you have rights to reproduce it. Mark any unsupported claim or missing context and describe the actual revision, rather than presenting a hypothetical correction as a completed edit.
Review before publication
Check the final video for readable product proof, permissioned footage, accurate text and removed private data. Save the original asset, annotated frames and review notes. Do not claim that an example produced views or conversions without verified evidence.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
Source and permission: __. Product fact and evidence: __. Actual asset or version: __. Review observation: __. Correction and approval: __.Browse the founder guide library for the next task in your workflow.