Every founder planning a launch eventually says "we need a demo video." Sometimes that's right. Usually it isn't. A demo and a teaser are not the same asset with different runtimes. They answer different questions, for different people, at different points in the funnel.
Build the wrong one and you spend a week producing something that nobody watches, then conclude that video doesn't work for your product. It works. You just made the asset for the wrong moment.
The difference in one line
A demo answers "how does it work?" for someone who already cares. A teaser answers "why should I care?" for someone who has never heard of you and is scrolling past at speed. That single distinction decides length, sound, placement and effort.
| Launch teaser | Product demo | |
|---|---|---|
| Viewer | A stranger in a feed | Someone already evaluating you |
| Question it answers | Why should I care? | How does it work? |
| Length | 30 seconds | 2 to 10 minutes |
| Sound | Works on mute | Usually needs narration |
| Where it lives | Social post, landing page hero, launch email | Sales call, docs, onboarding, pricing page |
| Failure mode | Too much information, nobody finishes it | Too vague, nobody understands the product |
If a viewer needs context before the video makes sense, it's a demo. If the video has to create the context, it's a teaser.
Why founders reach for the demo first
Because the demo is the thing they can already picture. You have been in the product all week. Showing the actual screens feels like the honest, substantive choice, and a teaser can feel like marketing gloss over real work.
The trap is that a demo is written for someone who has already agreed to spend attention on you. On a launch day you have the opposite audience. People are deciding in a second or two whether this is worth a click, and a screen recording of a settings panel is not going to win that decision. That's the same failure pattern behind most dead launch videos, which why launch videos fail covers in more detail.
When you genuinely need a demo
Demos are not the enemy. They are just a different job, and there are cases where the demo is the right first asset:
- The product is hard to believe. If the claim sounds impossible, showing it working is the argument.
- You sell to a buyer who evaluates before booking. Technical buyers want to see the flow before they take a call.
- Onboarding is the problem. If people sign up and stall, a demo is documentation, not marketing.
- Sales asks for it. If a human is sending it one-to-one, length matters much less.
A demo like that is a screen recording with a voice explaining what is happening. You make it with a screen recorder and your own voice. That is genuinely the right tool, and it is not what we build. We do not do screen recording, narration or timeline editing, and a generated motion-graphics asset is a poor substitute for a real walkthrough.
When you need a teaser
You need a teaser whenever the viewer has not opted in yet. Launch day on X or Product Hunt. The hero of a landing page. The top of the announcement email. A cold audience seeing your name for the first time. In all of those, you have a couple of seconds of borrowed attention and one idea worth landing.
The format follows from that constraint. Short, because attention is borrowed. Silent-first, because feeds autoplay muted and most people never turn sound on. Text-led, because the message has to survive without audio. Branded, because it should look like it came from the same company as the page it links to. The opening frame carries more weight than anything else in the asset, which is the whole argument of the three-second hook.
A simple way to choose
- Name the moment. Where exactly will this be watched: a feed, an inbox, a call, a docs page?
- Name the viewer's state. Do they already know what your product is? If no, teaser.
- Name the next action. A teaser earns a click. A demo earns a signup or a decision. If you can't name the action, you don't have an asset yet.
- Then pick the length. Length is an output of the first three answers, never the starting point.
Most early-stage teams need the teaser first, because most early-stage teams have a discovery problem rather than an explanation problem. Nobody is stuck halfway through evaluating you. They have not heard of you at all.
You can have both, in the right order
The healthy sequence is teaser first, demo second. The teaser earns the click on launch day and lives on the landing page. The demo waits behind the signup or the call, where the viewer has already decided you are worth a few minutes. Building them in the other order is how founders end up with a beautiful ten-minute walkthrough and a launch post that nobody clicked.
The practical difference is also production cost. A demo needs a stable build, a script, a clean account with realistic data, and a re-record every time the UI moves. A teaser can be regenerated from your live page whenever the page changes, which is what makes it survivable at launch cadence, and it is the logic behind the URL to video workflow.