Demo Teardown: The Room Went Quiet at Minute Nine and Never Came Back

The call

Three people on the invite. A managing partner, the head of the litigation group, and one member of the firm's risk committee. Forty-five minutes. The rep had done real discovery with the litigation chair two weeks earlier, had a champion, had a use case, had a live sandbox with the firm's own document types loaded in. This was not a bad rep and it was not a cold room.

Minutes one through eight were good. Better than good. He opened with a recap of what the chair had told him, got a nod, shared his screen, and started walking a single matter from intake through to a first draft. The chair interrupted twice, both times to ask how something would work with their document management system. Those are buying questions. The managing partner asked what the associates would stop doing. Also a buying question.

Then at about minute nine, the risk committee member spoke for the first time. She asked, roughly: "When one of our associates relies on this and it turns out to be wrong, what happens?"

And the rep said: "Great question — so every output is fully cited, you can see the source paragraph for each claim right here in the citation panel, and nothing gets generated without a traceable source."

He clicked the panel. He showed her. It was a good panel.

She said, "Okay."

And that was the last thing anyone on that call said that wasn't a pleasantry. The chair's questions stopped. The managing partner's camera stayed on but his answers got shorter. The rep finished the demo, asked about next steps, got a "send us the security documentation and we'll circle up internally," and ended four minutes early. Everyone was polite. The deal never moved again.

This is the most common way a multi stakeholder demo dies, and almost nobody who runs one can tell you the moment it happened. So here is the teardown.

Silence in a committee is not boredom

When a room goes quiet, most reps read it as one of two things: they're bored, or they're absorbing. On a demo that three senior people cleared their calendars for, boredom is rare. Absorbing is real but it's brief — people who are absorbing come back with a question inside a minute or two.

Sustained silence in a room with more than two buyers in it is almost always the third thing: private disagreement that nobody wants to have in front of the others.

Think about what it costs the risk committee member to keep talking after that answer. She asked about liability. She got told about a feature. She now believes one of two things — either this rep doesn't understand her job, or this product hasn't been built with her job in mind. Neither of those is something she wants to say out loud in front of the managing partner, because saying it out loud means she is the person who killed the litigation chair's project, on the record, in a meeting. That is expensive.

Waiting is cheap. She can say nothing for thirty minutes, be perfectly pleasant, and then in the hallway or on Slack say a single sentence — "I'm not comfortable with the exposure on this yet" — and the project quietly drops down the list. No confrontation. No meeting where she was the villain. From your side it looks like the deal went cold. From her side, she raised it, you didn't take it seriously, and she moved on.

So silence is not the absence of an objection. It is an objection that has decided to travel by a different route.

The tells are consistent and they show up together. Questions stop. Answers shorten into "makes sense" and "got it." The chat goes dead. Somebody who was leaning in sits back. And the call ends on time or early, which on a demo where things are going well almost never happens — good demos run over because people keep asking.

Why the feature answer did the damage

The rep's answer was accurate. That's what makes this worth taking apart, because "be accurate" doesn't save you here.

A feature answer assumes the product works. A risk question assumes it doesn't. That's the whole mismatch. She was not asking how the system prevents errors. She was asking what the firm does on the day the system produces one anyway, an associate doesn't catch it, and it goes out the door with the firm's name on it. The citation panel is an answer to the first question. She asked the second one.

There's a second problem, and it's the one I see more often: he answered fast. Speed reads as confidence to your champion and as dismissal to your skeptic. When someone raises the thing that keeps them up at night and you have a smooth, polished, immediate response, what you have communicated is that their concern is a common objection you handle rather than a real problem you have thought about. The risk person now knows exactly how much this has been considered: enough to have a slide about it.

And there's a third. He answered her, then immediately went back to the demo. He never checked whether the answer landed. "Okay" is not agreement. "Okay" is a person closing a door.

The move nobody makes: stop the demo

The single most valuable thing you can do when a room goes quiet is stop demoing. And essentially nobody does it, because the shared screen is a shield. As long as you're clicking, the meeting is happening, and you don't have to find out what people think.

Stopping is uncomfortable for a moment and then it becomes the most productive part of the call. Here's the version I'd want a rep to have practiced until it's boring:

Stop sharing. Not minimize — actually stop, so your face is the thing on the screen. Then name the silence, out loud, without apologizing for it.

The three-sentence recovery

Three sentences. In this order, for a reason.

One: name what you did, not what they did.

"I want to go back to your question — I gave you a product answer to a liability question, and I don't think it landed."

You are not asking her why she went quiet. You're not saying "you seem hesitant." Never make the quiet person account for their silence in front of their colleagues; that's the exact cost they were avoiding. You take it. You made the error, you're naming the error, and the room's temperature drops immediately because nobody has been put on the spot.

Two: restate their question harder than they asked it.

"What I think you're actually asking is: when an associate relies on this, doesn't catch that it's wrong, and it goes to a client — whose name is on that, what does the firm say, and does anything about that change because we're in the picture."

