Almost every brief we get opens the same way: "we need a video for the product."

Then the trouble starts. One stakeholder is picturing a sweeping launch film. Another wants a tight walkthrough of the new dashboard. A third just wants the thing that explains what we do for the homepage. They are all describing different videos — and if you build the wrong one, you spend the budget, ship something competent, and still miss.

These three formats are not interchangeable. An explainer sells the idea. A demo proves the product. A launch film creates the moment. Confuse the jobs and you get the classic failure: a beautiful film that does not move a single number. This is the format hub: what each one is for, a real example of the creative choice that defines it, and exactly when each one backfires.

Three formats, three different jobs

Read down a column to see what each format needs to work. Read across a row to see where they differ. Lengths and costs vary by brief, so treat the rows as the questions to ask, not fixed rules.

Swipe the table sideways to compare.

The explainer: sells the idea

An explainer answers the most basic question a stranger has: what is this, and why should I care? It trades in concept, not configuration. Usually short, often animated or lightly produced, and it lives where cold traffic lands. The job is clarity, not completeness. Selling cybersecurity? Here is how to make a security product explainer that shows the mechanism, not a padlock.

The reference everyone quietly copies is Slack's "So Yeah, We Tried Slack", made by the video studio Sandwich with its own team playing themselves. It opens on the communication chaos every team recognises and lands Slack as the fix. It works because it leads with a feeling before it ever touches the interface — you understand why Slack exists long before you see a single screen.

Watch for: how long it goes before showing the product. The feeling comes first; the interface second.

Where the explainer backfires

• Your buyer already understands the category. Someone comparing project tools does not need a charming metaphor — they need to see the thing run. An explainer here reads as stalling, and a sophisticated buyer feels patronised.
• It never shows the product. Two minutes of abstract animation and aspirational voiceover, and the viewer still cannot picture using the software. That is the most common explainer failure, and it is fatal.
• You are animating to hide a product that is not ready. Buyers can smell it, and when the real UI finally appears, you have spent trust you cannot refund.

The demo: proves the product

A demo answers the question that decides the deal: does this actually work for my situation? It shows the real interface doing real work. No metaphors, no mascots — the screen is the star. It belongs further down the funnel: product pages, sales follow-ups, the email you send after someone asks "can you show me how you handle X?"

The canonical example is famously unpolished. Dropbox's founder recorded plain screencasts: drag a file into a folder on one machine, watch it appear on another. Drew Houston later said that when a three-minute demo was posted to Digg in March 2008, the beta waiting list grew from 5,000 to 75,000 people overnight (Startup Lessons Learned, 2010). No animation and very little budget, just one useful thing happening on screen in real time. The modern descendants run on the same logic: Grammarly catching mistakes as you type, or a short Loom walking through a single workflow. The interface does the talking, not a voiceover full of adjectives. A note on the clip: this is a re-upload of the original 2007 screencast, which came before the Digg demo, and it looks its age. It is still one of the most cited product demos.

Watch for: one genuinely useful thing — a file appearing on a second machine — shown in real time. No polish, all proof.

Where the demo backfires

• You show it to a cold audience. A detailed walkthrough in front of someone who does not yet understand the category is a wall of context they cannot parse. Proof only lands once the viewer is sold on the idea.
• It is a feature tour with no narrative. "Here is the menu, here is settings, here is the reports tab" is a UI inventory. The demos that convert show a job getting done — a real workflow, start to finish.
• The product is not camera-ready. A demo exposes everything: the half-built feature, the placeholder data, the spinner that will not quit.

The launch film: creates the moment

A launch film answers a question of timing: why does this matter now? It is the hero asset for a moment — a new product, a major feature, a category bet. It carries more emotion, more production value and more brand than the other two, because its job is not only to inform. It is to make people feel like something happened, and to give the launch a centre of gravity that press, partners and your own team can rally around.

When Notion launched Agents in September 2025, the film opened on its one-line promise, "You assign the tasks. Your Agents do the work.", then walked straight into a real use case. Figma's AI-editing launch barely uses marketing copy at all; Stripe's Sessions keynote trades the static talking head for an event film that lets you feel the room; and Linear's launch films stay with plain product UI for minutes at a time, trusting a well-known pain to hold attention.

Watch for: the promise in the first line, the use case in the next. A moment with a shape people can share.

Where the launch film backfires

