Transforming abstract features into understandable visuals
When the product is intangible, video cannot be shot literally but must find the right metaphor and create movement to convey that idea.
For abstract features like infrastructure, data, or algorithms, do not explain technology literally. Choose a visual metaphor that represents how the product behaves, then animate that idea instead of just presenting a slide listing features. The main video should be concise, around 60 to 90 seconds, starting with a problem faced by the viewer, and always showing the interface or real results instead of just narrating.
- Intangible products (infrastructure, data): use metaphorical animations.
- Real interface: screen recording of motion (screen-in-motion).
- 60-90 second script for the sales page, under 45 seconds for social media ads
- List features on the slide instead of demonstrating how to solve the problem.
- stuffing many messages into one video dilutes the core idea
The most frequent question Sinh Vũ hears from tech clients is: "Our product is hard to explain, it’s too complex." In reality, the issue often does not lie in the product's complexity but in the approach: trying to explain technology literally instead of finding imagery that accurately describes how it behaves. A good explainer video does not require viewers to understand the technical architecture inside. They just need to understand what the product can do for them and feel confident that it is real.
Starting point: visual metaphor
For intangible products like cloud infrastructure, data processing algorithms, or automation modules, there is nothing to film directly. At this point, the most important step is not design or production but finding the right visual metaphor. A visual metaphor is a familiar image that the viewer understands, used to explain how the product behaves.
For example: a data permission system can be visualized as a chain of locks and keys in different colors. A real-time data synchronization tool can be represented as two water tanks balancing each other instantly when one side changes. Once the right metaphor is found, the rest of the video is just about animating that idea, rather than trying to explain further.
When to choose animation, when to screen record
Metaphorical animation: suitable when the product is intangible, when the concept needs to be simplified thoroughly before detailed introduction, or when the viewer is a business decision-maker rather than a technical team. Advantages: flexible, complete visual control, easy to maintain brand consistency. Limitations: does not show the actual product, may create distance if the viewer wants to see the interface before purchasing.
Screen-in-motion filming is suitable when the product's value lies in the experience of interaction, when the viewer is a direct user or technical team, or when you want to shorten the gap between the video and actual use. Limitation: if the interface changes, the old video becomes outdated quickly. In many cases, a combination of both is used: animation at the beginning to explain concepts, cutting to real screens for illustration.
The structure of a proven script
Google's ABCD framework, applied to technology videos, works as follows. Early attention: start with a problem the viewer is facing, not the product name or logo. Consistent branding: introduce the brand from the first seconds and maintain consistency in colors, voiceover tone, and motion style. Connection: use the viewer's language, not internal jargon. Clear direction: provide a single action at the end, not three or four options at once.
Voiceovers describing benefits while visuals show real actions. These two layers complement each other rather than repeat.
Practice explainer videos for software, Sinh Vũ Studio
The specific structure commonly used: hook in the first three seconds, the problem the viewer has, the solution is the product, benefits and demonstration of actions, call to action. Each video maintains one core message. If the product has multiple features, create several short videos on different topics, rather than cramming everything into one.
Length according to the source
- Homepage or sales page: 60 to 90 seconds. Long enough to explain, short enough to hold attention.
- An onboarding video for newcomers can be two to three minutes long because viewers already have a reason to watch.
- Social media advertising: under 45 seconds to match scrolling rhythm.
- Technical demo videos for the purchasing team: not tightly bound, but need a clear structure so viewers know where they are in the flow.
Common mistakes to avoid
- List features on slides instead of showing how the product solves a specific problem. Viewers don’t buy features; they buy results.
- Stuffing too many messages into one video. Each additional message dilutes the core message.
- Use internal terminology that the viewer does not have a framework to understand. Say 'reduce implementation time' instead of the technical name of that process.
- To have the logo appear late at the end. The brand needs to be recognized early, especially when viewers may leave before the video ends.
- A script that is too long for the duration leads to rushed narration. If it cannot be read comfortably, the script needs to be cut, not read faster.
The viewpoint of Sinh Vũ
Sinh Vũ approaches explainer videos through the lens of brand identity, not purely as video production. This means maintaining the same narrative voice, color scheme, and motion rhythm as the rest of the brand, so this video aligns with the website, sales materials, and other touchpoints. A beautiful video that is out of tune with the brand will create a sense of inconsistency and reduce trust.
Before incurring production costs, Sinh Vũ creates a storyboard and animatic to review ideas with you. This helps identify structural issues or metaphors early on, rather than after production is complete. In the long run, Sinh Vũ prioritizes building a reusable motion library, so future videos share a visual language and reduce costs for each new production.
Decision checklist
Topic: Video explaining abstract technology features. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Google Ads Help: About the ABCDs of effective video ads. Think with Google: A playbook for building effective creative on YouTube (ABCD framework). Wistia: Optimal Video Length. Practical experience in creating explainer videos for software from Sinh Vũ.
Frequently asked questions
Animation or screen recording, which is better for software?
There is no default answer. If the product's value lies in interface interaction, screen recording of motion design is often more convincing because viewers see exactly what they will use. If the product is infrastructure, data, or algorithms without a visual interface, metaphorical animation is a more reasonable choice because there is nothing to film literally. In many cases, a combination of both works: animation explains the concept, then cuts to the real screen.
How long should an explainer video be?
Stick to the delivery point. The main copy on the sales page or homepage should be within 60 to 90 seconds to maintain full attention. The guide for newcomers can be longer, around two to three minutes. The copy running on social media should be even shorter, under 45 seconds, to match the scrolling pace. Don’t shorten the script to fit the duration and then rush through it. If there’s too much content, split it into multiple videos by topic.