Practical founder guide

Turn a useful software discovery into a natural text-led video

Write a discovery-style wall-of-text video using a real product feature without claiming a fictional personal experience.

Choose what the viewer discovers

A discovery story draws attention to a specific useful detail. Begin with a real feature you can verify and a viewer task it supports. The discovery is a creative framing; it does not prove that a customer recently found the feature, that nobody knew about it, or that it improved a metric.

The example below imagines a fictional notes product, NorthStar Notes. Its project call note has a next-step section. Treat these as example facts to replace with your own verified product behavior.

Write the complete overlay

Try: “okay, the next steps are in the same call note.

open the project, choose the call, and check the next-step section.

one less place to look before the follow-up.” The first line names the discovery; the middle shows how to find it; the final line connects it to the viewer’s task. It does not say the app sends a follow-up or creates the next steps.

If your real interface uses different labels or steps, use those instead. If the section is optional or must be filled in manually, make that clear when it affects the promise.

From discovery to supported message
Planning choiceExampleCheck
Verified detailNext-step section in a call noteDoes the real app have it?
OpeningThe next steps are in the same noteDoes the screen show this?
ActionOpen the project and noteAre the interface steps accurate?
Personal claimI saved hoursRemove unless true and supported

Avoid turning a concept into a false testimonial

“I just found this and it saved me hours” asserts a personal experience and a measurable result. Use that only when it is true for the speaker and supported. “Here is where to find the next step” explains a feature without inventing a user story. Similarly, avoid “nobody knows this” unless you can substantiate the claim.

A generated presenter or background can illustrate a discovery, but it does not show that an actual customer discovered or used your product. Use a real product recording if the viewer needs to see the interface.

Edit for comprehension

Place the exact approved words in an editable text layer over permissioned footage. Read at normal phone size and check contrast over the full clip. Keep the screen clear enough that viewers can see the action, and remove private details from any account footage.

Ask someone unfamiliar with the draft what was discovered and what action they would take. If the answer is unclear, revise the first line or show the relevant screen. Check the exported words and product behavior before sharing; this review does not guarantee reach.

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 task: __. Verified detail: __. Discovery opening: __. Full overlay: __. Actual proof: __. Claim review: __.

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