You open a swipe file to copy what works. So here is what 106 enterprise SaaS product explainer videos share. 88% put no presenter on camera. Most end with no link and no ask. But what most teams do is a habit, not proof. There is no view or sales data here. So test each habit against your own product before you copy it.
An enterprise SaaS explainer is a short video that shows what one B2B software product does for a company buyer. A habit, in this report, is something at least half the videos do. ADVIDS Research coded 106 of them frame by frame, from 88 companies such as Salesforce, SAP, IBM and Anthropic.
Thirteen habits stand out. Most videos show the product screen (Mockup First). Few put a person on camera (Empty Chair). Few use camera scenes (Drawing Board). The screen comes early (Early Screen). It is usually a dashboard (Filled Dashboard). A voice tells the story (Voice Track). The name waits at the start (Cold Open). It shows at the end (Name Card). Most end with no ask (Next Step). Most stay short (Two-Minute Cap). Words stay on screen (Text Track). The picture changes often (Seven-Second Cut). And bright videos just edge out the rest (Own Ground).
ADVIDS Research · 106 enterprise SaaS explainers · 88 companies · all coded frame by frame · published 14 September 2026 · 24 min read
Top takeaways
Mockup First
75% of the videos show the product screen itself, and more draw it than record it.
Empty Chair
88% of the videos put no presenter on camera.
Drawing Board
65% use no camera scenes and no stock clips at all.
Early Screen
87% show a product screen, and the typical video gets there 14 seconds in.
Filled Dashboard
71% show a dashboard, far more than any other kind of screen.
Voice Track
70% use a voiceover, and the rest run on music and words on screen.
Cold Open
64% keep the name off screen for the first two seconds, and just 4 open on a logo.
Name Card
93% end with the company or product name on screen.
Next Step
65% end with no link and no ask on screen.
Two-Minute Cap
81% run two minutes or less, and the typical one runs 1:14.
Text Track
92% keep words on screen in at least half their scenes.
Seven-Second Cut
61% change the picture at least eight times a minute.
Own Ground
53% look mostly bright, but no single look wins half the videos.
Questions this report answers
What do enterprise SaaS product explainer videos have in common in 2026?
Thirteen habits, each shared by at least half of the 106 enterprise SaaS product explainer videos. 88% put no presenter on camera. That's the Empty Chair. Most show the product screen, which is Mockup First. And most end with no link or ask, which is Next Step. Each habit has an exception, and the report shows when to break it.
Should a SaaS explainer video use a screen recording or an animated interface?
Most draw it. That's Mockup First. 47 videos draw the interface as a mockup alone, and 27 use a screen capture alone. Record the real product when your demo account is full of believable data. If it's empty or messy, have it drawn instead.
How long is an enterprise SaaS explainer video?
Two minutes or less, in 81% of cases. That's the Two-Minute Cap. The typical video runs 1:14. Some longer ones walk through setup, like Cequence Security's, made for the engineer who sets the product up. If your buyer only needs the idea, stop at two minutes.
Do SaaS explainer videos use a presenter or a voiceover?
A voiceover, far more often. That's Voice Track. 70% of the videos use one, and only 13 put a presenter on camera, which is the Empty Chair. Those 13 include Bloomfire, Deel, Emburse, G-Stacker, etc. A presenter makes sense when a specialist is the product you sell.
Should an explainer video end with a call to action?
Yes, when nothing around the video carries the ask. That's Next Step. 65% of the videos end with no link or call to action on screen, though 93% end on the name. If your video gets forwarded or plays in a feed, put the link on the last frame. Nooks ends on Book a demo and its link.
Should a SaaS explainer video open with the logo?
Usually not. That's the Cold Open. 64% of the videos keep the name off screen for the first two seconds, and only 4 open on a logo. Microsoft opens Copilot Cowork on three words of text instead. Open on your logo only when the product has its own name to learn, as Zeta Global does with Athena.
How was this analysis done?
ADVIDS Research checked 188 videos against a rule written before the work began. 106 qualified, from 88 companies, and each was coded frame by frame. The 13 habits are simple counts: Mockup First, Empty Chair, Drawing Board, Early Screen, Filled Dashboard, Voice Track, Cold Open, Name Card, Next Step, Two-Minute Cap, Text Track, Seven-Second Cut and Own Ground.
How to read this report
This report looks at 106 enterprise SaaS product explainers from 88 companies, uploaded to YouTube from 5 January to 3 August 2026. Each figure counts videos, like 80 of 106. A habit is something at least half the videos do.
Insight 01 · Mockup First
1. Most videos show the product screen, drawn or recorded.
Most enterprise SaaS explainers put the product's own screen in the video. 75% do it (80 of 106). More of them draw the screen than record the real thing. So if your buyer works in that screen every day, show it. Draw it, or record it once your demo account looks ready.
Think of a floor plan next to the house. Your buyer moves in on day one. The video is the floor plan.
47 show only a drawn, animated screen. 27 show only a recording of the real product. So a drawn copy of the screen is the usual choice.
Example: Amplience records its real product. At 0:30, its video sits inside the Workforce Flows builder, with steps like Remove Background and Trim Image joined on a canvas.
Product screen shown: companies in this group include Anthropic, OpenAI, SAP, Bloomfire, etc.
Exception: when the point is where the product runs. Lyzr's LyzrGPT video is 0:36 of moving text on black, with no product screen. For a private chat that keeps data on your own servers, where the data stays is the message.
Source: Advids analysis of 106 enterprise SaaS explainers
Few videos mix the two. Just 6 use both.
Insight 02 · Empty Chair
2. Most videos put no presenter on camera.
Almost no enterprise SaaS explainer puts a person in front of the camera to talk. 88% have no presenter (93 of 106). A narrator's voice and the product screen do the work instead. So unless one person is your product, leave the presenter's chair empty and spend the money on design.
Think of a cooking video shot from above. No chef's face, just the hands and the pan. Your buyer came for the pan.
People still appear in 32 videos, inside scenes. But none of them talk straight to the camera.
Example: Pinecone explains its database with diagrams alone. At 0:48, its video lays out the system on a dark grid, from the Pinecone API down to storage. Nobody is in frame, and nothing feels missing.
No presenter: companies in this group include Neo4j, Atlassian, Cadence, HPE, etc.
Exception: when the specialist is the product. Deel's Deel Mobility video keeps a sales director on screen for most of its 1:11. When you sell a service run by experts, the expert is the product shot.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 03 · Drawing Board
3. Most videos skip camera scenes and stock clips.
Most enterprise SaaS explainers are made at a desk, not on a set. 65% use no camera scenes and no stock clips (69 of 106). They are drawn, animated, typed or recorded from the screen. If your product's work happens on a screen, you likely don't need a camera crew at all.
Nobody hires a camera crew to show a spreadsheet. It's already on the screen.
78 of 106 mix two or more ways of making the picture. So an enterprise SaaS explainer is a design job first, not a production job.
Example: Campfire builds its whole video from drawn screens. At 0:11, five accounting tasks sit on white, each marked active or inactive. No set, no crew.
No camera scenes: companies in this group include AIMS360, Airia, Akto, Alloy, etc.
Exception: a chore people can see. Jodoo's video shows managers counting boxes by hand, with real people on camera, before its screens arrive at 0:30. Acting out the old chore sets up the product.
Source: Advids analysis of 106 enterprise SaaS explainers
Camera scenes and stock clips sit at the bottom of the list.
Insight 04 · Early Screen
4. The product screen shows up in the first seconds.
Most enterprise SaaS explainers show the product screen, and they show it early. 87% put one on screen at some point (92 of 106). The buyer gets to see what they'd log in to. So if your buyer uses the product every day, don't make them wait to see it.
A car ad that never shows the inside leaves one question open. What is it like to sit in? Your buyer asks the same about your product.
In the typical video, the first product screen lands 14 seconds in. It might be a dashboard, a chat panel or a screen recording. In 69 videos, the product's screens stay up for a quarter of the runtime or more.
Example: Nexthink gets there at 0:07, when its Spark chat panel opens on a desktop. By 0:10, the panel greets you: Hi, I am Spark, your personal IT agent.
Product screen shown: companies in this group include IBM, Sword Health, Workday, Amplience, etc.
Exception: a product that works out of sight. Symantec's CBX video shows no product screen at all, just 3D dials labeled Protection, Uptime and Threat Detection. For a security layer nobody watches, the dial stands in for the console.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 05 · Filled Dashboard
5. When a product screen appears, it's usually a dashboard.
The dashboard is the screen most enterprise SaaS explainers show. 71% show one (75 of 106). That's far more than chat panels or diagrams. So if your product reports on work, show the dashboard. And fill every card with believable numbers before design starts. An empty dashboard looks like an unused product.
A shop window with empty shelves says the shop is closed. An empty dashboard says the same about your product.
Example: Salesforce shows a full one. At 1:06, a Revenue Cloud quote sits behind a Submit for Approval box with one comment: Please approve. It's enterprise software shown the way buyers use it, as records and numbers.
Dashboard on screen: companies in this group include AppsFlyer, Asana, Aviso, Board, etc.
Exception: a buyer who writes code. Anthropic's Claude Code video shows terminal windows, code changes and a pull request, with no dashboard anywhere. For a developer, the work itself is the screen.
Source: Advids analysis of 106 enterprise SaaS explainers
Chat panels and diagrams tie, both well behind the dashboard at 75.
Insight 06 · Voice Track
6. Most videos use a voiceover, not music alone.
Most enterprise SaaS explainers have a narrator. 70% use a voiceover (74 of 106). The rest run on music and words on screen. Longer videos lean on a voice more. So if your video runs past a minute, write it to be heard, and plan for a voice actor in the budget.
A museum audio guide tells you where to look. Your narrator does that for a dashboard.
Voiced videos typically run 1:21. Music-only ones run 0:59, and most of them lean on moving text on screen instead.
Example: FundApps runs an illustrated story under its narrator. At 0:31, two binocular circles look over blue water with shark fins. No words on screen. The voice carries it.
Voiceover: companies in this group include Amplitude, Arkose Labs, Cegid, Celigo, etc.
Exception: when a picture can make the point. Board's planning video runs 1:00 on music alone, with icons, news widgets and diagrams on dark navy. Linking outside events to internal plans needed no sentence.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 07 · Cold Open
7. Most videos hide the name for the first two seconds.
Most enterprise SaaS explainers don't open with the logo. 64% show no company or product name in the first two seconds (68 of 106). They open on a line of text, a scene or a screen. If your buyer doesn't know your name yet, spend those seconds on their problem instead.
A stranger who opens with their name gets a nod. One who opens with your problem gets a question back.
Only 4 videos open on a logo. In 54, the logo first shows up near the end.
Example: Microsoft opens Copilot Cowork on a single line of text. At 0:01.5, three words sit on a near-white background: ask for help. No logo. Just the request.
No name at the start: companies in this group include ClayHog, Crisp, Deel, Deliverect, etc.
Exception: a product with its own name. Zeta Global's Athena video shows the Athena logo from the first frame. When the product's name differs from the company's, that name is the first thing to learn.
Source: Advids analysis of 106 enterprise SaaS explainers
A logo is the rarest way to open.
Insight 08 · Name Card
8. Almost every video ends on the name.
Nearly all enterprise SaaS explainers put the name on screen at the end. 93% show the company or product name in the last frames (99 of 106). Most end on a logo screen. That matters because videos get forwarded. If yours can travel without you, end on a frame that says who made it.
A forwarded video arrives with no email around it. The last frame is its only signature.
Just 4 end on a YouTube Subscribe or Watch next screen. The name comes last, not first.
Example: Swimlane ends on its logo. At 0:46, it sits on black between a blue flare and a pink one. Nothing else is on the frame.
Name at the end: companies in this group include Campfire, Cequence Security, Contentstack, Dext, etc.
Exception: a video that's an invitation. Rho's Gmail Connector teaser ends on Join the beta and LOCK IN, with no Rho logo. When you invite customers into a beta, the invitation takes the name's place.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 09 · Next Step
9. Most videos end without a link or an ask.
Most enterprise SaaS explainers stop at the name. 65% end with no link and no call to action on screen (69 of 106). That's fine on a page that carries the ask. But videos get forwarded and play in feeds. If yours plays alone, put the next step on the last frame.
A business card with no phone number works when you hand it over. Forwarded, it's a name with no way back.
Example: Zoom ends on its Virtual Agent logo, in white on dark navy, at 2:09.8. No link. No ask.
No ask at the end: companies in this group include ElevenLabs, Emburse, Epicor, FundApps, etc.
Exception: a buyer who books meetings for a living. Nooks' AI Sequencing video ends on its logo, Book a demo and nooks.ai/request-demo. For a sales team, the close is a meeting request.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 10 · Two-Minute Cap
10. Most videos run two minutes or less.
Most enterprise SaaS explainers stay short. 81% run two minutes or less (86 of 106). They explain one job well and leave setup for later. If one task can explain your product, stop at two minutes. Move the setup steps to a separate walkthrough.
A trailer sells the plot. The manual comes in the box. Your explainer is the trailer.
The typical video runs 1:14. The biggest group runs between 0:46 and 1:30.
Example: Epicor explains Prism in 0:30. At 0:10, the Prism panel answers a question about item usage beside a forecast chart, under two words: Instant Answers. One question, one answer.
Two minutes or less: companies in this group include Doxis, GitLab, Global Payments, HubSpot, etc.
Exception: a buyer who sets it up. Cequence Security's AI Gateway video takes 2:45 to walk through the setup, step by step. When the viewer configures the product, the video runs as long as the setup.
Source: Advids analysis of 106 enterprise SaaS explainers
The typical video, at 1:14, sits in that middle group.
Insight 11 · Text Track
11. Almost every video keeps words on screen.
Words on screen are close to universal in enterprise SaaS explainers. 92% show readable text in at least half their scenes (97 of 106). People often watch with the sound off, or see the video forwarded. So write the on-screen lines with the voiceover, not later in the edit.
Think of a TV in a hotel lobby with the sound off. The words on screen do the talking.
60 videos use moving text scenes, and 11 burn captions into the picture.
Example: Celigo sets its lines in white and cyan on black. At 0:58, one line fills the frame: If you can dream it.
Text in half the scenes: companies in this group include G-Stacker, Infobip, IPRally, Jodoo, etc.
Exception: when people talking is the demo. Zoho Cliq's video is a scripted chat between two colleagues, with text in just 2 of its 8 scenes. For a chat and meeting tool, the talk is the proof.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 12 · Seven-Second Cut
12. Most videos change the picture eight or more times a minute.
Enterprise SaaS explainers move fast. 61% change scene at least eight times a minute (65 of 106). That's a new picture every seven seconds or so. Short lines need fresh pictures to match. So if your script is built from short lines, plan one new frame for every seven seconds of runtime.
Think of a flip book. The page count sets the speed before anyone draws a line.
18 videos reach ten or more scene changes a minute.
Example: Dext moves through two-word text beats. At 0:09, It learns sits in black on a pale peach background.
Eight or more scene changes: companies in this group include Jumio, Kantar, Kroolo, LangChain, etc.
Exception: a comedy sketch. ServiceNow's AI Control Tower video changes scene under four times a minute, following office workers whose queues have emptied. Each scene runs as long as its joke.
Source: Advids analysis of 106 enterprise SaaS explainers
Insight 13 · Own Ground
13. Just over half the videos look mostly bright.
No background color owns this category. 53% of enterprise SaaS explainers look mostly bright (56 of 106), just past half. Light, dark and mixed looks all have big followings. So don't copy the category. Take your background from your own product screen, light or dark, and keep it to the last frame.
Paint a room to match the furniture, not the neighbors. Your product's own screen is the furniture.
Light looks lead dark ones, 48 to 31. Neither reaches half.
Example: AIMS360 stays light. At 0:12, module tags like Inventory, Production and Accounting sit on a pale background, with All sales channels in violet.
Mostly bright: companies in this group include Lightcast, Microsoft, Nooks, Ofelia, etc.
Exception: when the dark is the subject. Arkose Labs' Arkose Titan video runs through dark-red 3D tunnels and a lightning-struck orb. When the product fights bot attacks, the dark is the threat.
Source: Advids analysis of 106 enterprise SaaS explainers
Light leads dark by 17 videos. Neither reaches half.
Benchmarks
Use these numbers to check your own SaaS explainer before you brief it.
Length, screens and pace
| Measure | Typical | What it means |
|---|---|---|
| Runtime | 1:14 | Half the videos run shorter than this |
| First product screen | 0:14 (92 videos) | Time into the video, among videos that show one |
| Time with a product screen up | 39 percent | Share of the video, across all 106 |
| Time with a dashboard up | 25 percent (75 videos) | Share of the video, among videos that show one |
| First logo | 0:54 (76 videos) | Time into the video, among videos with a logo screen |
| First scene | 0:07 | How long the opening scene lasts |
| Scene changes a minute | 8.4 | How often the picture changes |
| Words spoken | 158 (74 videos) | Words in the voiceover, among videos with one |
| Scenes with words on screen | 86 percent | Share of scenes with readable text, across all 106 |
Typical means half the videos sit below the number and half above it.
What only some videos do
| What the video does | Videos (of 106) |
|---|---|
| Looks light | 48 |
| Chat panel on screen | 43 |
| Diagram on screen | 42 |
| Opens on a text slide | 40 |
| Shows the product screen in the first 10 seconds | 40 |
None of these reaches half the videos, so none counts as a habit. An ask at the end (37) and a presenter (13) are rarer still.
13 questions for your next brief
Answer these 13 before you write the brief.
- Insight 01 Will your buyer work in the screen you're showing? Then show it. Record it if the demo account is full, or have it drawn.
- Insight 02 Is one person the product? If not, skip the presenter and pay for a narrator.
- Insight 03 Does the product's work happen on a screen? Then start with animation studios, not camera crews.
- Insight 04 Will your buyer log in? Get the product screen up by 0:14.
- Insight 05 Does the product report on work? Fill the dashboard with believable numbers before design starts.
- Insight 06 Does the cut run past a minute? Write it for a voice.
- Insight 07 Does your buyer know your name yet? If not, open on their problem, not your logo.
- Insight 08 Can the video travel without you? End on the name.
- Insight 09 Does the video play alone? Put the link or ask on the last frame.
- Insight 10 Can one task explain the product? Stop at 2:00 and move setup to a separate walkthrough.
- Insight 11 Can people watch it muted? Write the on-screen lines with the voiceover.
- Insight 12 Is the script built from short lines? Plan a new picture every seven seconds.
- Insight 13 Is your product light or dark? Match the video's background to it.
Now go back to the swipe file you opened. Most videos have no presenter and no ask. Neither is a rule. Each is a choice your product should make.
This week, open your last explainer brief. Answer the 13 questions in one column. Write one line for every habit you break.
A swipe file shows what everyone did. Your product decides what you copy.
Methodology
| Vertical | Videos |
|---|---|
| fintech | 12 |
| devtools | 12 |
| productivity | 5 |
| marketing | 5 |
| ai | 4 |
| retail | 4 |
| martech | 4 |
| enterprise | 4 |
| other verticals | 56 |
| Coding scheme | Values | Definition |
|---|---|---|
| Build | ui_mockup · screen_recording · 2d_animation · 3d_cgi · kinetic_type · live_action · stock | Coded from frames: every production method visible in the video, with a confidence of high or medium. A video can carry several. |
| Format | screencast · motion_graphics · kinetic_type · cinematic · talking_head | Coded from frames: the genre the video reads as. A video can carry several. |
| Interface motif | dashboard_ui · chat_ui · terminal_ui · handheld_device_ui · notification_alert · screen_recording_generic | Coded per timed segment, with the first timecode and the share of runtime covered. |
| Opening | first segment motif · name or logo in the first two seconds | The first coded segment gives the opening motif. The name check is coded from frames cut at 0.4 and 2.0 seconds: a logo, a title naming the product or a product badge counts; a corner watermark does not. |
| Presenter | talking-head segment present or absent | Coded per timed segment: a person speaking to camera. People in live-action or stock scenes who do not address the camera are not presenters. |
| Sound and text | voiceover · music only · on-screen text share · captions burned in | Voiceover or music only comes from audio analysis. On-screen text share is the share of coded segments carrying legible text. Burned-in captions are coded from frames. |
| Runtime and pace | seconds · scene changes per minute | Runtime is read from the file. Pace is coded segment boundaries per minute of runtime. |
| Frame | light · dark · mixed · brightness 0 to 255 | Computed, not coded: mean luminance across the nine sampled frames. It covers every frame, not the product interface alone. |
| Close | last segment motif · name in the final frames · URL or ask | The last coded segment gives the closing motif. Name and URL or ask are coded from frames cut 2.5 and 0.8 seconds before the end, combined with the on-screen text recorded for segments in the final 15 percent of runtime. |
| Not coded | altitude | What each video argues. The library records no altitude and this report does not code it from transcripts. |
Cite this report
Jai Ghosh, Advids. The 2026 Enterprise SaaS Video Swipe File: 106 Product Explainer Videos Analyzed for 13 Insights. 14 September 2026. https://advids.co/blog/enterprise-saas-product-explainer-video-swipe-file
Author & editor bio
About Advids
Advids produces video for AI, SaaS and DeepTech companies. ADVIDS Research publishes coded studies of what those companies ship, with the dataset attached so every count can be checked.