How to Run a B2B Discovery Call That Finds Real Pain

A B2B discovery call finds real pain when you stop pitching and dig into one specific business problem until you understand its cost, its owner, and why it hasn't been solved yet. The goal is to leave the call knowing whether the buyer has a problem worth paying to fix, not to collect polite answers about "challenges." That means asking follow-up questions three or four layers deep, quantifying the impact in the buyer's own words, and being willing to disqualify the deal if the pain isn't there.

Most discovery calls fail for a simple reason. The rep asks a list of surface questions, the prospect gives surface answers, and both sides walk away with a pleasant conversation and no deal. I've sat through hundreds of these calls as a founder, as a manager listening to recordings, and as a rep myself. The pattern is always the same. This article lays out the structure, the questions, and the habits that consistently turn a discovery call into a real diagnosis.

What is the actual purpose of a discovery call?

A discovery call is a diagnosis, not a presentation. You are trying to answer four questions by the end of it:

1. Is there a real problem? Something concrete and specific, not a vague wish for "more efficiency."
2. What does it cost them? In money, time, risk, or missed opportunity.
3. Who owns it? The person who feels the pain, and the person who can approve spending to fix it.
4. Why now? The reason this problem matters this quarter instead of "someday."

If you can't answer all four after the call, you don't have a qualified opportunity yet. You might have a friendly conversation, but you don't have a deal. Frameworks like BANT and MEDDIC formalize this. If you want to go deeper on how they differ, I've written about how to qualify B2B leads using BANT vs MEDDIC. Discovery is where you gather the raw material those frameworks need.

A useful mental shift: your job is to find out whether you should sell, not to sell. Reps who internalize this ask better questions, because they're genuinely curious rather than waiting for an opening to pitch.

How should you prepare before the call?

Good discovery starts 20–30 minutes before the call. Preparation isn't about memorizing the prospect's LinkedIn profile. It's about forming hypotheses you can test.

Build three pain hypotheses

Before every call, write down three specific problems you suspect this company has, based on their industry, size, recent news, and job postings. For example, if you sell outbound sales services and the prospect is a 40-person SaaS company that just posted two SDR roles:

• Hypothesis 1: Their founder is still closing most deals and pipeline drops whenever they get busy.
• Hypothesis 2: They hired SDRs before but ramp time was long and meetings booked were low quality.
• Hypothesis 3: They raised a round recently and the board expects pipeline growth the current team can't deliver.

You won't be right about all three. That's fine. Hypotheses give you sharper opening questions than "So, what are your biggest challenges?" AI tools can speed up this research considerably. I've covered a practical workflow in how to use AI to prepare for sales calls.

Know what "good" looks like

Decide in advance what you need to learn for the call to count as a success. For example: "I need to confirm the pain, get a rough cost figure, and learn who else is involved in the decision." Write it down. When the call ends, check yourself against it.

How do you structure a 30-minute discovery call?

Here's a structure that works well for most B2B calls. Adjust the timings for 45 or 60 minutes, but keep the proportions.

1. Opening and agenda (2–3 minutes). Confirm the time, state the purpose, and ask permission to ask questions.
2. Context (3–5 minutes). Understand their role, team, and current setup.
3. Pain exploration (12–15 minutes). This is the heart of the call. Go deep on one or two problems.
4. Impact and urgency (4–5 minutes). Quantify the cost and find out why now.
5. Decision process (3 minutes). Who's involved, how they buy, what the timeline looks like.
6. Next step (2–3 minutes). Agree on a specific, calendared action.

