Ask any experienced sales leader what separates their top performers from average ones, and the answer is almost never "better closing skills." It is almost always "better discovery." The ability to run a discovery call that genuinely uncovers the business problem, the political context, the cost of inaction, and the decision-making process is the foundational skill of B2B tech sales. And the most common mistake I see , the one that is quietly killing deals at every stage of the pipeline , is not a lack of questions. It is asking questions at the wrong depth. Reps learn to ask questions. They do not learn to follow the answer down to where the real information lives.
The Shallow Discovery Problem
Shallow discovery looks like this: a rep asks "what are your main challenges with your current system?" The buyer says "it is a bit slow and the reporting is not great." The rep notes "speed and reporting" and moves on to the next question. They have captured the surface answer, which is almost useless. They have missed the opportunity to understand what "a bit slow" means in terms of business impact. Is it slow enough that it is affecting customer service response times? Is it slow enough that their finance team cannot close the month on schedule? Is it slowing down a specific operational process that is directly tied to revenue? They have also missed the opportunity to understand the reporting problem. What decisions cannot be made because the reporting is inadequate? Who in the organisation is affected? What is the business cost of those decisions being delayed or made with incomplete information? Every surface answer in a discovery call contains at least two layers of useful information that a single follow-up question can unlock. The mistake is treating the surface answer as the discovery. It is not. It is the beginning of the discovery. According to Gartner's B2B buying research, buyers spend only 17% of their time meeting with potential suppliers during a purchase process. Your discovery window is narrow. Staying at the surface level wastes it.
“Every surface answer in a discovery call contains at least two layers of useful information. The mistake is treating the surface as the discovery.”
The Layers of a Real Discovery Conversation
A discovery conversation that builds the foundation for a compelling proposal operates across four layers. The first is the operational layer , the specific processes, tools, and workflows that are affected by the problem. What is happening, and where? The second is the impact layer , the business consequences of the problem. Revenue lost, time wasted, decisions delayed, customer satisfaction affected. This is the layer where the problem acquires financial weight. Without it, your proposal cannot make a credible business case. The third is the political layer , who cares about this problem, who owns it, who has the authority to approve a solution, and what competing priorities exist? This layer tells you whether you have a champion, whether you are talking to a decision-maker, and what the internal selling process will look like. The fourth is the urgency layer , what happens if nothing changes? Is there a specific date by which this needs to be resolved? Is there a trigger event , a contract renewal, a board presentation, a regulatory deadline , that creates natural urgency? Most discovery calls reach the first layer. Good ones reach the second. Exceptional ones reach all four, and those are the ones that produce proposals that feel precisely tailored rather than templated. For the methodology framework that supports this kind of layered discovery, read the comparison between NEPQ and SPIN.
The Mistake of Solving Before Understanding
The second major discovery mistake , related to but distinct from shallow questioning , is moving to solution mode before the problem has been fully understood. I see this in every cohort of new sales trainees. A buyer mentions a problem and, before the discovery has run its course, the rep is already saying "we actually have a feature that solves exactly that." The impulse is understandable , product knowledge is comfortable territory, and connecting a feature to a problem feels like progress. But it derails the discovery. The moment you transition to solution mode, the buyer's role shifts from storyteller to evaluator. They stop sharing. They start scrutinising. And because you moved before you understood the full problem, your solution is inevitably mapped to a partial picture. The result is a proposal that addresses the symptoms the buyer mentioned in the first five minutes but misses the deeper problem that a full discovery would have uncovered , and which, once surfaced in a competitor's proposal, makes yours look superficial by comparison. At Oracle, we had a strict rule in deal reviews: no proposal could be submitted without a documented discovery that covered all four layers. If the account executive could not articulate the impact layer and the political layer, the proposal went back. It was an uncomfortable discipline. It was also the practice that produced our highest close rates. For more on how this connects to consultative selling as a model, see consultative vs transactional sales.
“The moment you transition to solution mode, the buyer stops sharing and starts scrutinising. Move too early, and you map your solution to a partial picture.”
Building Discovery Skills Through Deliberate Practice
Discovery is a skill, not a talent. It can be learned, but it requires a specific kind of practice: recorded call review with structured feedback. Reading about discovery frameworks improves your conceptual understanding. Role-playing without feedback reinforces whatever habits you already have, good and bad. The practice that actually improves discovery is listening back to your own calls , or having a coach listen back , and identifying the specific moments where you stayed on the surface, where you solved before you understood, and where the buyer gave you a signal that you did not follow. Every one of those missed signals is a potential deal. Capturing them in review and practising the follow-up question that should have happened is how discovery skills develop. In the 12-Week Tech Sales Pro Programme at Imoye Academy, discovery training includes recorded role-plays, peer review, and instructor analysis. We identify the exact moment in the conversation where the depth dried up and work on building the questioning muscle to go further. Because discovery is not just a skill for your first job in sales. It is the skill that compounds most across a career. The best enterprise sales professionals I have met are, first and above everything else, exceptional listeners and disciplined questioners. That is what we build.