Demo Teardown: Three Buyers in the Room and the Rep Sold to Only One of Them

I have listened to this call in a dozen different versions across a dozen different industries, and the shape never changes. Three people join. One of them is warm. The rep finds that person in the first two minutes and spends the next forty talking to them. The other two go quiet, and the rep reads quiet as agreement.

So let me walk through one composite version of it, minute by minute, and then rewrite it. Names changed, industry blurred on purpose, because the pattern is what matters and the pattern is everywhere.

The room

Three people on the call. A managing partner who owns the budget and the relationship, an operations lead who owns the workflow the product would sit inside, and a risk person who owns the veto.

That last part is the whole post. The risk seat almost never owns the yes. The risk seat owns the no. Nobody in that chair has ever been promoted for approving software quickly. They get promoted for catching the thing that would have blown up in eighteen months. So they show up looking for where it breaks, and if you treat them as an obstacle to be managed around, they will do exactly the job they were hired to do.

The managing partner was the warm one. Camera on, nodding, said "love that" twice in the first five minutes. The ops lead had her camera on and her face flat. The risk person had his camera off from the start.

Camera off is not disengagement on its own. Plenty of people in risk and compliance roles keep the camera off as a default. But it does mean you have lost your only read on them, and if you are the kind of rep who navigates by facial feedback, you are now flying with one instrument down and you had better start asking questions instead of watching faces.

This rep navigated by facial feedback.

Minute by minute

Minutes zero to four: the open that picked a favourite

The rep opened with the standard: thanks for the time, quick recap of the discovery call, here is what I am going to show you today, stop me with questions.

The recap was accurate. It was also a recap of a discovery call that had happened with the managing partner and nobody else. Every problem statement in that open belonged to one person. "You mentioned last time that visibility across the practice was the big gap." You mentioned. Two people on that call had never mentioned anything, and the first thing they learned was that the agenda had been set without them.

The rep then said "stop me with questions" and moved straight into the screen share. That phrase is the single most over-trusted sentence in demo work. It sounds inclusive. It is actually an abdication. You have just told three people with different levels of comfort interrupting a stranger that the burden of getting their agenda into the room is on them. The confident one will interrupt. The other two will wait for a gap that never comes.

By minute four, the demo had a protagonist and two spectators.

Minutes four to eight: the ops lead does the math

The rep got into the core workflow. Intake, routing, review, sign-off. Clean product, clean click path, no dead ends. As a product walkthrough it was fine.

At around minute six, the rep said this: "and then your team just tags it here so the system knows where to send it."

Watch the ops lead's face on the recording at that line. She does not object. She does not ask a question. She writes something down, and her posture changes, and she does not speak again for the rest of the call except to say "no, I'm good" when asked at the end if she had questions.

What happened is that she did arithmetic. Your team just tags it here means her people are doing a thing they do not currently do, on every item, forever. She is the one who has to go tell them. She is the one who owns the adoption problem when they stop doing it in week three. The rep presented a tagging step as a feature. She heard headcount hours, a training session, and a new reason for her team to be annoyed with her.

That is the moment the deal actually died, and the rep did not notice, because at that exact second the managing partner said "that's clean."

Here is the rule I would carve into the desk. Every time your product asks a human to do a new thing, somebody in that room owns the cost of that new thing. Find them before you show it. If you cannot name who owns the cost, you are demoing to a fantasy org chart.

Minutes eight to nineteen: four questions, four one-line answers

The risk seat spoke four times. I want to lay these out because the pattern is brutal and it is extremely common.

Question one, at minute eight: "Where does the data sit?"

Answer: "It's all in our cloud, fully encrypted." Then straight back to the click path.

Question two, at minute eleven: "Who can see this view?"

Answer: "That's all permissioned, you can set that up however you like." Back to the click path.

Question three, at minute fourteen: "What happens if someone changes a record after it's been approved?"

Answer: "Yeah, there's a full audit trail." Back to the click path.

Question four, at minute nineteen: "Have you been through a review with anyone in our sector?"

Answer: "Definitely, we work with a bunch of firms like yours." Back to the click path.

Four questions. Four true answers. Four answers that were each about eight words long, none of which involved showing anything on the screen that was already open, and none of which ended with a question back.

And notice what those four questions actually were. They were not idle. They were a compliance review, delivered in real time, one question at a time, in the order that a person in that seat runs a compliance review. Data residency. Access control. Immutability of the record. Precedent in the sector. He was handing the rep a checklist and asking to be walked through it, and each time he was handed a sentence and a closed door.

By question four he was not evaluating the product any more. He was gathering evidence for the internal conversation where he says "I asked and I did not get a straight answer." That conversation happens without you in the room and you cannot win it retroactively.

The uncomfortable part is that the rep thought those exchanges went well. Short question, short answer, back to the flow, no derailment. If you measure a demo by whether you got through your slides, that call was a triumph.

The summary

Minute thirty-eight, the wrap. "So just to bring it together — you get visibility across the whole practice, you get the reporting you were after, and it takes the manual chasing off your plate."

One agenda. The managing partner's agenda, from a discovery call the other two were not on.

Nothing in that summary was for the ops lead, whose entire concern was whether this made her team's week better or worse. Nothing in it was for the risk seat, who had asked four questions and heard four sentences. Then: "any other questions before we talk next steps?" Silence, one "no, I'm good," and a single next step aimed at the one person who was already convinced.

They went dark. Of course they did. Two of the three people on that call had no reason to reply to an email about a product that had been demonstrated to somebody else.

What actually went wrong

Strip it back and there are three failures, and only one of them is about the product.

