Picture the brief for your next productivity video. A stressed team. Sticky notes on a wall. A spreadsheet nobody can read. Now look at 118 real ones. That picture almost never makes the cut. The mess arrives as a spoken line instead, at a typical 0:07. Follow the brief, and you pay for the one picture these videos skip.
A chaos-to-clean video is a B2B product video that names a messy way of working, then offers the product as the fix. The mess can be manual work, spreadsheets, silos, overload, errors or busywork. ADVIDS Research studied 118 of them, from Atlassian, Plaid, SAP, Zoho and others. The title's four visual frameworks come from the 31 coded frame by frame. Whether a video proves productivity is yours to test.
Seven findings stand out. The mess comes before the product (Mess First). It gets one short paragraph (Problem Budget). Disconnected tools are the top mess (Silo Line). The mess is written or drawn on screen (Drawn Mess). The product's own screen shows the fix (Clean Screen). Every video has a voiceover (Voice Track). And the mess often comes back after the product (Callback Line).
ADVIDS Research · 118 chaos-to-clean videos · 108 companies · 31 coded frame by frame · published 14 September 2026 · 20 min read
Top takeaways
Mess First
84% of chaos-to-clean B2B product videos name the mess before the product.
Problem Budget
66% of these B2B scripts spend a tenth of their words or more on the mess before the product.
Silo Line
53% of scripts name silos or disconnected tools, while spreadsheets show up in just 19.
Drawn Mess
61% of the 31 coded frame by frame show animated text, a flowchart or diagram or a drawing before the product's name.
Clean Screen
74% of the 31 coded frame by frame show the product interface after its name.
Voice Track
All 118 videos have a voiceover, and the typical one runs 1:25.
Callback Line
54% of scripts name the mess again after the product's name.
Questions this report answers
What is a chaos-to-clean B2B video?
A B2B product video that names a messy way of working, then offers the product as the fix. The mess might be manual work, spreadsheets or silos. ADVIDS Research studied 118 of them from 108 companies, including Atlassian, Plaid, SAP and Zoho. Seven findings stand out, from Mess First to Callback Line.
Should a B2B product video show the problem before the product?
Yes, if the problem is your buyer's own. That's Mess First. 84% of chaos-to-clean videos name the mess before the product, at a typical 0:07. The name follows at 0:17. Zendesk is one of the few that name the product first, because the mess it shows belongs to rivals.
How much of an explainer script should cover the problem?
One short paragraph. That's the Problem Budget. 66% of chaos-to-clean scripts spend a tenth of their words or more between the mess and the product. The typical mess-first script spends 19%, or about 33 words. Go longer only when the mess is the joke, as in Paycom's spot.
What problems do B2B software videos show?
Disconnected tools, mostly. That's the Silo Line. 53% of chaos-to-clean scripts name silos or disconnected tools. Overload and repetitive busywork come next. Spreadsheets, inboxes or sticky notes show up in just 19 of 118. Most scripts name two or more kinds of mess.
How do B2B videos show a messy workflow on screen?
They write it or draw it. That's the Drawn Mess. Of the 31 videos coded frame by frame, 61% show animated text, a diagram or a drawing before the product's name. Stock office shots show up in just 6. After the name comes the Clean Screen: the product interface.
Do chaos-to-clean videos use a voiceover?
Yes, all 118 do. That's the Voice Track. Part of that is by design, since only videos with a spoken script were counted. The typical video runs 1:25 and speaks 164 words, at 126 words a minute. Most use bright or mixed screens.
How was this analysis done?
ADVIDS Research screened 945 product videos against a rule written before the work began. 118 qualified, from 108 companies. Each script was read and timed, and 31 were coded frame by frame. The seven findings, Mess First, Problem Budget, Silo Line, Drawn Mess, Clean Screen, Voice Track and Callback Line, are simple counts. The full dataset comes with the report.
How to read this report
This report looks at 118 chaos-to-clean videos from 108 companies, uploaded 2 June 2023 to 14 July 2026. Each figure counts videos, and the visual frameworks use the 31 coded frame by frame. Mess first, then product, is the order sales teams call problem-solution selling.
Finding 01 · Mess First
1. Most scripts name the mess before the product.
Most chaos-to-clean scripts start with your buyer's problem, not your product. 84% name the mess before the product's name (99 of 118). The mess comes at a typical 0:07. The name follows at 0:17. A buyer has to see their own bad week first. Then your product reads as the answer.
Nobody reads the label on a box of painkillers until something hurts. Your product's name is the label. The mess is the headache.
Most get there fast: 72 of 118 name the mess in the first 10 seconds. The product is sold as an answer. So the question goes first.
Example: Plaid's video for mortgage lenders names the mess at 0:12: sorting through all that data takes forever. On screen, a checklist of pay stubs, tax returns and bank statements is tagged INCOMPLETE. Plaid's name comes at 0:28.
Mess first: companies in this group include Genesys, HPE, IBM, Plaid, etc.
Exception: the mess belongs to a rival. Zendesk's AI agents video names the product in its first line. Only at 0:55 does it say other vendors' agents "leave you tangled in endless configurations".
Source: Advids analysis of 118 chaos-to-clean videos
When the mess comes first, the product's name typically follows 0:14 later.
Finding 02 · Problem Budget
2. Most scripts give the mess one short paragraph.
Scripts that open on the mess don't rush it, and don't drag it. 66% spend a tenth of their words or more between the mess and the product's name (78 of 118). The typical mess-first script spends 19% there. Give the mess one short paragraph. Then hand over to the product.
A mechanic explains the knock in your engine in one sentence, and you believe her. A long lecture, and you wonder what she's selling.
Some go much longer: 31 of 118 spend a quarter of their words or more on the mess.
Example: FundApps' compliance video names the mess at 0:19: one person juggling filings, sanctions checks and reporting. Three yellow bars read Investors, Markets and Jurisdictions. At 0:34, FundApps arrives as one platform.
A tenth of the words or more: companies in this group include HPE, Moveworks, Paycom, FundApps, etc.
Exception: the mess is the joke. Paycom's personnel-forms spot spends 80% of its words on a missing raise and a botched transfer. One line names the product at 0:41, like a punchline.
Source: Advids analysis of 118 chaos-to-clean videos
The typical mess-first script spends 19% of its words before the product.
Finding 03 · Silo Line
3. The most named mess is disconnected tools, not spreadsheets.
You might expect the mess to be a spreadsheet. It rarely is. 53% of scripts name silos or disconnected tools (62 of 118). Overload and busywork come next. Spreadsheets, inboxes or sticky notes show up in just 19. If your buyer works across several tools, name the gap between them.
A kitchen isn't messy because of one dirty pan. It's the knives in one drawer and the board in another. Your buyer's silo is the same customer in the CRM, the billing tool and a spreadsheet.
Most scripts name more than one kind of mess: 81 of 118 name two or more.
Example: Celigo's Agent Builder video names the mess at 0:08. On screen, panels labeled App B and App C sit behind padlocks, their dotted links cut by red crosses. At 0:21, Celigo Agent Builder breaks down those walls.
Silos named: companies in this group include HPE, Salesforce, Adverity, Celigo, etc.
Exception: one risky step. Octopus Deploy's spot names one kind of mess, errors, and no silos. Before the product, deployments meant human error and late-night rollbacks.
Source: Advids analysis of 118 chaos-to-clean videos
Silos lead overload and busywork by 18 scripts. Spreadsheets show up in just 19.
Finding 04 · Drawn Mess
4. Before the product, the mess is written or drawn on screen.
Most videos don't show a stressed team at a desk. They write the mess or draw it. Of the 31 coded frame by frame, 61% show animated text, a diagram or a drawing before the name (19 of 31). Stock office shots show up in just 6. If your buyer's mess has no screen to point at, draw it.
A weather map doesn't photograph the wind. It draws arrows. Your buyer's silos are the wind, and a diagram is the arrow.
These are three of the title's four frameworks. Animated text leads, in 12 videos. Next come flowcharts and network diagrams, then illustration or abstract shots.
Example: Orange Business's contact center video names the mess at 0:02: volumes keep rising, and the data is scattered. An illustrated agent sits under a cloud of message, phone and email icons. The product arrives at 0:26.
Text, diagram or drawing before the name: companies in this group include IBM, Salesforce, Amplitude, Orange Business, etc.
Exception: the mess is a real document. Rackspace Technology's financial-spreading video shows an analyst with documents, then a close-up of spreadsheet numbers. When the mess is a document, show the document.
Source: Advids analysis of the 31 coded frame by frame
Animated text leads at 12. A product screen already shows before the name in 13.
Finding 05 · Clean Screen
5. After the name, the product's own screen shows the clean state.
Once the product is named, most videos stop drawing and show the real thing. 74% put the product's screen on view after the name (23 of 31). That's the fourth of the title's four frameworks. If your buyer will open the product after the video, show them that screen. They compare it on day one.
A real estate agent can describe the new kitchen. Or open the door. Your product's screen is the open door.
Many show a dashboard tour, 18 in all. Animated data charts are rarer, at 7. Either way, the clean state is the product's own screen.
Example: SAP's Autonomous CX video says at 0:10 that the data is trapped across systems. At 0:28, the answer is Joule. Then the screen fills with cards for Commerce Personalization, Service Resolution and more, beside a Joule chat panel.
Product screen after the name: companies in this group include HPE, IBM, Amplience, SAP, etc.
Exception: the product works out of sight. Swimlane's spot shows no product screen after the name, only animated text and a logo card. Its AI agents work behind a security team, so the clean state is said, not shown.
Source: Advids analysis of the 31 coded frame by frame
The product's screen mostly comes after the name. Only 13 show it before.
Finding 06 · Voice Track
6. Every video has a voiceover, and the typical one runs 1:25.
All 118 videos have a voiceover. That's partly by design, since only videos with a spoken script were counted. So the real choice is length, and the typical video runs 1:25. If your script carries the argument, budget a narrator from day one. Then write to the clock.
A museum audio guide doesn't change the paintings. It tells you where to look. Your narrator does that for the mess and the product.
Most also keep the screens bright or mixed: 78% do (92 of 118).
Example: ScienceLogic's Skylar Advisor video runs 2:01. At 0:12, the voiceover says most teams start the day overwhelmed by alerts and tickets. Ticket cards float on a pale gray screen. Skylar Advisor arrives at 0:31.
Voiceover: companies in this group include Zoho, Genesys, HPE, ScienceLogic, etc.
Exception: a long argument. Exabeam's security operations video runs 3:14 on dark screens. It spends 41% of its 420 words before the product, opening on "Security teams are overwhelmed with data."
Source: Advids analysis of 118 chaos-to-clean videos
Dark screens sit mostly with mess-first scripts: 24 of 99. Only 2 of the 19 product-first scripts use them.
Finding 07 · Callback Line
7. More than half the scripts bring the mess back after the product.
54% of scripts name the mess again after the product's name (64 of 118). Scripts that name the product first almost always do it: 17 of the 19. They haven't used the mess yet, so it lands as a contrast. If your product's name opens the script, bring the mess back after it.
A sale tag works because the old price is still on it, crossed out. The mess is the crossed-out price.
Some make the contrast plain, with lines like no more or say goodbye: 22 of 118 do.
Example: Atlassian's Product Collection video names the product at 0:15. At 0:25 the mess comes back: don't get lost searching for insights in a mountain of data. On screen, a grid of tiles holds charts, speech bubbles and placeholder text.
Mess again after the name: companies in this group include Zoho, Salesforce, Adverity, Atlassian, etc.
Exception: a four-sentence script. KEBA's asset-management video runs 0:38 and 57 words. One sentence names the mess, the next names KEBA, and the rest never returns to it.
Source: Advids analysis of 118 chaos-to-clean videos
Product-first scripts bring the mess back in 17 of 19. Mess-first scripts, which already used it, do so in 47 of 99.
Benchmarks by script order
Check your own script against each column. The product-first group holds just 19 videos.
Timing, length and frames
| Measure | Mess first (99) | Product first (19) | All (118) | What it means |
|---|---|---|---|---|
| Typical runtime | 1:24 | 1:34 | 1:25 | Half the videos run shorter than this |
| Typical words | 163 | 179 | 164 | Words in the voiceover |
| Typical words a minute | 127 | 125 | 126 | How fast the voiceover goes |
| Typical time the mess is named | 0:05 | 0:20 | 0:07 | Time into the video |
| Typical time the product is named | 0:21 | 0:09 | 0:17 | Time into the video |
| Typical share of words on the mess (%) | 19 | 0 | 16 | Words between the mess and the product; 0 when the product comes first |
What almost nobody does
| Picture | Videos | Companies |
|---|---|---|
| Data chart after the product is named | 7 of 31 | Foyr, HPE, IBM, Plaid, etc. |
| Stock office shots before the product's name | 6 of 31 | IBM, HPE, Rackspace Technology, SAP, etc. |
| A screen labeled with a mess word before the name | 5 of 31 | Otio, Rackspace Technology, Relativity, Rillion, etc. |
| A presenter on camera before the name | 4 of 31 | Deel, Nooks, SAP and WebWork |
| A split screen or before-and-after label | 3 of 31 | Atlassian, Otio and Workday |
The obvious pictures of chaos are rare. None shows up in more than 7 of the 31 videos coded frame by frame.
Seven questions for your next script
Answer these seven in writing before anyone storyboards.
- Finding 01 Is the mess your buyer's own? Then open on it, and name the product second.
- Finding 02 How many words sit between the mess and the name? Keep the problem stretch to one short paragraph.
- Finding 03 Does your buyer's mess cross more than one tool? Then name the gap between tools, not the spreadsheet.
- Finding 04 Can a camera point at the mess? If not, brief the problem section as text and diagrams, not stock office shots.
- Finding 05 Will your buyer open the product after watching? Have a presentable interface ready for the second half.
- Finding 06 Who carries the words? Budget a narrator from the first estimate, and time the script against 1:30.
- Finding 07 Did your product's name open the script? Then bring the mess back once, as a contrast.
Now go back to that brief: the stressed team and the sticky notes. In these videos, the mess was a spoken line at 0:07. The fix was the product's own screen.
This week, write your buyer's mess in one sentence. Then screenshot the one screen that fixes it. Write the script from there.
The chaos is a sentence. The clean is a screen.
Methodology
| Vertical (visual record only) | Videos |
|---|---|
| not recorded | 87 |
| fintech | 7 |
| itsm | 2 |
| retail | 2 |
| devtools | 2 |
| enterprise | 2 |
| cx | 2 |
| hr_tech | 1 |
| other verticals | 13 |
| Coding scheme | Values | Definition |
|---|---|---|
| Messy before-state | manual · spreadsheets · silos · overload · errors · busywork | Coded by reading the transcript: the kinds of disorder the script states as a condition a team, role, viewer or customer is in. A lexicon found candidates; a recorded call decided each. |
| Mess sentence and product sentence | sentence index · word position · seconds | The first sentence stating the mess and the first sentence naming the product or company as the fix, picked by reading. 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 | mess first · product first | Mess first when the mess sentence starts before the product sentence; within one sentence, an anchor phrase decides. |
| Problem share | 0 to 1 | Words from the first mess sentence up to the product sentence, over all words; 0 when the product comes first. |
| Mess-language share | 0 to 1 | Words in sentences carrying a messy-state term from the lexicon, over all words. |
| Mess after the product | yes · no | A sentence after the product sentence carries a messy-state term from the lexicon, as a restated problem or as a contrast such as no more manual work. |
| Visual framework | kinetic type · flowchart or network diagram · illustration, abstract or b-roll · product interface after · data chart after · stock office · presenter · messy-text interface · split or before-and-after label · spreadsheet, inbox or paper label | Coded from timed segment motifs and on-screen text overlapping the window before the product sentence, or around the mess sentence when the product comes first, and the window after the product sentence. Only videos with a full visual record carry these codes. |
| Sound and frame | voiceover · runtime · brightness 0 to 255 · light, mixed or dark frames | Voiceover from audio analysis; runtime from metadata; brightness and 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. 118 Chaos to Clean B2B Videos Decoded: The 4 Core Visual Frameworks Used to Demonstrate Productivity. 14 September 2026. https://advids.co/blog/chaos-to-clean-b2b-video-frameworks
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.