Choose what the opening must establish
The first scene should orient a viewer to a specific software task and give a reason to continue to the demonstration. Decide whether the viewer needs a spoken problem, a question or an immediate instruction. Each option should lead to the same supported product action.
Three fictional opening scripts
For a fictional call-note feature: problem opening, “the call ended and you need the next step”; question opening, “where did the action from the call go?”; instruction opening, “open your project note before the follow-up.” These are writing options, not owned recordings or tested hooks.
| Opening | Purpose | Proof |
|---|---|---|
| Problem | Establish a post-call situation | Open the relevant call note |
| Question | Ask where the next action is | Show the next-step section |
| Instruction | Tell the viewer what to open | Demonstrate the actual navigation |
Pair each opening with proof
Show the project, open the relevant note and hold its next-step section. If the real product uses a different workflow, rewrite the lines to match it. Do not imply that the software writes or sends a follow-up unless the demonstrated feature actually does so.
Review the actual first scenes
Record permissioned variants only when available. Ask a reviewer what task each opening sets up, then save real feedback and exact versions. The clearest opening is a review finding, not something that can be inferred from a sample script.
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.
Audience and task: __. Verified product fact: __. Planned words and action: __. Asset source and permission: __. Actual review observations: __.Browse the founder guide library for the next task in your workflow.