Most Discovery Starts Too Late
Why good discovery goes upstream — and why buyers who won't go there aren’t worth pursuing
By the time a buyer fills out your demo form, they've already formed a point of view.
They have an idea of what the problem is. They've probably decided what category of solution they need. They may already have vendors in mind.
Then your rep gets the meeting.
Most salespeople pick up the conversation right there.
What are you looking for? What problems are you trying to solve? What capabilities do you need? What's your timeline?
Those aren't bad questions. But they start too late.
Because everything that shaped the buyer's answers happened before your rep was in the room. And if you don't understand how the buyer got to their current point of view, you risk spending the rest of the sales process competing inside a frame someone else created.
Your buyer didn't arrive with a blank slate
Buyers rarely wake up one morning, objectively define a business problem, survey every possible solution, and begin a neutral evaluation.
Something happened first.
Maybe a peer recommended one of your competitors. Maybe an analyst report defined the category in a particular way. Maybe someone on the executive team used a vendor at their last company. Maybe the CFO said "we need a tool that does X" before anyone determined whether X was actually the underlying problem.
By the time the opportunity reaches your sales team, those influences have accumulated. The buyer has assumptions baked in. Some are right. Some are wrong. Some are actively working against you.
The problem is that most discovery processes treat those assumptions as facts. The buyer says what they need, the rep records it in the CRM, and then starts positioning the product against those requirements.
At that point, you're not shaping the decision. You're inheriting it.
The frame matters as much as the problem
Here's a concrete version of how this goes wrong.
A buyer comes to you saying they need better forecasting software. A standard discovery process explores what's wrong with the current forecast, how accurate it is, what systems they're using, who owns it, and what capabilities they're looking for.
Useful questions. But there's one that needs to come first:
Why do you believe forecasting software is the answer?
Because maybe the real problem isn't the software. Maybe managers aren't inspecting deals. Maybe opportunity stages mean different things across the team. Maybe reps aren't qualifying consistently. Maybe the CRO doesn't trust the data in the CRM.
If your rep accepts "we need better forecasting software" as the starting point, they may spend six weeks demonstrating forecasting functionality for a problem technology can't fix. Worse, they may be competing against a vendor whose product fits the buyer's incorrectly defined requirements better than yours does.
That's the cost of inheriting the frame.
Discovery has to uncover more than the buyer's current problem. It has to uncover how the buyer came to understand the problem in the first place.
Good discovery goes upstream
Going upstream doesn't mean turning discovery into an interrogation. It means getting curious about what happened before the sales conversation started.
Four questions get you there:
How did this become a priority? What changed inside the business? Was there a triggering event, a failure, an executive who suddenly started asking questions? The answer starts to tell you whether there's a real business priority behind the project or whether someone is simply running a process they were told to run.
What have you already looked at? This surfaces what's already been shaping their thinking. What vendors have they talked to? What internal solutions have they considered? What research have they done? You're not starting fresh. You're entering a conversation that's already been happening.
What led you to this category of solution? Buyers frequently define the solution before they've fully diagnosed the problem. This question creates room to separate the two.
What did you believe the problem was before you started evaluating vendors? This is where you start separating the original business problem from everything the buyer has learned, assumed, or been told since they entered the market.
That's where meaningful discovery happens.
It's also where differentiation begins.
This is how you find something worth challenging
Most sales teams teach reps to identify pain. Better ones teach them to implicate it. But there's another layer: identifying the assumptions surrounding the pain.
The buyer believes implementation speed matters more than anything else. Why?
They've decided they need a point solution rather than a platform. Why?
They've concluded they need a particular capability because every vendor they've spoken with has emphasized it. Why?
Those assumptions shape buying criteria. Buying criteria shape who wins.
If your reps never surface them, they're left responding to criteria instead of influencing them. That turns your sales process into a feature comparison.
Once you understand where the assumptions came from, you have an opportunity to challenge them.
Not to be provocative. Not to prove the buyer wrong.
Because you may know something the buyer doesn't.
You've seen dozens or hundreds of organizations solve similar problems. They've probably solved this problem once, if at all. That pattern recognition is part of what a good salesperson brings to the process.
The goal isn't to tell the buyer what they should care about. It's to give them a reason to reconsider an assumption.
"You told me implementation speed is the most important criterion. We've seen teams optimize for that before, only to find that adoption becomes the bigger issue six months later. How are you thinking about that tradeoff?"
That's different from arguing with the buyer.
You're bringing perspective they may not have and giving them a better way to evaluate the decision.
If you can change the way a buyer thinks about the problem, you can change the criteria they use to solve it.
Why reps skip this
The obvious answer is that the buyer seems ready to go. They filled out the form, they have budget, they have a timeline, they want a demo.
Slowing down feels like friction.
But that's only part of it.
The less comfortable answer is that most reps are being measured on activity. Calls booked, demos run, opportunities created, pipeline added.
Those metrics reward forward motion. They don't reward a rep who slows a deal down to ask better questions, and they definitely don't reward a rep who disqualifies something that looked like pipeline.
So the rep accommodates.
They jump to the demo. They answer the RFP. They build the business case. They forecast the opportunity.
And three months later, the deal goes dark or gets awarded to the vendor the buyer was already leaning toward before your rep joined the conversation.
What looked like momentum was activity.
Good discovery may feel slower at the beginning. It saves enormous amounts of wasted effort later.
But that only works when the organization actually rewards pipeline quality over pipeline volume.
Many say they do.
Their metrics often say otherwise.
A buyer's willingness to engage is also qualification data
There's another reason to go upstream that has nothing to do with discovery technique.
It tells you whether you should be in the deal at all.
If a buyer won't discuss how the initiative started, what they've already considered, how they arrived at their requirements, or what's actually driving the decision, that reluctance is information.
Trust has to be earned, and there are legitimate reasons a buyer might not share everything immediately.
But if you've established credibility and they still only want you to answer questions, run demos, and respond to requirements without letting you understand the decision itself, you need to ask what role you're actually playing.
Because if they won't let you understand how they got here, you're probably not shaping the decision.
You're participating in one that's already been made.
Those deals consume real resources. Rep time, SE time, leadership time, proposal work, legal reviews, forecast calls, discount approvals.
And they create one of the most expensive problems in a sales organization: pipeline that looks real until suddenly it isn't.
Going back to the forecasting software example: if that buyer won't tell you why they landed on software as the answer, you're probably the third vendor they're running through a process to justify a decision they've already made.
The discovery conversation isn't just how you learn more.
It's how you find that out before you've spent six weeks on it.
The answer isn't to chase harder.
It's to disqualify earlier.
Discovery is a pipeline quality mechanism
Discovery training is usually framed as a way to help reps have better customer conversations.
That's true, but it undersells the function.
Discovery is also how you keep garbage out of your pipeline.
A strong discovery process helps your team answer the questions that actually matter:
Is there a real business problem?
Is solving it a genuine priority?
Does the buyer understand the problem correctly?
Can we influence how they approach it?
Do we have access to the people and information required to shape the decision?
Is there a legitimate path for us to win?
If the answers point to no, that opportunity shouldn't keep advancing just because the prospect keeps accepting meetings.
The goal isn't maximum pipeline.
It's maximum credible pipeline.
That requires sellers who are comfortable slowing down when a buyer wants to rush ahead, and leaders who won't punish them for disqualifying deals that were never truly winnable.
Most discovery starts too late.
Move it upstream.
Understand how the buyer got here before you start telling them where to go next.
And when they won't let you?
Don't chase the deal.
Disqualify it.
If you want the tactical version of how to run that conversation, we've written about the most common mistakes reps make in discovery calls and how to fix them. Read the article.