Discovery Call

A discovery call is not a demo. It’s not a product walkthrough. It’s not a qualifying checklist where the rep runs through BANT questions and checks boxes. It’s not a pitch disguised as a conversation.

The most common mistake reps make is treating the discovery call as a warm-up for the “real” selling that comes later. In practice, the discovery call is the real selling. It’s where trust is built, urgency is created, and the foundation of the deal is laid. Everything after it either builds on that foundation or tries to compensate for its absence.

A well-run discovery call ends with the rep understanding three things:

• What the prospect’s problem actually costs them, in time, money, missed targets, or organizational pain
• Who cares enough about solving it to champion the deal internally
• What the buying process looks like: who approves, what they need to see, and how long it takes

A poorly run discovery call ends with the rep knowing the prospect “seemed interested” and not much else.

In a simple transactional sale, the buyer knows what they want, the price is straightforward, and the decision is made by one person. Discovery can be light.

In a complex B2B sale, none of that is true. The product is technical. The buyer needs to involve multiple stakeholders. The decision process includes security reviews, procurement, legal, and executive approval. The price is significant enough that someone needs to build a business case to justify it.

In that environment, the discovery call is doing heavy structural work. The rep isn’t just learning about a problem. They’re mapping an organization’s decision-making process, identifying the people who need to be involved, and building the case that will eventually travel through internal approvals without the rep in the room.

This is why discovery is harder in technical sales than in any other type of selling. The rep needs to understand enough about the prospect’s technical environment to ask credible questions, while simultaneously tracking the business context that will determine whether a deal gets funded. Holding both of those threads in a single conversation, under the pressure of a live call, is the core challenge.

The most effective discovery calls move from surface to depth, from context to consequence, from organizational pain to personal stakes.

Opening (2 to 3 minutes)

Set the agenda. Confirm how much time the prospect has. Establish what you already know so the prospect doesn’t have to repeat information. A good opening sounds like: “I’ve done some homework on your team and your current setup. I’d love to confirm a few things, then spend most of our time understanding what’s working and what’s not. Sound good?”

The opening accomplishes two things: it signals that the rep is prepared, which builds early credibility, and it sets the expectation that this is a conversation, not a pitch.

Context and current state (5 to 10 minutes)

Understand the prospect’s current situation. Not from scratch. The rep should have done enough pre-call research to ask specific, informed questions rather than generic ones.

Weak:“Tell me about your sales team.”

Better:“I saw you’ve got about 30 AEs across two regions. How is that team structured in terms of who handles enterprise versus mid-market?”

Every question that could have been answered by five minutes of research is a question that wastes the prospect’s time and signals the rep didn’t prepare.

Pain discovery (10 to 15 minutes)

This is the core of the call. The rep needs to move past the prospect’s current state and into what isn’t working. Not what they want to improve. Not what would be nice to have. What is actually causing pain, costing money, slowing growth, or creating risk.

When a prospect says “our reps struggle with technical questions on calls,” a weak rep nods and moves on. A strong rep asks: “When that happens, what does the prospect typically do? Does the deal keep moving, or does it stall until the follow-up lands?” Then: “How often is that happening across your team?” Then: “What does that do to your average deal cycle?”

Each follow-up takes the problem from an observation to a quantified cost. That cost is what builds urgency.

Implication and impact (5 to 10 minutes)

Once a pain is on the table, explore what it means. Not just for the team. For the person on the call. Organizational pain creates awareness. Personal pain creates action.

A VP of Sales who says “our reps take too long to ramp” is describing an organizational problem. That same VP who says “I personally have to join calls for every new hire’s first two months because I can’t trust them to run discovery alone” is describing something they feel every day. The questions that surface personal stakes are harder to ask but produce the conviction that moves deals forward.

Buying process and next steps (5 to 10 minutes)

Before the call ends, the rep needs to understand how a purchase actually happens in this organization. Who else needs to be involved? What does the evaluation process look like? Is there budget allocated, or does a business case need to be built?

A deal without a mapped buying process is a deal the rep can’t forecast, can’t plan for, and can’t influence. End the call with a specific, concrete next step: not “let’s reconnect next week,” but a confirmed action with a named date and a clear purpose.

Listening, not just hearing

Discovery is a listening exercise that happens to involve questions. The most common failure is a rep who asks a good question and then doesn’t listen to the answer because they’re already thinking about the next thing they want to say. Two seconds of silence after an answer often produces the real answer, the one the prospect was deciding whether to share.

Staying in the problem

The strongest instinct in sales is to solve. A prospect describes a problem and the rep’s brain immediately connects it to a feature. Staying in the problem means resisting that instinct. The pitch lands ten times harder after the prospect has fully felt the weight of their own problem. Jumping to it early short-circuits the urgency that makes deals close.

Asking questions the prospect hasn’t considered

The best discovery questions don’t just collect information. They create it. When a rep asks “what happens to your forecast when deals stall because discovery was weak?” the prospect might not have connected those two things before. A discovery call that helps the prospect think about their own problem in a new way is a call that earns the right to a second meeting.

Discovery calls are where qualification frameworks like MEDDPICC and BANT come to life. The framework provides the structure. The discovery call is where reps gather the actual evidence.

In MEDDPICC terms, a single discovery call should begin to surface:

• Metrics: how the prospect measures the impact of the problem
• Economic Buyer: who ultimately approves the purchase
• Decision Criteria: what the prospect is evaluating vendors against
• Decision Process: how the organization makes purchasing decisions
• Identified Pain: the specific, quantified problem driving the evaluation
• Champion: the person with personal motivation to push the deal forward

Not all of these will be fully resolved in a single call. But a discovery call that surfaces none of them isn’t discovery. It’s a friendly conversation.

The rep talks more than the prospect

If the rep is talking more than 30 to 40 percent of the time on a discovery call, they’re pitching, not discovering. The prospect should be doing most of the talking. That’s how information flows.

Accepting surface-level answers

“We want to improve sales productivity” is not a pain. It’s a goal statement. The rep’s job is to dig underneath it: what’s broken, what it costs, who it affects, and why it matters now.

Skipping discovery because the prospect seems ready

A prospect who came inbound, read the website, and said “this looks like what we need” is the most dangerous prospect for discovery. The rep assumes the deal is further along than it is and skips the work that would actually qualify it. Three months later, the deal stalls because no one ever mapped the buying process or identified the real exit criteria.

Turning the call into an interrogation

Twenty rapid-fire questions with no conversation in between isn’t discovery. The prospect stops giving real answers and starts giving short ones to get through it. Discovery questions need to be woven into a natural conversation. The best discovery calls feel like a dialogue between two people solving a problem together, not a survey.

Not mapping the buying process

Pain without process is a deal that can’t close. The rep leaves the call knowing the prospect has a real problem but not knowing who else needs to approve, what the evaluation looks like, or what timeline they’re working against. Two months later, the deal is stuck and the rep is surprised. They shouldn’t be. They never asked.

The two hardest things about a discovery call are knowing what to ask next and handling the moments when the prospect asks something the rep doesn’t know. Both happen under pressure, in real-time, with no opportunity to pause and look something up.

Commit solves both sides of that problem during the live call. When a prospect describes a pain, Commit pushes the follow-up questions that quantify it and explore its implications, so the rep stays in the problem instead of jumping to the pitch. When a technical question lands or a competitor gets named, Commit surfaces the right answer before the rep has to say “let me get back to you.”

The rep doesn’t need to memorize the discovery framework or hold every competitive detail in their head. The guidance is there in the moment, based on what’s actually being said, so the conversation stays natural and the discovery stays complete. That’s real-time sales enablement applied to the call that determines everything downstream.