The most useful thing in a competitor’s demo is almost never what the rep is showing you. It is the handful of things they reliably skip, which are exactly the things your own reps can be coached to do instead.
Mystery Demo takes competitors’ demos as a genuine buyer on a client’s behalf, and those skips are much of what we bring back. We book the call, attend as a real prospect, and log exactly which doors go unopened, then hand back the recordings and that log on one Notion board. After enough of these, the gaps tell you more than the demo does.
In a typical competitor demo, the rep rarely asks what you use today, rarely takes a position on what matters to you, rarely says a price unprompted, rarely shows the screen you will work in every day, and rarely admits one thing the product cannot do. The script rarely has a line for any of it, and the other side rarely notices the openings it leaves, because nobody there is looking for them.
Reps Rarely Ask What You Use Today
The opening question is usually some version of “what are you trying to solve.” It sounds like discovery, but it mostly decides which slides to skip, not what the buyer needs.
The question that would shape the entire demo, “what are you using today,” gets quietly skipped. The honest answer might be a spreadsheet that is working fine, which is not a fun answer for a seller to hear, so the only person who mentions the current stack is the buyer, once the silence gets awkward.
In a typical demo the real questions run out early, and the current-stack question is rarely one of them. Weak discovery is common enough that the competitor who asks what you run today is the one a buyer remembers.
.png)
Reps Show the Whole Product Instead of What You Asked For
That demo is a familiar shape. The unprompted full-product tour is the pattern we would bet on first: book in as a marketing team of six needing one dashboard and you can still get the full tour, in a demo booked to see one screen.
What a competitor chooses to lead with on a call is its real positioning, and a full tour shows features without choosing what matters to this buyer:
| A demo fitted to the buyer | The full tour | |
|---|---|---|
| What it opens on | The screen the buyer booked the call to see | The permissions matrix, the API settings, the enterprise SSO pitch |
| What it says about the rep | It shows a read on what matters to this buyer | It shows no read on what matters to this buyer, so it covers the surface and hopes something lands |
From the buyer’s seat you can watch the rep lose the room. The monologue runs long, the questions dry up, and by minute thirty the buyer has stopped mapping the product to their own work. The tour is meant to look generous; to the buyer it lands as noise.
The First Vendor to Name a Price Often Sets the Terms
Price is something the buyer raises, rarely something the rep volunteers: the default move is “happy to get you a tailored quote,” then a second call to deliver a number that would have fit in a text message. A demo can run its full hour with “pricing” said only by the buyer, and the follow-up can still arrive without a number. The refusal is strange, because the demand is loud: price is often the first thing buyers ask for and the last thing vendors hand over.
By staying silent on price, a rep lets the first vendor who does say a number set the terms of the whole comparison. The vendor who puts a real number on the screen becomes the anchor every later quote is measured against, and the one who hides it spends the next calls explaining a price the buyer already suspects is bad news.
Getting that number out, with the conditions that ride on it, is what a competitor pricing review is for. Mystery Demo builds a buying scenario fitted to each competitor, attends every call until the number comes out, and records it with its conditions, at 499 euros per competitor.
Reps Skip the Screen You Will Use Every Day
Reps demo the confetti moment of setup and skip the screen where the work happens, on the reasonable theory that work does not screenshot well. The Tuesday-morning screen, the one the buyer will spend two years inside, rarely appears, so the buyer sees the product’s best day, not its average one.
The vendors who do the opposite stand out immediately. When a rep hands over the keyboard and lets the buyer run one real task, the demo stops being a performance and starts being a trial.
That vendor is the one a buyer can still describe a week later, screen by screen, while the passive walkthroughs blur together. The absences stack up into a short list of doors the rep walks past, and each one tells you something you can use:
| The door left closed | What it can mean | What a buyer can ask that rep next | What your own rep can do instead |
|---|---|---|---|
| The current-stack question | The rep does not want “nothing, and we’re fine” as the answer | “What do teams switching from a spreadsheet keep doing by hand?” | Ask every prospect what they use today, spreadsheet included |
| A point of view | The full tour shows the whole product and takes a position on none of it | “Which two screens would you show a team of six, and why?” | Lead with the two screens that matter to this buyer |
| An unprompted price | The number that would close the loop waits for a second meeting | “What would a team our size pay, and what is that number conditional on?” | Say a number, with its conditions, on the first call |
| The daily-use screen | The launch animation gets airtime; the screen you will live in gets skipped | “Can I run one real task on it now?” | Hand over the keyboard for one real task |
| An honest gap | “It’s on the roadmap” covers for what the product does not do | “What would you tell a customer to use for that piece today?” | Name one thing your product will not do, and what to use instead |
An Admitted Gap Builds More Trust Than a Dodged One
It is rare to hear a competitor rep say “no, we don’t do that, you’d want a different tool for that piece.” The out-of-scope question tends to get “it’s on the roadmap” or “there’s a workaround,” and “it’s on the roadmap” is the most load-bearing sentence in enterprise software, holding up products that do not exist yet.
| The dodged gap | The admitted gap | |
|---|---|---|
| What the buyer tends to hear | “Probably can’t” | A limit the buyer can plan around |
| What it does to the rest of the call | The buyer starts discounting everything else the rep claims | The rest of the call becomes easier to believe |
The follow-up rarely repairs a dodge: the standard post-demo email is a calendar link and a one-pager with the company name swapped in, and the objection you raised never appears. Candor is the cheaper move: a rep who names one thing the product will not do buys credibility for everything else they claim, while the dodge protects one feature and taxes the whole demo.
There is a fair objection to all of this: a skipped screen is not a missing feature, and a rep who never showed the workflow may have a perfectly good one. That is right, and it is why a skip is a lead, not a verdict: the next call asks for it, and the record shows whether the rep then showed it, deferred it or talked around it. A demo records what a rep said and showed; it does not test the product behind it, and the board keeps those two apart.
A rep who breaks the pattern, who asks the stack question, says the price out loud or admits a gap, stands out across a whole competitive set. The rest keep skipping the same useful moments, because nobody on their side is paid to notice the skip.
How Mystery Demo Records the Doors a Rep Leaves Closed
The record of those skips is what Mystery Demo builds: operators who have sold B2B software take every demo with a buying scenario fitted to that competitor, ask for what the rep left out, and write up what happened, with every finding pointing back to the recording, the transcript line or the email it came from. Below is a per-competitor page from our public example board, where every company is invented and a real project’s board is built from its own calls. It opens with its sourcing line, the meetings and minutes behind it, then the insights about how that rep sells.
Across the whole set, the Executive Summary turns those pages into a line per competitor: where it wins, and where it loses. The “loses on” half of each line is usually where a skipped door shows up.
Your own team cannot take a competitor’s demo as itself: your domain is in their CRM, and a rep who knows who you are runs a different call, so you never see which of these doors they leave open. That blind spot is what a competitor product comparison maps, rep by rep, vendor by vendor, as part of a competitor sales-tactics review, at 499 euros per competitor with every meeting and the analysis included, one competitor in one to two weeks. Book an intro call, name the competitors, and Mystery Demo will take their next demos; you get the list back on the board, with the recording behind each line: the question they skipped, the price they held back, the workflow they never showed and the gap they dodged, or the recording that shows they did not.
.png)
