9
Excellent job addressing Charles's deep integration and security concerns with specific protocols and near real-time sync details, keeping him engaged through interactive demo transitions without letting the call derail.
0:00/0:00
The Playbook · Chapter 3 of 6
Demo call practice with a buyer who interrogates
A demo is not a feature tour, it's a conversation with proof in it. At most deals it's one or two people on a video call, half-distracted, deciding in real time whether to keep paying attention. The part that goes wrong under pressure is rarely the product; it's the talk track. Below are the moments that decide demo calls, and how to hold each one.
On the call
Where demo calls get hard
“Wait, go back. What did that setting do?”
Testing whether you know it or just demo it.
Answer like an operator. Show the setting, say what it does, say when you'd change it. Then return to the claim you were proving. Depth on demand, narrative on rails.
“How does this hold up in a security review?”
One vague answer ends this.
Be specific or be scheduled. Answer what you know precisely, and park the rest with a named follow-up and a date. The only wrong answer is vague reassurance, because that's the answer they came to catch.
“...”
Camera off, reading email two tabs over.
Stop presenting. Silence is data. “Let me pause. Which part of this are you most skeptical about?” An awkward question beats a smooth demo nobody is watching.
“Does it work with what we already run?”
If this means a migration, I'm out.
Answer the fear, not just the question. The question is integrations; the fear is disruption. Say what stays exactly the same first, then what changes, in that order. The order is the reassurance.
“Okay, but why does that matter to us?”
Features are not a reason to change.
Tie it to their stated problem. “You said this costs you X. This is the part that removes it.” If you can't finish that sentence for a feature, cut the feature from the demo.
Field notes
How to run a better demo call
Open with a claim, not a menu. State what you intend to prove in their terms before you share a screen. A demo without a claim is a tour, and tours get judged on aesthetics.
Welcome the interruption. Questions are engagement, not derailment. Practice answering directly and folding back into your thread, because parking everything for the end tells the buyer their concerns can wait.
Check engagement on purpose. Camera-off silence reads as agreement in the moment and becomes a lost deal later. Ask pointed check-ins tied to what you just showed, not a generic “any questions?”
Rehearse the recovery, not just the flow. Demos die in the unplanned moments: the question you can't answer, the screen that errors. The buyer remembers how you handled it longer than what happened, so the composure move is the thing to practice.
Hear this call handled
A sample call against an AI buyer, scored and broken down
Charles Whitaker
Your turn against the same buyer
Same persona, same call, same scorecard
Uses your mic. Hang up anytime. Scorecard at the end.
Walk into the demo having already survived it.
Start practicing demo calls