How to make an explainer video for a technical product
Most explainer-video advice assumes your product is something you can point a camera at. If you market cybersecurity, identity, or AI infrastructure, it isn't. Your product is a layer, a protocol, a model running somewhere you'll never see, and that changes everything about how you film it. If yours is a cybersecurity product, the security product explainer guide covers the part that can't be seen.
There's no satisfying hero shot for software. The moment you show the dashboard, you've made the same video as every competitor. So the real challenge of a technical explainer isn't production polish. It's making something abstract land: fast, with people who are sceptical, busy, and have already seen a hundred videos that all blur together.
This is the working method we use to do exactly that, across 500+ films for B2B tech brands. Four moves, in order.
Then the practical part: a filled-in sample brief, the production choices you'll face, and what a project actually includes.
| The move | What it does | Watch for |
|---|---|---|
| Stakes | Opens on the problem, not the product | Could your first 15 seconds sit on a rival's video unchanged? |
| Physical | Gives the abstract scale, weight and texture | Have you defaulted to a glassy blue dashboard? |
| Human | Anchors it to one person with a real stake | Is there a specific person, not a stock smile? |
| Reveal | Earns the reveal, then shows the product clearly | Does the product ever actually, clearly appear? |
Start with the stakes, not the software
The most common mistake in technical explainers is opening with the product. “Introducing [Product], the platform that…” Every one of them starts this way, which is exactly why none of them get watched.
Your buyer doesn't care about your product in the first ten seconds. They care about the problem it solves and what happens if it isn't. So open there. Before you write a word of script, answer one question: what breaks if this product doesn't exist? A breach that ends a career. A model that can't scale and a launch that slips. That tension is your cold open, and the product becomes the relief that arrives later, landing harder because you made the audience feel the problem first.
Watch for: if your first fifteen seconds could be swapped onto a competitor's video without anyone noticing, start again.
Make the invisible physical
You can't film a protocol. But you can give an abstract idea scale, weight, light and texture, and that's what makes a technical explainer memorable rather than forgettable. The lazy default is a glassy 3D dashboard floating in blue space. It looks like every other tech video because it is every other tech video.
The better path is a metaphor or a real-world scene that makes the concept tangible. For Thales, instead of diagramming identity and access management, we built a series around a recurring knight character: one visual device that made a genuinely technical subject accessible and engaging. The concept did the explaining; the product didn't have to.
That's the craft in one line: lead with the concept, make it tangible, then show the product once the viewer actually cares. Here's one of our explainers doing exactly that:
Find the one human truth
Even the most technical product is bought by a person whose job, reputation, or night's sleep depends on a decision. That person is your way in. Not a generic “happy employee at a laptop,” but a specific person with a specific stake. Anchor the abstract idea to one real human truth and the audience has somewhere to put their attention; the technology becomes meaningful because it matters to someone they recognise.
This is also what makes a video shareable internally. Decisions in complex tech are made by committees. A video that makes one person feel something is the one that gets forwarded to the rest of the buying group.
Withhold the product, earn the reveal
The strongest explainers don't open on the product; they earn their way to it. Think of it like a film trailer: you don't show the ending first. You build the tension, raise the stakes, then hit the moment where it pays off. By the time the product appears, the audience is leaning in, because you've spent the first half making them care about the problem it answers.
But holding back isn't hiding. The reveal still has to land, and when it comes, the product has to be shown clearly and stay technically true. An explainer that never quite shows the product, or buries it under two minutes of abstract animation, is the single most common way these films fail. Lead with the feeling; then deliver the proof.
A structure you can brief against
Open on the stakes: the problem and what's at risk, no product, no logo. Build the tension: specific and human. Make the turn: introduce the idea, not the feature list. Then the reveal: show the product doing its job, clearly. Add the proof: a real client, a real outcome. And finish with one clear next step: not “learn more,” but a specific action.
Most explainers run 60 to 120 seconds, about 90 at their tightest. If yours is sprawling well past two minutes, you're probably explaining features the audience doesn't need yet.
A sample brief for a technical explainer
Our one-page video brief asks nine questions. Here they are filled in for an imaginary product: an identity security platform that finds the API keys, service accounts and AI agents nobody owns. It is invented, but it has every problem a technical explainer has: nothing to film, a sceptical buyer, and a risk most of the audience has never seen.
| Brief field | Filled in |
|---|---|
| The one job | Create awareness. Most security teams count their people, not their machine identities, so the film has to make the problem real before it sells anything. |
| Audience | CISOs and identity and access leads at enterprises running cloud and AI workloads. Cold and unaware. |
| The stakes | One forgotten API key with admin rights is an open door. The cost is a breach traced back to a credential nobody knew existed, and an audit nobody can pass. |
| The one message | You can't secure identities you can't see. This finds every one, human or not. |
| The one feeling | Unease first, then relief: "so that's who has the keys". |
| Proof | A named customer and one measured outcome, such as how many unowned credentials it found in the first week. |
| Runs & format | Site hero and sales follow-up at 90 seconds, 16:9. Paid cuts at 15 and 30 seconds in 1:1 and 4:5, built to work with the sound off. |
| Next step | Book a 20-minute identity exposure review. |
| Practicals | Needed six weeks before the launch event. Budget range agreed up front. Mandatories: logo lock-up, legal review of any breach claims, no real customer data on screen. |
Notice what the brief leaves out: the metaphor, the structure, the shots and the craft. Those are the studio's job. A brief that specifies "show a dashboard with alerts" has already made the video every competitor made. A brief that says "make them feel they can't see who has the keys" gives the makers something to solve.
Animation, live action or both?
For a technical product, the format decision comes from one question: what does the viewer need to see to understand it? Pick the format that can show that. Here is how the main options fit.
| Format | Fits when | Watch for |
|---|---|---|
| 2D animation | The idea is a process or a flow: data moving, an attack path, a decision made in milliseconds. Easy to update when the product changes. | Icon soup. If every frame is arrows and shields, it looks like every other security video. |
| 3D animation | The product is hardware, or you need precision and scale. Our Thales Luna 8 launch film rendered a hardware security module that had no interface to film. | The glassy blue dashboard. 3D makes it very easy to look expensive and generic at the same time. |
| Live action | The story is human: a threat, a consequence, a character. Our Ransomware and IAM Knight films for Thales are live action. | Shoot days, cast and locations cost more and are harder to change after the shoot. |
| Mixed media | Real people in a real setting, with animation revealing the system they can't see. Often the best fit for "make the invisible physical". | Two crafts, two review tracks. Plan the handover between them in the storyboard. |
| Product UI | The reveal and the proof. Buyers need to see the real interface doing its job. | Opening on it. And real data needs masking, which adds post-production time. |
| AI-assisted | Speed in concept frames, backgrounds and early versions. | Consistency and rights. It still needs a director's judgement and a legal check. |
Format isn't the idea. Whichever you choose, the film still needs something nobody else in your category has: a metaphor, a quirk, a register of subtle humour, or a visual style that isn't worn out. One is the minimum. Without any, it's category video, however well it's made.
Four more choices to make early
- Length. 60 to 120 seconds for the hero film. Decide the cutdowns now (30, 60 and 90 seconds for sales, 15 and 30 for paid) so they are planned into the edit, not hacked out of it later.
- Frame. A 16:9 master for the site and YouTube. If it will run on LinkedIn or other paid social, plan 1:1, 4:5 and 9:16 versions from the storyboard. How to brief those.
- Voice or text. Voiceover carries nuance on the site. On social, most people watch muted, so key lines need to work as on-screen text too.
- Who signs off the technical truth. Name one engineer or product lead who approves accuracy, and book their review into the schedule. It is the step most often missing, and the one most likely to stall a project at the end.
What a technical explainer project includes
Scope is where most video projects go wrong: a quote for "one video" that quietly needed six. This is what a typical explainer project with us covers, so you can compare like with like.
| Stage | What's included |
|---|---|
| Film Blueprint | Research, a competitor teardown, the creative brief, concepts, script and storyboard. Free: you pay $0 until you sign off the storyboard. |
| Production | Animation, a shoot, or both, depending on the format chosen above. |
| Reviews | Unlimited revisions within the agreed scope. We build a technical accuracy review into the schedule. |
| Deliverables | The hero master plus the agreed cutdowns and social versions, with captions and any language versions in the brief. |
| Team | One dedicated producer and a single approval contact on your side. |
| Timeline | A typical launch set runs Day 00 to Day 28, brief to delivered cuts. Shorter is possible when work runs in parallel. |
| Billing | Fixed scope, fixed schedule, and one invoice you've seen from day one. |
| Not included unless scoped | Extra versions, travel, additional shoot days, talent renewals, translation and out-of-scope changes. |
Production starts from $5,000 per project. What moves the price is the scope: the format, how many cutdowns and versions, talent and licences, the number of approvers, and the deadline.
Where explainers backfire
The company first. Leading with who you are instead of the problem the viewer recognises. They tune out before you've earned their attention.
Everything at once. Trying to explain every feature instead of the one that matters. Clarity is the floor. The job is the one idea they remember.
All concept, no proof. Two minutes of abstract animation and the viewer still can't picture using the product. The most common explainer failure, and the most fatal.
The one-off. Treating the film as a single asset, when the same shoot could have produced social cut-downs and sales-enablement clips too.
Make them feel it first
Making an explainer video for a technical product isn't about better animation or a bigger budget. It's a shift in approach, from describing what your product is to making people feel the problem it solves. Lead with the stakes. Make the invisible physical. Anchor it to one human truth. Withhold the product until the reveal is earned.
Do that, and an abstract product becomes something people understand in ninety seconds, and remember long after. The kind your sales team reaches for on every call, and that keeps making sense long after launch day. That's the hardest job in B2B video, and it's the one we do best. Want to see what this could look like for your product? Talk to us: we'll show you, before you commit to anything.
Frequently asked questions
Most run 60 to 120 seconds, about 90 at their tightest. If yours runs well past two minutes, it is probably explaining features the audience doesn't need yet. Plan shorter cutdowns (30, 60 and 90 seconds for sales, 15 and 30 for paid social) at the same time.
Choose the format that can show what the viewer needs to understand. Animation suits processes and products with nothing to film, 3D suits hardware, live action suits human stakes and threat stories, and mixed media combines a real setting with an animated view of the system. The real interface belongs in the reveal, not the opening. Whatever the format, it needs one idea nobody else in your category has used.
Nine things: the one job, the audience, the stakes, the one message, the one feeling, the proof, where it runs and in what format, the next step, and the practicals (deadline, budget, mandatories). Leave the metaphor, structure and shots to the studio.
At Black Camel, a typical launch set runs Day 00 to Day 28, from brief to delivered cuts. Technical accuracy reviews and the number of approvers are what usually stretch a timeline, so name your technical approver at the start.
At Black Camel, the Film Blueprint (research, brief, concepts, script and storyboard) is free, and you pay $0 until you sign off the storyboard. Production starts from $5,000 per project. Format, cutdowns and versions, talent and licences, approvers and deadline set the final price.