One storyboard at the centre, established methodologies attached by the job they do in a deal, and published research behind every beat of the demo.
A 2020 survey of 400 revenue people at North American B2B software companies compared teams running Solution Selling, Challenger, FORCE, MEDDIC, SPIN, NEAT, Miller Heiman, Sandler and others. Its finding:
“How you apply a methodology is more important than which one you adopt, with little perceived difference in effectiveness across different types of methodologies.”
The same survey found a 13-point difference in reported effectiveness where a formal value-engineering function exists. Both figures are self-reported by practitioners (MetaCX with Revenue Collective, October 2020). So the architecture is built to be installed into whatever a company already runs: a fixed spine, and plug-ins chosen by the job in front of the team.
The storyboard comes from Corporate Storytelling training and is rebuilt here as a demo architecture. Each cut names its audience and the outcome it is driving toward, then runs one story beat per row:
The same rows generate four outputs, so the message, the material and the demo never drift apart:
The storyboard is central but not total. It does not say how to qualify a deal, unstick one, or run a proof of concept. Other methodologies do those jobs better, and they attach below.
Attention in a meeting drops in and out from the first minute rather than fading on a clock. Each beat of the storyboard is built around what the research says brings it back and makes the next point stick: open with a story, picture or live drawing, land the benefit in the moment that opens, prove it in a short stretch, then hand the thinking to the buyer.
A virtual audience arrives fragmented, and the longer and larger the meeting, the more of it goes elsewhere.
| Finding | What was measured | Source |
|---|---|---|
| About a third of remote meetings lose people to email | ~30% of meetings included email multitasking and ~25% work in other files; more in longer, larger, recurring and morning meetings | Microsoft Research and Stanford, CHI 2021; company telemetry plus a 715-person diary study |
| People switch screens in under a minute | Average time on one screen before switching: ~47 seconds, down from ~2.5 minutes in 2004 | Gloria Mark, UC Irvine |
| Lapses begin almost immediately | First lapses reported ~30 seconds in and again near 4.5 minutes, then in shorter cycles; no steady decline across the session | Bunce, Flens and Neiles, Journal of Chemical Education 2010 |
| Back-to-back calls stack stress | Brain-wave stress markers climbed across four consecutive 30-minute video calls; 10-minute breaks reset them and raised engagement | Microsoft Human Factors Lab, EEG, 2021; 14 people |
Stories, pictures and drawing reset attention and are remembered best.
| Finding | What was measured | Source |
|---|---|---|
| A change of activity brings attention back | Significantly fewer lapses during and right after a demonstration or question than in comparable stretches of straight lecture | Bunce et al. 2010 |
| Stories are understood and remembered better than exposition | About half a standard deviation better recall and comprehension for narrative; 37 articles, more than 33,000 people, robust across ages and delays | Mar, Li, Nguyen and Ta, Psychonomic Bulletin and Review 2021 (meta-analysis) |
| Engagement rises at a story's emotional moments, and predicts what is remembered | Viewers' engagement and brain activity synchronised at the same story moments; those signatures predicted which events people later recalled | Song, Finn and Rosenberg, PNAS 2021 |
| Pictures are remembered far better than words | Recognition after 1,000 items: ~90% for pictures against ~62% for words | Standing, Quarterly Journal of Experimental Psychology 1973 |
| Words with a picture beat words alone | Multimedia effect g = 0.68; text with diagrams was the strongest format, across 181 studies | Meta-analysis of Mayer's multimedia research, Educational Research Review 2025 |
| Watching a hand draw the diagram beats a finished slide | Better transfer when viewers watched the instructor's hand draw than with the same diagram pre-drawn (d = 0.35); animated drawing with no hand gave no gain | Fiorella and Mayer, Journal of Educational Psychology 2016 |
| The metaphor chosen steers the decision | Support for enforcement: 71% when crime was framed as a beast, 54% as a virus; only 15 of 485 people noticed the metaphor had influenced them | Thibodeau and Boroditsky, PLOS ONE 2011 |
The frame opens a short window in which the brain is primed to encode. The benefit statement is placed inside it, at a clear transition.
| Finding | What was measured | Source |
|---|---|---|
| Curiosity primes memory for what comes next, even unrelated material | In the 14 seconds after a curiosity-raising question, people remembered incidental faces better a day later; reward and memory circuits were more active and more connected | Gruber, Gelman and Ranganath, Neuron 2014 |
| The brain's memory system responds at transitions | Hippocampal activity peaked at the moments viewers marked as event boundaries, more strongly the clearer the boundary; 253 viewers in one dataset | Ben-Yakov and Henson, Journal of Neuroscience 2018 |
| What lands at a transition is remembered better | Words marking an event boundary in spoken stories were better remembered, and boundaries also strengthened memory for what came just before | Cognitive, Affective and Behavioral Neuroscience 2026; 40 people |
Watching tops out in minutes; short proof segments separated by questions reset attention.
| Finding | What was measured | Source |
|---|---|---|
| Viewing tops out around six minutes | Median engagement was at most ~6 minutes whatever the video length; videos over 9 minutes usually lost viewers before halfway | Guo, Kim and Rubin, edX 2014; 6.9 million viewing sessions |
| Short segments with a question between them halve mind-wandering | Online lectures in ~5-minute segments: mind-wandering fell from ~40% to ~20% with quick questions between; note-taking tripled; breaks alone did not help | Szpunar, Khan and Schacter, PNAS 2013 |
| Segmenting helps, though the size of the effect is debated | Small-to-medium gains in retention and transfer across 56 studies; a 2025 review of Mayer's research found no significant segmenting effect on its own | Rey et al., Educational Psychology Review 2019; 2025 meta-analysis |
| Understanding tracks how closely the listener follows the speaker | The more a listener's brain anticipated the storyteller's, the higher their comprehension; the coupling vanished when communication failed | Stephens, Silbert and Hasson, PNAS 2010 |
Buyers remember what they work out themselves; end every row by handing the reasoning to the room.
| Finding | What was measured | Source |
|---|---|---|
| Generating an answer beats hearing it | Information people produced themselves was remembered about 0.40 standard deviations better than information they read; 86 studies | Bertsch et al., Memory and Cognition 2007 (meta-analysis) |
| A question, not a pause, does the resetting | In the same lecture study, questions between segments cut mind-wandering; extra study time or a plain break did not | Szpunar et al. 2013 |
People remember openings and endings best, and the ending shapes how the whole experience is judged.
| Finding | What was measured | Source |
|---|---|---|
| First and last are remembered best | Recall is highest for the first and final items in a sequence (primacy and recency) | Serial position effect: Murdock 1962; Glanzer and Cunitz 1966 |
| The ending sets the memory of the whole | 682 patients: a gentler final few minutes made the whole procedure remembered as less unpleasant (4.4 vs 4.9 out of 10) and made patients more likely to come back (odds ratio 1.41) | Redelmeier, Katz and Kahneman, randomized trial |
Each finding comes from classrooms, laboratories or video platforms, not from sales demos. No study tests this exact sequence with buyers. The storyboard applies the findings; it does not claim they were measured on it.
Practice starts once the script and the storyboard are written. Its purpose is consistency: every team presenting the demo tells the same story, row for row, while still sounding like themselves.
Each presenter records their own run of the rows they deliver. The recording is the unit of practice, so nothing depends on a live audience to get feedback.
Starts as soon as a row is written
Recordings are reviewed as a team in buckets, one per storyboard row, so each area of functionality is tightened on its own before it has to fit with the others.
Cadence set by where each row stands and how close launch is
Closer to launch, the rows are run end to end: frames, transitions between rows, and the close walking the rows in reverse. The full run is reviewed on film the same way.
Final stretch before launch
The full demo is run for a series of internal colleagues, each playing a specific buyer profile and asking the questions that buyer asks. Every session is recorded and reviewed like the rest of the film.
Once the full run holds together
The last session is run for the C-suite. It is the final test before anyone takes the demo to market; a presenter who has not passed it does not present to buyers.
Last step before market
Each internal function hears its buyer counterpart’s questions every day, so it is the best-placed stand-in for that buyer.
| Internal stakeholder | Buyer profile they play | What their questions test |
|---|---|---|
| Sales | The economic buyer and the sceptic comparing vendors | Whether the benefit statements survive a competitive challenge, and whether the value case holds under price pressure |
| Professional services | The project owner who will have to implement it | Whether the demo implies a rollout the team can actually deliver, and on what timeline |
| Support | The operations lead who lives with it after go-live | Whether reliability, escalation and day-two questions have honest answers |
| Product | The technical evaluator and the architect | Whether the evidence on screen holds up to depth, integration and roadmap questions without over-promising |
| Others as the deal requires | Finance, legal, security or procurement | Whether the story survives every seat on the buying committee, not only the champion’s |
Questions that catch a presenter out are written down and fed back into the storyboard: a new trailing question, a sharper benefit statement, or better evidence for that row. The same list becomes the team’s shared answer bank, so the next presenter meets the question prepared.
Senior leaders give the least time and the hardest judgement, which is exactly what the first real buyer meeting will be like.
A review asks the same questions at every stage, from the first solo recording to the executive test: did the frame win attention in its time, was the transition clean, did the benefit statement land in the buyer’s world, did the evidence on screen prove it, and was the trailing question asked. Wording differences between presenters are expected and are not corrected.
Discovery is mandatory: no demo is booked until it is done. Discovery decides which storyboard rows run, in what order, which frames open them and which evidence proves them. A demo built without it shows the product; a demo built on it shows the buyer their own problem being solved.
Read the company before speaking to it: public filings, recent press, and a relationship map of who the firm already knows there. The first call then confirms and deepens what is known instead of asking for what could have been read.
| Discovery finding | Demo decision it drives |
|---|---|
| Who is in the room | Which frames are drawn from the frame library, and who on the buying side each row is aimed at |
| The problem and its cost | Which benefit statements lead, and which evidence is put on screen first |
| Why now | The order of the rows; for a senior audience, the finished outcome is shown first |
| Current state and incumbent | Where the reframe goes, and what the buyer keeps if they move |
| Technical landscape | How the demo environment is set up from its starting point: data, integrations and configuration that look like theirs |
| What they have seen | Where to steer the buying criteria, only where the diagnosis is true |
| Success in their words | The wording of the close and the next step asked for |
Every storyboard row ends on an open trailing question, so the demo keeps discovering. What the buyer says in answer goes back into the account notes and shapes the next meeting. Diagnose honestly first; steer only where the diagnosis is true.
The frame is the 20-to-60-second story, picture or diagram that opens a row. The metaphor chosen steers what the listener weighs when deciding, and few notice it happening (Thibodeau and Boroditsky, above). So frames are kept in a library, organised by the audience they speak to, and chosen from discovery for each meeting. The frames themselves are written by the presenting team from real stories; the library only decides which one fits whom.
| Audience | What discovery usually shows they weigh | Frame that tends to land |
|---|---|---|
| Chief executive or founder | Growth, competitive position, the board’s questions | A short story about a peer company’s turning point; a single picture of the market |
| Finance | Cost, risk, predictability, the audit | A before-and-after figure drawn live; a story about a surprise that cost money |
| Technology leader or architect | How it fits, how it fails, who maintains it | A whiteboard diagram of their own systems, drawn in the room |
| Operations or line-of-business lead | Throughput, handoffs, the team’s week | A day-in-the-life story of the person doing the work today |
| End users and practitioners | Time saved, fewer steps, less rework | The familiar frustration, shown in their own screen or words |
| Security, legal or compliance | Exposure, control, evidence for regulators | A story about the incident or finding that could have been caught |
| Procurement | Total cost, terms, vendor risk | A comparison that moves the conversation from licence price to total spend |
Two seats on every early demo: one presents, one owns discovery and the room. The sales lead’s part is a set of specific interaction points, planned before the meeting so the handoffs are clean and nobody talks over the story.
The questions the sales lead owns are the ones only they should ask: who else needs to see this, how the decision gets made, what the timeline hangs on, and what would stop it. Technical questions go to the presenter; the sales lead does not demo.
Two demos a day, as a rule. Three at most, and only when each is an hour or shorter.
Stress builds across back-to-back video meetings and resets with a break between them (Microsoft Human Factors Lab, above). A presenter past the limit is not delivering the locked pieces the way rehearsal built them, and cuts short the pre-demo checklist, including the demo reset, for the next buyer.
In deal order. A methodology is named only where the practice already does what it prescribes. trained marks formal training.
| Job | In practice | Named | Also drawn from |
|---|---|---|---|
| DiscoveryWhat is broken, and what does it cost? | Diagnose honestly first. Then ask the questions that tie a feature request to why it matters, who it affects and what it costs. Every storyboard row keeps a question open, so discovery continues inside the demo. | CustomerCentric Selling® trained SPIN, practised | Solution Selling · Gap Selling · SPICED |
| MessageWhy change, and why now? | A reframe that makes the status quo the losing option, winning on service depth, regulatory expertise and roadmap when behind on features. | Challenger trained | Sense Making · Command of the Message |
| CommitteeWho decides, and does the story survive them? | Every buying influence and the coach mapped before the first conversation, including relationships the firm already has. Two seats on every early demo: one presents, one owns discovery. | Buying-influence mapping | The Challenger Customer · Gartner buying-jobs research |
| QualificationHas the deal earned a place in the forecast? | A pricing case on every deal against the competitive field; references rotated so none is over-used; press-release triggers wired into the CRM. | The company's own qualification language | MEDDPICC · SPICED · ValueSelling |
| MomentumWhy has an agreed deal stopped moving? | Every touchpoint earns the next: demos recorded by default and the recording sent to set up the next meeting. Migrations run as campaigns, leading with what the client keeps. | — | Sandler up-front contract · The JOLT Effect |
| Demo and proofDo they believe it? | The storyboard is the demo. Two seats per demo, weekly review of recorded demos, and a storyboard that tracks each release so the value story matches what shipped. | The storyboard | Great Demo! · Demo2Win |