Section 1
Key takeaways
• No demo that closed a deal contained more than 76 seconds of uninterrupted talking; treat 76 seconds as your hard monologue ceiling . • A mid-demo question is discovery the buyer is handing you for free, it tells you which feature to slow down on and which to skip. • More questions isn't better. Across 326,000 calls, reps who lost deals asked more questions (~20) than reps who won (15–16); winners talked less and asked sharper . • Parking a question is only credible if you make it visible and anchor it to a specific later moment, an unwritten "I'll come back to that" reads as a dodge. • Every parked question is a pre-built, personalized reason to follow up, the parking lot becomes your close agenda.
Section 2
Why the script is the thing derailing your demo
The misconception runs deep: that a demo is a performance you deliver, and questions are the audience breaking the fourth wall. Peter Cohan, founder of Great Demo and author of the book by the same name, gave this its sharpest name. He defined the "Harbor Tour Delusion" as "presenting a long, tortured demo that attempts to cover all of the possible customer needs and problems before any reasonable discussion of the customer's situation" . That's what the script optimizes for, total coverage. And total coverage is exactly what loses. Allego, summarizing Cohan's framework, reports that poorly executed demos end in prospect apathy and rep disappointment roughly 90% of the time . The walkthrough that tries to show everything anchors the buyer's attention to nothing. Here's the reframe that changes how you run the next live demo: a question is not an interruption to the demo. The question is the demo. When a buyer interrupts to ask "wait, can it pull from our CRM automatically?", they've just told you which feature matters to them and which eleven slides you can compress. They are doing your discovery work mid-walkthrough, for free. The rep clinging to the script treats that gift as a threat. This is the same muscle that separates a good discovery and qualification call from a checklist interrogation: you're not extracting information to fill a form, you're following the buyer's attention to where the deal actually lives. The demo is just discovery with the product on screen.
Section 3
When do you answer a question now versus park it?
Not every question earns a live answer, and not every question should be deferred. The skill is a fast triage, not a reflex in either direction. Answer now when: • It's a one-line verbal answer. "Does it integrate with QuickBooks?", "Yes, native two-way sync." Done. Resist the urge to show it. PreSales.rocks' tactical guidance is explicit: respond verbally first and resist diving into the software, because every detour into a sub-screen is another monologue you have to climb back out of . A verbal yes keeps the thread; a five-click demonstration breaks it. • It's a buying-signal question. "Could my onboarding team run this without me?" or "What does the handoff to a client look like?" These aren't logistics, they're the buyer imagining ownership. Answer those immediately and briefly, because they signal the prospect has moved from evaluating to envisioning. Killing the momentum to park one of these is malpractice. Park it when: • It jumps ahead of the thread. "How much is this?" at minute three, before you've built any value, is a question you answer too early at your peril. Park it and anchor it to the pricing moment. • It needs a genuine deep dive. "Walk me through how permissions work across multiple client workspaces" is a real demo segment, not a one-liner. Trying to satisfy it on the spot blows your sequence apart and usually produces a worse explanation than the planned one would. • It's a rabbit hole only one person in the room cares about. Park it, log it, and offer to cover it in a focused follow-up so you don't lose the other four stakeholders. The triage itself takes about three seconds: one line or buying signal → answer; ahead-of-thread or deep dive → park. You will get faster with reps. What you cannot do is default to "park everything" (you'll read as evasive) or "answer everything" (you'll blow past 76 seconds and lose the room).
Section 4
The mechanics of a park that keeps the thread
"I'll come back to that" is where most parks die. Said and unwritten, it's a promise the buyer has heard a hundred times and watched go unkept. To park credibly, the question has to leave your head and become visible. Advisorpedia's breakdown of the parking-lot move is precise about why: writing the question down "gives credibility to the participant," and once it's written, the responsibility to circle back becomes yours, not theirs . You've converted a vague "later" into a logged commitment the buyer can see you holding. In practice, on a live screen-share, that means a literal running list. Keep a visible notes panel, a shared doc, or a corner of the slide where parked questions accumulate by name. When a question gets parked, do three things in one motion: 1. Name it out loud. "That's the multi-workspace permissions question, important one." 2. Write it where they can see it. Type it into the visible list so the buyer watches it get logged. 3. Anchor it to a specific moment. "I'll walk you through exactly that right after the reporting view, about six minutes from now." The anchor is the part nobody does and the part that keeps the thread. "I'll come back to that" is a dodge. "I'll show you exactly that at the pricing view in four minutes" is a sequence. The difference is whether the buyer believes you're managing the demo or hiding from a question. Anchoring also quietly tells the buyer the demo has a structure, that there's a reason you're not jumping around, which raises your authority without a word about authority.
Section 5
Who should be talking when a question lands?
Founders assume that a question is their cue to talk more. The talk-time data says the opposite. Across 326,000 sales calls of at least ten minutes, reps who won deals talked 57% of the time and asked 15–16 questions; reps who lost talked 62% and asked about 20 questions . Winners talked less and asked fewer, better questions. Read that carefully, because it inverts the usual advice. The lesson is not "ask more questions to seem engaged." Losers did that. The lesson is that the question that lands in your demo is often best answered with a question back, to convert a feature query into a needs conversation. Buyer: "Does it let me set different approval rules per client?" Weak answer: a four-minute tour of the approvals engine. Strong answer: "It does, how are you handling approvals across clients today?" Now you've turned their question into discovery, learned what the feature has to beat, and earned the right to show the one configuration that matches their reality instead of the generic tour. You talk less, they reveal more, and the feature you eventually show lands because it's aimed. This is the same talk-to-listen discipline that governs handling objections without getting defensive, the reflex to over-explain is what turns a manageable moment into a lost one. The buyer's question is an opening to listen, not a prompt to lecture.
Section 6
The counter-intuitive part: more questions isn't the goal
There's a trap in over-correcting. Read "questions are good" and you might conclude the demo should become a free-for-all where you chase every query the moment it surfaces. The data closes that door: losing reps asked more questions, not fewer . Volume of interaction isn't the win. Quality of triage is. A demo that answers all twenty questions live is a demo with no spine, it wanders wherever the loudest voice points, never builds an argument, and ends with a buyer who saw everything and remembers nothing. That's the Harbor Tour again, just democratized. The winning pattern is tighter: short bursts of demonstration (under your 76-second ceiling), frequent speaker switches, a handful of sharp questions back, and a disciplined parking lot catching everything that doesn't earn a live answer. You're not maximizing interaction. You're maximizing the signal in the interaction and deferring the noise to follow-up, where it actually helps you.
Section 7
The BGA framework: the 76-Second Rule + Park-and-Anchor loop
Here's the system, built to run live without a co-pilot. 1. Set the 76-second ceiling. Treat 76 seconds as the hard maximum you'll talk without a speaker switch . In practice, aim well under it, break every demonstrable point into a sub-60-second burst and end with a check ("does that match how your team works?"). If you catch yourself past a minute with no handoff, stop and ask something. The ceiling isn't a target; it's a tripwire. 2. Triage every question in three seconds. One-line answer or buying signal → answer now, verbally first, resist diving into the software . Ahead-of-thread, deep dive, or single-stakeholder rabbit hole → park. 3. Park visibly, not verbally. Name the question, write it in a shared/visible list so the buyer watches it get logged (this "gives credibility to the participant" ), and never let a park exist only in your head. 4. Anchor every park to a moment. "I'll show you exactly that at the [specific view] in [N] minutes." The anchor converts a dodge into a sequence and keeps the thread intact. 5. Escalate speaker switches in the back half. Winning demos increase speaker switches per minute by 36% in the second half . As you near the decision, trade off more, more "what would you do here?", more "does this fit?", not a closing monologue. 6. Close the loop with the parking lot as your agenda. Before you end, run the visible list out loud: "We parked three, multi-workspace permissions, the QuickBooks sync depth, and your pricing question. Let's book 20 minutes Thursday and I'll walk you through exactly those." Every parked question is a pre-built, personalized reason to follow up, and a reason the next meeting exists. That follow-up belongs inside a real post-demo follow-up sequence, not a one-off email, so the parked questions become the system that carries the deal forward. The metric to hold yourself to: RevenueHero's benchmarks, drawn from over one million inbound form submissions, put a typical demo-to-meeting conversion at 50–60%, with 70%+ considered exceptional . If your live demos are converting to a next meeting below ~50%, the problem is rarely the product, it's a walkthrough that monologued past the room. Run the loop and watch that number, not your slide count.
Section 8
You're running the 76-Second Rule + Park-and-Anchor loop right when…
…you can't remember the last time you talked for two straight minutes in a demo. When a buyer interrupts, you feel a flash of useful information arriving, not annoyance. There's a visible list of parked questions on screen by the end of every call, each anchored to a moment you actually hit or explicitly rescheduled. You answer the small questions verbally in one line and the buying-signal questions immediately, and you catch yourself asking a question back at least as often as you deliver a feature. Your speaker switches go up as the demo nears the decision, not down. And your follow-up email writes itself, because it's just the parking lot with three calendar links attached. When all of that is true, the question isn't derailing your demo anymore. The question is running it.