Demo Teardown: The Buyer Who Asked About Price Four Times in 25 Minutes

The call

Twenty-five minutes. Four price questions. One rep who never gave a number, and a buyer who had checked out by minute eighteen and was answering Slack messages with the camera on.

I listen back to a lot of demos. This one stuck with me because the rep did almost everything else well. Good discovery on the call before. Clean screen share. He knew the product cold. And he lost the room over a question he could have answered in eleven seconds.

Here is the shape of it.

Minute four. Rep is two clicks into the workflow. Buyer, unprompted: "Before we go too far — what does something like this run?"

Rep: "Great question. Let me park that and come back to it, because it really depends on what we scope, and I want to make sure you're seeing the right pieces first."

Minute nine. Rep finishes the first module. Buyer: "So is that a separate SKU or is that included?"

Rep: "Everything you're seeing today is in the same platform. We'll get into packaging at the end."

Minute fifteen. Buyer, flatter now: "Ballpark, are we talking five figures or six?"

Rep: "Honestly it varies so much by seats and volume that if I throw a number out I'll probably mislead you. Give me five more minutes and I'll walk through it properly."

Minute twenty-two. Buyer: "Can you just send pricing over after this?"

That fourth one isn't a question. That's the buyer leaving. "Send it over" means "I have stopped participating and I'd like the artifact so I can end this." The rep got his five more minutes and spent them talking to someone who wasn't there anymore.

He closed with a next-step ask. The buyer said he'd loop in a colleague. There was no colleague.

What the rep thought was happening

He thought he was protecting value. This is the thing every one of us gets taught early: don't price before you've built value, because a number in a vacuum is just a number, and the buyer will anchor on it and judge you against it before they understand what they're buying.

That advice is not wrong. It's just being applied to the wrong moment.

The fear underneath it is that if you say a number too early, the buyer says "that's too expensive" and the demo dies. So the rep defers. And deferring feels safe, because nothing bad happens in the next thirty seconds. The bad thing happens at minute eighteen, quietly, and you don't notice it until you're asking for a next step and getting a colleague who doesn't exist.

Here's what I'd say to him if it were my rep: you didn't protect value. You told a buyer who was already interested that you weren't going to answer him, three separate times, in a meeting he cleared his calendar for.

What was actually happening

When a buyer asks about pricing during a demo once, that can be impatience, or habit, or a procurement person doing their job.

When a buyer asks four times in twenty-five minutes, they have already decided the product probably works.

Think about it from their chair. Nobody asks the price of something they've written off. If the demo were failing, they wouldn't be pricing it — they'd be asking narrow, skeptical questions designed to find the crack, the way a freight ops room does when they're running your demo through everything that could break. Price questions are the opposite of that. Price questions mean the buyer has stopped evaluating whether it works and started evaluating whether they can get it bought.

That second job is much harder than the first one, and it's a job you can't do for them. Somewhere in that person's head is a rough map: who owns the budget, what number triggers a second signature, what they'd have to give up to fund this, and whether the conversation with their boss is going to be easy or a fight. They are trying to run that map while you're showing them dashboards. And they can't run it without a number.

So they ask. You deflect. They try a different angle — is it a separate SKU, five figures or six — because they're not being difficult, they're trying to get any input into the model they're building. You deflect again. At some point they conclude that either you don't know, or you're going to make this a negotiation, and either way this meeting has stopped being useful to them. So they mentally leave and ask for the PDF.

The buyer wasn't impatient. He was doing your job for you, internally, in his head, and you wouldn't give him the one input he needed.

Answer the first ask. Every time.

My rule is simple: the first time a buyer asks about price, they get a real range, in the same breath, no throat-clearing.

Not a discovery question in return. Not "what were you hoping to spend." Not "depends on scope." A range, out loud, in the moment.

The range does three things. It tells the buyer you're not going to play games, which is worth more than most reps realize. It lets them keep building their internal model while you keep demoing, so they stay in the room. And — this is the part people miss — it turns their next question into discovery for you.

Because once a real number is on the table, what the buyer says next is enormously informative. "That's fine" is information. "Oof" is information. "Is that annual?" is information. "That's above what I can sign" is the best information you'll get all quarter. You cannot harvest any of that if you never put the number down.

The exact wording

Here's the structure I use. Three parts, in order: the range, the tie-back, the reason it moves.

"Yep, happy to. Companies your size usually land somewhere between [low] and [high] a year. Where you sit in that comes down to [the one or two variables that actually move it]. And just so the number means something — what I showed you thirty seconds ago is the piece that's supposed to pay for it. Let me finish this bit and then let's talk about which end of that range you'd be on."

Swap in your own figures. If your typical mid-market deal runs from the high five figures into the low six, say that out loud. If it's forty thousand to seventy thousand depending on seats, say forty to seventy.

Notice what that wording does and doesn't do.

It gives a number. The buyer can now do arithmetic. He knows whether this is a card-swipe, a budget-line conversation, or a board-level fight, and that determines everything about how he engages with the rest of your demo.

It does not concede a number. A range is not a quote. You haven't discounted, you haven't committed, and you've explicitly named that position within the range is earned, not given. That last bit matters — if you say "forty to seventy" and stop, every buyer hears forty. If you say "forty to seventy, driven by seats and how many sites you roll out to," you've made the range a function of something real instead of a negotiating posture.

