Decide what the speaker needs to explain
A talking-head opening gives context in a human voice; a product recording shows what happens in the app. Choose one audience task and one verified product action before writing. If the screen alone explains the whole task, a silent demo may be enough. Use a speaker when a brief explanation helps the viewer understand why the action matters.
This example is a fictional planning brief for NorthStar Notes: a project call note contains a next-step section. It is not a customer story or an actual export.
Write the complete script and shot plan
Speaker: “After a call, you might need to find the next step before following up.” Cut to a project recording. Speaker: “Open the project and choose the call note.” Show that action. Speaker: “The next-step section is in the note, so you can check what comes next.” Hold the section long enough to read it.
For your own app, replace the assumed feature with a supported one and verify the current labels. If the feature requires a setting or manual input, do not imply that it happens automatically. Remove private data before recording.
| Beat | Spoken line | Screen or review |
|---|---|---|
| Setup | Find the next step after a call | Speaker introduces the task |
| Action | Open the project and call note | Show the actual navigation |
| Proof | Check the next-step section | Hold a readable real screen |
| Review | What should the viewer do next? | Confirm the export answers the question |
Keep the handoff understandable
Start the screen recording at a frame that gives enough context to identify the project, then show the relevant interaction. If a transition feels abrupt, a short bridge label can clarify where the viewer is. Time speech with the visible action; do not say “here” while the relevant control is hidden.
Captions should reproduce the approved spoken words and leave the interface readable. A generated speaker is an illustrative presenter, not a real user endorsement. Do not attribute invented personal experiences or results to the speaker.
Review the finished version
Watch the final export at phone size. Check that the words, actions and resulting screen agree, and that the audience can identify the next step. Ask someone unfamiliar with the app to explain what was demonstrated. If they cannot, simplify the script or re-record the screen instead of adding unsupported claims.
Keep the script and any approved product footage for future iterations. This worksheet is a production plan, not proof that a video was recorded or that a particular format will drive results.
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 action: __. Speaker script: __. Screen recording: __. Privacy review: __. Final check: __.Browse the founder guide library for the next task in your workflow.