Everything in Module 10 assumes the demo you're delivering is well‑built and well‑sequenced. Two separate pieces of survey and product‑analytics data say the bigger problem for most SEs is upstream of that: the demo is eating time it shouldn't, and the audience isn't watching most of what does get built anyway. Neither fact is this manual's opinion — both come from named sources below.

The time is going somewhere, just not to the good part

A survey of 400+ practising SEs found 46% spend at least five hours a week customising demo environments, and a further 23% spend five‑plus hours a week just maintaining them — before a single new demo gets built. The squeeze shows up exactly where you'd expect: 80% of SEs spend fewer than ten hours a week on the actual designing and solutioning work that's supposed to be the job's higher‑value core. Customisation and maintenance aren't the job description; they're what's crowding it out.

Buyers are already voting with their attention

Separately, product analytics across roughly six million buyer interactions on a demo platform found the average demo runs 15 minutes 14 seconds, while the average viewer actually watches 5 minutes 14 seconds of it — a third of what was built, and the gap widened year over year, not narrowed. Where a demo includes discovery questions at all (only 42.75% do), 75%+ of viewers answer just one question before moving on, and 90% answer two or fewer. Buyers are already self‑selecting the shortest path to the part they came for, whether or not the demo was built to allow it.

What actually follows from this

• Build modular, not monolithic. Three to five self‑contained 3–5 minute segments, each openable independently, beat one 15‑minute linear script — it's the "menu, not an agenda" principle from Module 10, taken to its logical conclusion once you know most of the agenda won't be watched anyway.
• Front‑load the segment most likely to be the only one watched. Outcome before mechanism (Module 10) matters even more when there's a real chance mechanism never gets seen at all.
• When you don't have room for full discovery, ask one sharp question, not zero. A single well‑chosen question before or inside a demo — not a five‑question qualification form nobody will finish — matches how buyers actually engage, and one real answer still beats a demo built on pure assumption.
• Treat per‑demo customisation as a cost to budget, not a favour to say yes to every time. A demo rebuilt from scratch per prospect is the direct cause of the 46% figure above; a small library of modular, swappable segments is the way most of that time gets back.

The same data says something about threading, too

The gap between what a demo covers and what one viewer watches is also an argument for not building the demo around one viewer in the first place. The same buyer‑behaviour analytics found that a deal with just one additional stakeholder looped into shared demo content is 35% more likely to be attached to that content than a single‑threaded one, and a deal with seven or more stakeholders looped in is 92% more likely — and, separately, that the buyers who actually convert spend an average of 7 minutes 39 seconds watching demo content, 2.3 times longer than an average viewer. Read together with the watch‑time data above: a shareable, modular asset that a champion can forward to the security lead or the CFO without you in the room reaches exactly the stakeholders Module 18's power/interest map says you can't afford to under‑invest in, and it does it asynchronously, on their schedule rather than a meeting you'd have to book.