Demo Teardown: The Feature Tour That Lost the Room in Minute Six

Why I tear down demos instead of coaching them

Telling a rep "be more consultative" does nothing. Telling a rep "at 5:40 you said I'll get to that in a moment and you never got the room back" does something, because they can hear it. So I want to walk a full demo, in order, and stop at each place it bled out.

What follows is a composite. I have listened to a lot of demos, and this one is stitched from the same mistakes showing up in the same order, with one consistent set of details so the thing holds together as a story. The company, the product and the people are disguised. The mistakes are not.

Setup: a mid-market operations platform. Deal in the low five figures annually. Discovery had gone well — genuinely well, which is what makes this painful. The rep, call him Marcus, had run a solid first call two weeks earlier with the champion, an ops manager. On that call the champion said three things that mattered. His team was rebuilding the same schedule by hand every morning. That rebuild took his lead about ninety minutes a day. And when a job got rescheduled after 4pm, nobody downstream found out until the next shift showed up.

That is a gift. That is a demo that writes itself. Ninety minutes a day, the 4pm problem, the manual rebuild. Three hooks, all in the buyer's own words.

The demo ran thirty-eight minutes. Four people in the room on their side: the champion, his VP, the operations lead who does the ninety-minute rebuild, and someone from IT who joined late and left early. The deal did not close. It did not officially die either, which is worse. It went to "let's circle back after the quarter" and then it went nowhere.

Here is where it went.

Minutes 0 to 4: the company intro nobody asked for

Marcus opens fine. Good energy, names everyone, confirms the time. Then:

"Before I jump in, let me give you just a bit of background on us. We were founded in 2016 by two operations guys who were frustrated with…"

And we are off. Four minutes on the founding story, the funding, the logo slide, the three pillars of the platform, and a customer quote from a company in a different industry.

Nobody asked for this. The champion had already been on a call, already seen the website, already sold the story internally to get these people in the room. The VP is checking something on her laptop by minute two. That is not rudeness. That is a person correctly reading that the next four minutes contain nothing she needs.

Here is the real cost. Those four minutes are the most attention you will ever have. It is the only moment when everyone is fresh, nobody has an objection loaded, and the room is deciding whether this is going to be worth their time or something to endure. Spending it on your Series A is a choice to be endured.

The replacement line. Open by handing the agenda back to them, built out of what your champion told you:

"Dave told me two weeks ago that your team rebuilds the schedule by hand every morning, that it takes Priya about ninety minutes, and that when something moves after 4pm the next shift finds out the hard way. I built today around those three things. I'm going to show you the morning rebuild first, because that's the one with a number attached. Before I start — Priya, Dave described your morning to me secondhand. What did he get wrong?"

That does four jobs in twenty seconds. It proves you listened. It puts the agenda in their language. It hands the first real speaking turn to the person who has to live with the tool. And it invites a correction, which is the cheapest way in the world to find out what discovery missed.

Notice what I did not do: I did not ask "so, any questions before we dive in?" That question gets you silence and nothing else. Ask a specific person a specific thing they know the answer to.

Minute 5:40: the interruption, and the six words that killed it

Marcus finally shares his screen and starts on the dashboard. Forty seconds in, the operations lead — Priya, the one who does the ninety minutes — speaks for the first time:

Priya: "Sorry, can I ask — if I move a job on that view, does it push to the guys' phones or do I still have to text them?"

This is the single best moment of the entire call. She has stopped listening to the tour and started imagining Tuesday morning. She used the word I. She described her actual workaround, which is texting people. That question is the deal.

Marcus: "Great question. I'll get to that in a moment — that's actually coming up in the notifications section."

And he goes back to the dashboard.

I have heard some version of that line in almost every bad demo I have sat through. It always sounds reasonable. The rep has a structure, the question is out of order, and the answer is genuinely three slides away. The logic is fine and the effect is a disaster.

What Priya hears is: my question is less important than your sequence. She will not ask a second one. And she is the person whose ninety minutes are the entire business case.

The replacement line. Answer it. Immediately, in the product, out of order, badly if necessary:

"It pushes. Let me just do it — I'll drag this job to 2pm and you'll see the notification fire on the mobile view here. So no texting. Is texting how you handle it now, or do you call?"

Twenty seconds. Then you ask a question back, because her interruption told you where her pain actually is and you would be an idiot not to dig there. If it breaks your flow, your flow was too rigid. If you genuinely cannot show it — the honest answer is "we can't do that today, here's what people do instead" — say that, in that second, and take the hit while it is cheap.

Interrupting buyers are not a problem to manage. They are the only ones telling you the truth. I have written whole scripts around this, like the manufacturing demo script for plant managers who interrupt, because in some rooms the interruption is the meeting and the deck is just an excuse to get everyone on the call.

Minute 9: the notebook closes

On the recording you can hear it, or rather you can see it if there is video. Priya had been taking notes. Somewhere around minute nine, she stops, sits back, and does not write again for the rest of the call.

What happened in between? Marcus finished the dashboard, moved to the reporting module, and said the word "robust" twice.

Here is what I want reps to internalise about that moment. The person who stops taking notes has decided the tool is not for them. They have not decided it is bad. They have decided it is somebody else's decision. And once the daily user has mentally handed the decision to their VP, you have lost the only advocate who could have made this urgent, because the VP does not have ninety minutes a day back — Priya does.

There is no replacement line for minute nine. Minute nine is a symptom. The fix was at 5:40. That is why I tear these down in order: most of the damage in a bad demo is done in one specific place and then just accumulates.

If you want a habit that catches this in flight: every five or six minutes, name a person and ask them something concrete. "Priya, on your Tuesday, would you run this from the desktop or the tablet?" You are not being polite. You are taking the room's temperature. A one-word answer from someone who was engaged ten minutes ago means back up and find out what you lost them on.

