Demo Teardown: Everyone Said Yes and Nobody Said Who Would Run It

Every rep has one of these in their pipeline right now. The demo where nothing went wrong.

The room showed up. Cameras on. Someone asked a genuinely sharp question about the API. The VP said "this looks great, send over pricing." You hung up, moved the opp to Proposal, and told your manager it was the cleanest call you'd run that month.

Then four weeks of nothing. A polite reply to your third follow-up saying they're still discussing internally. Then closed-lost, no decision, revisit next fiscal.

I have sat in on a lot of these calls, both as the rep and as the guy listening in on the back of the line, and the pattern that shows up most often is not a pricing problem or a competitor problem. It is that everyone in the room said yes and nobody in the room said who would run it. The deal didn't lose. It just never had an owner, and a thing with no owner does not survive contact with a budget cycle.

So let's tear one down. What follows is a composite — the specific lines are stitched together from the same conversation I have watched play out again and again across ops-heavy buyers, but the failure is identical every time. The point isn't the transcript. The point is the three moments the rep sailed past, and what you say instead.

The setup

Mid-market company. Four people on the call. A VP who owns the budget, a director who booked the meeting, an ops lead who joined late, and a technical person who was mostly there to make sure nothing exploded.

The rep did a lot right. Short recap of discovery. Didn't open with a company slide. Got into the product inside six minutes. Handled a hard question about data residency by admitting the limitation and saying what the workaround was.

By every visible measure it was a good demo. Engagement was high. The VP leaned in twice. Nobody multitasked.

And it was dead before the call ended, because of three exchanges that sounded like buying signals and were actually the opposite.

Moment one: the passive voice

About eleven minutes in, the rep showed the alerting view and asked how they were handling that today.

The director said: "Right now it's pretty manual. The team would use this a lot."

The rep said "great" and kept going.

Read that answer again. The team would use this. Not "my team." Not "Sarah's group would live in this." The team. Passive, ownerless, hypothetical. It is the grammatical equivalent of a shrug.

When a buyer describes future usage in the passive voice, they are describing a benefit that will accrue to somebody who is not in the room and whose calendar they have not checked. It feels like enthusiasm because the words are positive. It is actually the buyer telling you, in the politest possible way, that they have not thought about who does the work.

Compare it to what a real owner sounds like. A real owner says "I'd have Dave in here every morning before standup." A real owner uses names, times of day, and existing rituals. They have already run the movie in their head and you're just confirming the details.

The rep heard positive sentiment and banked it. What he should have heard was a gap, and the gap has a follow-up question attached to it: which team, and what would they stop doing to make room for this?

That second half is the part reps skip because it feels negative. It is not negative. It is the single most useful thing you can ask in a demo, because the answer tells you whether this is a new job or a replacement job. A replacement job survives. A new job needs headcount, and headcount needs a plan, and nobody on that call had one.

Moment two: nobody answered "who does this today"

The rep did ask a version of the right question. Around minute nineteen he said, "So who's handling this today?"

The director said: "It's kind of spread across a few people. It's part of why we're looking."

The rep said "makes sense, that's exactly the problem we solve" and moved to the next screen.

Here is the thing about "it's spread across a few people." That is not an answer. It is a non-answer that sounds like an answer because it contains a diagnosis of their own pain. The rep got a sentence that agreed with his pitch, so he took it and ran.

But the question was never really about today. "Who does this today" is a proxy for "who will do this tomorrow," and when the answer is nobody in particular, the tomorrow answer is also nobody in particular. Diffuse ownership does not concentrate itself because you bought software. It stays diffuse, and then the tool goes unused, and then somebody notices the line item in Q3 and kills it.

What the rep needed to do was refuse to move on. Not aggressively. Just:

"Spread across a few people — got it. If this were live next month, whose name is on it? Not who touches it, who's accountable when it breaks at 6am."

That question is uncomfortable to ask on a demo. It sounds like you're auditing them. In practice, buyers respect it, because it is the exact question their own boss is going to ask them the moment they walk into the budget conversation. You are rehearsing them for the meeting you will not be in.

And if the honest answer is "we don't know yet," you have just learned the most important fact about this deal, in minute nineteen, when there is still time to do something about it. That beats learning it in week five from silence.

I want to be precise about the failure here, because it is subtle. The rep asked the right question. He just accepted the first thing that came back. Most of the demo calls I have listened to fail on the second question, not the first. Reps have been trained to ask; they have not been trained to sit in the pause when the answer is mush.

Moment three: the ops lead asked about staffing twice and got features both times

This is the one that actually killed it.

The ops lead — the person who joined late, who had said almost nothing — asked two questions in the back half of the call.

The first: "How much setup is there on our side?"

The rep answered with implementation speed. Talked about the connector library, said most customers are live in a couple of weeks, mentioned that the onboarding team handles the mapping.

The second, ten minutes later: "And once it's running, is this something someone's checking daily, or does it just run?"

The rep answered with automation. Said the alerts are push-based so you don't have to go looking, said the digest email covers most of it.

Both answers were true. Both answers were about the product. Neither answer was about her.

She was not asking about setup time. She was asking whether she was about to be handed a new responsibility with no additional people. She asked it twice, in two different shapes, because the first answer didn't land. And when the second answer also came back as a feature, she stopped asking. She went quiet for the rest of the call and nodded along at the end.