This is the sentence that does the work. When you restate a skeptic's concern in a form more severe than they were willing to say out loud, you prove three things at once — you understood, you're not afraid of it, and you're not going to make them do the work of dragging it out of you. In my experience it is the fastest way to convert a quiet objector into a talking one, and a talking objector is a deal you can still work.

Saying it harder than they did also gives them somewhere to go. Very often the response is "well, not quite that far — my real concern is narrower," and now they're negotiating the size of their own objection instead of nursing it.

Three: hand them the meeting, with a door behind it.

"Can I stop the demo and take that properly for the next few minutes, or would you rather I finish the workflow and we handle it separately?"

This one gets skipped and it shouldn't. You are asking a room of senior people for permission to change the agenda they agreed to, which is the polite move, but more than that you're running a test. If she says "yes, let's take it now," the objection is live and central and you've just been handed the real meeting. If the managing partner says "finish the demo, we'll come back to it," you've learned that the partner is protecting the momentum — which tells you something useful about who wants this. And if she says "no, it's fine, keep going," that's the worst answer, and you now know the deal has a hidden blocker, which is still better than not knowing.

After the recovery, do not resume the demo immediately. Ask the other two whether it's their question too: "Is that the same thing you're weighing, or is yours different?" That converts a one-on-one exchange into a room conversation, and it stops the chair and the partner from sitting there silently forming their own private opinions about how you handled it. A room that is talking to each other in front of you is a room that is buying.

Prepping a demo where three people want three different things

Most of this is lost before you share your screen. Here's the prep I'd want done.

Write down, for each attendee, not their title but the thing they are personally accountable for when it goes badly. The managing partner is accountable for the firm's money and the firm's name. The litigation chair is accountable for whether his people actually use this and whether it makes their day better or worse. The risk committee member is accountable for the worst day. Three different jobs, one demo.

Then write the one question each of them is going to ask that you cannot fully answer. Not the easy one. The one you'd rather they forgot. Then prepare the answer to the scariest of the three and rehearse it out loud, because the difference between a written answer and a spoken one is enormous under pressure.

Sequence by veto, not by seniority. The instinct is to aim the demo at the most senior person in the room. Wrong instinct. Aim it at whoever can stop it. In a law firm that's frequently the risk seat, and the managing partner will not be offended — partners are used to risk having a say, and watching you take risk seriously is itself a signal about how you'll behave once you're a vendor.

Then say the plan out loud before you share, and be specific about who should watch what:

"I'm going to run one matter end to end. Chair, the part I want your read on is the associate handoff in the middle — tell me if that's how your people actually work. I'm going to stop twice, deliberately, to show what happens when the system gets something wrong, because I'd rather you see that from me than find it later. And I'll close on what this does to write-offs."

That paragraph does something structural: it pre-authorizes interruption, and it tells the risk person that her moment is coming, so she doesn't have to decide whether to fight for airtime. Rooms that have been given explicit permission to interrupt do not go quiet. Rooms that have been talked at for nine minutes do. I've written the longer version of this sequencing in the legal demo script for a managing partner, litigation chair and risk committee, including where to put the deliberate failure demonstrations.

The shape isn't specific to law firms. A freight and 3PL demo room comes in looking for where it breaks, and clinical operations buyers do the same thing — different vocabulary, same instinct, same silence when you answer the breakage question with a feature.

Knowing which of the three is your real buyer

The economic buyer and the real buyer are frequently not the same person. The economic buyer signs. The real buyer is the one whose problem is bad enough that they will spend political capital to get this done — chase the other two, defend the line item, answer the risk memo, follow up in the hallway. Without a real buyer, you have a committee that is mildly interested, and mildly interested committees don't buy.

You can usually tell before the demo starts. Who booked the meeting. Who replied when you had to move it. Who added the other two to the invite. Who says "we need to fix this" versus "they've been complaining about this." Who can describe what happens if the firm does nothing, in specifics, with a date attached.

And ask, on the pre-call, the two-part version of a question most reps only ask half of: "If this goes well, who signs it — and separately, who has to not object?" Those are different people and different jobs. Getting the second name is what stops minute nine from being a surprise.

One last thing about the veto. Your goal with the risk seat is not enthusiasm. You are not going to make a risk committee member excited about a legal AI tool, and if you think you have, you've misread the room. What you're going for is a specific, low-key sentence: I have no reason to block this. That's the win condition. Design her portion of the demo to produce that sentence and nothing more.

What I'd do next

Pick the question in your current live deal that you least want asked — the one you'd quietly hope doesn't come up — and practice the three-sentence recovery against it out loud until it's dull. Not written. Out loud, at speaking pace, with someone pushing back. That's the gap DrillCall exists to close: AI role play where the room asks the hard question at minute nine and doesn't accept the feature answer, so the first time you hear it isn't in front of a managing partner. Silence in a committee demo is a skill problem, and skill problems get fixed with reps, not with a better slide.