From Presenting to Asking: How Discovery Questions Find the Pain That Actually Closes
by Oscar Uribe
Picture the same first meeting run twice.
In version one, the rep opens the deck. Twenty minutes on the company, the platform, the integrations, a customer logo slide. The prospect nods, asks two polite questions, and closes with the sentence that kills more deals than any objection ever has: "Interesting — send me the presentation and we'll get back to you."
In version two there is no deck. The rep asks how the prospect's team works today, where it grinds, what that costs. The prospect talks for two-thirds of the meeting. At the end, the prospect proposes the follow-up — because somewhere in minute twenty they heard themselves describe a problem out loud, with a number attached, for the first time.
Same product. Same prospect. The difference is that version one is a presentation and version two is a discovery — and most reps run version one while calling it version two.
Why good reps present
Presenting isn't a rookie mistake. It's a comfort behavior, and experienced reps are often the worst offenders because they're genuinely good at it.
A pitch is controllable. You know every slide, you've answered every question before, nothing unexpected can happen. Questions are the opposite: you hand the room to someone else and you don't know what comes back. So under pressure — a senior title in the room, a short meeting, a quarter that needs pipeline — reps retreat to the thing they can control.
The problem is what a pitch produces. After thirty minutes of presenting you know exactly nothing you didn't know walking in. You don't know what this company struggles with, what it costs them, who feels it, or whether they'd pay to fix it. You've traded your one chance to learn for the fleeting pleasure of being listened to.
And polite interest is not a buying signal. People buy when they've connected your product to a pain they've admitted having — and they can't admit it while you're talking.
A complaint is free. A pain has a price tag.
The first thing discovery has to do is separate real pain from conversational filler, because prospects hand out complaints for free. "There's never enough time." "Data quality could be better." "We should really be more structured." None of that is pain. That's small talk wearing pain's clothes.
A real pain has three properties:
- It has a cost. Somebody can put a number on it — hours, kronor, lost deals, missed deadlines — or at least gets uncomfortable trying.
- It has an owner. A specific person is measured on the thing that's broken, and it's costing them personally: their target, their evenings, their standing.
- It has a consequence of inaction. If nothing changes, something specific gets worse. If nothing gets worse, there is no deal — there's a nice-to-have, and nice-to-haves lose to every other priority in the budget meeting.
The job of a discovery question is to walk a vague complaint down to something with all three properties — or to establish that it doesn't have them, which is just as valuable, because now you can stop chasing it.
The ladder: pain, then number, then value
The mechanism that does this is a three-rung ladder, and it's worth seeing in action. Meet Klarvik, a fictional company selling route-planning software, and their rep Sara, in a first call with Braxen Logistik — a regional delivery firm with forty trucks — represented by Henrik, who runs operations.
Rung one: the open question. Not "do you have challenges with route planning?" — a yes/no question invites a no and teaches you nothing. Instead:
"Walk me through what happens between an order coming in and a truck actually driving the route. Who touches it, and where does it get slow?"
Henrik describes the morning: two dispatchers, a spreadsheet, a wall of Post-its, and a daily scramble whenever a driver calls in sick. So far this is a complaint — colorful, but free. Most reps pitch right here: "That's exactly what we solve!" Sara doesn't. She climbs.
Rung two: the number. The follow-up that turns a story into a cost:
"The re-planning when someone calls in sick — how often does that happen, and how long does it take the two of them to rebuild the day?"
Henrik thinks. Two, three times a week. A couple of hours each time, both dispatchers, and the first trucks leave late. Now there's arithmetic in the room: call it five hours a week of senior dispatcher time, plus late departures that ripple into missed delivery windows. Notice that Henrik produced the number. A cost the prospect calculates themselves is believed; the same figure on your slide is marketing.
Rung three: the value. The question almost nobody asks:
"If those five hours went away and the trucks left on time — what would that be worth to you? Not to Braxen in the abstract. To you, this quarter."
This is where discovery stops being an interview and starts being a decision. Henrik says on-time delivery is the number his boss actually looks at, and it's been red for two quarters. Now the pain has a cost, an owner, and a consequence of inaction — all three properties, all stated by the buyer, in the buyer's own words.
Sara has said almost nothing about Klarvik yet. That's not a delay in the selling. It is the selling.
Ask for halfway
There's a version of the value question that consistently outperforms the rest, and it's built on a deliberately modest promise:
"Suppose we couldn't fix all of it — but we got you halfway. Half the re-planning time, meaningfully fewer late departures. What does halfway get you?"
Halfway works for two reasons. First, it's believable — every buyer has been promised the moon by a vendor before, and their defenses are calibrated to full-moon promises. Nobody's defenses are calibrated to "half." Second, if half the value already justifies the decision, the business case is robust; it doesn't depend on everything going perfectly. When Henrik concludes that even half is worth having, he's effectively pre-approved a realistic outcome instead of an optimistic one.
Discovery isn't only about pain
Some prospects won't hand you pain — the operation runs fine and saying otherwise would feel disloyal. That's not a dead end; it just means you switch from probing wounds to probing ambitions:
"If order volume grew forty percent next year, what breaks first?" "What would the team take on if the morning scramble disappeared — what's the thing you never get to?"
Possibility questions surface the same raw material as pain questions — a gap between today and a state the buyer wants, with a cost attached to staying put. Growth plans, hiring plans, a new market, a service level they want to promise but can't yet. A rep who can only sell against pain loses every deal where the buyer is winning; the gap between "good" and "what we're aiming for" closes deals just as well as the gap between "broken" and "fixed."
The mechanics: silence, depth, and their exact words
Three habits separate reps who ask questions from reps who do discovery:
Let silence work. After a real question, the first three seconds of quiet are where the prospect decides whether to give you the rehearsed answer or the true one. Reps who can't sit through those seconds answer their own question — "…or maybe that's not an issue for you?" — and hand the prospect the exit.
Never accept the first answer. The first answer is the polished one. "Tell me more" and "how do you mean?" are the two most underrated tools in selling. The real material is almost always one layer down: the first answer is "planning takes time"; the third answer is "honestly, I do it Sunday evenings so Monday doesn't fall apart." One of these builds a business case.
Write down their exact words. Not your summary — their phrasing. If Henrik says "the morning scramble," then the follow-up email, the demo, and the proposal should all say the morning scramble. Buyers trust their own words in a way they will never trust yours, and a demo framed in the prospect's language feels custom-built even when it isn't.
Earn the pitch
None of this means you never present. It means the presentation is earned — and scoped.
The demo that follows a real discovery doesn't tour the product. It answers the two or three pains the prospect named, in the order they care about, in their vocabulary, with their numbers on the value. Everything else in the product is noise this buyer didn't ask about — every extra feature you show dilutes the two that matter and invites a "this looks complex" objection you didn't need to take.
One more thing, learned the hard way by every team that gets discovery right: what's said in discovery has to survive the call. The pains, the numbers, Henrik's exact words — if they live in a rep's notebook or memory, the next meeting starts from zero, and a handover or a follow-up three weeks later loses everything the first call earned. Whatever your tooling, the discovery record belongs in the system, where the next conversation — and the next colleague — can start from what was actually said. That principle, incidentally, is much of why we built what we built.
Your next first meeting
If you run one experiment this week, run this:
- Open the call with a question, not a slide. If you must have a deck, don't share your screen until the second half.
- Chase every complaint down the ladder. Story, then number, then value — and let the prospect do the arithmetic.
- Ask the halfway question before you promise anything.
- Count the talk ratio. If you spoke more than forty percent of the meeting, the meeting was a pitch, whatever the calendar invite said.
- End by playing back their pains in their words — and let the summary propose the next step for you: "You said the morning scramble costs you five hours a week and on-time delivery is red. If we can show you exactly how we'd take half of that away, who else should be in that meeting?"
The rep who presents leaves the room hoping. The rep who asks leaves the room knowing — what hurts, what it costs, what fixing it is worth, and whether there's a deal here at all. Buyers, it turns out, are far more persuaded by their own answers than by anyone's slides.
Want your team's discovery — the pains, the numbers, the buyer's exact words — captured in the system instead of in notebooks? Book a demo and see how Funnelfeedr turns every call into a record your next meeting can build on →