Practical founder guide

Answer a SaaS objection with a talking-head explanation and real proof

Plan a talking-head SaaS video that answers a specific question with a real product demonstration, using a clearly hypothetical objection.

Start with a question you can answer

Choose an objection or uncertainty that a potential user may have, then identify what your product can actually show in response. Prefer a question you have heard with permission to use it. Otherwise label it as a hypothetical planning example; do not present it as a customer quote. Avoid answering a broad concern with a feature that does not resolve it.

This fictional example assumes NorthStar Notes keeps a call note and a next-step section together. The hypothetical question is: “Where do I find the next steps after a call?” The example is not a customer interview.

Write an explanation and a screen action

A short script could be: “If you need the next steps from a call, open the project and choose the call note. The next-step section is in that note.” Show the project view, opening the note and the relevant section as the words describe them. If the actual app requires more steps, show or explain those steps rather than hiding them.

A weak answer would be “our AI automatically handles all your follow-ups” over the same recording. The visible note does not establish automatic writing, delivery or completion. Remove those claims unless your product actually supports them and the proof is shown.

Question-to-proof review
Question or statementEvidence requiredEditing decision
“Where are the next steps?”A real note showing its sectionShow the section when it is named
“The app writes the follow-up”Verified automation and its outputRemove if the clip only opens a note
“I use this every day”Truthful speaker experienceDo not use for an invented presenter
Price or privacy questionCurrent official product informationCheck documentation before stating it

Make speech and evidence agree

Create a two-column review before filming: each spoken sentence on one side and the corresponding screen or source on the other. Delete or qualify a sentence that has no supporting evidence. Use a sample account or obtain permission for any real information shown. If the question involves price, privacy or a feature limit, check current product documentation rather than guessing.

A generated presenter can deliver an illustrative script, but it is not a real customer endorsing the product. Make the speaker’s role clear and do not invent a personal experience or outcome.

Review the handoff and finish

When the speaker says “choose the call note,” the recording should show the relevant click or a clear resulting screen. Avoid covering the control with subtitles, and give viewers enough time to read the result. If the action is difficult to see, crop or rerecord the screen while retaining context.

Check the final export on a phone and compare the spoken script, captions and screen. Ask someone unfamiliar with the product whether the original question was answered. A successful review shows clarity, not evidence of conversions or guaranteed performance.

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.

Question and source: __. Hypothetical or actual: __. Verified answer: __. Spoken script: __. Screen proof: __. Claims to remove: __.

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