Demo Teardown: The Exec Who Joined, Never Unmuted, and Killed the Deal Two Weeks Later

The call that went well

Seven people on the invite. Six of them showed. The champion opened by saying how much the team had been looking forward to this. Two analysts asked sharp, specific questions about data mapping. Somebody laughed at the rep's joke about spreadsheets. The rep ran long by four minutes because there was so much good conversation, and everybody said that was fine.

And sitting in the top-right tile, camera on, muted the entire time, was the person whose budget line this was going to come out of.

Forty-five minutes. Not a word. Not a question. Nodded twice. Typed something once. At the end, when the rep said "any questions before we wrap?", they unmuted just long enough to say "no, this was helpful, thanks," and dropped off eleven seconds before the hour.

Two weeks later: no decision. Not a loss to a competitor. Not a budget freeze. Just the champion going quiet, then a note saying leadership wants to revisit in the next planning cycle.

The rep called it a great demo. It was not a great demo. It was a demo run for the wrong half of the room, and the silence should have been the loudest thing on the call.

This is the most expensive of the common multi stakeholder demo mistakes, and it is expensive precisely because it does not feel like a mistake while it is happening. Engagement from the people who will use the product feels identical to engagement from the person who will pay for it. Right up until it doesn't.

Why silence reads as agreement and almost never is

When a senior person says nothing for the length of a demo, reps tell themselves one of two stories. Either the exec is bought in and letting the team drive, or the exec is busy and half-listening and will defer to the champion. Both stories let you keep your forecast where it is.

The likelier story is duller. The exec came to the call with one question, the question never got answered, and they decided somewhere in the middle that answering it would take more effort than it was worth in front of six other people. So they sat there, made a private judgment, and left.

I have watched a lot of second-stage demos, and the pattern I see over and over is that executives arrive with a single specific reason for attending, and that reason is rarely "see the product." They already believe the product probably works. What they want to know is whether this is the thing their team should spend the next two quarters implementing instead of the other three things on the list, and whether the person selling it understands what it costs them to say yes.

Nothing in a standard feature walkthrough answers that. So they go quiet.

Silence in a demo is not neutral. It is a stakeholder telling you they have stopped participating in the evaluation, and you have somewhere between ten and twenty minutes to notice.

The teardown

Let me walk the three places this call went sideways, because none of them look like errors in the moment.

Minute 2: the round-the-room that skipped what the exec actually said

The rep opened well, by the standards most people are trained to. Went around the room. "Before we dive in, I'd love to hear from each of you — what would make this a good use of your time today?"

The champion said they wanted to see the reporting. Analyst one said they wanted to understand the integration with the existing system. Analyst two said they wanted to see how exceptions get handled. The exec said, and this is close to verbatim for how these usually go: "I'm mostly here to listen. The team's been driving this one."

And the rep said "great, thanks," and moved on.

That was the mistake. "I'm here to listen" is not an answer. It is a polite decline to answer, and it is the single most important sentence anyone said on that call. An executive who blocks an hour to listen has a reason to be listening. They just don't want to state it in front of their own team, because stating it would reveal something — that they're skeptical, that they're under pressure from above, that they've been burned before, that they don't entirely trust the champion's judgment on this one.

What the rep should have done is treat it as an opening rather than an exit. Something like:

"Totally fair. Let me ask it a different way — when this comes back to you in a few weeks and the team is recommending we move forward, what's the thing you'll want to be sure of before you sign off?"

That question is answerable. It does not require the exec to critique their own team in public. It gives them a frame where being demanding is the expected behavior rather than a signal of distrust. And whatever comes back — "I want to know it won't need three headcount to run," "I want to know we're not doing this again in eighteen months," "I want to know what happens to the current system" — is now the actual agenda for the next forty minutes.

If they still deflect, you have learned something too. You have learned they are not going to help you, and you should be building the rest of your call so that the outcomes land whether they participate or not.

Minute 18: the deep dive into a workflow the exec will never touch

This is where the call was lost, and it was lost while it looked like it was going best.

Analyst two asked a genuinely good question about exception handling. What happens when a record fails validation? The rep, delighted, went in. Clicked into the exception queue. Showed the retry logic. Showed the audit trail on the retry. Showed how you configure the retry threshold. An analyst asked a follow-up. The rep went one level deeper.

Eleven minutes on exception handling.

The analysts loved it. Those eleven minutes probably won the technical evaluation outright. And they were eleven minutes of an executive watching a screen showing a configuration panel they will never open, in a workflow they will never run, solving a problem they have never personally had.

That is where the internal calculation happens. Not "this product is bad." Something more like: this is a tooling decision, the team can handle it, I'll look at it when it comes to me with a number attached. And once an exec has mentally reclassified your deal from initiative to tooling purchase, the deal now has to survive a budget conversation on its own merits with nobody senior arguing for it. Most don't.

The fix is not to refuse the deep dive. The analysts' question deserved a real answer, and refusing to go deep in front of technical evaluators costs you the technical evaluation. The fix is the exit. You go deep, and then you climb back out loudly and deliberately:

"Okay — that's the mechanics of it. Sarah, the reason I spent time there: the reason teams end up with a person manually reconciling failures every Monday morning is that the retry logic isn't configurable. That's the headcount cost of this problem, and that's what this removes. Is that consistent with what you're seeing?"

Thirty seconds. It translates the depth into a consequence the exec owns, and it does it while the demo is still live rather than in a summary slide at the end that everybody has stopped listening to.

Minute 43: "any questions?" into a wall

The close was the third mistake, and it is the one almost every rep makes because it is what we were all taught.

