The SaaS explainer scripting framework
If a prospect can't explain your product back to a colleague after watching, the script failed — not the edit. Here's the five-beat structure we script every explainer against.
Beat 1 — The familiar problem (0:00–0:12)
Open on a situation your buyer already recognizes, stated in their language, not yours. Skip the category jargon entirely — describe the workday friction, not the market gap.
Beat 2 — The stakes of doing nothing (0:12–0:24)
Name the cost of the status quo in concrete terms: time lost, revenue missed, or risk carried. This beat earns the viewer's attention for the solution that follows — skipping it makes the product feel like a nice-to-have rather than a fix.
Beat 3 — The solution, shown not told (0:24–0:55)
This is where screen capture does the heavy lifting. Narrate only what the viewer can't infer from the screen — the "why," not the "what." If a click is self-explanatory, let the visual carry it silently.
Beat 4 — Proof it actually works (0:55–1:10)
One concrete result — a metric, a before/after, or a specific customer outcome — lands harder than a general claim of quality. Keep it to a single proof point; stacking several dilutes all of them.
Beat 5 — One clear next action (1:10–1:20)
End on a single call to action, stated as plainly as possible. Explainers that offer two competing CTAs — "start a trial" and "book a demo" in the same breath — consistently convert worse than ones that commit to one path.
A note on length
Ninety seconds is a ceiling, not a target. If your product's value can land in 45 seconds, a longer cut only adds drop-off risk. Script to the shortest version that still earns the CTA.