A suite explainer here is a SaaS video that names at least three parts of one platform, checked by reading every script; top brands is the reader's test, because the library holds no ranking, revenue or audience data and no company here is ranked. Across 120 such explainers from 99 companies, uploaded between 23 March 2022 and 3 August 2026, 78 of them in 2026, 97 name four or more parts, 99 name more parts by plain label than by product name, 94 of 112 name the suite before its first part and 71 of 102 give one part at least three times the airtime of another. Zoho, Genesys, Microsoft and Workday are in the set; the scripts of all 120 answer how, and the pictures answer it for the 30 with a full visual record.
All 945 rows in the Advids video library were screened against a rule written before screening, and 120 qualified from 99 companies. Every one is a platform overview, explainer, launch or demo video for B2B software that names at least three distinct parts of one platform in its script, runs 0:30 to 3:37, and was uploaded to YouTube between 23 March 2022 and 3 August 2026. In this report a suite explainer is one such video, a part is one named module, product, app, agent or capability, and a company is the software company that published it.
ADVIDS Research · 120 SaaS suite explainers · 99 companies · 616 named parts, 578 timed · 30 with a coded visual record · published 14 September 2026 · 19 min read
Top takeaways
97 of 120 suite explainers name four or more parts
97 of 120 SaaS suite explainers uploaded between 23 March 2022 and 3 August 2026 name four or more parts, a median of 5; the 23 that name exactly three include Asana, Atlassian, Crisp, CyberArk, etc.
99 of 120 explainers name parts by label, not product name
99 of 120 SaaS suite explainers name more parts by plain label, such as payroll or real-time alerts, than by product name; the 11 that give every part a product name include Anthropic, Asana, Atlassian, Board, etc.
94 of 112 name the suite before its first part
94 of 112 SaaS suite explainers with a transcript name or frame the suite before the first part; the 18 that name parts first include Zoho, Airwallex, Atlantic.Net, Deel, etc.
65 of 120 frame the suite, then take parts one by one
65 of 120 SaaS suite explainers frame the suite and then take the parts one by one, against 30 that list the parts in a sentence and 18 that thread one workflow through them; DTN runs one event night through its Weather Hub.
82 of 112 hold the first part until 0:15 or later
In 82 of 112 timed SaaS suite explainers the first part is named at 0:15 or later, a median of 0:27, 27 per cent of runtime; Veeqo names its rate shopping tool at 0:05.
71 of 102 give one part three times another's airtime
71 of 102 SaaS suite explainers give one part at least three times the airtime of another, counting from one part's first mention to the next; Backbase splits its six layers at a ratio of 1.5.
27 of 41 six-plus-part explainers run two minutes or less
27 of 41 SaaS suite explainers naming six or more parts run 2:00 or less, and runtime barely tracks part count (correlation 0.17); Staffbase takes 2:40 for 13 parts.
19 of 30 coded explainers put a part's name on screen
In 19 of 30 SaaS suite explainers with a coded visual record, at least one part's name is on screen as text; icon grids appear in 0 of 30 and a title card for every part in 2.
Questions this report answers
How do SaaS companies present a suite of products in one explainer video?
Across 120 SaaS suite explainers from 99 companies, 94 of 112 name the suite before its first part and 65 of 120 then take the parts one by one. 30 name the parts in a single list and 18 thread one workflow through them.
How many modules should a platform overview video show?
The median SaaS suite explainer in this set of 120 names 5 parts, and the middle half names 4 to 6. The files carry no view data, so the count shows what the set does, not what works.
How long is a SaaS platform overview video?
The median SaaS suite explainer in this set of 120 runs 1:30, and more parts do not mean a longer video: explainers naming three parts run a median 1:44, four or five parts 1:24 and six or more 1:34.
How much time does each module get in a suite explainer?
Airtime is uneven: in 71 of 102 SaaS suite explainers one part gets at least three times the airtime of another, measured from each part's first spoken mention to the next. The median part gets 9 seconds.
Should module names appear on screen in a platform explainer?
Most with a coded visual record do: 19 of 30 show at least one part's name as on-screen text and 8 show every part's name. A dashboard appears in 22 of 30, a diagram in 13 and an icon grid in none.
How was this analysis done?
ADVIDS Research read the transcripts and on-screen text of 654 videos against a rule written before screening, and 120 SaaS suite explainers from 99 companies qualified. Part names, structure and airtime come from the scripts; the visual chapter rests on the 30 with coded frames.
How to read this report
The set is 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026; each names at least three parts of one platform, read from its script.
A figure such as 97 of 120 means 97 of the 120 videos carry the pattern. The base is all 120 unless the line names a smaller one: the 112 counted from a transcript, the 112 with three or more timed parts, the 102 with two or more timed parts before the last, or the 30 with a coded visual record.
A headline holds for at least half its base and at least 8 videos. Airtime is spoken time, from one part's first mention to the next.
Finding 01 · Parts named · base: 120 suite explainers
1. 97 of 120 suite explainers name four or more parts
97 of 120 SaaS suite explainers uploaded between 23 March 2022 and 3 August 2026 name four or more distinct parts of one platform in the script, and the median names 5. 56 name four or five, 41 name six or more and 23 name exactly three; the most parts in one script is 13. Across the set that is 616 named parts. AIMS360 sets six apparel ERP modules on screen as chips. A suite explainer names more parts than it needs to qualify.
Companies in this group include Zoho, Cadence, Genesys, Microsoft, etc.
Atlassian names three and stops. Its May 2026 Product Collection video runs 1:49 and introduces the Feedback app, Jira Product Discovery and Rovo, one job each: capture feedback, build the roadmap, rework it. Where a collection is sold as one decision loop, three products are the whole loop.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
Three parts, the floor of the rule, is the smallest group; a suite explainer names more parts than the minimum.
Finding 02 · How parts are named · base: 120 suite explainers
2. 99 of 120 explainers name parts by label, not product name
99 of 120 SaaS suite explainers uploaded between 23 March 2022 and 3 August 2026 name more of their parts with a plain label, such as payroll, real-time alerts or configurable dashboards, than with a product name. Of the 616 parts named across the set, 480 are labels and 136 are product names; 58 explainers use no product name at all, and 11 name every part with one. 11 parts are human services set out as part of the offering. Symantec labels its CBX dials data security and network security. The function is the name the buyer hears.
Companies in this group include Deel, IBM, Moveworks, Oracle, etc.
DataGrail names every part as a product. Its June 2024 explainer runs 1:10 and walks Live Data Map, Request Manager, Consent Management and Risk Monitor, each named once with the job it does. Where each part is sold and priced on its own, the product name is what a buyer asks for.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
Finding 03 · Order · base: 112 with a transcript
3. 94 of 112 name the suite before its first part
94 of 112 SaaS suite explainers with a transcript, uploaded between 23 March 2022 and 3 August 2026, name or frame the suite as one offering before the first part is named. The other 18 name a part first and frame the whole later, often in the last lines. The order is read from word position in the transcript, so a logo on screen before the script starts does not count. Asana opens its retail video on the Asana logo. The whole comes first, then the pieces.
Companies in this group include Asana, Keka, Workday, Adverity, etc.
Airwallex names five parts before it names the whole. Its March 2026 walkthrough runs 2:16: it opens a global account at 0:35, then shows local payment methods, multicurrency cards, Airwallex Spend and platform APIs, and only near the end says it replaces everything with one product. Where the buyer is a finance lead comparing tools, each tool is proven before the bundle is claimed.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
Finding 04 · Structure · base: 120 suite explainers
4. 65 of 120 frame the suite, then take parts one by one
65 of 120 SaaS suite explainers uploaded between 23 March 2022 and 3 August 2026 frame the suite first and then take its parts one after another, each with a sentence or more of its own. 30 name the parts together in one or two sentences, 18 thread one task, user or scenario through the parts, and 7 develop the parts before framing the suite. The suite-then-parts scripts run a median 1:41, the lists 1:06 and the single workflows 2:02. Contentstack moves between its products on type and title cards. Most suite explainers are a tour of the menu, not a story about one user.
Companies in this group include AIMS360, Appspace, Atlassian, Backbase, etc.
DTN runs one event night through its Weather Hub. Its February 2026 video runs 1:45: storms build over a live show, and radar, real-time alerts, lightning intelligence, dashboards, the mobile app and a chat with meteorologists arrive as the team needs them, 7 parts in all. Where the buyer runs one high-stakes shift, the shift is the order.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
A single scenario carrying the parts is the smaller choice here: 18 of 120.
Finding 05 · First part · base: 112 with three or more timed parts
5. 82 of 112 hold the first part until 0:15 or later
In 82 of 112 SaaS suite explainers with three or more timed parts, uploaded between 23 March 2022 and 3 August 2026, the first part is spoken at 0:15 or later. The median first part arrives at 0:27, 27 per cent of the way through the video, and the median last part at 73 per cent; 90 of 112 name their last part at 60 per cent of runtime or later. Times come from the word-timed caption track for 60 parts and from timed speech segments for 517. Doxis opens on a scatter of document icons before it names a part. The parts are packed into the middle of the video.
Companies in this group include Airwallex, Ataccama, Billtrust, BrowserStack, etc.
Veeqo names its first tool in the first sentence. Its September 2024 video runs 1:22 and names the rate shopping tool at 0:05, with no problem set up first, then bulk ship, smart order routing and digital picking software. Where the buyer already ships orders every day, the problem needs no introduction.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
Finding 06 · Airtime · base: 102 with two or more timed parts before the last
6. 71 of 102 give one part three times another's airtime
71 of 102 SaaS suite explainers with at least two timed parts before the last, uploaded between 23 March 2022 and 3 August 2026, give their longest part at least three times the spoken airtime of their shortest. The median ratio is 5.5 to one, and the median part gets 9 seconds between its first mention and the next part's. The longest span falls on the first part in 33 of 102, so the lead part is not always the one that gets the time. ScienceLogic gives Prioritized advisories 47 seconds and Ask Skylar Advisor chat 14. The script picks a hero part and passes over the rest.
Companies in this group include Atlantic.Net, Bold Commerce, Cequence Security, ContractSafe, etc.
Backbase gives its six layers close to equal time. Its April 2026 Banking OS launch runs 3:03 and spends between 12 and 18 seconds on each of the layers before the last, a ratio of 1.5. Where the claim is that the layers only work together, no layer can be the star.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
Finding 07 · Runtime · base: 41 naming six or more parts
7. 27 of 41 six-plus-part explainers run two minutes or less
27 of 41 SaaS suite explainers naming six or more parts, uploaded between 23 March 2022 and 3 August 2026, run 2:00 or less. Runtime barely tracks part count: explainers naming three parts run a median 1:44, four or five parts 1:24 and six or more 1:34, a correlation of 0.17 across the 120. Instead the time per part shrinks, to a median 19 seconds of runtime per part, and 64 of 120 give each part under 20 seconds. Cadence covers six HDI design parts in 1:40. Adding a module cuts its share of the video; it does not buy more video.
Companies in this group include Campfire, Doxis, Dragos, DTN, etc.
Staffbase takes 2:40 for 13 parts. Its March 2026 employee app video walks login, homepages, podcast summaries, Shorts, hubs, tasks, forms, a chatbot, search, communities, the directory, push notifications and offline mode in turn. Where the product is an app every employee opens, the tour is the explainer.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
Finding 08 · On screen · base: 30 with a coded visual record
8. 19 of 30 coded explainers put a part's name on screen
In 19 of the 30 SaaS suite explainers carrying a coded visual record, uploaded between 23 March 2022 and 3 August 2026, at least one part's name appears on screen as text; in 8 every part's name does. A dashboard appears in 22 of 30, a title card in 22, kinetic type in 15, a diagram in 13 and an icon grid in 0; a dashboard for every part in 11 and kinetic type carrying a part name in 3. This base is 30 videos, so each figure is directional. 10 of the 30 carry medium-confidence build codes. Salesforce sets Contracts and Billing on screen among its revenue module chips. Names reach the screen; an icon grid of modules does not, in any of the set.
Companies in this group include Anthropic, Board, Contentstack, Crisp, etc.
Superblocks names no part on screen. Its August 2026 Superblocks 3.0 demo runs 2:25 across 13 dashboard segments, building a CRM from one prompt while the voiceover names the security agents, build agent and agent orchestration. Where the demo is the build itself, the parts are heard and the product is watched.
Source: ADVIDS Research coded set, 120 SaaS suite explainers from 99 companies, uploaded 23 March 2022 to 3 August 2026
The suite is shown through its screens and cards, not drawn as a map of tiles.
Benchmarks
Descriptive figures for placing your own suite explainer against the set.
Parts, timing and runtime
| Measure | Value | What it means |
|---|---|---|
| Named parts, median | 5 | Half the suite explainers name fewer parts than this |
| Named parts, middle half | 4 to 6 | The span of the middle 50 per cent of videos |
| Runtime, median | 1:30 | Across all 120 |
| Runtime by part count, median | 1:44 · 1:24 · 1:34 | Three parts · four or five · six or more |
| Runtime per part, median | 19 seconds | Runtime divided by named parts |
| First part named, median | 0:27 (27 per cent of runtime) | Among the 112 with three or more timed parts |
| Last part named, median | 73 per cent of runtime | Among the 112 with three or more timed parts |
| Airtime per part, median | 9 seconds | From one part's first mention to the next |
| Longest to shortest part, median | 5.5 to one | Among the 102 with two or more timed parts before the last |
What most suite explainers skip
| Coded value | Videos | Base |
|---|---|---|
| A diagram on screen | 13 | of 30 |
| Every part's name on screen | 8 | of 30 |
| One workflow through the parts | 18 | of 120 |
| Every part with a product name | 11 | of 120 |
| An icon grid | 0 | of 30 |
None of these reaches half its base, so none is a finding. A single workflow carries 18 of 120 scripts, and an icon grid appears in 0 of the 30 with a visual record.
What to do with this
- Finding 01 If 97 of 120 SaaS suite explainers name four or more parts, decide which modules the script names before the storyboard starts, and name the rest on the page around the video.
- Finding 02 If 99 of 120 name parts by plain label, test whether your buyer knows your module names before building the script around them.
- Finding 03 If 94 of 112 name the suite before the first part, write the one line that frames the whole before writing any module line.
- Finding 04 If 65 of 120 frame the suite and then tour the parts, choose that outline or a single workflow deliberately; only 18 of 120 chose one workflow.
- Finding 05 If the median first part arrives at 0:27, time your setup against that and cut problem lines that delay the first module.
- Finding 06 If 71 of 102 give one part three times another's airtime, pick the hero module in the brief rather than in the edit.
- Finding 07 If 27 of 41 naming six or more parts still run 2:00 or less, budget for less time per module rather than more runtime.
- Finding 08 If 19 of 30 put a part's name on screen, write the on-screen module names into the script alongside the voiceover.
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.
Image credits and licensing
Video frames on this page are reproduced for analysis and commentary. Copyright in each frame remains with the company credited in its caption; to license a frame, contact that rights holder. Advids grants no rights over them.
Charts and images credited ADVIDS Research, and the coded dataset behind them, are © 2026 Advids and licensed CC BY 4.0: reuse them with attribution to Advids and a link to this page.