The 30-second product demo — a five-beat structure that actually lands
Most product demo reels lose the viewer in eight seconds. Here's the script structure I use when I'm building one for a launch.
A 30-second product demo is the most over-engineered, under-scripted artifact in modern software marketing. Founders pay studios five figures for a 90-second mood reel that opens on a slow zoom over a stock-photo office. By second eight, the viewer is gone.
Demos die for a structural reason: they're shot like trailers when they should be shot like answers.
Here's the structure I use.
The five beats
Thirty seconds, no audio assumed, no narrator needed. Five beats, roughly:
| Beat | Time | Job |
|---|---|---|
| Hook | 0–3s | Show the result, not the setup. |
| Context | 3–8s | One line: who this is for. |
| Demo | 8–22s | The product, mid-flow, doing the thing. |
| Proof | 22–26s | One stat or fact that says this is real. |
| CTA | 26–30s | One explicit ask. |
Total: 30 seconds. If you're at 45, you're showing too much. If you're at 20, you're showing too little.
1. Hook (0–3s) — show the result
You have three seconds to make someone not close the tab. Don't open with your logo. Don't open with a sweeping camera move over an empty workspace. Don't open with the words "Introducing…".
Open on the result. A booking notification arriving. An invoice clearing. A waitlist auto-filling a salon chair. The thing that, if your viewer never watches another frame, you'd still want them to remember.
If the result is hard to show in three seconds, your product is harder to demo than you think — and that's its own problem.
2. Context (3–8s) — one line of who
A single line of typography overlaid on the next product shot. Not narration. Text. Specific, not categorical:
- ✗ "For modern teams" — means nothing.
- ✓ "Built for salons that lose money to no-shows."
- ✓ "For founders booking a Series A in 60 days."
This is the second-fastest thing the viewer reads. It's the first thing that tells them whether they're the audience.
3. Demo (8–22s) — the product, mid-flow
Fourteen seconds. The longest beat. The product doing the thing, in real UI, mid-flow. Cuts can be quick — every second should advance the story. No setup screens, no empty states, no "first, click here." The viewer fills in the gaps; treat them as smart.
Two rules that save most demos:
- No mouse cursor unless it's making a meaningful click. Idle mouse-wiggling reads as amateur.
- No "lorem ipsum" or
[email protected]. Use realistic-looking content. The brain spots placeholder data instantly and writes the whole demo off as fake.
4. Proof (22–26s) — one fact
Four seconds. A single line of text or a chart frame that says this works in the real world. Not five facts. One.
- "14,000 reschedules processed this month."
- "Replaced three Calendly tools at Allbirds."
- "Avg. 27 seconds from cancellation to refill."
If you don't have a real number yet, name a real customer. If you don't have a real customer yet, skip the proof beat and lean harder on the demo. Don't fabricate a stat. People can tell.
5. CTA (26–30s) — one ask
Don't waste the last beat on a logo flourish. Show the URL. Show the email. Show the calendar link. Whatever you actually want them to do, only one of them, in plain readable text.
If you can't decide between "Sign up" and "Book a call," you don't have a CTA — you have indecision. Pick.
Common ways this gets wrecked
A non-exhaustive list of demo-reel anti-patterns I see weekly:
- The 90-second mood reel. Slow zooms, ambient music, "for the founders who…" voiceover. This is a film school exercise, not a demo.
- The feature parade. Six features, four seconds each, no narrative thread. The viewer leaves remembering nothing.
- The "before/after" gimmick. "Without our product: chaos. With our product: zen." Insulting to the viewer and never as funny as you think.
- Music that fights the product. If the soundtrack tells the viewer what to feel before the UI does, the music is wrong.
- No captions. Most people watch on mute. If your demo needs audio to make sense, it's not a demo — it's a screencast.
Length, audio, format
- Length: 30 seconds is the right target. 45 seconds is forgivable if the product is genuinely complex. 60 is rarely justifiable. 90 is a mistake.
- Audio: optional, never required. The demo has to make sense silent. If you add music, make it ambient and short.
- Format: render landscape (16:9) for the website hero, then cut a vertical (9:16) version for Reels/Shorts and a square (1:1) for Instagram feed. Same script, three cuts. Plan for it from the start.
The point
A demo reel isn't a brand exercise. It's a 30-second answer to one question: would you keep reading? Everything in the cut serves that.
If you're scripting one and you're not sure which line to cut, cut the line. The viewer will fill it in.