Practical founder guide

Build a hook-plus-demo series around separate real product actions

Plan three distinct hook-plus-demo episodes around one SaaS feature, each with a different viewer task and its own proof.

Choose one feature with multiple real uses

A series is useful when each episode answers a different question, not when the same clip is republished with a changed adjective. Start with one feature you can verify, then list separate audience tasks that it actually supports. Plan each opening, screen action and ending together.

These three episodes are fictional planning exercises for a note-taking app with project call notes and a next-step section. They are not owned videos or customer results.

Episode 1: find the next step after a call

Opening: “the call ended. where did the next step go?” Product proof: open the relevant project and call note, then show its next-step section. Ending: “check the action you recorded.” This episode addresses the caller preparing to follow up. Do not claim automatic writing or sending unless the real product demonstrates it.

Record a sanitized note that the viewer can read, and confirm the section actually exists in the current interface.

Three episode briefs
EpisodeDistinct viewer taskScreen proof
1Prepare a follow-upCall note and next-step section
2Understand a teammate handoffProject and authorized note
3Prepare for a later meetingPrior call note and recorded action
ReviewAvoid duplicate tasksCheck actual feature and permissions

Episode 2 and 3: two different contexts

Episode 2, teammate handoff: “taking over this project? start with the last call note.” Show the project and a note the teammate is authorized to access. End with “review the recorded next action.” Verify that the teammate can actually access the note before claiming a handoff.

Episode 3, preparing for a later meeting: “before the next meeting, check what was agreed last time.” Show the prior call note and its next-step section. End with “bring the recorded action into the next discussion.” This is a preparation context, not a claim that the product automatically schedules a meeting.

Review each episode on its own

Make an evidence record for each actual clip: approved hook words, product screen, permission, export and review feedback. If two episodes show the same task and proof with no meaningful distinction, combine them. If a proposed episode depends on a feature or permission you lack, revise or leave it unproduced.

Watch each final export at phone size and check exact overlays. These briefs do not establish that the episodes have been filmed, reviewed or tested.

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.

Feature: __. Episode 1 task and proof: __. Episode 2: __. Episode 3: __. Access conditions: __. Actual exports reviewed: __.

Browse the founder guide library for the next task in your workflow.