• There is no real news. A launch film manufactures significance. Dress a minor update up as an event and the audience clocks the gap between the drama and the substance.
• The hero film is the only asset, and nobody planned what happens after launch day. If buyers will need to see the product working or sales will need something short to send, plan those pieces now. A film that creates interest with nothing behind it hands the attention to whoever answers the next question.
• It is all spectacle, no clarity. Cinematic does not mean cryptic. If a viewer still cannot say what shipped, you have made an art piece, not a launch asset.

Three briefs, three different choices

These three briefs are illustrative. They are composites written to show the reasoning, not client projects, and the details are invented.

Brief 1 (illustrative): an unfamiliar security category needs an explainer

A security company has built a new way to stop attackers from abusing the service accounts and API keys inside a cloud estate. The product works. The trouble is that most security leaders it calls have never thought of machine identities as an attack surface, so a demo of the console lands as noise. The buyer cannot evaluate a fix for a problem they have not yet recognised. The job here is to make the problem visible and the mechanism repeatable in a sentence, so a security leader can explain it to their CISO without the rep in the room.

Commission first: an explainer of roughly 90 seconds that shows how the attack happens and how the product breaks it.
Defer: the demo, until sales calls reach the stage where buyers ask how it would work in their own environment.

Brief 2 (illustrative): a buyer comparing software needs a focused workflow demo

A fraud prevention platform keeps reaching the final two in evaluations. The buyers are fraud and risk teams who already know the category well and are comparing three vendors on how fast an analyst can investigate a flagged transaction. They do not need persuading that fraud is a problem. They need to see one investigation done, start to finish, on data that looks like theirs, so they can compare it fairly with the other two. Sales has been asked the same question on the last six calls, and a recorded answer can be sent before the next one.

Commission first: a two-minute demo of that single investigation workflow, with no feature tour around it.
Defer: the launch film, because there is no news moment, and a new explainer, because these buyers already understand the category.

Brief 3 (illustrative): an established audience and a meaningful release need a launch film

An AI data infrastructure company with a large customer base is shipping a capability its users have asked for over two years, and it is the headline of its annual conference keynote. The audience already understands the category and the company. What the release needs is a moment: a reason for customers, partners and press to pay attention in the same week, and a clear statement of what changed. The date is fixed, the feature is shipping, and the film has to work on the main stage and in the launch post the same morning.

Commission first: a launch film for the keynote, with the sales and social cutdowns scoped in the same brief.
Defer: a standalone demo of the new feature until the interface is final and prospects start asking to see it working.

So which one do you actually need?

Stop asking what kind of video to make. Ask three sharper questions instead.

1. Where is the buyer standing? Cold and unaware, reach for an explainer. Interested and evaluating, a demo. Already in your orbit and waiting for news, a launch. The format follows the stage, not the other way around.

2. What is the single job? Not three jobs. One. Try to make awareness, proof and excitement happen in the same ninety seconds and you do none of them well.

3. Is the product ready to be seen? Camera-ready UI makes a demo your most persuasive — and often cheapest — option. If it is not ready, an explainer can carry the idea while you build.

Then apply one rule to the budget. Fund the most important buyer job first. Add a second asset only when a distinct audience, placement or sales need justifies it: a cold audience the first film cannot reach, a channel that needs a different length or shape, or a question sales keeps being asked that the first film does not answer. Some launches will end up with all three formats. Many will not, and a single well-chosen film that does its one job beats three that each half-do theirs. If you are weighing what a second asset would cost, our cost guide sets out what changes the price.

Pick one job. Commit.

Every film on this page makes the same creative choice: it picks one job and commits to it. Dropbox's screencast proves. Slack's film sells an idea. Notion's launch creates a moment. None of them tries to be all three, and none uses production value as a substitute for clarity. They are other companies' films, and their results belong to those companies, not to a forecast for yours. The choice is the part worth copying.

That is the real lesson of the "vs." It is also where much of a video budget gets wasted: not on the wrong production company, but on the wrong format for the job. Choose by what the viewer needs to understand and do next, and the format usually picks itself.

Before you brief anyone, answer these five

1. Buyer stage: does the buyer not yet see the problem, are they comparing options, or are they waiting for your news?

2. Single job: what is the one thing this video must make the viewer understand or do?

3. Available product proof: is there a camera-ready interface, a real workflow or a shipped release to show?

4. Placement: where will it be watched first, and with or without sound?

5. Budget and deadline: what can be spent, and what date can't move?

If you have the answers, you have most of a brief. Our video brief template turns them into one, and the cost guide shows what each choice does to the price.