Plan a Software Demo Video: Audience, Task and Cut

A good software demo comes from three decisions you make before you record anything: who is watching, the one task you'll show start to finish, and which cut the job needs (teaser, hook, pitch or demo). Get those right and the script, the recording and the edit mostly follow. Get them wrong and no amount of editing saves the video, because it's trying to do four jobs at once.

This is part 2 of how to make a product demo video. It takes about 15 minutes and fits on one sticky note.

Decision 1: Who is watching

Name one person. Not a segment, a person in a situation:

• A founder scrolling X who has never heard of you. They decide almost at once whether to keep watching.
• Someone on your Product Hunt page who already clicked. They'll give you half a minute to decide whether to sign up.
• A buyer comparing three tools after a sales call. They want to see the thing that was promised actually working.
• A new user who just signed up and doesn't know where to start. They want the shortest path to their first result.

Each of these people needs a different video. The scroller needs a reason to stop. The Product Hunt visitor needs the problem, the product and a reason to trust it. The buyer needs proof. The new user needs steps.

Write it down: "This video is for ___, who is ___ when they see it."

Decision 2: The one task your software demo shows

A software demo video shows one task, start to finish. Pick the task that makes your viewer think "I need that".

Good tasks have three things:

1. A clear start. A problem the viewer recognizes: a messy inbox, a failed deploy, a spreadsheet nobody trusts.
2. A few steps in your product. Few enough to show without speeding up the footage into a blur.
3. A visible result. Something changes on screen: a chart appears, an email sends, a bug goes green.

Some examples of the shift from "feature" to "task":

Instead of showing	Show the task
"Our dashboard"	"See which customers are about to churn, then email them"
"Integrations page"	"Connect Stripe and see this month's revenue in under a minute"
"AI features"	"Paste a messy support thread, get a reply draft you can send"
"Team permissions"	"Invite a contractor who can only see one project"

If you can't pick one task, pick the one your best customers mention first when they explain why they pay. If you don't know that yet, pick the one people do in their first session.

What to leave out

Everything else. Settings, onboarding screens, the pricing page, the five other features. A demo is not a tour. If a viewer wants more, the call to action takes them to your site or docs.

Decision 3: Which cut fits the job

The four cuts are four different jobs. Lengths are the maximum for each.

Cut	Length	What it does	Use it for
Teaser	up to 30 s	Shows a sliver and holds back the rest, so people wait for launch day	Waitlist page, X, the week before launch
Hook	up to 20 s	One idea in the first second, stops the scroll, one call to action	X, TikTok, Reels, Shorts, ads
Pitch	up to 45 s	Problem, your real screen, proof, the offer	Product Hunt, your homepage, YC application
Demo	up to 60 s	One task, start to finish, on your own recording	Onboarding, docs, sales follow-ups

Teaser: curiosity before launch

A teaser makes people curious and holds back how it works. Show the result, or a glimpse of the interface, and stop. The call to action is "join the waitlist" or "launching Tuesday". Don't use a teaser after launch; once people can try it, show them how.

Hook: stop the scroll

A hook carries one idea and lands it in the first second. It's made for feeds where people decide almost instantly whether to keep watching. Lead with the most surprising frame of your task: the result, the before and after, the thing that took an hour now taking ten seconds. One call to action.

Pitch: persuade

A pitch persuades. The structure is problem, product, proof, offer. It's the video for your Product Hunt gallery (which only takes YouTube links for video), the top of your homepage, or your YC application. Your real screen has to be in it. A pitch made only of animated text asks people to trust a product they haven't seen.

Demo: show how it works

A demo, sometimes called an explainer, shows the product doing one real task, start to finish. It's about how it works, not why to buy it. This is the software demo for onboarding emails, docs and the follow-up after a sales call. It's the longest of the four and still lands around a minute.

If you need more than one

Launches usually need several. A typical set for one launch: a teaser the week before, a pitch for launch day, a hook for the launch thread on X, and a demo for the docs and sales follow-ups. All four can come from the same recording if you record the task cleanly once.

A SaaS demo video plan on one card

Fill this in. If any line is empty, you're not ready to record.

Viewer:     ___ who is ___ when they see it
Task:       ___ (start: ___ / result on screen: ___)
Cut:        teaser | hook | pitch | demo   (max ___ s)
Plays on:   ___
One CTA:    ___
Proof:      ___ (a number, a customer, a before/after; pitch only)

A filled-in example, for a made-up invoicing app:

Viewer:     a freelance designer on Product Hunt who hates chasing payments
Task:       turn a finished project into a sent invoice with a pay link
            (start: project marked done / result: client's inbox shows the invoice)
Cut:        pitch (max 45 s)
Plays on:   Product Hunt gallery, homepage
One CTA:    "Send your first invoice free"
Proof:      the time it takes, shown on screen, not claimed in the voice-over

Common planning mistakes

• Planning for everyone. A video for founders, buyers and new users at once is a video for nobody. Make two short ones instead.
• Picking a feature, not a task. "Show the dashboard" has no start and no result. "Find the customers about to churn" does.
• Choosing length before content. Pick the cut, and let the cut set the length. A demo stretched to fill two minutes feels padded. See how long a demo video should be.
• Proof you can't show. If the pitch says "10x faster", the viewer should see it. If you can't show it, don't say it.
• Faking the product. Mockups of features that don't exist yet will come back to you in the comments. Record what's real.

What to do next

With the plan on a card, write the voice-over against it: product demo script templates. Then record the task.

Frequently asked questions

What is a software demo video?

A software demo video shows the product doing one real task, start to finish. It explains how the software works rather than why to buy it, and it usually runs about a minute.

What's the difference between a teaser, a hook, a pitch and a demo?

They do four different jobs. A teaser (up to 30 seconds) shows a sliver and holds back the rest before launch, a hook (up to 20 seconds) stops the scroll with one idea, a pitch (up to 45 seconds) persuades with problem, product, proof and offer, and a demo (up to 60 seconds) shows one task start to finish.

How do I choose what to show in a SaaS demo video?

Show the one task that makes your viewer think "I need that." A good task for a SaaS demo video has a clear start, a few steps in the product and a visible result; if you can't choose, pick the task your best customers mention first, or the one new users do in their first session.

Who should a software demo be made for?

One person in one situation, such as a founder scrolling X, a visitor on your Product Hunt page, a buyer comparing three tools, or a new user who just signed up. Each of those viewers needs a different software demo, so a video made for all of them works for none.

What kind of video should I use for a Product Hunt launch?

A pitch: problem, product, proof and offer, in 45 seconds or less, with your real screen in it. Product Hunt's gallery only takes YouTube links for video, so upload the pitch to YouTube first.

How many demo videos does a product launch need?

Often four. A typical launch set is a teaser the week before, a pitch for launch day, a hook for the launch thread on X and a demo for docs and sales follow-ups, and all four can come from one clean recording of the task.

How long does it take to plan a software demo video?

About 15 minutes. Planning a software demo comes down to three decisions (who is watching, the one task, and which cut), and the plan fits on one card.

If you'd rather not edit it yourself, Demo Editor takes your recording and landing page and cuts it into any of the four cuts, with a storyboard you can correct before a frame is made.