TL;DR
An explainer video MVP demonstrates a product working as though it already
exists, then measures who signs up after watching. It is the demand test for
products that text cannot convey: things that are invisible, run in the
background, or only make sense once you see them move. Dropbox used one to take
a beta waitlist from around 5,000 to 75,000 overnight. The method's whole
difficulty is honesty, because you are showing software that does not yet do
what the screen says it does.
Key Takeaways
- An explainer video MVP shows the product in motion before it exists, and uses
the response as demand evidence. - Use it when the product is hard to describe in words, invisible in operation,
or expensive enough to build that a wrong guess costs months. - It is closer to a fake door than a
landing page, because you are demonstrating
capability you have not built. - The video is the experiment. The landing page underneath it is only the
instrument that records the answer. - Make it for a specific audience in a specific place. Dropbox's video was
written for the community it was posted to, and that is why it worked. - The honesty line: demonstrating a product you intend to build is fair.
Demonstrating capability you know is not achievable is not. - Measure the signup rate of people who watched, not the view count. Views are
the vanity number.
What is an explainer video MVP?
An explainer video MVP is a validation method where you produce a short
demonstration of a product working, publish it, and treat the resulting signups
as evidence of demand. No functioning product sits behind it. The video is the
product, for the purposes of the test.
It belongs to the demand-validation family alongside the other
types of MVP, and it is almost always paired with a
landing page MVP, which captures the emails the video
generates.
The distinguishing feature is what it can communicate. Every other demand test
relies on a written promise: a headline, a description, a price. Some products
cannot be sold that way. If the value is a behaviour rather than a feature, a
sentence describing it will lose to thirty seconds of watching it happen.
When a video beats a landing page
A landing page is faster, cheaper and easier to change. Use one by default. A
video earns its extra cost in four specific situations:
The product is invisible. File sync, background automation, anything whose
job is to work without being noticed. There is no screenshot of "it just works",
but there is a demonstration of it.
The value is in the motion. Products where the point is how something
changes over time, or how two things connect. Static copy has to describe a
sequence; video simply shows it.
The concept is unfamiliar. If your product has no obvious category, readers
have nothing to map it onto. Watching removes the need to imagine.
The build is expensive. The more months a wrong guess costs, the more a few
days of production is worth. This is the calculation Dropbox faced: the sync
engine was genuinely hard, so validating before building it was worth real
effort.
If none of those apply, write a landing page instead. A video for a product that
a sentence could sell is production spend buying nothing.
Explainer video MVP vs the other demand tests
| Method | What you show | What you are asking |
|---|---|---|
| Landing page MVP | A written promise | Does this description appeal? |
| Fake door MVP | A button that leads nowhere | Would you use this feature? |
| Paid ad MVP | A promise, to strangers | Does this land cold? |
| Pre-sales MVP | A price | Is this worth paying for? |
| Explainer video MVP | The product, apparently working | Now that you can see it, do you want it? |
The last row is why this method carries an obligation the others do not. A
landing page describes something that does not exist, which everyone
understands. A video shows something that does not exist, and viewers read a
demonstration as proof of capability.
The four jobs the video has to do
A demand-testing video is not a marketing video, and the difference shows up in
what you cut.
1. Show the problem in the first few seconds. Viewers who do not recognise
the problem will not stay for the solution. Open on the frustration, not on your
logo.
2. Show the product doing the thing. Not a feature tour. One continuous
demonstration of the core behaviour, ideally in real time, so the viewer sees
the sequence rather than a summary of it.
3. Make the audience feel it was made for them. Dropbox's video was full of
in-jokes for the specific community it was posted to. That is not decoration, it
is what converted a demo into something people shared.
4. End on one action. A single ask. Not "learn more, follow us, join the
beta". Just the email field.
Everything else is production polish, and production polish is not what you are
testing.
How to run an explainer video MVP: a seven-step playbook
Step 1: Write the decision the video will make
"If fewer than N people from M viewers sign up, we do not build this." Write it
before you touch a camera, because a video that took a week to produce will
otherwise be judged by how good it looks rather than what it proved.
Step 2: Script the sequence, not the pitch
Write what happens on screen, in order, as a sequence of actions. If you cannot
write the sequence, you do not yet understand the product well enough to
demonstrate it, which is itself useful to discover before building.
Keep it short. Two to three minutes is plenty, and shorter is usually better.
Step 3: Build only the surface you will film
You do not need a working product. You need the parts that appear on screen to
look right in the order you film them. A clickable prototype, a mockup, or
careful editing will carry most demonstrations.
This is the step where the method saves you months, and also where the honesty
question arises. More on that below.
Step 4: Put a landing page underneath it
The video generates interest. The page captures it. One promise, one field, and
nothing else competing for attention. The
landing page MVP guide covers the build.
Step 5: Pick the room before you make the film
Decide exactly where it will be posted and who is there, then make the video for
those people. A video made for everyone converts nobody. Dropbox's worked partly
because Houston knew precisely which community he was posting to and wrote for
them.
Step 6: Publish once, in that room, and watch
Post it where your audience already gathers. Do not spread it thin across every
platform on day one; you will not be able to tell which audience responded.
If you have no room to post in, pair it with a paid ad MVP
to buy the audience instead.
Step 7: Read the signup rate, not the views
Compare against the threshold from step one. Views measure how shareable the
video was. Signups measure whether anyone wants the product. Those are different
things, and only one of them is your question.
The honesty line
This is the method's real difficulty, and most guides skip it.
You are showing software doing something it cannot yet do. Viewers interpret a
demonstration as evidence the thing exists. That is a stronger implied claim
than a landing page makes, so it carries a stronger obligation.
Where the line sits, in practice:
Fair. Demonstrating a product you intend to build, whose behaviour you are
confident is achievable, while collecting emails for a beta you genuinely plan
to run. This is a promise about the future, made in good faith.
Not fair. Demonstrating capability you know you cannot deliver, taking money
against it, or presenting a mockup as a shipping product to people making a
purchasing decision now.
Three practical safeguards:
- Frame it as coming soon. Say the beta is not open yet. Dropbox's video
invited people onto a waitlist, which sets the expectation correctly. - Do not take payment against a video alone. If you want money as the
signal, that is a pre-sales MVP, and it comes with
refund obligations. - Follow up with the people who signed up. They raised their hand for
something that did not exist. Tell them what happened either way.
The reputational asymmetry is worth understanding. A landing page that never
becomes a product is forgettable. A convincing demo that never becomes a product
is remembered, because people felt they saw it.
Real explainer video MVPs
Dropbox
Before building the sync engine, Drew Houston made a short screencast showing
Dropbox working: files moving between machines, appearing where they should. The
product behind it was not finished. He posted it to a community he knew well,
narrated with in-jokes aimed squarely at that crowd, and the beta waitlist went
from roughly 5,000 to 75,000 overnight.
The reason it is the canonical example is the match between method and problem.
File sync is invisible by design, genuinely difficult to build, and almost
impossible to convey in a paragraph. Every condition favoured video. Our
Dropbox MVP case study covers the full story.
Dollar Shave Club
In 2012 the company launched with essentially one asset: a deadpan explainer
video shot for very little money. It drove tens of thousands of signups within
48 hours and proved demand for subscription razors before the operation existed
at scale.
The instructive difference from Dropbox: the product was not hard to understand,
so the video was not doing explanatory work. It was doing positioning work,
establishing a voice that made an unremarkable category feel different. That is
a legitimate second use of the format, but it is a harder thing to plan for.
Common mistakes
Making a marketing video. Polish, music, brand shots and a feature montage
produce a nice video that tests nothing. You want a demonstration.
Measuring views. Shareability is a property of the film. Your question is
about the product.
Filming a feature tour. Six features shown for ten seconds each proves
nothing about any of them. One core behaviour, shown properly.
Posting everywhere at once. You lose the ability to tell which audience
responded, which is half the learning.
Spending too much. If production costs more than a slice of the build you
are trying to avoid, the economics have inverted.
No landing page. Interest with nowhere to go is not a measurement.
Overselling capability. The line above exists for a reason, and crossing it
costs more than the test could ever return.
When an explainer video MVP is the wrong choice
- A sentence would do it. If your product is easy to describe, use a
landing page MVP and save the days. - You are testing a feature for existing users. That is a
fake door MVP. - You have no audience and no budget. A video with nowhere to be posted is
an expensive private film. Pair it with a
paid ad MVP or pick a cheaper method. - The product's value is in data or results over time. A demo can show an
interface but cannot demonstrate that the output is any good. Consider a
concierge MVP instead. - You are in a regulated category. Demonstrating capability you do not have
can carry consequences beyond reputation in health, finance and similar
sectors.
How to graduate from a video to a build
Build what you filmed, in that order. The sequence you demonstrated is now
the specification your signups are expecting. Deviating from it means delivering
a different product to people who chose the one they saw.
Talk to the people who signed up. They watched a demonstration and acted.
Ask what they thought they were getting, because the gap between that and what
you filmed is your positioning risk.
Keep the video honest as you build. If the product ends up working
differently, update or retire the video rather than leaving a demonstration up
that no longer matches.
Scope small anyway. A strong response validates the core behaviour, not a
roadmap. Your MVP scope should still be the smallest thing
that delivers what the video promised.
A worked example
A founder wants to build a tool that automatically reconciles delivery invoices
against what was actually received, for small restaurants.
The problem with copy: the value is entirely in what the software does
quietly, comparing two documents and surfacing discrepancies. A landing page
describing it reads like accounting software, which is not appealing.
The decision: if fewer than 40 signups come from 1,000 views, we do not
build it.
The video: ninety seconds. Opens on a restaurant owner squinting at a paper
invoice at 11pm. Then the tool, in one continuous take: photograph the invoice,
wait two seconds, see three flagged discrepancies with amounts. No features, no
logo animation, no music.
The build behind it: a clickable prototype and careful editing. Nothing
functional.
The room: two restaurant-owner communities the founder is already active in.
The result: 1,400 views, 96 signups, and eleven unprompted replies asking
when it launches.
The read: proceed, build exactly the flow that was filmed, and note that the
eleven replies are the most valuable output. They are the first interview list.
How MVP Development helps
Founders who arrive with a video and a signup list have already resolved the two
questions that make estimates vague: what the product does, and whether anyone
wants it. The filmed sequence doubles as a specification, which is unusually
clear input for a build.
If you want a sense of what the real version costs before committing to
production, our
MVP cost calculator
gives a realistic range with no signup.
Related guides
- Dropbox MVP: the full case study of the canonical
explainer video MVP. - MVP validation: all the demand-testing methods and how
to choose. - Landing page MVP: what your video should point at.
- Paid ad MVP: how to buy an audience if you do not have
one. - Types of MVP: every method mapped in one place.
- MVP examples: famous MVPs across every type.
Frequently asked questions
What is an explainer video MVP?
An explainer video MVP is a validation method where you produce a short
demonstration of a product working, publish it, and measure how many viewers
sign up. No functioning product exists behind it. The video, and the landing
page it points at, are the entire experiment.
What was the Dropbox explainer video MVP?
Before building the sync engine, Drew Houston posted a short screencast showing
Dropbox working, narrated with in-jokes for the community he posted it to. The
beta waitlist rose from around 5,000 to 75,000 overnight, validating demand for
a product that was not finished. See our
Dropbox MVP case study.
How long should an explainer video MVP be?
Two to three minutes at most, and shorter usually performs better. You are
demonstrating one core behaviour, not touring a feature set. If the sequence
takes longer than three minutes to show, the scope you are testing is probably
too broad.
Do I need a working product to make one?
No, and that is the point. You need the surfaces that appear on screen to look
right in the order you film them, which a clickable prototype and careful
editing will usually achieve.
Is it dishonest to demo a product that does not exist?
Not if you are demonstrating something you intend to build, are confident is
achievable, and you frame it as coming soon rather than available now. It
becomes dishonest when you show capability you know you cannot deliver, or take
money against a demonstration alone.
What should I measure?
Signups from viewers, against a threshold you set before publishing. Views and
completion rates describe the video, not the product. A video can be widely
shared and validate nothing.
Where should I post the video?
In one specific place where your audience already gathers, chosen before you
make it, so you can write for those people. Posting everywhere at once destroys
your ability to tell which audience responded.
How much should an explainer video MVP cost to make?
Meaningfully less than the build you are trying to de-risk. Many effective ones
are screen recordings with a voiceover. If production costs approach a
significant slice of the development budget, the economics of the method have
inverted.
What is the difference between an explainer video MVP and a landing page MVP?
A landing page tests a written promise; a video tests a demonstrated one. Use a
video when the product is invisible, unfamiliar, or expensive enough to build
that a wrong guess is costly. In practice they are run together, with the video
sitting on the page.
Where does the explainer video MVP fit among the other MVP types?
It belongs to the demand-validation family, alongside the landing page, fake
door, crowdfunding, pre-sales and paid ad methods. What sets it apart is that it
communicates through demonstration rather than description. See
types of MVP for the full map.
Sources and references
- Shortform, on the Dropbox MVP explainer video
- The Lean Startup, on validated learning and demand testing
- Y Combinator Library, on early customer discovery
- Atlassian, on defining a minimum viable product
