Make the opening a promise to the reader
An opening slide should help the intended reader decide whether the remaining slides address their task. Write the body first, then describe its actual subject in one short line. A curiosity gap can invite a swipe, but it should not promise a result or feature the later slides do not show.
The examples below use a fictional notes app with a call note and a next-step section. They are original planning examples, not recorded campaigns or verified outcomes.
Pair each opening with its body
For a story sequence about finding an agreed action after a call, an opening could be “the call is over. where did the next step go?” The body should then show the situation, the note, and the next-step section. It should not turn into an unrelated list of generic productivity tips.
For a tutorial sequence, “how to find the next step from a call” sets an instructional expectation. Follow it with the project, call note, next-step section and a review step. Confirm the real interface before using those instructions.
For a feature story, “keep the next step with the call note” names the feature directly. The following slides should explain its context and show the actual section where permitted.
| Opening | Body must contain | Review |
|---|---|---|
| Where did the next step go? | Situation, note and next-step section | Does the sequence resolve the question? |
| How to find the next step | Accurate ordered instructions | Can the reader follow the steps? |
| Keep the next step with the note | A supported feature explanation | Is the feature shown or verified? |
| It sends every follow-up | Evidence of automatic sending | Remove if unverified |
Remove unsupported hooks
“This app sends every follow-up for you” is a poor opening if the body only shows a note. Either demonstrate a verified sending feature and its conditions or replace the claim with the action that is actually visible. Avoid invented statistics, testimonials or promises of instant results.
Write a short promise check: opening claim, body slide that supports it, and source of evidence. If no body slide answers the promise, revise the opening or the sequence.
Review the first slide on a phone
Use readable text and enough contrast against an owned or permissioned visual. A long title may need fewer words instead of smaller type. Check that cropping or platform controls do not obscure the text. Then view all slides in order and ask a reader what the opening led them to expect and whether the sequence answered it.
Save the exact opening and body together so a later revision does not accidentally break the match. This is a clarity exercise, not a guarantee of higher 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.
Intended reader: __. Body sequence: __. Opening promise: __. Supporting slide: __. Evidence: __. Final text: __.Browse the founder guide library for the next task in your workflow.