Three People on the Demo and Only One Is Talking: How to Read the Quiet Ones

I have sat on a lot of demos where three or four people join, one of them talks the whole time, and everyone leaves feeling good. Then the deal dies eleven days later and nobody can tell you why.

Here is why. The meeting you ran was not the meeting that decided anything. The meeting that decided anything happened after you dropped off, when the four of them stayed on the call or walked back to a desk and the person who said nothing for twenty-five minutes finally opened their mouth. That person had one line ready. "I don't think this clears our data review." Or "we tried something like this at my last place." Or just "I didn't really follow what it does." One line, no pushback in the room, deal cooked.

So the skill in a multi-stakeholder demo is not the demo. Most reps can drive the product. The skill is running a room where the quiet ones get pulled into the conversation while you are still there to answer them.

The person talking is rarely the person to worry about

The loud one is usually your champion, or the person who booked the call, or the one whose problem is most obviously the thing you fix. They are talkative because they are already partway sold. Every question they ask is a question they want you to answer well, because they need ammunition for later.

That is nice. It is also not information you need. You already know what they think.

The security lead who joined two minutes late with their camera off, the ops manager who is clearly doing email, the person on the invite whose title you did not recognise and whose name you have not heard yet — those are the ones carrying risk. And the trap is that a quiet room feels like a good room. Nobody objecting feels like nobody objecting. It is not. It is objections being saved up for a cheaper venue.

I would rather have someone interrupt me at minute six with "this looks like the thing we ripped out last year" than have them say it to their boss on Thursday. In the first case I get to answer. In the second I get a polite email.

Four kinds of silence, and how to tell them apart

Silence is not one thing. If you treat all of it the same you will waste your rescue attempts on people who do not need rescuing and miss the one who does.

Bored

This is the person who is on the call because someone forwarded them the invite. They are not hostile. They just do not have a stake in this part of the conversation, and you are eleven minutes into a workflow that is not theirs.

Tells: camera off or camera on with obvious screen-glow eye movement. Delayed responses when addressed. Generic replies — "yeah, looks good." They will unmute for the scheduling part at the end and nothing else.

Bored is mostly harmless, but bored people vote with the majority in the debrief, and if the majority is negative they add weight to it. Bored is also fixable, because it is usually your fault — you are showing them something irrelevant to their day.

Sceptical

The dangerous one. Sceptical looks similar to bored from the outside, which is why people get it wrong.

Tells are different though. Sceptical people are watching. Camera on, usually. They are taking notes at odd moments — not when you say the headline thing, but when you skip over something. They ask one question, and it is a hard, specific question, and then they go quiet again once they have their answer. That is not disengagement. That is a person who got what they came for and is now scoring you.

If someone asks "where does the data sit" at minute nine and says nothing for the rest of the call, they did not lose interest. They are done evaluating.

Outranked

This is the person who has plenty to say and will not say it because their boss is on the call. Very common in rooms with a clear seniority gap. The manager two levels down knows exactly why your product will not work with the way their team actually operates, and they are not going to contradict the VP who is enthusiastic about it.

Tells: they answer when asked directly, and the answer is careful. They look at the senior person before they speak. They agree fast. Sometimes they will type something in the chat rather than say it out loud, which is a gift — take it seriously.

Outranked silence resolves badly for you because it does not stay silent. It comes out during implementation, or during the internal debate about scope, and by then the enthusiasm at the top has cooled and the person who never spoke turns out to be the one doing the work.

Not the buyer

Sometimes the quiet person is quiet because it genuinely is not their decision and they have no opinion worth having. Legal joined to hear whether there is anything alarming. Finance joined to hear a number. They are waiting for their two minutes and everything else is background noise.

This is fine. You just need to know which of the four you have got, because the treatment is different. Bored needs relevance. Sceptical needs a direct invitation to attack. Outranked needs cover. Not-the-buyer needs their two minutes early so they can leave, or at least stop worrying about when their bit is coming.

The first two minutes decide the rest

Everything above is much easier if you have not walked into the room blind. So the multi-stakeholder demo starts before you share your screen, and it starts with naming the roles out loud.

Here is roughly what I say, adapted to the room:

"Before I show anything — there are five of us and I don't want to spend twenty minutes on something that only matters to two people. Sarah, you and I have talked, so I know where you sit. Marcus, you're on the security side, is that right? And Priya, I've got you down as operations but tell me if that's wrong. What I'd like is one line from each of you: what would have to happen in the next forty minutes for this to have been worth your time?"

That last question does a lot of work. It is not "do you have any questions" — nobody has questions at minute one. It is asking for a condition. People find it easy to answer because it does not commit them to anything and it does not require them to have an opinion on your product yet.

What you get back is a list of exit criteria, in their words, that you can hold them to at the end. "For me it's just whether this touches PHI." "I want to see what happens when the file's malformed." "Honestly I want to know what my team has to do differently."

Write them down. Say them back. "Okay, so Marcus, PHI. Priya, change management for your team. Sarah, the reporting piece. I'll hit all three, and if I get to the end and I've missed yours, stop me."

Now every quiet person in the room has already spoken once, on the record, about something they care about. Pulling them back in later stops being an ambush and becomes a callback. That is the whole difference between "Marcus, thoughts?" — which is a horrible question to receive — and "Marcus, this is the PHI bit you asked about."

One warning. Do this with genuine brevity or you will burn eight minutes on introductions and the senior person will start checking the time. One line each. Move.

