In consultative selling, the seller often sees the real problem before the buyer does. That’s the value of a good consultant. It can also be the reason a promising deal stops moving.
It’s a pattern I see often. Discovery went well. The problem is real. The solution fits. The buyer was engaged and asked good questions. Then the follow-ups go unanswered, the decision slides to next quarter, and the deal quietly stalls.
The usual response is to look at the pitch, the proposal or the follow-up cadence. Sometimes that’s where the issue is. But often the reason is simpler. The seller and the buyer are looking at different problems, and the deal can only move on the buyer’s version.
What does the buyer think the problem is?
Take an IT managed services provider talking with the owner of a growing distribution business. The owner reached out because of outages. The network goes down a few times a month, and the warehouse loses a morning. “It’s annoying,” the owner says, “but we manage.”
The provider listens and sees something bigger. Every technology decision has been made one at a time, usually after something breaks. No one owns the overall plan. The outages aren’t the problem. They’re what the problem looks like from the warehouse floor.
Underneath that, the provider senses something harder. The owner has always treated technology as a cost to keep low. Investing in it as a capability would mean changing how the business thinks about spending, and the owner built the business by being careful with money.
All three are true. The outages are the symptom. The missing plan is the problem. The owner’s view of technology is the tension that has kept the problem in place for years.
The provider can see all three. Right now, the owner sees the outages.
Why isn’t a real problem enough to move the deal?
The first way this deal can stall is simple. The symptom may not be worth acting on.
The owner has lived with outages for a long time. They’re disruptive, but they’re familiar. From where the owner sits, the cost of the problem is a few lost mornings a month. That’s an irritation, not a priority.
The provider knows the real cost is much higher. Growth is being built on infrastructure no one has planned for. But that cost belongs to the provider’s understanding, not the owner’s. A buyer weighs action against the problem they can see. If what they see is tolerable, tolerating it is a reasonable choice.
When does good discovery work against the sale?
The second way is less obvious. It often happens precisely because discovery went well.
Having seen the underlying problem, the provider proposes to solve it: a technology roadmap, ownership of planning, a phased investment over two years. It’s a thoughtful proposal and probably the right one.
But the owner asked about outages. Measured against a few lost mornings a month, a two-year roadmap looks out of proportion. The proposal answers the seller’s diagnosis, not the buyer’s question. To the owner, it can even look as if the provider wasn’t really listening.
This is the trap in consultative selling. The better a consultant is at seeing beneath the surface, the easier it is to sell to what they see instead of what the buyer sees.
Can the seller change how the buyer sees the problem?
The seller can help. They can’t do it for the buyer.
A good consultant can ask questions that connect the outages to the missing plan. They can share what they’ve seen in similar businesses. They can challenge an assumption, or reframe the problem in terms the owner already cares about. All of that is useful, and it’s much of what makes consultative selling valuable.
But the shift in understanding has to happen for the owner. Being told what the real problem is isn’t the same as recognizing it. In my experience, a buyer who has been told tends to push back. A buyer who has recognized it tends to move.
It’s also worth holding the seller’s diagnosis a little loosely. Sometimes the deeper problem is real. Sometimes it’s simply the problem the seller’s offering is built to solve. A good consultant checks which one they’re looking at.
What if the buyer does see it?
Suppose the conversations work. The owner starts to see that the outages come from how technology decisions get made. The underlying problem is now shared.
The deal still may not move.
Recognizing the problem means facing the tension behind it. For this owner, that means rethinking a long-held view about what technology spending is for. Seeing that clearly is one thing. Being willing to act on it is another. Understanding makes action possible. It doesn’t make it inevitable.
What this means when a good deal stalls
When an apparently good-fit opportunity stops moving, it’s worth asking a different set of questions before reaching for a better pitch or another follow-up.
What does the buyer believe the problem is, in their own words? As they see it, is that problem worth acting on? Is the proposal sized to their understanding or to ours? And has anything actually changed in how they see it since the first conversation?
These questions won’t always restart a deal. But they can explain why it stopped, and that changes what the team does next. Sometimes the answer is more patient discovery. Sometimes it’s a smaller first step that matches the problem the buyer can see. Sometimes it’s recognizing that the buyer isn’t going to move yet, which is useful to know too.
A different question
Sales teams put real effort into making sure they understand the customer’s problem. In consultative selling, that’s the starting point, and it matters.
But a deal doesn’t run on the seller’s understanding. It runs on the buyer’s.
So it’s worth asking a second question alongside the first. Not only “do we understand their problem?” but “whose version of the problem is this deal running on?”