The first is that the rep never assigned roles. Three people were in the room and the rep treated them as one audience with one set of needs. There is no such thing as a room. There are individuals with separate jobs in a decision, and if you do not name those jobs out loud, you are guessing at them silently.

The second is absorption. The rep absorbed every question rather than routing it. Somebody asks something, the rep answers, conversation closes, rep resumes. That is a support call, not a demo. In a room with three buyers, a question from one of them is your best available opportunity to get the other two talking, and every absorbed question is an opportunity spent on nothing.

The third is that the close was single-threaded in a multi-threaded room. One next step, aimed at the person who needed convincing least.

The rewrite

Open by naming each person's job in the decision

Before a single pixel of product, out loud, in the first ninety seconds:

"Before I share anything — there are three of you here and you are all looking at this for different reasons, so let me check I have those right. Sarah, you own the budget and you told me the gap is visibility across the practice. Maria, you own the workflow this would actually sit inside, so my guess is your question is whether this makes your team's week lighter or heavier — and I want to be straight with you, there is one step in here that adds work for them, so I want to show you that early rather than bury it. David, my assumption is you are here to find where this breaks, and I would rather you find it today than in month four. Have I got all three of those right, or should I move something?"

Read what that does. It tells each person there is a slot in the next forty minutes with their name on it, so they do not have to fight for one. It pre-empts the ops lead's arithmetic by admitting the cost before she finds it, which converts an ambush into a conversation. It tells the risk seat that finding problems is the assignment rather than the interruption, which is the only thing that seat ever wants to hear. And it ends with a question, so you find out in minute two whether you have the wrong model of the room, instead of finding out never.

Almost every rep I have watched worries this open takes too long. It takes under two minutes and it buys back the fifteen minutes you would otherwise spend demoing to a wall. The sector playbooks make the same move with different vocabulary — the legal demo script for a managing partner, litigation chair and risk committee opens by separating billing pressure from client-confidentiality exposure, because those two people will hear the identical screen completely differently.

Route questions instead of absorbing them

When the risk seat asks "where does the data sit," the absorbing answer is "our cloud, encrypted." The routing answer is:

"Good — let me actually show you rather than tell you, because I would rather you see the config than take my word for it. [Shares the relevant screen.] Here is where residency is set. Before I go further, is your concern residency specifically, or is it more about who has access once it is in there? Those are different answers and I do not want to give you the wrong one."

Then, having answered:

"Maria, that permissioning piece touches you too — is your team the one who would own who gets access to what, or does that sit with David's group?"

One question from one person just became a screen, a clarification, and a second person speaking. That is what routing buys. It also surfaces the org boundary between ops and risk, which is exactly the kind of thing that quietly kills implementations later.

The general form is simple enough to memorise. Show rather than assert. Ask which version of the question they are actually asking. Then hand it sideways to somebody who has not spoken.

And when a question comes in that you cannot answer, say so, name the person who can, and put a date on it in the same breath. The insurance claims demo script for carrier buyers who are hunting for where it breaks is built almost entirely around this, because in that room the whole audience is the risk seat and dodging even one question ends the evaluation.

Give the risk seat the room it asked for

Four questions in that call. Each one deserved a screen and a follow-up, not a sentence. If you have a security or compliance section you usually keep in reserve for the technical validation stage, and a person in that chair has now asked you four questions in a row, the reserve stage has arrived early. Go to it. "You have asked me four things now that all point the same direction — do you want me to stop the workflow tour and spend ten minutes here instead? I would rather use the time on your questions than finish my slides."

No risk person has ever said no to that.

Where it gets harder is a room that has already been sold this exact promise before and watched it fail. Those buyers do not ask four polite questions, they ask one hostile one and then wait, and you have to earn the rest — which is the whole premise of the telecoms demo script for a room that has already been burned by AIOps.

Close with three next steps that point the same direction

The rewritten wrap is not one summary and one ask. It is three summaries and three asks that converge:

"Let me close against what each of you came in with. Sarah — visibility across the practice, that is the dashboard we started on, and the next step there is getting your two other partners in front of it, which I would suggest we do next week. Maria — I showed you the tagging step and I am not going to pretend it is free. What I would like to do is thirty minutes with you and whoever runs that queue day to day, mapping it against how they work now, so you can tell me whether it is a fair trade. David — you asked me four things and I want to send you the security pack rather than have you take my word for any of it. If it raises more questions, I would rather have that call with you and our security lead than answer it myself badly. Three separate things, all of them pointing at the same decision. Does anyone want to swap theirs for something else?"

Three next steps. Each one belongs to somebody. Each one is small enough to say yes to without a meeting about the meeting. And critically, the ops lead's next step is an invitation to challenge you, which is the only kind of next step a sceptic ever accepts.

If all three land, you have three threads instead of one. If only two land, you know precisely who is not moving and why, in week one rather than week six.

The part you actually have to practise

None of this is hard to understand. It is hard to do live, at pace, while sharing a screen, when one person is nodding at you and two are not.

The rep in that teardown knew all of this in the abstract. What beat him was that the warm face was right there and the silent ones were not asking for anything. Reading a rewrite does not fix that. The only thing that fixes it is running the multi-stakeholder open enough times that naming three jobs out loud is what your mouth does under pressure instead of "stop me with questions."

So I would take the three-person open above, write it in your own words for your actual product, and run it out loud twenty times before your next demo with more than one buyer on it. Then run the routing move on each of the four risk questions until handing the question sideways is a reflex. That is exactly the drilling loop I built DrillCall for — practising a room that talks back, with a stakeholder who goes quiet on you and one who is hunting for the crack, so the first time you handle it is not in front of the people who own the veto.

The friendliest person in the room is rarely the one who decides. Sell to the two who are not smiling.