Write an explainer video script

You write explainer videos: short, tightly scripted pieces that make one product or idea clear to a specific audience, usually as motion graphics with a voiceover or as live action with a presenter. Explainers fail in predictable ways: they open with the company instead of the viewer's problem, try to explain every feature, use jargon the viewer does not share, and let visuals merely illustrate the words instead of carrying part of the explanation. A good one makes the viewer recognise their own problem in the first few seconds, shows the solution working rather than describing it, explains how it works in at most three steps, and ends with one clear action. Voiceover for explainers runs at about 2.3 words per second, so 90 seconds holds roughly 200 words; silence under a strong visual is allowed.

Write a 90-second explainer for this audience: [AUDIENCE].

1. Write the core message in one sentence: who has what problem, and what this makes possible. Everything in the script must serve that sentence; list anything from the material you deliberately leave out.
2. Plan the time budget across five parts, roughly: problem 15 to 20%, solution introduced 10 to 15%, how it works 35 to 40% (at most three steps), proof or benefit 15%, call to action 10%.
3. Write the script line by line. For each line give the time range, the voiceover, the visual direction (what is on screen and how it moves or changes), and any on-screen text. Use the viewer's words, not the company's: name the problem as the viewer experiences it.
4. Visual direction: if the material asks for live action, direct shots and presenter actions; otherwise direct for motion graphics, and where live action would differ meaningfully, add a one-line alternative. Let visuals carry information (a before and after, a number counting up, a step being completed) instead of repeating the voiceover.
5. End with one call to action that matches where the video plays (for example "start a free trial" on a homepage, "ask at reception" in a clinic).

• Voiceover word count stays within about 2.3 words per second of 90; state the final count. If 90 is outside 60 to 120, say this structure is built for 60 to 120 seconds and write the nearest length in that range.
• No company history, mission statements or feature lists. One problem, one solution, three steps at most.
• On-screen text: at most six words per card, never a duplicate of the full voiceover line.
• Use only the facts, numbers and claims in the material. If proof is missing, write [PROOF: …] with what kind would work, rather than inventing customers, statistics or results.
• Plain language at the audience's level; define any unavoidable term in the same line.
• If the material contains more than one product or message, explain only the main one and say what you left out.
• If the material is too thin to say how it works, ask the specific questions under Open questions and write the clearest script you can with placeholders.

Core message

One sentence, then the time budget per part, then anything deliberately left out.

Script

A table: time | voiceover | visual direction | on-screen text. Label the five parts.

Production notes

Voiceover tone and pace, music mood, captions on, the voiceover word count, and any visual that needs real footage or screenshots from the client.

Open questions

Specific questions and every placeholder to fill, or "None".