A data unification video, as coded here, is a B2B product video whose script says the product joins data, systems or work from at least two named sources, tools or departments. 89 qualified among 945 screened, from 83 companies including Oracle, Salesforce, Slack and Workday, uploaded 23 March 2022 to 26 June 2026. 73 of 89 name the systems they join and 64 name no department. 69 run past one minute, with a median of 1:27, yet 78 state the unification claim inside the first minute, and 57 name the product before it. On the 15 with a full visual record, 11 show a dashboard. Departmental harmony and the 60 seconds are the reader's tests: the files record what a script names and when, not how teams work together.
945 product videos were screened against a rule and a lexicon written before intake; 312 transcripts used a joining term, every one was read, and 89 qualified, from 83 companies.
ADVIDS Research · 89 data unification videos coded · 83 companies · 15 with a full visual record · 135 sampled frames · published 14 September 2026 · 18 min read
Top takeaways
69 of 89 run past a minute; the claim lands inside it
78 of 89 data unification videos uploaded 23 March 2022 to 26 June 2026 state the unification claim inside the first minute, at a median 0:24, though 69 run past a minute and the median runs 1:27; Zoho, Salesforce and Orange Business hold the claim past 1:00.
73 of 89 unification scripts name the systems they join
73 of 89 data unification scripts from 23 March 2022 to 26 June 2026 name a system or data category they join, a CRM in 10 and email in 9; 69 name three or more sources, as Umbraco, Odoo and Backbase do.
Nearly two in three name the product before claiming the join
57 of 89 data unification scripts name the product before claiming the join, at a median 0:15 against 0:24 for the claim; 9 state the claim first, among them Slack, Neo4j and Backbase.
Seven in ten unification scripts name no department
64 of 89 data unification scripts uploaded 23 March 2022 to 26 June 2026 name no department; 25 do, HR in 6 and IT in 5, as Freshworks, UKG and Microsoft do.
In the visual record, dashboards and diagrams carry the join
On the 15 data unification videos with a full visual record, 11 show a dashboard and 10 a network diagram or flowchart, as Salesforce, Neo4j and Relativity do; a logo grid appears in 1.
Flow and hub words run through the scripts; single view trails
Flow language runs through 51 of 89 data unification scripts and hub language through 45, while single-view language appears in 25; in the claim sentence hub language leads at 25, as in Odoo, Workday and Klaviyo.
Questions this report answers
What is a data unification video?
A B2B product video whose script says the product joins data, systems or work from at least two named sources, tools or departments. ADVIDS Research found 89 among 945 screened product videos, from 83 companies including Oracle, Salesforce, Slack and Workday, uploaded 23 March 2022 to 26 June 2026.
How long is a data unification explainer video?
69 of 89 run past one minute and the median runs 1:27; the middle half runs 1:02 to 2:08, and 20 run a minute or less. The unification claim still lands inside the first minute in 78 of 89, at a median 0:24; Zoho holds it until 1:48.
Which systems do data unification videos name?
73 of 89 scripts name a system or data category they join: CRM in 10, email in 9, ERP in 7 and inventory in 5. 24 name products such as Salesforce, Slack and Workday, and 69 name three or more sources.
Do data unification videos name departments?
Seven in ten do not: 64 of 89 scripts name no department or business function. HR appears in 6, IT in 5 and sales in 4, and Freshworks names five.
When should a product video state the unification claim?
57 of 89 scripts name the product first, at a median 0:15, and state the claim at 0:24. 23 make the claim in the naming sentence and 9 before it, as Slack and Neo4j do.
How do data unification videos show the join on screen?
On the 15 with a full visual record, 11 show a dashboard and 10 a network diagram or flowchart, and 9 have one of those, a data chart or a logo grid on screen while the claim is spoken. The base is 15 videos, so the counts are directional.
How was this analysis done?
ADVIDS Research screened 945 product videos against a rule and a lexicon written before intake; 312 transcripts used a joining term, each was read, and 89 qualified from 83 companies. Timing came from captions and speech segments, and the coded dataset ships with the report.
How to read this report
This report catalogues 89 B2B product videos from 83 companies, uploaded to YouTube 23 March 2022 to 26 June 2026, whose scripts say the product joins data, systems or work from at least two named sources, tools or departments. A figure such as 73 of 89 counts videos against a base. Script, runtime and framing findings stand on all 89; the on-screen findings stand on the 15 with a full visual record, so they are written as counts and read as directional. There are no periods, so nothing here describes change over time.
Finding 01 · Runtime · Runtime and the first minute · 89 data unification videos, 23 March 2022 to 26 June 2026
1. 69 of 89 run past a minute; the claim lands inside it
69 of 89 data unification videos uploaded between 23 March 2022 and 26 June 2026 run past one minute; the median runs 1:27, the middle half 1:02 to 2:08, and the shortest 0:30. 20 run a minute or less. The unification claim lands at a median 0:24 and inside the first minute in 78 of 89, including 58 of the 69 longer videos. Among videos of a minute or less, 19 of 20 state it by 0:30; among the longer ones, 34 of 69, a gap of 45.7 points. The 60 seconds describe where the claim sits, not how long the video runs.
Runtime past 1:00 (69 of 89): companies in this group include Genesys, Deel, Microsoft, Workday, etc. Without Genesys, the company with the most videos in the set, the runtime share moves 1.1 points; without Genesys, the claim share moves 0.6.
Zoho goes the other way. Its August 2025 Zoho Contracts launch runs 2:21 and holds the unification line until 1:48, when the script says its CRM integration can "break down silos between legal and sales". Where the join is one feature of a contract product, it arrives after the product has been shown.
Source: ADVIDS Research coded set, 89 videos from 83 companies, uploaded 23 March 2022 to 26 June 2026
Among the 69 that run past a minute, 58 still state the claim inside it.
Finding 02 · Script · Named sources · 89 data unification videos, 23 March 2022 to 26 June 2026
2. 73 of 89 unification scripts name the systems they join
73 of 89 data unification videos uploaded 23 March 2022 to 26 June 2026 name a system or data category the product joins, such as a CRM, an ERP, email, inventory or a data warehouse. 24 name a product by name and 25 name a department or business function. 69 of 89 name three or more sources, tools or departments, and the median script names 3. Across the set the scripts name 162 distinct systems or data categories, 46 products and 31 departments or functions; CRM appears in 10 scripts, email in 9, ERP in 7 and inventory in 5. The join is sold as systems a buyer already owns, named one by one.
Names a system or data category (73 of 89): companies in this group include Airwallex, Amdocs, Amplience, Appspace, etc. Without Genesys, the share moves 0.3 points.
Arena goes the other way. Its December 2024 supply-chain spot runs 0:58 and names no system or product: it joins supply chain, engineering, product teams and manufacturing partners in "a single source of truth for your internal teams and external partners". Where the problem sits with people outside the company, the script names teams, not software.
Source: ADVIDS Research coded set, 89 videos from 83 companies, uploaded 23 March 2022 to 26 June 2026
The median script names 3 sources; 39 name four or more and 9 six or more.
Finding 03 · Script · Script order · 89 data unification videos, 23 March 2022 to 26 June 2026
3. Nearly two in three name the product before claiming the join
57 of 89 data unification scripts uploaded 23 March 2022 to 26 June 2026 name the product before they say it joins sources; 23 make the claim in the sentence that names the product, and 9 state it before the name. The product is named at a median 0:15, 18 per cent of the way into the words, and the claim lands at 0:24, 37 per cent in. In the name-first scripts the product arrives at 0:14 and the claim at 0:32. 53 of 89 state the claim by 0:30 and 32 inside the first quarter of their words. The name comes first, and the join explains it.
Product named before the unification claim (57 of 89): companies in this group include Atlassian, Aviso, Cequence Security, Contentstack, etc. Without Deel, one of three companies tied for the most videos in the pattern, the share moves 0.8 points.
Slack goes the other way. Its March 2026 work OS explainer runs 1:04, says at 0:21 that apps, people, projects and knowledge are "connected in one central hub", and names Slack only at 0:51, in its closing ask. Where the script explains a category, the join is the lesson and the product is the answer.
Source: ADVIDS Research coded set, 89 videos from 83 companies, uploaded 23 March 2022 to 26 June 2026
When the name comes first, the claim follows a median 0:16 later.
Finding 04 · Script · Departments · 89 data unification videos, 23 March 2022 to 26 June 2026
4. Seven in ten unification scripts name no department
64 of 89 data unification scripts uploaded 23 March 2022 to 26 June 2026 name no department or business function among the sources they join; 25 name one or more and 21 name two or more. Departments are named 57 times across the set, against 213 systems or data categories and 56 products. HR appears in 6 scripts, IT in 5 and sales in 4, and 31 distinct departments or functions are named in all; 5 scripts name departments and nothing else. Departmental harmony is the reader's test: the scripts name systems, and the files record nothing about how teams work together.
Names no department or business function (64 of 89): companies in this group include Ataccama, Billtrust, ChartHop, CoSupport AI, etc. Without Genesys, the share moves 0.1 points.
Freshworks goes the other way. Its January 2026 Freshservice for Business Teams launch runs 2:05, names five departments, HR, finance, facilities, legal and IT, beside Slack and Microsoft Teams, and says "we unify people, processes, and platforms into one connected ecosystem". Where the product takes every team's requests, the departments are the sources.
Source: ADVIDS Research coded set, 89 videos from 83 companies, uploaded 23 March 2022 to 26 June 2026
HR appears in 6 scripts, IT in 5 and sales in 4.
Finding 05 · Screen · On screen · 15 of the 89 with a full visual record
5. In the visual record, dashboards and diagrams carry the join
Only 15 of the 89 data unification videos carry a full visual record, so every figure here is a count of 15. 11 show a dashboard interface and 10 a network diagram or flowchart, 7 of them a network diagram; 9 show both. From two seconds before the spoken claim to eight seconds after it, 9 have a dashboard, diagram, chart or logo grid on screen: a dashboard in 6, a diagram in 3. Data charts appear in 4, a logo or tool-icon grid in 1, and unification words in on-screen text in 4. On screen, the join is drawn as connections or shown as one interface.
Dashboard interface on screen (11 of 15): companies in this group include HPE, Orange Business, Relativity, Salesforce, etc. Without Amplience, the at-the-claim share moves 2.9 points.
Nooks goes the other way. Its April 2026 AI Sequencing launch runs 0:55 with a presenter on camera, an alert and an abstract orb, and none of the five: the line "Nooks consolidates everything into one unified workspace" is spoken, not drawn. Where a presenter carries the launch, the join stays in the voice.
Source: ADVIDS Research coded set, 89 videos from 83 companies, uploaded 23 March 2022 to 26 June 2026
While the claim is spoken, 9 of 15 have one of the five on screen, a dashboard in 6.
Finding 06 · Script · Framing · 89 data unification videos, 23 March 2022 to 26 June 2026
6. Flow and hub words run through the scripts; single view trails
51 of 89 data unification scripts uploaded 23 March 2022 to 26 June 2026 use flow language somewhere, such as sync, pipeline, real time or orchestrate, and 45 use hub language, such as one platform, one place or central. Silos-to-connected language appears in 32 and single-view language, a single source of truth or a 360 view, in 25; 71 use flow or hub language and 10 use none of the four. In the claim sentence, hub language appears in 25, flow in 12, silos to connected in 7 and single view in 4, and 44 of 89 claim sentences use none. The claim names a place; the rest of the script describes movement.
Flow language in the script (51 of 89): companies in this group include Arena, Backbase, Cubewise, DTN, etc. Without Deel, the hub share moves 1.1 points; without Genesys, the flow share moves 0.8.
Elastic goes the other way. Its April 2026 Elastic Security launch runs 1:30 and uses none of the four framings: the script says the product unifies SIEM and XDR with automated response and names no hub, view, silo or flow. Where the buyer knows the categories, the category names carry the join.
Source: ADVIDS Research coded set, 89 videos from 83 companies, uploaded 23 March 2022 to 26 June 2026
In the claim sentence itself, hub language leads at 25; 44 claim sentences carry none of the four.
Benchmarks by length
Descriptive medians for placing your own script against each length. The group of a minute or less holds 20 videos, so its medians describe a small group.
Timing, names and frames
| Measure | A minute or less (20) | Past a minute (69) | All (89) | What it means |
|---|---|---|---|---|
| Runtime, median | 0:51 | 1:45 | 1:27 | Half the videos in the group run shorter than this |
| Words, median | 97 | 216 | 172 | Words in the transcript |
| Words a minute, median | 132 | 123 | 125 | Words over runtime |
| Product named at, median | 0:08 | 0:17 | 0:15 | Time into the video |
| Claim stated at, median | 0:16 | 0:31 | 0:24 | Time into the video |
| Product position, median per cent of words | 16 | 18 | 18 | Share of the script before the product sentence |
| Claim position, median per cent of words | 37 | 36 | 37 | Share of the script before the claim sentence |
| Named sources, median | 3 | 3 | 3 | Distinct sources, tools or departments named as joined |
| Sentences with a joining term, median per cent | 25 | 17 | 18 | Share of sentences carrying a joining term from the lexicon |
| Frame brightness, median | 169 | 169 | 169 | Mean luminance over nine sampled frames, 0 to 255 |
What the set rarely uses
| Pattern | Videos | Companies |
|---|---|---|
| Unification claim after the first minute | 11 of 89 | Airwallex, Contentstack, Deel, IFS, etc. |
| Claim before the product is named | 9 of 89 | Ataccama, Backbase, Billtrust, Daktela, etc. |
| Claim sentence with silos-to-connected language | 7 of 89 | Amplience, Arena, Backbase, Nooks, etc. |
| Logo grid on screen (visual record) | 1 of 15 | Relativity |
| Claim sentence with single-view language | 4 of 89 | Hightouch, Neo4j, PagerDuty and Tesorio |
A single source of truth and a 360 view are the phrases a brief reaches for first, yet single-view language sits in 4 claim sentences and silos-to-connected language in 7. On the 15 visual-record videos, a wall of partner or tool logos appears in 1, and the logo-grid code reads segment text, so it can also catch a cluster of tool icons that is not a partner wall at all.
What to do with this
- Finding 01 If 78 of 89 state the claim inside the first minute while 69 run longer, script the unification line for the first minute whatever the final length.
- Finding 02 If 73 of 89 scripts name the systems they join, list the buyer's own systems, such as the CRM, ERP or email, in the brief instead of all your data.
- Finding 03 If 57 of 89 name the product before the claim, test a first line that names the product and a second that says what it joins.
- Finding 04 If 64 of 89 name no department, decide whether your buyer thinks in teams before writing departmental lines; 25 scripts in this set did.
- Finding 05 If 11 of the 15 visual-record videos show a dashboard, have one presentable interface ready and treat the diagram as the second picture.
- Finding 06 If flow language appears in 51 of 89 scripts and hub language in 45, choose one place word for the claim and let the flow words describe the product at work.
Methodology
| Vertical (visual record only) | Videos |
|---|---|
| not recorded | 74 |
| sales | 2 |
| retail | 2 |
| fintech | 2 |
| restaurants | 1 |
| hr | 1 |
| legal-tech | 1 |
| itsm | 1 |
| other verticals | 5 |
| Coding scheme | Values | Definition |
|---|---|---|
| Inclusion | two or more named sources joined by the product | Coded by reading the transcript against the rule. A lexicon of joining terms found candidates; a recorded call decided each. |
| Named source | department or business function · system or data category · named product | Every source, tool or department the script says the product joins, anywhere in the script, written as a short name by the reader. |
| Claim sentence and product sentence | sentence index · word position · seconds | The first sentence saying the product joins sources, and the first naming the product or company. Position is the first word's index over all words; seconds come from word-timed captions where they exist and from interpolation inside timed speech segments otherwise. |
| Order | before · with · after the name | Before when the claim sentence precedes the product sentence, with when they are the same sentence, after otherwise. |
| Framing | hub · single view · silos to connected · flow · none | Fixed word lists matched in the claim sentence and anywhere in the script; a sentence can carry more than one. |
| On screen | dashboard · network diagram · flowchart · data chart · logo grid | Coded from timed segment motifs and segment text on visual-record videos only: anywhere in the video, and from two seconds before the spoken claim to eight seconds after it. A logo grid is an icon-grid motif or segment text naming logos or app, tool or integration icons. |
| Runtime and sound | runtime · voiceover · light, mixed or dark frames | Runtime from metadata; voiceover from audio analysis; light, mixed or dark computed over nine sampled frames, not the interface alone. |
| Not coded | cast · altitude · surface · build | Who appears and what the video argues are not recorded in the library. Surface and build exist only for the visual-record videos, so they are not coded for the set. |
Cite this report
Jai Ghosh, Advids. 89 Data Unification Videos Decoded: How Enterprise Systems Visually Explain Departmental Harmony in 60 Seconds. 14 September 2026. https://advids.co/blog/data-unification-video-explainers
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.
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.