Notice what's missing: a product demo. If you spend more than a few minutes talking about your solution in discovery, you've skipped the diagnosis. A useful benchmark is the prospect should talk for roughly 60–70% of the call. If you record your calls, check your talk ratio after a week. Most reps are surprised by how much they talk. (If you're choosing a tool for this, see my comparison of AI call recording tools for sales teams.)

A strong opening

Something like this works:

"Thanks for making time. I've got us down for 30 minutes. Does that still work? My goal today is to understand how you're handling [area] right now and whether there's a problem worth solving. I'll ask a fair number of questions. At the end, if it looks like we can help, we'll talk about next steps. If not, I'll tell you honestly. Sound fair?"

That last line matters. Telling a buyer you're willing to walk away lowers their guard and gets you more honest answers.

How do you get past surface-level answers?

This is where most discovery calls die. The prospect says something like "We want to improve our pipeline," the rep writes it down and moves to the next question. That's a symptom, not a pain.

Use the "three layers deep" rule

For every problem the prospect mentions, ask at least three follow-up questions before moving on. Here's what that looks like in practice:

• Prospect: "Our pipeline is a bit thin."
• Layer 1: "When you say thin, what does that look like in numbers? How many qualified opportunities are you seeing per month versus what you need?"
• Prospect: "We're getting maybe 8 a month. We need closer to 20 to hit plan."
• Layer 2: "What happens if that gap stays at 12 for the next two quarters?"
• Prospect: "We'd miss the annual target, and honestly, the next funding round gets harder."
• Layer 3: "Who feels that most internally? Who's having that conversation with the board?"
• Prospect: "Our CEO. She's been asking me about it every week."

Now you have something real: a measurable gap, a business consequence, and a person under pressure. "Our pipeline is a bit thin" told you nothing. Three follow-ups told you everything.

Questions that consistently unlock real pain

Keep a short list of go-to follow-ups. These work across almost any B2B sale:

• "Can you walk me through the last time that happened?"
• "What did that cost you, roughly?"
• "What have you already tried to fix it?"
• "Why didn't that work?"
• "What happens if nothing changes in the next six months?"
• "Who else is affected by this?"
• "How are you measuring this today?"

"Walk me through the last time that happened" is the most powerful question on this list. It forces the prospect out of generalities and into a specific story, and specific stories contain the details you need: who was involved, how long it took, what broke.

Listen for emotional language

When a prospect says "frustrating," "honestly," "nightmare," or "I'm tired of," slow down. That's where the real pain lives. Reflect it back: "You said it's been frustrating. What's the most frustrating part?" People rarely buy to fix problems they feel neutral about.

How do you quantify the pain without sounding like a calculator?

Buyers need a number to justify spending money, and you need one to build a credible proposal later. But asking "What's the ROI of solving this?" feels clumsy and puts them on the spot.

Instead, build the number together in small pieces:

1. "How many deals does a typical rep close per quarter?"
2. "What's your average contract value, roughly?"
3. "If the pipeline gap is about 12 opportunities a month, and you close maybe 1 in 5, how many lost deals is that?"

Let them do the math out loud. If they close 1 in 5, a gap of 12 opportunities a month is roughly 2–3 deals a month, or around 30 a year. Multiply by their average deal size and the cost of inaction becomes obvious, and it's their number, not yours.

This figure becomes the backbone of everything that follows. When you later write a B2B sales proposal that gets signed, you'll anchor it to the cost the buyer quantified themselves. And when price objections come up, you'll be comparing your price to a problem they've already sized, which makes those conversations far easier.

What mistakes ruin discovery calls?

After listening to a lot of call recordings with teams, I see the same mistakes over and over:

• Pitching too early. The moment a prospect mentions a problem your product solves, the rep jumps in with "We actually do exactly that!" The conversation is over. You've traded diagnosis for a feature list.
• Stacking questions. "How's your team structured, and what tools do you use, and who handles outbound?" The prospect answers the easiest one. Ask one question at a time, then stay quiet.
• Accepting "we're fine." Sometimes it's true. Often it's a defensive reflex. Try: "That's great to hear. If you could change one thing about how it works today, what would it be?"
• Interrogating instead of conversing. Running down a checklist of 25 questions makes buyers feel processed. Use your question list as a map, not a script.
• Not disqualifying. If there's no pain, no budget path, and no urgency, say so. A clean "no" saves you weeks of chasing and makes your forecast honest.
• Ending without a next step. "I'll send over some info" is not a next step. A next step has a date, a time, and named attendees.

How do you uncover the decision process?

Real pain doesn't close deals on its own. Someone has to approve the purchase, and in B2B there are usually several someones. Toward the end of the call, ask:

• "If you decided this was worth solving, how would that decision get made?"
• "Who else would need to be involved?"
• "Have you bought something similar before? How did that process go?"
• "Is there anything that's blocked a purchase like this in the past?"

The question about past purchases is underrated. It reveals the real process (procurement, legal review, a CFO sign-off threshold) rather than the idealized version.

A note from doing business in Turkey: in many Turkish companies, especially family-owned or founder-led businesses, the final decision often sits with the owner or general manager even when you're talking to a capable department head. Ask about this respectfully and early: "Typically, would something like this go to [owner/GM] for final approval?" It's a normal question, and buyers appreciate that you understand how their company works.

How do you close a discovery call with a real next step?

End by summarizing what you heard, then propose a specific action:

"Let me make sure I got this right. You're generating about 8 qualified opportunities a month against a need of 20. That gap puts roughly 30 deals a year at risk, and your CEO is feeling pressure from the board. You tried hiring two SDRs last year but ramp took too long. Did I miss anything?"

The prospect will usually correct or add something, which is gold. Then:

"Based on this, I think it's worth a 45-minute session where I show you how we'd approach that gap specifically. It'd help to have your CEO there, since she owns the target. Would Thursday at 2 or Friday at 10 work better?"

Offer two specific times. Send the calendar invite before you hang up if you can. Speed here directly affects deal velocity, one of the simplest ways to shorten the B2B sales cycle.

If your team struggles to get enough discovery calls on the calendar in the first place, that's a pipeline problem rather than a discovery problem. That's the work we do at SAAS Corner, which runs outbound sales and lead generation for B2B SaaS companies, and the discipline described here is exactly what we expect after a meeting is booked.

FAQ

How long should a B2B discovery call be?

Most B2B discovery calls work best at 30 to 45 minutes. Thirty minutes is enough for a focused conversation about one or two problems, while complex enterprise deals with multiple stakeholders may need 45 to 60 minutes. Whatever the length, the prospect should be doing most of the talking.

How many questions should I ask in a discovery call?

There's no fixed number, but fewer, deeper questions beat a long checklist. Many strong calls revolve around 8 to 12 core questions, each followed by two or three follow-ups. Depth on one real problem is far more valuable than shallow answers on ten.

What if the prospect doesn't have any real pain?

Then you should say so and end the sales process politely, or agree to reconnect later if circumstances change. Pushing a deal without real pain leads to stalled pipelines, inaccurate forecasts, and wasted time on both sides. A clean disqualification is a successful discovery call.

Should I demo the product during discovery?

Generally, no. Discovery is for understanding the buyer's problem, and a demo shifts attention to your features before you know which ones matter. Save the demo for the next meeting, where you can tailor it to the specific pain and numbers the buyer shared.

Conclusion

Finding real pain in a discovery call comes down to a few disciplined habits: prepare hypotheses instead of generic questions, go three layers deep on every problem, let the buyer quantify the cost in their own numbers, map the decision process, and never leave without a calendared next step. None of this is complicated, but it takes practice and honest self-review, ideally by listening to your own recordings every week.

When discovery is done well, everything downstream gets easier. Proposals write themselves, objections shrink, and your forecast starts reflecting reality. If you'd like to talk through how your team runs discovery, or how to build the pipeline that feeds it, feel free to [get in touch with me here](/).

Related Posts

• How to Write a B2B Sales Proposal That Gets Signed
• How to Handle Price Objections in B2B Sales Calls
• How to Qualify B2B Leads: BANT vs MEDDIC Explained
• How to Shorten the B2B Sales Cycle: 7 Practical Methods