Tech teams often ask for “a video about the product” and mean two different films. One is for someone deciding whether to buy. The other is for someone who already bought and has to get value fast. They need different scripts, different pacing and different lengths, and commissioning one when you needed the other is the most common way a product video disappoints.
Making a film for a tech company? See AI video production for tech companies — investor, launch, demo and training films from $5,000, in 7–10 working days.
This guide is for product, marketing and training leads at tech companies. It explains what each film is for, gives you a decision table, a way to choose in one question, a structure for each, the mistakes to avoid, how the brief-to-master process works, and answers to the questions buyers ask before they start.
The demo film: for the person deciding

- Viewer: a prospect who does not yet trust you.
- Job: make one capability instantly clear and believable.
- Shape: the problem, the product solving it once, the outcome. Everything else is a link or a call.
- Where it lives: the homepage, a landing page, outbound email, a sales deck.
If your sales calls spend their first ten minutes explaining what the product is, you need the demo film first. See our AI product demo video service.
The onboarding film: for the person who bought

- Viewer: a new user or new employee who wants to be competent quickly.
- Job: remove the first-week questions.
- Shape: a sequence of short steps in the order the user meets them, one idea each, so a viewer can find and replay just the part they need.
- Where it lives: in-app, the help centre, the welcome email, the internal learning system.
If your support inbox keeps answering the same setup questions, you need the onboarding film first. See our AI training video service.
Demo vs. onboarding: the decision table

