How does this video script generator work?
It's a set of sentence patterns, not an AI model. We wrote three hook patterns, three endings and a set of lines for each scene, in three tones. Your answers fill the gaps, the length you pick decides which scenes appear, and the time is split across them by weight. Because nothing is invented, the script only says what you told it, which is the point: a launch video should make claims you can stand behind.
- Fill in the nine fields. Name, what it does, who it is for, the problem, up to three features, optional proof and a call to action. The example values show the shape each answer should take.
- Pick a length and a tone. Choose 15, 30, 60 or 90 seconds and a plain, bold or playful voice. The length decides which scenes appear and how long each one gets.
- Read the script. Each scene has its timecode, on-screen direction and text, and the voiceover line, with a word count against that scene's budget.
- Check the fit. The total is checked at 150 words per minute. Aim for under 90% of the budget so the first second and the end card can run without voiceover.
- Regenerate for another version. Rotates through three hook patterns and three endings, nine versions per tone, without changing your inputs.
- Copy it and edit. Copy the script as plain text, replace the [bracketed] notes, and read it aloud with a timer.
Word counts are for the voiceover only; on-screen text is read, not spoken. The read time uses 150 words per minute, the usual planning pace for a voiceover: VideoScribe plans 130 to 150 (VideoScribe), Descript suggests 150 to 160 for explainers and commercials (Descript), and a study of 862 online videos measured an average of 156 (Guo, Kim and Rubin, 2014). If you read slower, time your draft in the script length calculator at your own pace.
What goes in each scene of a launch video script?
Six beats, in the same order as our video script template: problem before product, proof before the ask. The seconds below are what the generator gives each scene when every field is filled in.
| Scene | Its job | Built from | 15 s | 30 s | 60 s | 90 s |
|---|---|---|---|---|---|---|
| Hook | Stops the scroll. Opens on the viewer's problem, the audience, or the result. | Problem, who, or what it does | 3 s | 4 s | 5 s | 6 s |
| Problem | Makes the problem feel familiar and says what it costs. Dropped at 15 seconds. | Problem | – | 5 s | 9 s | 14 s |
| Solution | Names the product and says what it does in one sentence. | Name, what it does, who | 5 s | 6 s | 8 s | 12 s |
| Features | One sentence and one shot per feature: 1 at 15 s, 2 at 30 s, 3 at 60 and 90 s. | Features 1 to 3 | 4 s | 8 s | 24 s | 36 s |
| Proof | One reason to believe. Left out if you leave it blank, and at 15 seconds. | Proof | – | 4 s | 7 s | 12 s |
| Call to action | Name and one next step, with the URL on an end card. | Name, call to action | 3 s | 3 s | 7 s | 10 s |
The hook is the scene that changes most between versions. "Problem first" opens on the problem in the viewer's words. "Call out the audience" names who it's for, then the problem. "Result first" opens on what the product does and moves the problem to the next scene. Whichever you pick, the problem scene never repeats the hook: if the hook already stated the problem, the next scene says what it costs instead.
What does a generated launch video script look like?
Illustrative example. Parcelpine is a made-up product, not a real company, and its beta figure is invented to show the shape of a proof line. These are the generator's starting values, so you can see this exact script in the tool above.
60-second script: Parcelpine, order tracking for small online shops
| Scene | On screen | Voiceover |
|---|---|---|
| Hook0:00–0:05 · 9 / 13 words | The problem moment in their day. Text: “Customers email every day asking where their order is” (shorten to 6 words or fewer for screen) | Customers email every day asking where their order is. |
| Problem0:05–0:14 · 16 / 23 words | Today's workaround, shown plainly: the inbox, the spreadsheet, the extra tabs. One short caption at most. | It takes time you'd rather spend on the real work, and it comes back every week. |
| Solution0:14–0:22 · 19 / 20 words | Logo: Parcelpine. Text: “Turns your shipping emails into one tracking page”. Then the main screen. | Parcelpine turns your shipping emails into one tracking page. Built for small online shop owners. Here's how it works. |
| Feature 10:22–0:30 · 8 / 20 words | Product UI, one action. Text: “Pulls tracking numbers from your shipping emails” | It pulls tracking numbers from your shipping emails. |
| Feature 20:30–0:38 · 10 / 20 words | Product UI, one action. Text: “Sends each customer one link that updates itself” | It also sends each customer one link that updates itself. |
| Feature 30:38–0:46 · 11 / 20 words | Product UI, one action. Text: “Flags parcels that stop moving before the customer notices” (shorten to 6 words or fewer for screen) | And it flags parcels that stop moving before the customer notices. |
| Proof0:46–0:53 · 13 / 18 words | Large type: “In the beta, 38 shops cut "where is my order" emails by half” (shorten to 6 words or fewer for screen). Hold 3 seconds. | In the beta, 38 shops cut "where is my order" emails by half. |
| Call to action0:53–1:00 · 9 / 18 words | End card: Parcelpine · Try it free for 14 days at parcelpine.example. Hold 3 seconds or more. | Parcelpine. Try it free for 14 days at parcelpine.example. |
95 spoken words of a 150-word budget, about 0:38 of voiceover at 150 wpm. Plain tone, version 1.
Notice what the template doesn't do. It doesn't call Parcelpine "revolutionary" or promise to "transform" anything; every claim is one of the inputs. It leaves about a third of the 60-second budget unspoken, which is normal: the opening shot and the end card usually carry no voiceover, and feature shots need a beat to show the product working.
The same product at 15 seconds
| Scene | On screen | Voiceover |
|---|---|---|
| Hook0:00–0:03 · 9 / 8 words | The problem moment in their day. Text: “Customers email every day asking where their order is” (shorten to 6 words or fewer for screen) | Customers email every day asking where their order is. |
| Solution0:03–0:08 · 9 / 13 words | Logo: Parcelpine. Text: “Turns your shipping emails into one tracking page”. Then the main screen. | Parcelpine turns your shipping emails into one tracking page. |
| Feature 10:08–0:12 · 8 / 10 words | Product UI, one action. Text: “Pulls tracking numbers from your shipping emails” | It pulls tracking numbers from your shipping emails. |
| Call to action0:12–0:15 · 9 / 8 words | End card: Parcelpine · Try it free for 14 days at parcelpine.example. Hold 3 seconds or more. | Parcelpine. Try it free for 14 days at parcelpine.example. |
35 of 38 words: Fits 15 seconds, just. Under 90% of the budget leaves room for a silent opening and end card, so trim a few words if you can.
Three tones, three hooks
The same inputs, opened nine ways. Tone changes the voice; the hook pattern changes what the viewer hears first.
| Tone | Problem first | Call out the audience | Result first |
|---|---|---|---|
| Plain | Customers email every day asking where their order is. | Most small online shop owners know this one. Customers email every day asking where their order is. | Parcelpine turns your shipping emails into one tracking page. Here's why that matters. |
| Bold | Customers email every day asking where their order is. Let's fix that. | Small online shop owners, you've put up with this long enough. Customers email every day asking where their order is. | Parcelpine turns your shipping emails into one tracking page. No more workarounds. |
| Playful | Be honest. Does this sound familiar? Customers email every day asking where their order is. | Raise your hand, small online shop owners, if this sounds familiar. Customers email every day asking where their order is. | Imagine if something just turns your shipping emails into one tracking page. Now something does. |
How do you write a 15, 30, 60 or 90-second launch video script?
15 seconds (about 38 words)
One idea. The generator drops the problem and proof scenes and keeps the hook, the product in one sentence, one feature and the call to action. Use it for ads, story formats and a teaser before launch day. Let the on-screen text do more of the work than the voiceover, and keep the hook to one short sentence.
30 seconds (about 75 words)
The problem gets one sentence, the product one, and two features share a scene. If you have proof, keep it to one number. This length suits a post on X or LinkedIn, or a cut-down to run beside the full video. At 30 seconds the budget fills fast, so a long feature line is the first thing to shorten.
60 seconds (about 150 words)
All six beats, with one sentence and one shot per feature. This is the version to write first and cut the others from. Landing at 100 to 135 spoken words is fine, since the first seconds and the end card often run without voiceover. Keep any on-screen text up long enough to read; TechSmith suggests at least three seconds (TechSmith).
90 seconds (about 225 words)
Room for one detail only your customers would recognise in the problem scene, and a sentence on what each feature saves them. The generator marks those spots with [notes]. Use the extra time for a customer quote in the proof scene, not for more features. Don't fill the budget just because it's there; a tight 70-second script beats a padded 90.
How do you get a better script out of the generator?
- Write the problem the way a customer would say it. "Customers email every day asking where their order is" works. "Post-purchase communication inefficiency" doesn't, and no template can fix it.
- Start "what it does" and each feature with a verb. "Turns", "sends", "flags". The generator reads a verb phrase as "It turns…"; a noun phrase like "Slack sync" stands as its own short sentence.
- Make features actions, not adjectives. "Flags parcels that stop moving" can be shown on screen. "Powerful and intuitive" can't.
- Only add proof you can back up. A beta number, a named customer, a measured result. If you don't have one yet, leave it blank and the scene disappears.
- Give one call to action with the URL. "Try it free at yoursite.com" beats three options.
- Read it aloud with a timer. Every script reads differently out loud. Paste it into the script length calculator or convert word counts with the words to minutes converter.
Should you use the generator or the video script template?
Use this generator when you want a complete first draft fast: structured answers in, a full script with on-screen text, tone and a fit check out. Use the video script template when you'd rather write each beat yourself; it has blank 30, 60 and 90-second templates with a word budget per beat, three example scripts and a simpler builder. A good workflow is to generate a draft here, then rewrite it beat by beat against the template.
Once the script is done, how to make a launch video covers turning it into the video itself. Launching on Product Hunt? The video goes on your product page as a YouTube link; the Product Hunt launch guide covers the rest of the page, and the product launch checklist covers everything else around launch day.