And it ties the price to the thing you just demoed, while the demo is still on the screen. This is the single highest-leverage second in the whole call. The buyer's eyes are on the outcome. Attach the number to it right there and the number is priced against a result. Wait until slide nineteen and the number is priced against nothing, which means it gets priced against their budget anxiety.

The width of the range matters too. Too tight and you've quoted. Too wide and you've said nothing — "anywhere from ten to five hundred thousand" is a deflection wearing a number's clothes, and buyers hear it as one. I want a range where the top is meaningfully more than the bottom but a buyer could still tell his boss the honest version of it in one sentence.

Then use the repeats

Here's the reframe that changed how I run these calls. Once you've answered the first ask honestly, a second price question is not a repeat. It's a new question wearing the same coat, and it's usually the most valuable thing the buyer will say all meeting.

So don't answer it as a price question. Answer it as discovery.

When they come back with "is that per user or per site," what they're really saying is I need to know which line this hits. Good response:

"Per site, in most cases. Is site-level how you'd budget it, or does this come out of one central pot?"

When they come back with "and that's annual, committed?", what they're really saying is I need to know if this needs a signature I don't have. Good response:

"Annual, yeah. Out of curiosity — at what number does this stop being your call and start needing someone else's?"

That question is worth an entire discovery call and buyers answer it readily, because you've just been straight with them and reciprocity is real. I've had people tell me their exact approval threshold, who sits above it, and what that person cares about, all in one breath, thirteen minutes into a demo. You do not get that by deflecting.

When they come back a third time with "what would it take to get to the bottom of that range," they've told you they're going to advocate for this. Nobody negotiates on behalf of a product they're not planning to buy. Response:

"A couple of things move it. Before I go into them — if the number landed where you wanted, what does the approval path look like from there? Who else has to be comfortable?"

Every one of those turns a price question into a map of the buying process. That map is the actual deliverable of a demo. The demo itself is just the excuse for the meeting.

And notice the rhythm: answer, then ask. Never ask before you answer. If you respond to a price question with a question, buyers correctly identify it as a dodge and their guard goes up. Answer first, cleanly, then earn the right to ask.

When you genuinely can't give a number

Sometimes you can't. Usage-based product with fifteen variables, or a company where pricing is genuinely bespoke, or you're new and don't have the authority.

You still have to say something with a number in it. "I can't share pricing" is not an answer a serious buyer accepts, and it shouldn't be.

What I'd say:

"I'm not going to give you a precise number on this call because I'd be guessing and I'd rather not be wrong in either direction. What I can tell you is the smallest deal we do in your segment is around [floor], so you can rule us in or out on that basis right now. If [floor] is already off the table, tell me and we'll stop — I'm not going to waste twenty more minutes of your day."

A floor is a number. It lets the buyer disqualify you, which sounds bad and is actually the second-best outcome available. The worst outcome is four more meetings and a no.

That willingness to be ruled out is also what buys you credibility for the harder conversation later. In my experience the reps who can hold a number in a real negotiation — the ones who don't crumble when a brokerage says we've already picked you, now sharpen the pencil, which is the whole problem that pricing conversation is built around — are the same reps who were comfortable saying a number out loud at minute four. It's one muscle. If you can't say the price when there's no pressure, you definitely can't hold it when there is.

The handoff into a real pricing conversation

One more piece. Giving a range mid-demo isn't the pricing conversation. It's a placeholder that keeps the buyer in the room. You still have to schedule the real one, and you should name it as a separate thing so it doesn't get skipped.

At the end of the demo:

"So — the range I gave you was [low] to [high]. Based on what we just talked about, I think you land nearer [specific end], and I can show you exactly why. What I'd like to do is put a real number in front of you, with the assumptions written out so you can hand it to [name they mentioned] without translating it. Fifteen minutes on Thursday, and I'll come with the actual figure. Does anyone else need to be on that, or do you want to see it first?"

Four things happen in that paragraph. You restate the range so it's the anchor, not whatever they half-remember. You narrow toward a specific end, which makes the follow-up meeting about a real number instead of a document request. You promise the assumptions in writing, because your champion has to sell this without you in the room and a naked figure is impossible to defend. And you ask who else needs to be there, which is the question that turns a pricing call into a decision meeting.

That last question is also your check on everything you learned from the repeat asks. If the approval threshold they mentioned is below your range, you now know your champion needs air cover and the Thursday call has a different job entirely.

The habit underneath all of this

Every interruption in a demo is a request for something. Price questions are a request for a number. Skeptical questions are a request for proof. "Can you go back a slide" is a request for time to think. The failure mode is always the same — the rep hears an interruption as a threat to the flow of the demo and defends the flow instead of serving the request. That's the same instinct that gets reps run over by a plant manager who interrupts ninety seconds in, and it costs you exactly the same way: the buyer stops asking, and you mistake silence for agreement.

The demo is not the point. The demo is a device for getting a buyer to tell you what they need in order to buy. When they hand you that information unprompted, four times, take it.

If you know you flinch on this — and most reps do, including me for longer than I'd like to admit — the fix isn't reading about it. It's saying your range out loud, mid-sentence, while a screen share is running and someone is cutting you off, until it comes out flat and unbothered instead of apologetic. That's what I'd go do next: pick your low and your high, write the three-part answer on a sticky note, and run it in DrillCall against a buyer who asks four times, until the fourth ask stops feeling like an attack and starts feeling like the deal telling you how to close it.