You're Talking Too Much in Discovery

In several recent first meetings with customers, I watched the same pattern play out. A capable Sales Engineer, well prepared and sharp, opened with a good question about the customer's environment. The customer began to answer. Within two minutes the engineer heard a familiar keyword and was off: "We handle exactly this. Our platform does X, Y, and Z, and it integrates with..."

Forty minutes later, the vendor team had done most of the talking. Everyone left believing discovery had taken place. It hadn't. What took place was a product tour, with a few questions used as on ramps.

Why smart people get this wrong

Technical people are hired for answers. We spend years building expertise, and expertise wants to be useful. When a customer describes a problem, the reflex is to solve it on the spot, out loud. In a support queue, the reflex serves us well. In a first meeting, it costs us the deal.

Account Executives are no different. I watched several steer every answer back to the portfolio they represent. Different job title, same instinct: lead with what we sell rather than what the customer needs.

The numbers back this up. Gong Labs analysed 25,537 B2B sales calls and found the highest-converting talk-to-listen ratio sits around 43:57, with the buyer speaking more than the seller. The author of the study measured his own calls and found he was talking 72% of the time. A separate Gong analysis of 519,000 discovery calls found the most effective ones surfaced three to four business problems. You won't surface four problems while presenting one solution.

I'd push the ratio further. 43:57 is close to an even split, and it blends every type of sales call, demos included. Gong's own researchers expected the ideal ratio to shift by stage of the sales cycle.

In a first discovery conversation, my standard is firmer. The vendor team, Sales Engineer and Account Executive combined, speaks no more than 30% of the time. The customer holds the other 70%: explaining, sharing, and walking you through how they think they will get there. Once your side passes 30%, you have stopped learning and started selling.

What discovery is for

Discovery has one job: to understand the customer's world well enough to earn the right to propose anything. You are listening for four things, in the customer's own terms:

• What they want to achieve, and why now.
• Their environment: systems, people, constraints, history, and politics.
• How they think: how they frame the problem, what they have tried, and what good looks like to them.
• How they believe they will get there, and who else needs convincing.

None of these mentions your product.

The customer is the champion, not you

The best outcome of a discovery conversation is not a customer impressed by your technology. It is a customer who leaves clearer about their own problem than when they arrived, and who sees themselves as the person who will solve it.

They will carry the case into rooms you never enter: the budget meeting, the architecture review, the executive committee. If the story belongs to your product, it falls apart the moment you leave. If it belongs to them, they will defend it.

The Technical Win follows the same logic. It arrives when the customer concludes, in their own words, the solution fits their goal, their environment, and their way of working. You won't get there without first understanding all three.

What good discovery sounds like

• Ask open, exploratory questions. "Walk me through how this works today." "What happens when it goes wrong?" "What would change for your team if this were solved?" "Who else feels this?"
• Follow the thread. The second and third questions on the same topic are where the insight lives. Resist the pull of the next item on your list.
• Use silence. Count to three after the customer stops speaking. The most useful thing they say often comes next.
• Play it back. Summarise what you heard, in their language, and ask what you have missed. This proves you listened, and it corrects your assumptions before they turn into a proposal.
• Park the solution. When you hear a problem your product solves, write it down. Don't say it. A better-informed moment will come.
• Agree the next step on their terms. End with what they want to explore next, not what you want to demo.

Expertise sounds like questions

In discovery, expertise shows in the quality of your questions, not the volume of your answers. The senior engineer asks what nobody else in the room thought to ask: about the migration which stalled three years ago, the team who will support this at 2am, the integration everyone is quietly worried about. Credibility is earned there, not in the feature list.

For leaders, this is a coachable skill. With the customer's permission, record and review first calls. Measure talk time against the 30:70 standard. Open every deal review with "What did you learn?" before "What did you show?"

At Apex Edge Sales Engineering, this is the discipline we practise and coach. The customer speaks for 70% of the conversation, and no solution goes on the table until their goals, environment, and thinking are clear. Discovery is where trust starts, and trust shortens the path to the Technical Win.

Next time you leave a first meeting, ask yourself two questions. Who did most of the talking? And whose story was it?

If the honest answer to the first is you, you already know the fix.

Talk less. Win more.

References

• Gong Labs, "The Highest Converting Talk-to-Listen Ratio in Sales, Based on 25,537 Sales Calls", gong.io
• Gong Labs, "Mastering discovery calls to close deals effectively" (analysis of 519,000 discovery calls), gong.io