Practical founder guide

Choose hook, talking-head, wall text or slideshow from a reference idea

Choose between reaction-plus-demo, wall-of-text and slideshow treatments for the same SaaS message.

Extract the task before selecting a reference format

A reference can suggest a format, but the format should serve your viewer’s task and your actual product. Identify the verified feature, the proof available and whether the reader needs to see a screen action, read a short story or follow several steps. Record the reference source and use only assets you have permission to reuse.

The examples below are fictional plans for NorthStar Notes, a notes app with a call note and next-step section. They are not finished assets or measured results.

Express the same brief three ways

Reaction plus demo: “wait, the next steps are right here,” followed by a real recording that opens the note and holds the section. Choose this when the feature can be understood visually in a short sequence.

Wall of text: “the call is over. the follow-up is tomorrow. open the project note and check the next-step section.” Place the words over calm permissioned footage. Choose this when the situation and written observation are the main message.

Slideshow: “where did the next step go?” then the post-call situation, open the project note, check the section, and start with the next action. Choose this when the reader benefits from separate beats or instructions.

Format decision
FormatWhat carries the messageProof or review
Reaction plus demoOpening and visible app actionCan the feature be understood on screen?
Wall of textWritten situation and supported factCan the overlay be read in time?
SlideshowA sequence of separate beatsDoes each slide advance the task?
No suitable formatThe product cannot support the claimRevise the message or reject the reference

Match proof and production constraints

A generated background illustrates a scene; it does not demonstrate your software. Use an actual sanitized screen recording or screenshot when the message depends on showing the interface. Confirm labels, access conditions and whether the user must create the note manually. If a reference depends on a feature you do not have, change the claim rather than copying it.

Use original text and footage or obtain the appropriate permission for each reused element. A popular reference does not establish permission or guarantee that your version will have similar results.

Make a decision and review it

Choose the format that most directly explains the task with the proof you can supply. If all three contain the same words and no distinct purpose, develop one useful asset rather than making near-duplicates. Preview the final version on a phone and ask an unfamiliar viewer to identify the product action.

Record the chosen concept and the actual review feedback. Treat audience fit and performance as hypotheses until you observe real data.

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 task: __. Verified feature: __. Available proof: __. Reference rights: __. Three concepts: __. Selected format and reason: __.

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