Practical founder guide

App Demo Storyboard Template: Plan the Screens Before You Edit

Plan a demo shot by shot with a six-frame example, a recording handoff worksheet and continuity checks.

Start with one visible answer

Write the viewer’s question above the storyboard. “Where is the next step from Monday’s call?” tells the recorder which screen proves the answer. “Show our productivity platform” leaves that decision unresolved.

NorthStar below is a fictional notes app, not a customer or an integration. Its project Atlas contains a Monday call note with a next-step section. Replace these labels with real controls in your product.

Draw the frames that carry the task

A box with the selected object, control and annotation is enough. Number each frame and identify its start state, the action between frames and end state. Separate the click on Call notes from the readable list that appears.

The schematic below is an original planning diagram, not an app screenshot. Expand its three major states into the six recording instructions in the table. A storyboard is useful when it resolves what to capture, rather than merely repeating narration.

Original illustrative planning diagram. These boxes are not product screenshots.

Context

ATLAS PROJECT Call notes →

Selection

MONDAY CALL Open this note →

Result

NEXT STEPS Send the sample agenda

Original illustrative planning example
Decision or stateExampleReview
1 — ContextAtlas project and call notesHold the project title.
2 — SelectionCall notes selectedKeep the control visible.
3 — ChoiceMonday call in the listShow the list before opening.
4 — ActionMonday note opensRetain the transition.
5 — ResultNext-step sectionAllow a phone reviewer to read.
6 — EndingReal help or product destinationVerify the destination exists.

Preserve continuity across cuts

Carry one recognizable object through the sequence: Atlas, Monday’s call and its next step. Switching sample projects makes an accurate demonstration hard to follow. Mark crop boundaries so the selected control and result remain connected.

When moving to a close-up, retain an orientation cue. Do not cut directly from an overview to a finished note if viewers need to learn how to open it.

Hand the plan to the recorder

Give each frame a filename and retake condition. “03-open-monday; retake if a notification covers the title” is actionable. Record with approved sample data and compare the footage with the strip before editing.

If a control is unavailable, revise storyboard and narration together. Do not manufacture a screen to preserve a sentence. Ask a fresh reviewer which note was opened and where the next step appeared; incorrect answers identify missing evidence.

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 question:
Frame / purpose:
Starting screen and sample object:
Control -> action -> result:
Crop boundary and continuity cue:
Source filename:
Retake condition:
Ending destination:

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