Every module owner wants a scene in your platform video. So the brief lists them all. Now look at what real suite videos do. More modules didn't make them longer. Three-module videos typically ran 1:44, and those with six or more ran 1:34. So every extra module takes seconds from the others. Your brief has to pick a lead.
A suite video is a SaaS explainer or platform overview that shows several modules of one platform. A module here is any product, app, agent or feature the script names. ADVIDS Research studied 120 of them, from 99 companies like Zoho, Genesys, Microsoft and Workday. Which ones count as top brands is your call, since the videos carry no ranking or view data.
Eight findings stand out. Most name four to six modules (Short List). They call modules by their job (Plain Labels). The whole platform comes first (Frame Line). Modules come one at a time (Guided Tour). A short setup runs before the first module (Setup Window). One module gets most of the time (Hero Part). More modules don't add runtime (Fixed Runtime). And module names show on screen (Screen Names).
ADVIDS Research · 120 SaaS suite videos · 99 companies · 30 coded frame by frame · published 14 September 2026 · 19 min read
Top takeaways
Short List
81% of SaaS suite explainers name four or more modules, and the typical one names 5.
Plain Labels
83% call more modules by their job, like payroll, than by a product name.
Frame Line
84% say what the whole platform does before they name the first module.
Guided Tour
54% show the modules one at a time, and 15% follow one workflow through them.
Setup Window
73% wait at least 15 seconds before they name the first module.
Hero Part
70% give one module at least three times the time of another.
Fixed Runtime
66% of videos with six or more modules still run two minutes or less.
Screen Names
63% of the 30 videos coded frame by frame put a module's name on screen as text.
Questions this report answers
How do SaaS companies present a suite of products in one explainer video?
Most SaaS suite explainers say what the whole platform does, then show the modules one at a time. 84% name the whole platform before the first module. That's the Frame Line. Then 54% take the modules one by one. That's the Guided Tour. Fewer list them in one sentence or follow one workflow.
How many modules should a platform overview video show?
Four to six is the norm. That's the Short List. 81% of suite videos name four or more modules, and the typical SaaS suite explainer names 5. The videos carry no view data, so this shows what companies do, not what works. Put the rest on the page around the video.
Should a platform explainer use module product names or plain labels?
Mostly plain labels. That's Plain Labels. 83% of suite videos call more modules by their job, like payroll or real-time alerts, than by a product name. Product names fit when each module is sold and priced on its own. Just 9% of the videos name every module that way.
How long is a SaaS platform overview video?
The typical one runs 1:30, whatever the module count. That's Fixed Runtime. Adding modules doesn't make a longer video. 66% of videos with six or more modules still run two minutes or less. So each module gets fewer seconds instead.
When should the first module appear in a platform explainer?
After a short setup. That's the Setup Window. The typical suite video names its first module at 0:27. If your buyer lives the problem every day, skip most of the setup. Name a module in your first line, the way Veeqo's shipping video does.
How much time does each module get in a suite explainer?
Not the same time. That's the Hero Part. 70% of suite videos give one module at least three times the time of another. The typical module gets 9 seconds before the next one is named. Equal time fits only when the modules work as one, like layers of one system.
Should module names appear on screen in a platform explainer?
Most do. That's Screen Names. 63% of the 30 videos coded frame by frame show a module's name as on-screen text. 73% show a dashboard. None uses a grid of module icons. 30 is a small group, so read this as a hint.
How was this analysis done?
ADVIDS Research checked 945 product videos against a fixed rule. 120 qualified, from 99 companies. Each script was read and timed, and 30 videos were also coded frame by frame. Each of the eight findings is a simple count. They are Short List, Plain Labels, Frame Line, Guided Tour, Setup Window, Hero Part, Fixed Runtime and Screen Names.
How to read this report
This report looks at 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026. Each figure counts videos, like 97 of 120. Finding 8 looks at just 30 videos frame by frame, so read it as a hint.
Finding 01 · Short List
1. Most suite videos name four or more modules.
Most SaaS suite explainers don't stop at three modules. 81% name four or more (97 of 120). So you don't need to show everything. If your platform has more modules than one video can carry, pick four to six. Send the rest to the page around the video.
Think of a tasting menu. The kitchen can cook it all, but the menu shows five dishes. Your explainer is the tasting menu.
Four or five is the most common count, and the typical video names 5.
Example: AIMS360's apparel ERP video runs on music alone. At 0:13, its modules sit on one screen as chips: Inventory, Production, Reporting, Omnichannel Orders and Accounting.
Four or more modules: companies in this group include Zoho, Cadence, Genesys, Microsoft, etc.
Exception: three modules that close one loop. Atlassian's Product Collection video shows the Feedback app, Jira Product Discovery and Rovo, one job each. Sold as one loop, three products are the whole offer.
Source: Advids analysis of 120 SaaS suite videos
Three modules is the smallest group. Most videos show more.
Finding 02 · Plain Labels
2. Most videos call modules by their job, not their name.
Most suite videos don't lead with product names. They say what each module does, like payroll or real-time alerts. 83% use more of these plain labels than product names (99 of 120). If your buyer doesn't know your module names yet, call each one by its job.
Airport signs say Baggage, not the name of the belt system. Until your buyer buys, your module names are the belt system.
48% use no product name at all (58 of 120).
Example: Symantec's CBX video runs on music, with no voice. At 0:35, amplifier dials carry the labels Data Security and Network Security. It shows four features and zero product names.
Plain labels: companies in this group include Deel, IBM, Moveworks, Oracle, etc.
Exception: modules sold on their own. DataGrail's privacy video walks Live Data Map, Request Manager, Consent Management and Risk Monitor by name. When each module has its own price, its name is what a buyer asks for.
Source: Advids analysis of 120 SaaS suite videos
Finding 03 · Frame Line
3. Most videos say what the whole platform does first.
Most scripts open with the big-picture line: the sentence that says what the whole platform does. 84% say it before the first module (94 of 112 with a script). The rest name a module first and explain the whole later. If your buyer doesn't know your platform yet, start with the big picture.
People buy a puzzle for the picture on the lid. Your big-picture line is the lid.
Only the spoken script counts here. A logo on screen before anyone speaks is not the big-picture line.
Example: Asana's retail video opens on its logo at 0:02. The first module, a single portfolio, isn't named until 0:32.
Big picture first: companies in this group include Asana, Keka, Workday, Adverity, etc.
Exception: buyers who compare tools one by one. Airwallex's finance walkthrough opens on a global account at 0:35, then shows cards, spend tools and APIs. Only near the end does it say one product replaces them all.
Source: Advids analysis of 120 SaaS suite videos
Finding 04 · Guided Tour
4. Most videos show the modules one at a time.
After the big picture, most videos take the modules one at a time. 54% do it, giving each module a sentence or more (65 of 120). A quarter list them all in one sentence instead. Few follow one task or one user through the modules. If your modules serve different teams, show them one by one.
An estate agent shows a house room by room. A family shows you one evening in it. Your outline picks one of the two.
Just 15% follow one workflow (18 of 120). So most suite videos are a tour of the menu, not a story about one user.
Example: Contentstack's platform overview names its content system at 0:40. By 0:52, a text card hands over to the next product, and three more follow in turn.
One at a time: companies in this group include AIMS360, Appspace, Atlassian, Backbase, etc.
Exception: one shift that runs through every module. DTN's Weather Hub video follows a live event as storms build. Radar, alerts, lightning data and the mobile app arrive as the team needs them.
Source: Advids analysis of 120 SaaS suite videos
Just 18 of 120 follow one workflow through the modules.
Finding 05 · Setup Window
5. Most videos set up the problem before the first module.
Most suite videos don't open on a module. They set up the problem first. 73% wait at least 15 seconds before they name one (82 of 112 with a timed script). If your buyer needs the problem explained, give it that short window. Then name your first module.
A doctor asks where it hurts before naming the cure. Your setup is that question.
The typical first module arrives at 0:27. After that, the modules come fast.
Example: Doxis opens on document chaos. At 0:08, a company icon sits among scattered CSV, PDF and invoice files. The first module, pre-trained AI models, arrives at 0:58.
A setup first: companies in this group include Airwallex, Ataccama, Billtrust, BrowserStack, etc.
Exception: buyers who live the problem every day. Veeqo's shipping video names its rate shopping tool at 0:05, with no setup. Its buyers ship orders daily, so the problem needs no introduction.
Source: Advids analysis of 120 SaaS suite videos
Finding 06 · Hero Part
6. One module usually gets far more time than the rest.
Suite videos rarely split time evenly. 70% give one module at least three times the time of another (71 of 102 with enough timed modules). Time here means the seconds before the next module is named. If one module carries most of your deals, give it the time. Let the rest pass quickly.
Every album has a single that gets the radio play. Your hero module is the single.
The typical module gets just 9 seconds. So most scripts pick a hero module and pass quickly over the rest.
Example: ScienceLogic's Skylar Advisor video names its prioritized advisories at 0:39. It stays on them for 47 seconds. The chat feature gets 14.
Uneven time: companies in this group include Atlantic.Net, Bold Commerce, Cequence Security, ContractSafe, etc.
Exception: modules that only work together. Backbase's Banking OS video gives each layer 12 to 18 seconds. When the layers only work as one, no layer can be the star.
Source: Advids analysis of 120 SaaS suite videos
Finding 07 · Fixed Runtime
7. More modules don't make a longer video.
You might expect more modules to need more time. They don't. 66% of videos with six or more modules still run two minutes or less (27 of 41). Each module just gets fewer seconds. If your module list grows, keep the runtime and cut the seconds per module.
Pack more into a carry-on and the bag stays the same size. Your runtime is the carry-on.
Three-module videos typically run 1:44. Videos with six or more run 1:34.
Example: Cadence fits six design modules into 1:40. Its HDI overview names three editors by 0:32, and a via render is on screen at 0:36.
Six or more in two minutes: companies in this group include Campfire, Doxis, Dragos, DTN, etc.
Exception: an app every employee opens. Staffbase's employee app video takes 2:40 for 13 modules, from login to offline mode. When everyone uses the app daily, the long tour is the point.
Source: Advids analysis of 120 SaaS suite videos
Finding 08 · Screen Names
8. Most videos show module names on screen.
When the voiceover names a module, most videos show the name too. 63% of the videos coded frame by frame put a module's name on screen as text (19 of 30). That's a small group, so read it as a hint. If your voiceover names a module, put that name on screen as it plays.
Directions say turn left at Market Street, but you still look for the sign. Your voiceover is the directions, and the screen is the sign.
A dashboard view shows up in 22 of the 30. Fewer use moving text, and none uses a grid of module icons.
Example: Salesforce's Revenue Cloud demo speaks quotes, contracts and billing at 0:09. By 0:18, the screen shows those modules as chips joined by dashed lines.
Names on screen: companies in this group include Anthropic, Board, Contentstack, Crisp, etc.
Exception: a demo where the build is the show. Superblocks' 3.0 demo builds a CRM from one prompt while the voiceover names its agents. The modules are heard, and the product is watched.
Source: Advids analysis of 30 suite videos coded frame by frame
Modules show up as screens and cards, not as a grid of icons.
Benchmarks
Check your own suite video against these. Half the videos fall below each typical figure, and half above.
Parts, timing and runtime
| Measure | Typical | What it means |
|---|---|---|
| Modules named | 5 | Products, apps or features the script names |
| Runtime | 1:30 | Across all 120 videos |
| Runtime by module count | 1:44 · 1:24 · 1:34 | Three modules · four or five · six or more |
| Runtime per module | 19 seconds | Runtime divided by modules named |
| First module named | 0:27 | Time into the video |
| Time per module | 9 seconds | Until the next module is named |
| Longest module vs shortest | 5.5 to one | How much more time the lead module gets |
What most suite videos skip
| Pattern | Videos | Out of |
|---|---|---|
| A diagram of the whole platform | 13 | of 30 |
| Every module's name on screen | 8 | of 30 |
| One workflow through the modules | 18 | of 120 |
| A product name for every module | 11 | of 120 |
| A grid of module icons | 0 | of 30 |
None of these shows up in even half the videos. Not one shows a grid of module icons.
Eight questions for your next suite brief
Answer these eight in writing before anyone storyboards.
- Finding 01 How many modules can a buyer judge on their own? Name four to six, and put the rest on the page around the video.
- Finding 02 Does your buyer know your module names? If not, call each module by its job.
- Finding 03 Does your buyer know what the platform is? If not, write the one line that frames the whole first.
- Finding 04 Does one buyer's day run through every module? Yes: follow a single workflow. No: tour the modules one by one.
- Finding 05 Does your buyer live the problem every day? If not, name the first module by 0:27. If so, name it in your first line.
- Finding 06 Do the modules only work together? If not, pick the hero module in the brief, not in the edit.
- Finding 07 How many seconds does each module get? Divide the runtime by the modules, and budget for less time per module, not more runtime.
- Finding 08 Is the demo the build itself? If not, write each module's on-screen name beside the voiceover line.
Now go back to those module owners who each wanted a scene. They can all be in the video. Only one gets the time.
This week, list every module on one page. Circle the one your last ten deals mention most. That's your hero.
Every module in is the brief. One hero is the video.
Methodology
| Vertical (visual record only) | Videos |
|---|---|
| fintech | 5 |
| devtools | 3 |
| retail | 3 |
| enterprise | 2 |
| ai | 1 |
| customer_support | 1 |
| cybersecurity | 1 |
| document_mgmt | 1 |
| Other | 13 |
| Not recorded | 90 |
| Coding scheme | Values | Definition |
|---|---|---|
| Named part | proper name · plain label · service | Read from the transcript: a part of the offering a buyer could evaluate on its own, named with a proper name (Knowledge, Assist, Sales Hub) or a noun label (payroll, real-time alerts). Capabilities described only in verbs, steps, attributes, integrations and data types are not parts. A human service counts when the script sets it out as part of the offering. |
| Suite named first | yes · no | Whether the words that name or frame the suite as one offering come before the first part's name in the transcript. |
| Structure | suite then parts · parts as a list · one workflow · parts before the suite | One call per script: the suite framed, then parts taken one after another; parts named together in a sentence or two; a single task, user or scenario carrying the parts as steps; or parts developed before the suite is framed. |
| First part | timecode · share of runtime | When the first part is first spoken, located by its verbatim first-mention words in the transcript and timed from the word-timed caption track, or from the timed speech segments. |
| Airtime split | longest part ÷ shortest part | Each part's span runs from its first mention to the next part's first mention. The ratio compares the longest and shortest spans, leaving out the last part. |
| Runtime | seconds · parts per runtime | Read from the file; set against the number of named parts. |
| On screen | part name as text · dashboard · title card · kinetic type · diagram · icon grid | Only for the videos carrying the coded visual record: the segment motifs, and whether any segment's on-screen text carries a part's name. |
| Not coded | cast · surface · altitude · build | The skill's five dimensions are coded from frames, which only the visual-record rows carry; this report codes parts and order from scripts and does not code those dimensions for the whole set. |
Cite this report
Jai Ghosh, Advids. 120 Modular SaaS Explainers Decoded: How Top Brands Visually Present Complex Feature Suites. 14 September 2026. https://advids.co/blog/modular-saas-suite-explainer-videos-decoded
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.