Minutes 14 and 22: two buying signals, both walked past

Signal one, minute 14, from the VP:

"Does this replace what we're doing in the spreadsheet, or does it sit alongside it?"

That is not a feature question. That is a woman doing implementation maths in her head. She is asking what happens to the artefact her team has built their entire morning around. Marcus says "you can absolutely import from Excel" and keeps clicking.

The replacement line:

"It replaces it. And that's the part I'd want to be careful with, because that spreadsheet is how your team thinks, not just where the data lives. What normally happens is we mirror it for the first two weeks so nobody's flying blind, then it goes away. Is that spreadsheet yours, or does Priya own it?"

You answered the question, you named the risk before they had to, and you found out who owns the thing you are about to take away. That last part will decide whether this deal survives implementation.

Signal two, minute 22, from the champion:

"How long does it usually take to get set up? Just roughly."

"Just roughly" is what people say when they are asking a real question and pretending it is a small one. He is not curious. He is trying to work out whether he can get this live before the busy season, which means he is picturing owning it.

Marcus says "it varies, but it's pretty quick" and moves on.

The replacement line:

"Depends on the two things I'd want to check with IT. But let me flip it — is there a date you're working back from? Because if there's a season you need this in front of, that changes what we do first."

You do not need a precise timeline. You need to know what is behind the question. Every timeline question is a deadline question wearing a disguise, and the deadline is the only thing that will make this deal move this quarter instead of next.

Two signals, both of them the buyer leaning forward, both answered as though they were trivia. This is the most common failure I see in demos that are otherwise competent. The rep is so busy driving that they treat questions as interruptions to the drive. The questions are the road.

Minute 31: the screen with no number attached

At minute 31, with seven minutes left, Marcus opens the analytics module. Custom dashboards. Filterable. He is proud of it and it is genuinely good software.

Not one person in that room mentioned reporting. Not in discovery, not on the call. The champion talked about a manual rebuild, ninety minutes, and the 4pm problem. Nobody said "and we can't see our data."

So here is the rule I would tattoo on the inside of a rep's eyelids: do not show a screen you cannot tie to a number the buyer gave you. Not a number from your case study. A number out of their mouth. Ninety minutes. The 4pm handoff. If a screen does not connect to one of those, it is not a demo, it is a tour, and tours are how you fill time you should be spending on the close.

Those seven minutes were the ones Marcus needed at the end. He spent them on a module nobody asked about, which meant the ask got squeezed into the last ninety seconds while people were reaching for their next meeting.

That discipline gets harder in rooms with mixed seniority, where you are tempted to show something for everyone. It is not a coverage exercise. In the real estate demo script for principals who interrupt I make the same argument: pick the one workflow the loudest person in the room described, run it end to end, and let the rest come up as questions.

Minute 36: the ask that gave the room permission to leave

Marcus: "So that's the platform. I know we're coming up on time — I'll send over the deck and some materials, and maybe we can find some time to circle back once you've had a chance to digest?" VP: "Yeah, let's circle back after the quarter." Marcus: "Perfect. I'll follow up."

Every word of that is the rep asking for less than nothing. "Maybe." "Find some time." "Circle back." "Once you've had a chance." He offered them the easiest possible exit and they took it, politely, the way anyone would.

And "I'll follow up" means there is no next meeting in anyone's calendar, which means the deal now depends on Marcus's persistence rather than the buyer's momentum. Those are not the same thing and only one of them closes.

The replacement:

"Before we drop — Priya, you asked about the phone notifications early on and I want to make sure that landed. Did it?

Here's what I'd suggest. The number that matters here is the ninety minutes a morning. I'd rather prove that than argue about it, so give me your last two weeks of schedules and I'll load them into a sandbox and run your actual Tuesday. That's a couple of hours on my side and about twenty minutes on Priya's.

Can we put thirty minutes in the diary for next Thursday to look at it? Dave, is Thursday morning workable for you?"

Specific ask, small commitment from them, a date, and a named person to answer. Compare that to "maybe we can circle back." Same deal, same product, completely different meeting.

If they say no to that, you have learned something valuable and cheap: this is not a priority. Far better to know at minute 38 than after six weeks of follow-up emails. Rooms full of people looking for reasons to say no are their own discipline, which is why the freight and 3PL demo script is built around forcing the objection into the open before the call ends rather than letting it walk out the door unspoken.

The three rules this teardown proves

Answer interruptions immediately. Out of order, in the product, even badly. "I'll get to that in a moment" is the most expensive sentence in software sales because it teaches the one person you needed to convince that their question is an inconvenience. There is no structure worth losing a live buyer for.

Show the workflow they described in discovery. Not your best workflow. Theirs. In their words, with their job names and their Tuesday morning. A demo is not a product overview, it is a rehearsal of their week with your tool in it, and if you did discovery properly you already have the script.

Never demo a screen you cannot tie to a number they gave you. Ninety minutes a day. The 4pm handoff. If you cannot say out loud which of their numbers this screen moves, close the tab. You will need those minutes at the end, and the end is where deals actually get made or lost.

None of this is complicated. All of it is hard under pressure, when the room goes quiet and the instinct is to fill the silence with features you know well.

What I would do next

If I were coaching Marcus, I would not send him a document. I would make him run the 5:40 moment twenty times until answering an out-of-order question in the product felt like less work than deflecting it. That is a reps-under-pressure problem, not a knowledge problem — he already knew the answer, he just had a plan and the plan won. That is exactly the kind of thing we built DrillCall for: putting reps in front of a buyer who interrupts at the wrong moment, over and over, until the right response is the reflex instead of the thing they think of in the car afterwards. Pull your own last lost demo, find the minute the room went quiet, and drill that one minute. It is usually the whole deal.