Complex needs reveal themselves across stakeholders, decisions, and changing business conditions.
Discovery is one of those sales activities that often becomes complete long before the customer’s situation is understood.
The meeting happened. Questions were asked. Notes were entered. The CRM field says discovery complete.
So the team starts designing the solution.
That is usually where the trouble begins.
Imagine a customer tells a managed-services provider that the priority is reducing operating cost. The first conversation centres on consolidation, automation, and a cleaner commercial model. Useful discussion. The seller leaves with a requirement and the solution team gets to work.
Then other people enter the conversation.
Operations is less worried about cost than the instability caused by aging platforms and knowledge walking out the door. Security is concerned about privileged access. Finance likes the savings but needs predictable transition costs. HR sees workforce implications nobody has discussed. A business leader is worried that the change will collide with a critical market launch.
None of them is contradicting the original requirement.
They are revealing the rest of the decision.
I have seen this pattern often enough to be cautious when a team says, “We already did discovery.” What they usually mean is that they held a discovery meeting.
Those are not the same thing.
A customer’s first answer is often the most available answer—the problem they can see, explain, and defend from where they sit. It may be completely valid. It is rarely complete.
A completed discovery meeting can still leave the buying decision almost entirely undiscovered.
This does not mean turning every sales conversation into an interrogation or delaying the pursuit until we know everything. We never know everything.
It means treating discovery as something that continues while the deal continues.
As stakeholders change, assumptions should be tested. As the solution becomes more concrete, new consequences become visible. As commercial terms take shape, different risks surface. A proposal, a security review, or even a difficult procurement conversation can teach us something that should change how we understand the need.
The important question is whether the sales team is still listening.
Too many pursuits lock onto the first requirement, build an elegant answer, and then defend it all the way to the finish line. By the time the broader need appears, changing direction feels expensive. So the team calls it scope creep, stakeholder misalignment, or a late objection.
Sometimes it is simply late discovery.
The commercial consequences are real. The seller loses relevance. The sales leader gains a forecast built on partial evidence. Delivery inherits assumptions it did not help test. And the customer gets a solution designed around the first problem articulated rather than the full outcome required.
Good discovery is not a stage we complete. It is a discipline of remaining curious enough to let new evidence change the deal.
That is a harder standard than asking better questions in the first meeting. It requires the courage to revisit what we thought we knew—even after the solution is taking shape and the forecast is looking attractive.
Before your next deal review, ask one question:
What has the team learned since discovery was marked complete—and did it change the pursuit?
If that question exposes a gap in one of your major opportunities, reach out. I’m always happy to compare notes.
