Discovery Call vs Demo: What Belongs in Each When the Buyer Says "Just Show Me the Product"

"Can you just show me the product?"

You send an invite that says discovery call, thirty minutes. The reply lands the same afternoon: can we skip ahead, I just want to see it.

Most reps do one of two things here. They cave completely and open the screen share armed with nothing but a company name and a job title. Or they dig in and deliver the little speech about how they need to understand the business first so the demonstration can be tailored. Both are bad. The first one costs you the deal quietly, weeks later, when the buyer stops replying and you never learn why. The second one costs you the deal in the first ninety seconds, when the buyer decides you are going to be work.

The useful way to think about this: discovery and demo are two different calls with two different jobs, and a buyer asking to skip one of them is information, not an obstacle. Sometimes that information says give them exactly what they asked for. Sometimes it says they do not know what they are asking for and you have to protect them from it. Telling those apart is most of the skill.

What a discovery call is actually for

A discovery call exists to answer one question: what is broken, and what is it costing the person who has to live with it?

Everything else is decoration. Not budget, not timeline, not the org chart — those are downstream. If you leave a discovery call knowing the buyer has forty thousand a year to spend and a Q3 deadline but you cannot describe, in their words, the thing that is going wrong on a Tuesday morning, you did not run discovery. You ran a qualification interrogation and the buyer felt it.

The reason this matters is that a demo is a set of answers. Without discovery you do not know the questions, so you show everything, and showing everything is the same as showing nothing. The buyer sits through a tour of a product and forms exactly one impression: it looks like software. Then they go quiet, because there is nothing for them to be excited about. Nothing you showed them was aimed at them.

Good discovery also does something reps underrate. It gets the buyer to say the problem out loud, in their own language, to another human being. That sentence — the one where a maintenance leader says "I find out a line is down when somebody walks over and tells me" — is worth more than anything you will ever say. You get to repeat it back to them for the rest of the cycle. You get to put it in the recap email. You get to say it to their boss. If you skip discovery you never own that sentence, and you spend the rest of the deal describing your product instead of their problem.

If you sell into plants, the version of this I would run is the one in the manufacturing discovery playbook, because operations buyers will answer specific, concrete, ground-level questions all day and will shut down completely on abstract ones. Ask a plant manager about strategic initiatives and you get a wall. Ask them what happens between the moment a line stops and the moment the right person knows, and you cannot get them to stop talking.

What a demo is actually for

A demo is not a product tour. A demo is proof.

Specifically, it is proof of a claim you already made. You told the buyer the thing they described can be handled a different way. The demo is where you show them that is true, using their situation, with as few clicks as you can manage. Every screen you show should be attached to something they said. If you cannot attach it, cut it.

This is why the demo is easier to run well than discovery, and why reps like it more. Discovery is uncomfortable — you are asking a stranger to admit something is not working. A demo feels like performance, and reps are usually good at performance. That comfort is exactly why the demo swallows the discovery call whenever you let the two blur together.

What it costs you to blur them

The blur goes in both directions and both are expensive.

The common one: the call is booked as discovery, you ask two questions, the buyer mentions something adjacent to a feature you love, and you say "actually, let me just show you." Twenty minutes later you have burned the entire call on a product tour built off a single half-answered question. The buyer is polite. They say it looks great. You send a recap you cannot really write, because you have nothing to recap except your own talking. That call had two jobs and did neither.

The rarer one, but it happens with disciplined reps: the call is booked as a demo, the buyer shows up with three colleagues, and you spend the first fifteen minutes running discovery because you want it to be perfect. Now four people who cleared their calendars to see a product are watching you ask questions. The senior person in the room checks out. You get to the screens with eight minutes left and rush the only part they came for. You did nothing wrong by the textbook and you lost the room anyway.

The fix is not more discipline. It is knowing which call you are actually on, which is determined by the buyer, not by what the invite says.

Three times demo-first beats disciplined discovery

There are situations where fighting for a clean discovery call is the wrong play. Here are the three I would not argue with.

The cycle is short and the ticket is small

If the deal closes in days and the price does not need a committee, a separate discovery call is a tax. You are asking a buyer to spend two meetings on a decision that deserves one. Every extra meeting is another chance for the deal to die of scheduling.

In a short cycle the demo is the discovery call. You run both in the same thirty minutes, in the order the buyer wants, which means product first. The technique further down handles this. What you should not do is book the second meeting purely because a methodology told you discovery comes first. Buyers notice when your process costs them more time than their problem is worth.

The buyer is already informed and switching from a known competitor

This is the one reps get wrong most often. Someone books a call and says they use a competing product, they are evaluating alternatives, and they want to see yours.

That buyer has already done discovery. On themselves. They know what is broken because they have been living inside a tool that does not do it, and they have almost certainly read your site, your comparison pages, and whatever your competitor's fans say on Reddit. When you open with "so tell me about your current process," you are asking them to do unpaid work explaining a category they understand better than some of your colleagues.

With this buyer you skip to the screens and you do your discovery through the demo. "You are coming off [competitor]. Most people switching off it are hitting one of three walls — here they are. Which one is yours?" Then you show that one. You have just run discovery, established that you know the landscape, and earned the right to ask harder questions, all inside the first three minutes. That is a better opening than any question list.