That silence read as agreement. It was a decision.

The ops lead is almost always the person who decides whether these deals live, and she is almost never the person the rep is presenting to. Everyone above her is evaluating whether the outcome is worth the money. She is evaluating whether the work is going to land on her desk on a Friday afternoon. If you never speak to that, she will not fight you in the meeting — she will simply not advocate, and an internal purchase with no advocate dies of natural causes.

What the answer should have sounded like:

"Let me answer that as a staffing question rather than a product question, because I think that's what you're actually asking. Day to day, somebody owns the queue — usually that's fifteen minutes in the morning, and it's typically a person who's already doing a version of that work in a spreadsheet. It's not a new hire. It's a job that moves. Does that match how you'd want to run it, or does that fifteen minutes not exist right now?"

Notice what that does. It names the work. It names the shape of the person who does it. And then it hands the question back and asks her to confirm or deny, out loud, in front of the VP who controls the budget.

That last part matters more than the answer.

The fix: one question before you build the second half

Here is the change I would make to how you run these, and it costs you nothing.

Do not build your whole demo before the call. Build the first half. Then, somewhere around the midpoint, before you go into the deeper workflow, ask the ownership question and let the answer decide what you show next.

The question is some version of:

"Before I go further — if you moved forward, whose day changes? I want to make sure the next part of this is aimed at the right person's job."

That framing is the whole trick. You are not interrogating their org chart. You are asking permission to be useful. Nobody refuses that.

And the answer sorts the deal into one of three buckets immediately.

They name a person who is on the call. Best case. Now the rest of the demo is for that person. Talk to them by name. Show the screens they'd live in, not the screens the VP finds impressive. Every time you show something, check it against their week: "Is that Monday morning for you, or is that something you'd look at when something's already gone wrong?"

They name a person who is not on the call. Fine, and now you have a clear next step that isn't "send pricing." You need that person in a room. Say so: "Then I'd want twenty minutes with them before we talk numbers — not a re-demo, just so they can tell me whether this fits how they actually work." That is a better next meeting than a proposal review, and it is far easier to get.

They can't name anyone. This is the composite call. And the honest thing to do — the thing that saves you four weeks — is to say it plainly: "Okay. Then I think the real question isn't whether the software works, it's who runs it. Can we spend the last ten minutes on that instead of me showing you more screens?"

I have never had a buyer be offended by that. I have had buyers visibly relax, because you just said the thing they were already worried about and gave them cover to talk about it.

This is also why demo structure has to flex by who's in the room. A plant manager who interrupts you every ninety seconds is telling you exactly where the ownership friction is if you let the interruptions steer, and a VP of operations in construction who has already been burned by one rollout is not evaluating your product at all — they are evaluating whether the last failure was the vendor's fault or their own staffing. Same for a telecom team that's been through an AIOps deployment nobody had time to tune. The demo is the same. The ownership conversation is completely different, and you cannot script it in advance if you haven't asked who's going to do the work.

How to run the last five minutes

The close of a demo is where most reps get vague on purpose. They want the good feeling to survive to the follow-up email. So they say "I'll send over the recording and some pricing, and we'll go from there," and everybody nods, and the good feeling evaporates on the drive home.

Instead, spend the last five minutes naming the owner out loud.

Start by saying what you heard: "So if I've got this right, this would sit with Sarah's team, and Marcus would be the one in it day to day." Then stop talking. Let somebody correct you. If they correct you, that correction is worth more than the entire demo.

Then ask the confirming question directly to the person who was named, if they're there: "Marcus, is that how you'd want it? Or is that not realistic given what's on your plate right now?"

Give them a genuine door to say no. If they take it, you have not lost anything — you have found out now, with the VP listening, that the operational plan doesn't exist. That conversation is a deal you can still fix. Silence is a deal you cannot.

And if nobody was named, close on that gap instead of pretending it isn't there:

"One thing I'd flag before pricing. Everything we talked about assumes somebody owns this once it's live, and I don't think we landed on who that is. In my experience that's the thing that decides whether this works, more than anything about the software. Who inside the business would you want to have that conversation with, and can we get them into the next twenty minutes?"

That is a stronger close than "send the pricing." It moves the deal to the real blocker instead of the imaginary one. And it means your follow-up email has a subject that isn't a proposal — it's a named person and a calendar invite.

What good looks like

A demo where nobody said who would run it is not a demo you won. It is a demo you enjoyed.

The tell is in the language. Passive voice about future usage. "Spread across a few people" as an answer to who owns it today. An ops person asking the same worry twice in different words and getting a feature both times, then going quiet. Any one of those, on its own, is worth stopping the demo to chase. All three together and you should assume the deal is already gone unless you fix it live on the call.

The fix isn't a new discovery framework. It's asking one question at the midpoint, letting the answer reshape the second half, and refusing to end the call without a name said out loud by someone other than you.

If you want to get sharper at this specific moment, the thing I'd do is practice the second question — the one after the mush. Get a rep to give you "it's spread across a few people" and drill the follow-up until it comes out calm instead of confrontational. It's the kind of thing that's awkward the first ten times and automatic after that, which is most of why we built DrillCall to let reps rehearse these exchanges against a buyer who pushes back the way real ones do, before the call that matters.

Good questions and an engaged room are not a forecast. A name is.