Allocating the screen time on purpose

Most demos are built for one persona because that is who the deck was made for. In a mixed room that means one person gets thirty minutes and everyone else gets scraps at the end when attention is gone.

I plan it the other way. If there are four people and forty minutes, I am not giving anyone forty. I am giving the primary user maybe half, and I am carving out a genuine, uninterrupted five for each of the others, and I am announcing the structure so people know their turn is coming.

"I'm going to spend most of this on the day-to-day workflow because that's what three of you live in. Marcus, around the twenty-five minute mark I'm going to switch entirely to how data moves and where it sits, and that section is yours — I'd rather you interrupt me constantly during it than save anything up."

The security or risk person almost never gets this. They are used to being an afterthought, asked at minute thirty-eight whether they have concerns, with the meeting already running long. Giving them a named slot changes their posture completely. I have watched people turn their camera on for it.

This matters more in some industries than others. In regulated rooms the quiet person is often the one with a veto and no incentive to use it politely — which is why the legal demo playbook for a managing partner, litigation chair and risk committee treats the risk seat as its own segment rather than a Q&A afterthought. Same logic in claims, where the insurance demo script for carrier buyers is built around the assumption that at least one person in the room is there specifically to find where the product breaks. If that person is silent, they have not stopped looking. They have found something.

And if you are selling into a room that has already been through a failed deployment, the silence is thicker still. The telecom demo script for a room that's been burned by AIOps exists because in those calls the quietest person is usually the engineer who owned the last tool, and their silence is not neutrality, it is a decision they made in the first five minutes.

The four rescue questions

When someone has been quiet too long, you need to bring them in without making it feel like a cold call in front of their colleagues. These four work. They all share a property: they are answerable without an opinion on your product.

"Does this look like how it actually works on your side, or is that a simplified version of your process?"

This one is nearly foolproof. You are asking about their world, not yours. Everybody can describe their own process, and almost everybody enjoys correcting an outsider's version of it. What comes back is usually the real objection dressed as a clarification — "well, we'd have three approvals there, not one" is an implementation concern wearing a hat.

"What would your team say if I showed them this on Monday?"

Good for the outranked. It lets them voice an objection that belongs to someone else. They are not disagreeing with their boss, they are reporting on their team. I have had people who said eleven words in twenty minutes give me two solid minutes of detail off this question.

"Am I showing you the part you care about, or should I skip ahead?"

The rescue for boredom. It is also honest. If they say skip ahead, skip ahead — you just bought back five minutes and a bit of credibility. The worst outcome is that you keep showing a person things they do not care about while telling yourself they are absorbing it.

"You went quiet after the integration bit — was that a problem or just note-taking?"

The direct one, for the sceptic. You have to say it lightly and you have to genuinely be fine with either answer. It works because it names what you noticed without accusing them of anything, and because sceptical people generally respect being read correctly. Half the time you get "no, just thinking" and half the time you get the objection, and the objection is what you came for.

What I avoid: "any questions?", "thoughts?", "how does that sound?" and the truly dire "Marcus, you've been quiet." All of them put the burden of framing on the other person, in front of colleagues, with no obvious safe answer. People respond to those with "nope, all good," which is the sentence that precedes a lost deal.

Reading the room while your screen is shared

Harder than it sounds, because when you are sharing you cannot see faces properly. A few habits help.

Stop sharing periodically. Genuinely stop, not minimise. Every eight or ten minutes, drop the share for thirty seconds to ask something. You get faces back, and the change of mode wakes people up.

Watch the chat, and treat anything typed there as a bigger signal than anything spoken. People type when they do not want to interrupt, or do not want to say it out loud. "Does this support SSO?" in chat from the quiet one at minute twelve is worth more than three minutes of enthusiasm from your champion.

Notice who is taking notes and when. Note-taking is engagement, even when it is silent. Someone writing during your pricing slide and nowhere else has told you their job on this call.

And count the unmutes. If a person has not unmuted by the halfway mark, that is your cue, not the end of the call.

If you failed to rescue them

Sometimes you get a room where one person genuinely will not engage. It happens. Do not pretend otherwise in the follow-up.

What I do is name it, privately, to the champion. Not "Marcus seemed negative" — you do not know that. Something like: "Marcus didn't say much and I couldn't tell whether that's because I didn't cover his area properly. Would it be worth me doing fifteen minutes with just him?" That gives your champion a reason to go find out, and it very often surfaces the objection before the debrief hardens into a decision.

The separate short call with the silent stakeholder is one of the highest-return meetings in enterprise sales and almost nobody books it. People will tell you things one-to-one that they would never say in front of four colleagues. Buyers who spend their whole day looking for failure modes — the pattern behind the freight and 3PL demo script for a room looking for where it breaks — will often lay the whole objection out for you in a fifteen-minute call, because there is no audience and no cost to being blunt.

Where I'd start

If I were trying to get better at this, I would not start with the demo flow. I would start with the first two minutes and the four rescue questions, because those are the parts you can say out loud until they stop sounding scripted. The role-naming open in particular sounds clumsy the first three times you do it and completely natural the fourth, and the only way through is reps.

That is what we built DrillCall for — running the same opening and the same rescue question against a room that pushes back, over and over, before you use it on a deal that matters. But you can do a version of it with a colleague pretending to be the quiet security lead who answers everything in four words. What you cannot do is improvise it live and hope. The room does not give you a second attempt, and the debrief is not a meeting you are invited to.