The room will not sit through questions

Some rooms are simply not going to do it. A plant floor where the manager is taking your call between two other problems. A revenue leader who has three tools up for renewal and a board meeting on Thursday. A group call where five people joined and none of them agreed on why.

These rooms need something on the screen fast, because the screen gives them a shared object to react to. Interruptions are not rudeness in this setting, they are the discovery. The manufacturing demo script for plant managers who interrupt is built entirely around this — you show one thing, get cut off, and the interruption tells you what they care about, which is the information a discovery call would have given you anyway. Same with a revenue team already cutting tools; the SaaS demo script for that room assumes the buyer is in defensive-budget mode and wants to see the thing before they will spend attention on your questions.

When the room will not sit still, discovery does not disappear. It changes shape. It stops being a list of questions and becomes a series of small bets you place on the screen.

How to run ninety seconds of discovery inside a demo

Here is the actual mechanic. It is not complicated and almost nobody does it.

When a buyer says just show me the product, you say yes. Immediately, with no hedging, because the hedge is what makes you sound like every other rep. Then you buy yourself ninety seconds.

"Yep, happy to. Screen's coming up. Before I start clicking — I can take this in about four different directions and three of them will bore you. What made you take the call?"

That is it. You have already agreed. You are already sharing. The question is framed as being for their benefit, which it is, and it is one question rather than a list. Almost nobody refuses to answer it, because refusing means sitting through the boring version.

Then the second question, and only the second:

"Got it. And when that happens — who feels it first?"

Now you know the problem and the person. That is enough to start. Ninety seconds, two questions, and you have more than most reps get out of a full discovery call because you asked while the buyer was leaning forward instead of waiting for the tour.

Show one thing. Then go back to questions.

The trap after those ninety seconds is relief. You got your answer, you have permission, and now you tour the product for twenty-five minutes. Do not.

Show one thing. The single screen that speaks to what they just told you. Narrate it in their words, not yours — if they said "I find out too late," your line is "so here is where you find out," not "this is our real-time alerting module."

Then stop and ask.

"Is that the moment you were describing, or is it happening earlier than that?"

This question does more work than anything else in the call. If the answer is yes, you have confirmation and you can go deeper on that path. If the answer is no, you just saved yourself twenty minutes of demoing the wrong thing, and the correction they give you is deeper discovery than you would have gotten by asking cold. Either way you learn something and either way the buyer talks.

Then you show the next one thing. Ask again. That loop — show, ask, show, ask — is a discovery call and a demo happening at the same time, and to the buyer it just feels like a good conversation. Reps who run this well look like they are demoing. They are actually interviewing with pictures.

Keep a question in your back pocket for the silence

Every demo has a moment where the buyer goes quiet and you cannot tell if it is good quiet or bad quiet. Fill it with a question, never with more product.

"You've gone quiet on me. Is that because it is obvious, or because it is not landing?"

Buyers answer this honestly more often than you would expect, because you gave them a socially easy way to say it is not landing. The alternative — you keep clicking and hoping — is how demos end with "send me some information."

Protecting yourself from demoing to someone who never told you what is broken

All of the above assumes the buyer will eventually tell you something. Sometimes they will not. They want the tour, they want it silent, and they deflect every question. That buyer is usually one of three things: doing free research for a decision that is already made, building a comparison document for procurement, or a junior person who was told to go look at options and has no authority to describe the problem.

You protect yourself in three places.

Before the call, ask one question in writing when you confirm. Not a form. One line in the email: "So I don't waste your time on the wrong screens — what made this worth a look now?" The answer, or the absence of one, tells you what kind of call you are walking into. A buyer who writes two sentences back is a real buyer. A buyer who writes "just want to see the product" and nothing else is one you should be careful with.

During the call, use the trade. If they will not answer a question, name it lightly and keep moving: "I'll show you that either way — but if I know which of those two it is, I can show you the version that matters." You are not withholding. You are making the value of answering obvious. If they still will not, you have learned something real about how this deal will go.

At the end, never let a demo close without one forward question. My preferred one:

"If this were going to go somewhere, what would have to happen next on your side?"

Not "what are the next steps," which invites a polite non-answer. This version makes them describe their own process, and a buyer who cannot describe it is a buyer who does not have one yet. That is fine — it just means the real discovery call has not happened, and now you have a reason to book it. "Sounds like the next conversation is with whoever owns that. Want me to help you get ready for it?"

Where this actually gets fixed

None of this is hard to understand. It is hard to do live, at speed, with a stranger, when the buyer's tone knocks you off your script in the first thirty seconds. Reading a playbook does not build the reflex to say "yep, screen's coming up, what made you take the call?" without flinching. Reps who can do it have said it out loud dozens of times before it mattered.

So the thing I would do next is rehearse the switch, not just the scripts. Pick the demo playbook that matches your buyer, then run the same opening against a buyer who wants to skip discovery, a buyer who interrupts, and a buyer who goes silent — and see which version of you falls apart. That is exactly what we built DrillCall for: AI roleplay where the buyer pushes back the way real ones do, so the first time you handle "just show me the product" is not in a live pipeline deal.

The short version of all of it: discovery finds the problem, the demo proves you can fix it, and the buyer decides what order those happen in. Your job is to get both jobs done regardless of the order you are handed.