Separate the problem from the claim
A talking-head script should move from a recognizable task to a product action the screen can demonstrate. Start with a person, a moment and one supported action. Avoid stating a customer problem as a verified universal fact unless you have the evidence.
For this fictional exercise, a small team needs to check next steps after a call. The example app, NorthStar Notes, contains a project call note and a next-step section. These are assumed facts, not a customer interview.
Compare a vague script with a specific one
Vague: “Managing work is hard. Our AI platform makes your team more productive. Try it today.” This does not say which task the app performs, and it promises a broad outcome without proof.
Specific: “After a call, you may need to check what comes next. Open the project, choose the call note, and look at the next-step section. That gives you a starting point for the follow-up.” Record the app action as the speaker names it. Check that the real interface and wording match before using this script.
| Script element | Weak version | Specific version |
|---|---|---|
| Problem | Work is hard | Find the next step after a call |
| Product claim | Makes teams productive | Open a call note |
| Screen proof | Unrelated dashboard | Show the next-step section |
| Closing | Try it today | Start with the relevant action |
Map each sentence to a shot
Use a talking-head shot for the setup, then cut to a readable app recording when the action begins. As “choose the call note” is spoken, show the note being opened. Hold the next-step section while the final sentence is spoken. Do not add fictional automation or an unverified time-saving claim to make the ending stronger.
If the screen action takes longer than the spoken line, leave a short visual pause rather than racing through the interface. Use a sample account and remove identifying or confidential information.
Review the spoken words and final video
Read the script aloud at a natural pace. Remove sentences that do not help the viewer understand the task. If subtitles are used, check that they match the speaker and do not hide the important screen control. A generated presenter can illustrate the script but should not pose as a customer with an invented experience.
Ask a reviewer to explain the problem and the demonstrated action after one viewing. If the connection is unclear, improve the script or rerecord the proof. No view or conversion result can be inferred from this example.
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.
Viewer and moment: __. Verified app action: __. Spoken setup: __. Screen action: __. Ending: __. Claims to check: __.Browse the founder guide library for the next task in your workflow.