Product Launch Video Examples: 3 Launch Videos Broken Down Second by Second
Three complete product launch videos, a SaaS tool, an AI product, and a developer tool, broken down second by second: every beat, line, and timing explained.
September 2026
Most lists of launch video examples show you famous videos and tell you they are great. That is inspiring and nearly useless, because you can't see why a beat works, how long it lasts, or what was cut to make it fit. This article does the opposite: three complete launch videos, taken apart second by second.
The three examples are the launch templates that ship with Demogent, each written for an invented product so the copy could be complete. Because they are templates, we know every timing exactly, not approximately. You can watch each one below, read the beat table, and then apply the same template to your own product.
Example 1: Relay, a SaaS launch in 23 seconds
Relay is a fictional AI support agent that reads a company's docs and past tickets, answers customers on its own, and hands the rest to a human with the context attached. The video follows the classic launch shape: hook, reveal, three proof beats, and a close.
| Time | Beat | Text track | Component track |
|---|---|---|---|
| 0 to 3s | Hook | “Your team answers 200 tickets a week?” | Nothing. The line has the frame to itself. |
| 3 to 6s | Reveal | “Support that answers itself.” | Logo Reveal with the name Relay |
| 6 to 10.5s | Ask | “Customers ask in plain English” | Query Submit: “Why was I charged twice this month?” types and sends |
| 10.5 to 15.5s | Answer | Empty on purpose | Mobile Notifications: Refund approved, Password reset sent, Shipping delay explained, Escalated to Sam |
| 15.5 to 19.5s | Proof | “Most tickets never reach a human” | Progress Ring filling to 92%, “Tickets resolved automatically” |
| 19.5 to 23s | Close | Empty on purpose | CTA Outro: “Give your team their week back.”, a Try it Today button, and “No Credit Card Required” |
What to take from it
- The hook is a question with a number in it. “200 tickets a week” lets the right viewer recognize themselves in three seconds.
- The product is shown being used, not described. The Ask beat is a real customer question typing itself, which is more convincing than any feature line.
- The fourth notification is the honest one. Ending the stack on a ticket escalated to a human answers the objection “what about the hard ones?” without a word of copy.
- One stage for the whole product act. A single dark violet background runs under the first 19.5 seconds, with a faint grid switching on at six seconds instead of a scene change. Only the close moves to a light stage, which makes the final card feel like an ending.
Example 2: Kestrel, an AI product explained in 26.5 seconds
Kestrel is a fictional AI analyst that connects to a company's data warehouse and answers questions asked in plain English. AI products have a specific problem in launch videos: viewers have seen a hundred of them and can't tell what any one actually does. So this video is written as an explainer that has to pass one test. After one viewing, someone should be able to say what Kestrel is, who it is for, and what happens when you use it.
| Time | Beat | What is on screen |
|---|---|---|
| 0 to 4s | Problem | “Your data team is three weeks behind. So everyone else guesses.” |
| 4 to 7.5s | What it is | “Kestrel is an AI analyst that connects to your warehouse and answers questions in plain English.” |
| 7.5 to 11.5s | Show me | “Ask it the way you'd ask a colleague.” while a Search Field types “Why did churn spike in March?” |
| 11.5 to 14.5s | How fast | A Progress Ring on 1.2s, “Median time to answer”, with “It writes the SQL, runs it against your data, and explains what it found.” |
| 14.5 to 16s | Breath | The text track pauses so the next claim lands as its own thought |
| 16 to 19.5s | What else | A Text Marquee of real questions, with “If your warehouse can answer it, so can Kestrel.” |
| 19.5 to 22.5s | Setup | “It reads your schema on the first connection. No dashboards to build. No tickets to file.” |
| 22.5 to 26.5s | Next | CTA Outro: “Ask your first question in under a minute.” |
What to take from it
- The definition comes at second four, in a full sentence. Most AI launch videos never say plainly what the product is. This one spends its most valuable seconds doing exactly that.
- A number needs a mechanism. “1.2 seconds” on its own is a stat. Paired with “It writes the SQL, runs it, and explains what it found,” it becomes a reason to believe.
- The marquee lists questions, not categories. Real questions like “Which plan retains best?” say “and everything else you were about to ask” faster than a feature grid.
- It answers the objection nobody voices. “What do I have to set up first?” is on every buyer's mind. The Setup beat answers it before the call to action asks for anything.
- No upload slots. Every component draws itself from text, so the template plays complete the moment it is applied.
Example 3: Forge, a developer tool launch in 29 seconds
Forge is a fictional deploy tool that reads a repository instead of a pipeline config file. It is aimed at the audience that most resents being marketed to, so it spends as little time as possible talking. Eight of its 29 seconds are a terminal running a real-looking deploy with no copy over it at all.
| Time | Beat | What is on screen |
|---|---|---|
| 0 to 5s | Problem | “Every service you ship has its own pipeline file. Nobody remembers how any of them work. So, Introducing” |
| 5 to 7s | Name | Logo Reveal, silent, with the name Forge |
| 7 to 11s | What it is | “Forge is a deploy tool that reads your repository instead of a config file.” |
| 11 to 19s | The deploy | A Terminal runs forge ship: reads 3 services, finds no pipeline file and infers the build, runs 214 tests, ships behind a 10% canary, goes live in 41s, then rolls back in 4s |
| 19 to 24s | Replaces | Logos Spread with four tiles (CI, K8, YML, SH), then “It replaces the CI config, the manifests, and the shell scripts holding them together.” |
| 24 to 29s | Next | Feature Split: “One command. Any service.” with a brew install forge button and a Read the docs link |
What to take from it
- The product explains itself. The terminal output is written to be read in order: it finds your services, works without a config, tests, ships safely, and can undo it all. That is the whole product specification, delivered without a line of marketing copy.
- Context first, output second. A wall of terminal text means nothing to a viewer who doesn't know what they are watching, which is why the first eleven seconds are a problem, a name, and a definition.
- The hook hands off to the reveal. The opening lines end on “So, Introducing”, and the silent logo card finishes the sentence.
- Name the category, not a competitor. The Replaces beat shows abstract tiles for CI, Kubernetes manifests, YAML, and shell scripts rather than another company's logo.
- One unchanging background. The whole film sits on one flat scene. When the pitch is that the tool is calm, a background that never cuts helps it land.
The patterns all three share
| Pattern | Relay | Kestrel | Forge |
|---|---|---|---|
| Problem stated first | 0 to 3s | 0 to 4s | 0 to 5s |
| Product named or defined by | 3s | 4s | 5s (name), 7s (definition) |
| Longest single beat | 5s notification stack | 4s | 8s terminal |
| Backgrounds | One dark stage, light close | One blue family | One scene throughout |
| Music | One track, unbroken | One track, unbroken | One track, unbroken |
| Total length | 23s | 26.5s | 29s |
- Every beat has one job. None of the three ever asks a scene to announce, prove, and sell at the same time.
- Text goes quiet when a component speaks. When the notification stack, the terminal, or the closing card carries its own words, the text track is deliberately empty.
- Length follows the product, not a rule. Forge is the longest because its most convincing moment, the terminal, needs eight seconds to be read.
- Every boundary lands on a half second. Clips on the timeline snap to half seconds, which keeps cuts on a steady rhythm without anyone counting frames.
- The close asks for one thing. One button, one line under it at most.
Use these examples as your starting point
All three are available as templates in Demogent: SaaS Launch (Relay), AI Product Launch (Kestrel), and Dev Tool Launch (Forge). Apply the one closest to your product, then replace it one field at a time: your problem line, your name and logo, your screenshots in the frames, your number, your call to action. Because the timing is already tuned, you spend your effort on the words, which is where a launch video is won or lost.
If you would rather build from scratch, our step-by-step launch video guide covers the same structure from a blank timeline.
Apply a launch template to your product
Pick SaaS Launch, AI Product Launch, or Dev Tool Launch, swap in your copy and screenshots, and export a finished launch video from your browser.
Frequently asked questions
What makes a good product launch video?
A specific problem in the first few seconds, a one-sentence definition of the product, the product shown working rather than described, one proof point, and a single clear next step. All three examples above follow that order.
Are these real products?
No. Relay, Kestrel, and Forge are invented products written for Demogent's templates, so every line of copy could be complete and every timing could be shown exactly. The structure transfers directly to a real product.
How long are good launch videos?
These three run 23, 26.5, and 29 seconds. Most effective launch videos land between 20 and 60 seconds. Our length guide breaks that down by channel.
Can I use these as templates for my own launch?
Yes. All three ship inside Demogent. Applying one gives you the complete, timed video, and you replace the product name, copy, logo, and screenshots with your own.
Make your next product video in Demogent
Start from a finished launch template or a blank timeline, drop in your screenshots and logo, and export in your browser. Free to start, with no editing experience needed.