| Demo film | Onboarding film | |
|---|---|---|
| Goal | Win the decision | Make the new user successful |
| Audience | Prospect, evaluator, buyer | New customer, new hire, new admin |
| Their state of mind | Sceptical, short on time | Motivated, wants to get it right |
| What it shows | One capability, once, with the outcome | The steps in the order the user meets them |
| Structure | One continuous story | A set of short, separate chapters |
| Length | Short; it ends as soon as the point is made | Each chapter short; the total can be longer |
| Call to action | Book a call, start a trial, request a quote | Complete the next setup step |
| Where it plays | Homepage, landing page, email, sales deck | In-app, help centre, welcome email, internal learning system |
| How you judge it | Do prospects understand the product faster? | Do the same setup questions stop arriving? |
| Tone | Confident, concise | Calm, practical, patient |
How to choose in one question
Where is the company losing people: before the purchase or after it?
Before: demo film. After: onboarding film. Most tech companies eventually need both; start where the loss is. If you honestly cannot tell, look at two places. Listen to the first ten minutes of your last few sales calls, and read the last few weeks of support questions. Whichever is more repetitive points to the film you need first.
Anatomy of a good demo film
1. Start with the problem, not the product
Open on the person with the problem in the moment they have it. A viewer who recognises their own situation in the first scene is already paying attention.
2. Show the product solving it once
Choose the capability that is the clearest and the most valuable to this buyer. Stage it properly and stay with it long enough to be believed. Do not tour the interface; a tour is a list of things you built, not a reason to buy.
3. Show the outcome
End the demonstration on what changed for the person: the report that is now done, the task that no longer needs three people. The outcome is what the viewer takes away.
4. Name who it is for
Specific buyers feel seen; “teams” do not. Say who the product is for in plain words.
5. One call to action
Tell the viewer the single next step. Two options split attention and usually produce neither.
Anatomy of a good onboarding film
1. Start from the first-week questions
Collect the actual questions new users ask: from support, from customer success, from the people who run implementations. The film is an answer to those questions, in the order they come up.
2. Make chapters, not one long video
Each chapter covers one idea and stands alone. A new user who is stuck on step four should be able to jump to step four, watch it, and get back to work. Short separate chapters also make future updates cheaper, because you replace one chapter rather than the whole film.
3. Show the screen the user will actually see
If your interface is different for admins and regular users, or for different plans, say so clearly and show the right one. Nothing erodes confidence faster than a film that shows a screen the viewer does not have.
4. Say what success looks like at the end of each step
Each chapter should finish with the moment the user knows they did it correctly: the confirmation message, the first record in the table. Without that, they hesitate and open a support ticket anyway.
5. Keep the tone calm
This viewer is motivated. They do not need persuading, they need clarity. Slower, plainer pacing works better here than in a demo.
Common mistakes
Commissioning one film to do both jobs
A film that tries to persuade a prospect and also teach a new user ends up too slow for the first and too shallow for the second. Decide which is the priority and brief that.
Showing a feature tour
It is the most common failure in both film types. Choose what matters to this viewer and cut the rest.
Writing from the product’s point of view
“Our dashboard provides…” is the product talking about itself. “You can see which orders are late before the customer calls” is the viewer’s point of view.
Making the onboarding film one long video
Long films are hard to navigate and hard to update. Chapters are better for the viewer and for you.
Hiding the call to action
If the viewer reaches the end and does not know what to do next, the film has not finished its job.
Forgetting that the product will change
Interfaces change. Plan from the start for which parts of the film will date first, and keep those parts separable.
Three illustrative situations
These are hypothetical examples to show how the question works in practice. They are not client stories.
A scheduling tool that nobody understands on the homepage
Visitors arrive, scroll, and leave. Sales calls begin with a long explanation of what the product does. The loss is before the purchase, so the first film is a demo: one scene of a manager untangling a rota, one demonstration, one outcome, one call to action. The onboarding film can wait.
A data platform with strong sales and heavy support load
Deals close, but every new customer asks how to connect their first data source, and the same three questions fill the support queue for a month. The loss is after the purchase, so the first film is onboarding: a short chapter for each connection step, each ending on the confirmation the user should see.
A company with both problems
Start with whichever is more expensive to leave. If a stalled deal costs more than a support ticket, begin with the demo. If churn in the first month is the concern, begin with onboarding. Brief the second film once the first has shipped, so you can apply what you learned about your own audience.
Matching the film to where it plays
The placement shapes the film as much as the audience does. Decide it before the script.
- Homepage. The viewer is a stranger. The film should make sense with the sound off, open on the problem, and end on one action. It should not need the rest of the page to be understood.
- Sales deck or outbound email. The viewer was sent here by a person. A demo film can assume a little context and go straight to the capability that matters to that buyer.
- In-app. The viewer is already inside the product, so the film can show the real screen and refer to what is in front of them. Chapters should be short and linkable from the step they explain.
- Help centre. The viewer arrives from a search for a specific problem. Chapters must be titled the way the user would phrase the question.
- Welcome email. One chapter, the first step, and a link to the rest. Do not send the whole film to someone who has not logged in yet.
- Internal learning system. The viewer is a new employee. Add the internal vocabulary and the internal process here, and keep it separate from customer-facing material.
Writing the script: a few rules that hold up
- One film, one viewer. If the script has to say “whether you are a manager or an engineer…”, it is two films.
- Use the viewer’s words. Take terminology from sales calls and support tickets, not from internal documents.
- Let the screen do the work. If narration describes exactly what the picture shows, remove one of them.
- Cut the introduction. The viewer already clicked. Begin with the problem or the first step.
- Read it aloud. Any sentence you stumble on will sound worse in a voice-over.
- End when you are done. Do not add a recap if the film already made its point.
How to tell whether the film worked
Decide this before production, so the film has a job you can check. We do not promise specific results; what we can say is what to look at.
- For a demo film: listen to the first part of your sales calls. If you spend less time explaining what the product is, the film is doing its work. Watch where prospects drop off on the page that hosts it.
- For an onboarding film: watch the support queue for the specific questions the film answers. If those questions fade, the chapter works. If they persist, the chapter is unclear or hard to find, and that is a fixable problem.
- For both: ask a handful of real users to describe in their own words what the film showed them. Their answers are more useful than any number.
How AI production fits
Product interfaces change. Films built with AI production are practical to update when a screen or a flow changes, rather than re-shooting. Daniel and his team still direct them as films: script, look and pacing come first, then production. AI does not change what makes a good demo or a good onboarding film; it changes how practical it is to produce and revise one.
That matters most for onboarding, where the film is only useful if it matches what the user sees, and where chapters will need to be revised as the product evolves. More on our approach for tech companies.
How the brief-to-master process works
- Brief. You tell us which film you need first, who the viewer is, and where the film will play. For a demo film, send the capability you want shown. For an onboarding film, send the first-week questions and the order in which users meet the product.
- Approved brief. Daniel and his team confirm back what the film will be: the viewer, the structure, the length and the call to action. You approve it. This is the point from which the delivery window runs.
- Script and look. The script is written and the visual direction is set. You review both before production starts, because changes are cheapest at this stage.
- Production. The film is produced and assembled, with sound, captions and pacing worked as part of the film.
- Review. You review the cut and your feedback is worked into the final version.
- Master. You receive the final film in the formats you need for the places it will play.
Delivery is 7–10 working days from approved brief.
What to send us before you start
- Which question applies: are you losing people before the purchase or after it?
- The viewer, in one sentence, and the single next step you want them to take.
- For a demo film: the one capability you want shown, and who it matters to.
- For an onboarding film: the list of first-week questions, in the order users meet them.
- Where the film will play: homepage, in-app, help centre, email, internal learning system.
- Anything that must be accurate, such as screen names and terminology, and its source.
- Any constraints: brand rules, legal wording, screens you cannot show.
Cost and timing
Tech-film work starts from $5,000. Delivery is 7–10 working days from approved brief. See the pricing page for what is included.
Frequently asked questions
Which should we make first, the demo film or the onboarding film?
The one that addresses where you are losing people. If prospects do not understand the product quickly, start with the demo. If new customers keep asking the same setup questions, start with onboarding.
Can one film do both?
It can, but it will usually do both less well. The viewers have different goals, and the pacing that suits one frustrates the other. Two focused films serve you better than one compromise.
How long should each film be?
A demo film should end as soon as the point is made. An onboarding film should be built from short chapters, each covering one idea, so the total can be longer without any single chapter being long. Your content should set the length, not a target number.
What happens when our interface changes?
Films produced with AI are practical to update, rather than re-shooting. Building an onboarding film in separate chapters helps further, because you replace the chapter that changed, not the whole film.
What do you need from us to start?
Which film you need first, the viewer, where it will play, and either the capability to show (demo) or the first-week questions (onboarding). The checklist above covers the rest.
How long does it take?
Delivery is 7–10 working days from approved brief.
What does it cost?
Tech-film work, including demo and onboarding films, starts from $5,000. The pricing page sets out what is included.
Can the same material be reused for investors?
A demo film can inform an investor film, but the story is usually different, because an investor wants to believe in the team and the market, not only in the product. See investor pitch video.
Should the demo film show our real interface?
Yes. Show the screens a buyer will actually see after they sign up. A demo that shows something the product does not do costs more trust than it earns.
Who should approve the brief on our side?
One person who can decide. If product, marketing and support all review separately, send consolidated notes from a single owner so the film keeps one point of view.
Is a demo film the same as an explainer?
Not quite. An explainer teaches a concept; a demo shows your product doing a specific job for a specific buyer. Many companies need the demo first.
Next step
Tell Daniel and his team which question above describes you. Start a project.