"Any questions before we wrap?"

That question, asked to a group, is answered by whoever is most comfortable speaking. It is never the person who has been quiet for forty minutes. Open questions to a room reward the already-engaged and let the disengaged stay disengaged. You have just given the one person you needed to hear from a clean, socially acceptable way to say nothing at all.

Worse, "no questions" from a silent exec gets logged as a positive signal in the CRM. The rep writes "no objections raised." There were objections. They were raised in someone's head at minute nineteen and never made it to the call.

What closes this properly is a direct address that is specific and easy to answer, and that does not make the person feel cornered:

"Sarah, I know you said you were here to listen, so I want to check one thing before we wrap. If this went ahead, the biggest lift on your side is going to be the four weeks of parallel running while the old system winds down. Is that the kind of thing that's a real problem in your planning cycle, or is that a normal cost of doing business for you?"

Notice what that does. It names a cost you have already identified rather than asking them to volunteer one. It offers two acceptable answers, so agreeing or disagreeing both feel safe. And it is about their world — sequencing, planning cycles, disruption — not about your product's features.

Most of the time you will get a real answer. Sometimes the real answer is bad news, which is worth far more than two weeks of silence and a polite deferral.

The rewrite

Find out why the exec is on the invite before the call

When a senior person is added to a demo invite, somebody added them for a reason, and your champion knows what it is. Ask.

"I saw Sarah's on the invite for Thursday — I want to make sure we use her time well. What made her want to join this one? And is there anything she's said about this project that I should know going in?"

That second question is the one that pays. Champions will tell you things like "she's been burned by an implementation before," or "she's under pressure to cut the vendor count," or "honestly she's not sure we need this and I'm trying to convince her." All three change how you run the hour completely. The third one especially — if your champion is using your demo as an internal persuasion tool, you are not running a demo, you are running a business case with screens in it, and you should structure it accordingly.

Do this in writing if you can, a day or two out, so the champion has time to actually think about the answer rather than say something reflexive on a call.

Build the demo on two tracks

The reason mixed-seniority demos fail is that most reps build one demo and hope it lands with everybody. It cannot. Operators need to see the thing work in enough detail to believe it. Executives need to see the consequence of it working in enough detail to fund it. Those are different demos.

So run both, in the same hour, deliberately alternating. Depth for the operators, then a thirty-second climb-out for the exec. Depth, climb-out. Depth, climb-out. The rhythm matters more than the content, because the climb-outs are what keep the senior person in the evaluation instead of drifting into email.

This is the whole structural idea behind the way I approach demos for a managing partner, litigation chair and risk committee in the same room, where the associates want to see document handling and the risk committee wants to know about privilege and malpractice exposure, and neither group finds the other's segment interesting. Same problem in a clinical demo for a CMIO who has already killed two vendors — the nurses want the click count in the workflow, the CMIO wants to know what happens to the safety review and whether this creates a new place for an error to hide. If you run one demo for both, you lose the one with the veto.

A good test before the call: write down, in one sentence, what the exec should be able to say to their boss after this demo. If you cannot write that sentence, you have not built the second track.

Ask direct questions that give people an exit

The fear that stops reps from addressing an exec by name is that it will feel like being put on the spot. It will, if you ask a question they cannot answer well. "Sarah, what do you think?" is an ambush dressed as inclusion.

The format that works is: name, context, specific either/or.

"Sarah — you mentioned the planning cycle. Does something like this typically get decided inside the quarter, or does it need to wait for the annual?"

"Sarah, quick one while we're here. Is the priority on this the cost side or the risk side? Because it changes what I'd show you next."

Both give the exec a way to answer in three words and look decisive doing it. Neither asks them to evaluate the product, which is the thing they don't want to do out loud in front of their team.

In brokerage and wealth leadership rooms this matters more than anywhere, because the seniority gradient is steep and the junior people will not contradict the senior one — so if you do not get a direct read from the person at the top, you have not got a read at all. That dynamic drives a lot of how I'd structure a demo for wealth management buyers: the room defers, and deference looks exactly like consensus until the deal stalls.

Get the private read afterwards

The last piece, and the one nobody does. Send the exec a separate note. Not the group recap. A short one, to them only, same day:

Sarah — thanks for the time today. I know most of that hour was aimed at the operational team, so I wanted to send you the short version: the reason we think this matters for you is [one sentence on the outcome], and the main thing it will cost you is [one sentence on the honest cost].

If it's useful, I'm happy to do fifteen minutes with just you on the business case rather than the product. If it's not the right time, I'd genuinely rather know that now than chase it.

That last line does more work than everything above it. You have made "no" a low-friction, respectable answer, which means the answer you get is the true one. Some percentage of the time — and I am not going to pretend to know what percentage — you get back a two-line email that tells you the deal was never real, and you free up a month of forecast hygiene. The rest of the time you get a fifteen-minute call with the actual decision-maker, alone, where they will say the thing they would not say in front of their team.

The thing to take away

A quiet stakeholder is data. Treat the silence as an event that requires a response, the same way you would treat a hard objection, because it is a hard objection that has simply gone unspoken.

And if you want to get better at the direct-address question — the one where you say someone's name out loud in a room of six people and ask them something real without it landing as an ambush — that is a muscle, not a script. It is worth rehearsing before you spend it on a live call with a budget holder on the line. Practising exactly that kind of moment against a room that pushes back is what I built DrillCall for, and it is where I would put my reps' reps if I were running a team facing multi-stakeholder demos every week.

The exec who never unmutes is not disengaged. They are waiting for someone to talk to them. Usually nobody does.