Junior SEs walk into demos wanting to demonstrate they know the product cold. That instinct makes sense. Deep product knowledge is what got them hired. The SEs who develop fastest learn to redirect that instinct toward something more useful: demonstrating that they understand the customer.
The difference between those two demos is larger than it looks from the outside.
A demo built on product knowledge covers features in order, navigates menus confidently, answers technical questions accurately. It shows the SE is prepared. It rarely shows the customer that they've been understood.
A demo built on understanding leads with the customer's own problems, shows only what connects to those problems, and makes the customer feel seen rather than impressed. That's the demo that moves a deal.
Getting junior SEs from the first version to the second is the actual coaching challenge.
The coaching methodology that closes that gap is called the Earned Demo. The product demonstration stops being something the SE delivers and starts being something the customer asks for. Getting there is a two-stage process: the So What Drill, which builds the habit in practice, and Demo by Invitation, which applies it in the room.
If you're an individual SE looking for the practitioner angle on running a great demo, this article covers the structure and mindset. What follows is the coaching methodology for SE leaders.
The trap that looks like discovery
SEs who've gotten the "ask questions" coaching usually implement it the same way: pause after each feature section and ask "do you have any questions?"
That technically counts as asking a question. It checks the box. But no one in the room takes it seriously, including the SE asking it.
Real discovery questions are specific. They connect directly to what was just shown. They invite the customer to reveal something: how their current process works, where the friction actually lives, what success looks like for them. "Do you have any questions?" doesn't invite any of that. It invites the customer to nod and wait for the next section.
The SEs who run great demos have trained themselves to ask the right question at the right moment. The exercise that builds that habit is simple to describe and genuinely hard to sustain.
Stage one: The So What Drill
During demo practice, ask the SE to pause after every feature they show and every point they make, and ask themselves a single silent question: so what?
Why are they showing this? What should the customer walk away thinking? Why does it matter to the specific person in this room, at this company, right now?
Then have them say the answer out loud.
Instead of navigating through an incident timeline and moving to the next section, they stop and add: "What makes this valuable is that the on-call team sees the full context in one place. At most companies I talk to, assembling that picture manually can add twenty minutes to every incident. This cuts it to seconds." Then a real follow-up: "How does your team assemble that picture today? Is it one tool or several?"
That's a different conversation than "do you have any questions?"
The exercise produces results quickly. Customers engage more. The discussion gets richer and more specific. Sometimes the SE surfaces things in the demo that discovery should have found, and that's fine. Real information is moving.
There's a real cost, though. This step makes the demo at least twice as long.
The trade-off worth making
A demo that gets cut off at the 45-minute mark because the conversation took over is a better outcome than a demo that runs the full 90 minutes on schedule and leaves nobody moved.
SE leaders who ask "did you get through everything?" after a session are measuring the wrong thing. The better questions are "what did you learn?" and "how did the room respond?" If the customer interrupted to ask a detailed question, if someone pulled in a colleague, if the meeting ran over because the customer kept talking, those are signs the demo worked.
SEs who go through this stage also start learning something about their own demos: most of what they planned to show didn't need to be there. The sections that generate real conversation are almost never the ones the SE spent the most time preparing.
Stage two: Demo by Invitation
Once the SE is consistently answering the "so what" question out loud, the next evolution is to stop leading with the feature at all.
Early in a deal, buyers don't need to understand the technical mechanics of how the product works. They need to understand what changes if they use it. The feature is the path. The value is the point.
The graduated demo leads with the answer and works backward into the product only if the customer wants to see it.
"Companies with large distributed systems usually see mean time to resolution drop by about half when they solve this. Want to see how?" Then show it.
Value statement, discovery question, product demonstration on request. That's the sequence the best demo conversations are built from. The SE navigates a conversation they've thought through, because they know what matters and why.
What this produces
SEs who train through this method start thinking about demos differently. The question shifts from "how do I get through the full product?" to "what does this specific customer need to feel, and what's the fastest path to that moment?"
They also get better at knowing when a demo is going well. Not because they covered the material. Because the room leaned in.
The "so what" question is simple. Running it consistently during practice, out loud, until the answers become automatic, that's where most SE coaching stops short. Understanding the idea is easy. Doing it until it's instinct is the work.
That gap between understanding something and doing it in front of a customer is where most SE development programs stall. This exercise closes it.
The goal of both stages is the same: a demo the customer had to ask for. That's the Earned Demo.