Discovery Call Framework: Questions, Scripts & the 30-Minute Structure

Discovery Call Framework: The Complete Guide to Running Discovery That Wins Deals

Updated March 2026 — A complete discovery call framework with the 30-minute structure, 30+ questions organised by BANT, MEDDIC, and SPICED, talk track examples, qualification and disqualification criteria, common mistakes, and 8 FAQs.

Discovery is where deals are won or lost. Not in the demo, not in the negotiation, not in the proposal — on the discovery call.

The best closers in B2B sales are not silver-tongued presenters. They are disciplined discoverers who ask better questions, listen more carefully, and leave every call with a clear picture of whether the deal is real.

Yet most teams treat discovery as a checkbox. "Did you do a disco call? Great, schedule the demo." No structure, no framework, no systematic approach to uncovering pain or qualifying whether the opportunity is worth pursuing.

I am Jamie Partridge, founder of UpliftGTM. I run sales enablement programmes and fractional VP of Sales engagements (see our fractional VP Sales roundup) for B2B technology companies, and discovery is the single area where I see the biggest gap between what good looks like and what actually happens. This is the framework we use with every client.

By the end you will have a minute-by-minute structure for a 30-minute discovery call, 30+ questions across three frameworks, talk tracks, and qualification criteria. If you are building a broader sales playbook, this slots directly into the discovery section.

---

Why Discovery Matters More Than Any Other Sales Stage

Before we get into the framework, let us establish why discovery deserves more attention than any other part of your sales process.

The data on discovery and win rates

Research from Gong, analysing millions of B2B sales calls, consistently shows that the number of questions asked on a discovery call directly correlates with deal progression. Calls with 11-14 discovery questions have the highest conversion rates to next steps. Fewer than that and you are not uncovering enough. More than that and you are interrogating, not conversing.

Separate research from RAIN Group found that sellers who excel at understanding buyer needs win 2.5x more often than those who lead with product features. And Forrester's B2B buying research shows that buyers consistently favour vendors who were first to add insight during the evaluation — which almost always happens during discovery, not in the demo.

What bad discovery costs you

When discovery is weak, everything downstream suffers:

• Demos miss the mark. You present features that do not address the prospect's actual problem because you never uncovered it.
• Proposals get ignored. Your proposal does not resonate because it addresses what you think they need, not what they told you they need.
• Deals stall. You cannot build urgency because you never explored the cost of inaction.
• Forecasts collapse. You qualified based on surface-level information and the deal was never real.
• Win rates drop. Competitors who run better discovery understand the buyer better and position more effectively.

Poor discovery is the root cause of most pipeline problems. Fix discovery and you fix a surprising number of downstream issues. Salesforce's annual State of Sales report reinforces this — high-performing reps consistently spend more time understanding the buyer before they ever pitch a solution.

---

The 30-Minute Discovery Call Structure

Every discovery call should follow a structure — not a rigid script, but a framework that ensures you cover the right ground in the right order. Here is the 30-minute structure we use with clients.

Minute 0-3: Opening and Agenda Setting (3 minutes)

The first three minutes set the tone. Your goals: make the prospect comfortable, establish credibility, set an agenda, and get permission to ask questions.

Talk track example:

"Thanks for making time today, [Name]. Before we jump in, let me suggest how we use the next 30 minutes. I would love to start by understanding your current situation and what prompted this call. Then I can share some context about how we have helped similar companies. At the end, we can decide together whether it makes sense to continue. Does that work, or is there anything specific you want to make sure we cover?"

What this achieves:

• Respect for their time. You have acknowledged that 30 minutes is the commitment.
• Shared agenda. They know what to expect and can add their priorities.
• Permission to discover. You have explicitly set up that you will be asking questions first — not pitching.
• Clear exit criteria. You have framed the outcome as a mutual decision, not a hard sell.

One critical detail: always ask if there is anything they want to add to the agenda. If they say "actually, I mainly want to understand pricing," you now know their real priority and can adjust accordingly.

Minute 3-5: Rapport Building (2 minutes)

Rapport is not small talk for its own sake — it is two minutes of genuine connection that makes the next 25 minutes more productive. People share more openly with someone they feel comfortable with.

Effective rapport-building approaches:

• Reference something specific from their LinkedIn profile or recent company news: "I saw you joined [Company] about six months ago — how has the transition been?"
• Acknowledge a shared connection or experience: "I noticed you used to be at [Previous Company]. We actually worked with their team on [relevant context]."
• Comment on something relevant to their role: "I imagine leading [function] at a company growing as fast as [Company] keeps you pretty busy."

What to avoid:

• Generic weather or sports chat — it wastes time and signals you have nothing more thoughtful to say.
• Over-researching to the point of seeming like a stalker — one or two observations is enough.
• Spending more than two minutes — you are on the clock and they know it.

Minute 5-10: Situation Questions (5 minutes)

Situation questions establish the current state — team, tools, process, metrics — before you probe for problems. Think of this as laying the foundation.

Key situation questions:

1. "Can you walk me through how your team currently handles [relevant process]?"
2. "What tools are you using today for [relevant function]?"
3. "How is your team structured? How many people are involved in [relevant area]?"
4. "What does your current workflow look like from [starting point] to [end point]?"
5. "What metrics are you tracking, and how are they trending?"

Talk track example:

"Before we get into the challenges, help me understand the lay of the land. Can you give me a quick overview of how your team currently handles [relevant process] — team size, tools, typical workflow?"

Important notes on situation questions:

• Do not linger past five minutes. Situation questions are factual and can feel like an interrogation if overplayed.
• Research before the call so you do not waste time on questions you could have answered with LinkedIn or their website.
• Listen for implicit signals. "We are using [tool] but we built a lot of custom workarounds" has just handed you a problem.

Minute 10-18: Problem Questions (8 minutes)

This is the heart of discovery. Problem questions uncover the gaps and frustrations in their current state — where great sellers separate themselves from average ones.

Go deep, not wide. Better to fully explore two or three problems than to touch superficially on seven. When you hit a pain point, resist the urge to pitch. Stay curious and keep digging.

Key problem questions:

1. "What is working well with your current approach, and where are you seeing the biggest gaps?"
2. "If you could change one thing about how [process] works today, what would it be?"
3. "What happens when [relevant process] breaks down? How often does that occur?"
4. "Where are you spending the most time on things that feel like they should be easier?"
5. "What have you tried in the past to solve this? What worked and what did not?"

The layering technique:

When a prospect mentions a problem, layer your follow-up questions to go deeper:

• Layer 1 — Surface: "You mentioned [problem]. Can you tell me more about that?"
• Layer 2 — Frequency: "How often does this come up? Is it occasional or constant?"
• Layer 3 — Cause: "What do you think is driving that? Where does it originate?"
• Layer 4 — Attempts: "What have you tried to fix it?"
• Layer 5 — Implication: "What happens to the business when this goes unresolved?"

Talk track example:

Prospect: "Our biggest challenge is that we do not have visibility into our pipeline. By the time we realise a deal is stuck, it is too late."

You: "That sounds frustrating. When you say you do not have visibility, what does that look like in practice? Are reps updating the CRM inconsistently, or is the data there but not surfaced in a useful way?"

Prospect: "Both, honestly. Reps hate updating Salesforce, and even when they do, the reports we pull are not actionable."

You: "Got it. So you have a data quality issue on the input side and a reporting gap on the output side. How is that affecting your ability to forecast?"

Notice how each question builds on what they just said. You are not running through a checklist — you are following the thread of their pain and pulling it further.

Minute 18-23: Impact Questions (5 minutes)

Impact questions quantify the consequences of the problems they have described, connecting operational pain to business outcomes — revenue, cost, risk, time, and opportunity cost. Most prospects have not done this calculation themselves. Help them see the true cost of inaction and you create urgency without being pushy.

Key impact questions:

1. "What is the business impact of that? Can you put a number on it?"
2. "When deals stall because of [problem], what does that cost you per quarter?"
3. "How is this affecting your team's ability to hit their targets?"
4. "If this problem continues for another 12 months, what happens?"
5. "Beyond the financial impact, how is this affecting your team's morale and retention?"

Talk track example:

"You mentioned that pipeline visibility is causing forecast misses. If I understand correctly, you are missing your forecast by roughly 15% each quarter. On a £2M quarterly target, that is £300K in missed revenue. Over a year, we are talking about £1.2M. Is that roughly right, or am I overestimating?"

Why impact questions matter so much:

• They build the business case for change without you having to make it yourself — the prospect does it in their own words.
• They create internal urgency that the prospect carries back to their stakeholders.
• They give you the ROI story you need for the proposal and the executive sponsor conversation.
• They separate real problems (with quantifiable impact) from nice-to-haves (annoying but not costing real money).

Minute 23-26: Future State Questions (3 minutes)

Future state questions shift the conversation from pain to aspiration. Help the prospect articulate what success looks like — that becomes the blueprint for your demo, proposal, and value narrative.

Key future state questions:

1. "If you solved this problem, what would that look like in 12 months?"
2. "What would your team be able to do that they cannot do today?"
3. "If you had perfect [process/visibility/data], what decisions would you make differently?"
4. "What does success look like for this initiative — how will you measure it?"
5. "When you think about where you want the team to be by [relevant date], what needs to change?"

Talk track example:

"So we have talked about the challenges — pipeline visibility, forecast accuracy, rep adoption. Let me flip the question. If we fast forward 12 months and you have solved these problems, what does that look like? What are the first things you would notice are different?"

This question is powerful because it gets the prospect to sell themselves on the outcome. They are not just describing problems anymore — they are imagining a better future. And when you later present your solution, you are not pitching features — you are connecting capabilities to the future they just described.

Minute 26-30: Next Steps and Close (4 minutes)

The final four minutes are about aligning on what happens next. This is where many reps lose the plot — ending with a vague "let me send you some information" or pushing for a demo without confirming qualification.

The structured close:

1. Summarise what you heard. Replay their key problems, impacts, and desired outcomes. This proves you listened and gives them a chance to correct anything.
2. Confirm mutual interest. Ask whether this is worth continuing to explore, based on what you have discussed.
3. Propose a specific next step. Not "let's reconnect sometime" but a concrete action with a date and time.
4. Identify who else needs to be involved. If there are other stakeholders, get names and roles now.

Talk track example:

"Let me make sure I have this right. Your biggest challenges are [problem 1], [problem 2], and [problem 3]. The business impact is roughly [quantified impact]. What you are looking for is [future state]. Is that a fair summary?"

[Prospect confirms or adjusts]

"I think there is a strong fit here. My recommendation is a 45-minute session where I can walk you through relevant case studies and show you the product in the context of your use case. Would next Tuesday or Thursday work?"

"One more question — who else on your team would benefit from being in that session?"

---

30+ Discovery Questions Organised by Framework

Different qualification frameworks emphasise different aspects of the opportunity. Here are question sets for the three most widely used: BANT, MEDDIC, and SPICED.

BANT Discovery Questions

BANT (Budget, Authority, Need, Timeline) is the original qualification framework — popularised by IBM and still widely covered by sales-training resources like the HubSpot Sales Blog. It is straightforward and works well for transactional and mid-market sales. Its weakness is that it can feel like an interrogation if you run through the letters sequentially. Weave these questions naturally into your conversation.

Budget:

1. "Have you allocated budget for solving this problem, or would this be a new budget request?"
2. "What is the typical approval process for an investment of this size?"
3. "Is there a budget range you are working within, or is it more about proving the ROI first?"
4. "Have you invested in solutions for this before? What did that look like?"
5. "If we can demonstrate clear ROI, is budget a constraint or a formality?"

Authority:

6. "Who else is involved in evaluating solutions like this?"
7. "Walk me through how decisions like this typically get made at [Company]."
8. "Is there an executive sponsor for this initiative?"
9. "If we get to the point where this is a go, who signs off?"
10. "Who on your team would be most affected by a change here?"

Need:

11. "On a scale of 1-10, how critical is solving this problem for your team right now?"
12. "What prompted you to start looking at solutions now, as opposed to six months ago?"
13. "If you do nothing and keep the current approach, what happens?"
14. "How does this initiative rank relative to your other priorities this quarter?"
15. "Is this a must-solve or a nice-to-solve?"

Timeline:

16. "Is there a specific date or event driving your timeline?"
17. "When would you ideally want a solution in place and operational?"
18. "What is your evaluation process? How many vendors are you talking to?"
19. "Are there any internal milestones — board meetings, planning cycles, fiscal year changes — that affect timing?"
20. "If we agreed this was the right solution, how quickly could you move?"

MEDDIC Discovery Questions

MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is the gold standard for enterprise sales — deeper than BANT and designed for multi-stakeholder deals with longer cycles.

Metrics:

1. "What KPIs are you measured on that this initiative would impact?"
2. "If we solved this problem, what number would move? By how much?"
3. "How are you measuring success for this project?"
4. "What is the current performance gap between where you are and where you need to be?"

Economic Buyer:

5. "Who ultimately owns the budget for this decision?"
6. "What does the economic buyer care about most — cost savings, revenue growth, risk reduction, or efficiency?"
7. "Have you already spoken with [economic buyer] about this, or is that a conversation that still needs to happen?"
8. "What would the economic buyer need to see to approve this investment?"

Decision Criteria:

9. "What are the must-haves versus the nice-to-haves in your evaluation?"
10. "Beyond product capabilities, what other factors matter — implementation timeline, support model, integration requirements?"
11. "Are you comparing us against other vendors, an internal build, or doing nothing?"
12. "What criteria will you use to make the final decision?"

Decision Process:

13. "Can you walk me through the steps between here and a signed agreement?"
14. "What does your procurement or legal review process look like?"
15. "Is there a formal evaluation committee, or is it more informal?"
16. "What could derail or delay this process?"

Identify Pain:

17. "What is the single biggest frustration your team has with the current situation?"
18. "What has this problem cost you in the last 12 months?"
19. "How long has this been an issue? What has changed to make it urgent now?"
20. "If you had to present the case for change to your board, what would you say?"

Champion:

21. "Who on your team is most passionate about solving this problem?"
22. "If we are not in the room, who is advocating for this solution internally?"
23. "What would help you build the internal case for this?"
24. "What obstacles do you anticipate from other stakeholders, and how can we help you address them?"

SPICED Discovery Questions

SPICED (Situation, Pain, Impact, Critical Event, Decision) is a newer framework that works well for SaaS. It emphasises urgency through critical events and is particularly effective for understanding why now.

Situation:

1. "Give me the 60-second version of your current setup for [relevant area]."
2. "What has changed in the last 6-12 months that is relevant to this conversation?"
3. "How does your team currently measure success in [area]?"

Pain:

4. "What is not working the way it should?"
5. "Where are you losing the most time, money, or opportunities?"
6. "What keeps you up at night about [relevant area]?"

Impact:

7. "What is the downstream effect of that pain on the broader business?"
8. "How is this affecting your ability to hit your goals this year?"
9. "What is the cost of inaction — what happens if you do nothing for another quarter?"

Critical Event:

10. "Is there a specific event or deadline driving this initiative?"
11. "What happens if you do not have a solution in place by [date]?"
12. "Is this tied to a board commitment, a funding round, or a go-live date?"

Decision:

13. "What does your decision process look like from here?"
14. "Who needs to be involved, and what do they each care about?"
15. "What would make this an easy yes — or a definitive no?"

---

Talk Track Examples for Common Discovery Scenarios

Frameworks are only useful when you can apply them fluidly. Here are talk tracks for five common scenarios.

Scenario 1: The Prospect Who Wants to Jump Straight to a Demo

The prospect has decided they want to see the product and views discovery as an obstacle. Resist the urge to comply — a demo without context wastes everyone's time.

"I completely understand — and I want to make sure that when I do show you the product, I am showing you the parts that actually matter for your situation. If you give me 10-15 minutes of context, I can tailor the demo to your use case and make it dramatically more useful. Fair?"

Scenario 2: The Prospect Who Gives One-Word Answers

Some prospects are guarded, busy, or not sure whether they trust you yet. Ask more open-ended questions and share relevant observations to get them talking.

"A lot of [type of company] at your stage are dealing with [specific challenge]. Is that something your team is experiencing, or is it a different set of priorities for you?"

If they remain monosyllabic, address it directly:

"I want to use your time well. It feels like you might have something specific on your mind — would it be more helpful if I addressed a particular question first?"

Scenario 3: The Prospect Who Has Already Decided on a Competitor

When a prospect is late in their evaluation and leaning toward another vendor, uncover the criteria they are using and whether those criteria actually serve their needs.

"It sounds like you have done a thorough evaluation. What were the top three criteria you used to narrow your options? And looking back at your original goals for this project, do those criteria still feel like the right ones?"

Scenario 4: The Prospect Sent by Someone Else

Often the person on the call is not the decision-maker — they were sent to do a preliminary evaluation. Your goal is to equip them to be your champion.

"Thanks for taking the time, [Name]. Who asked you to evaluate this, and what did they say they were hoping to solve? I want to make sure I give you everything you need to bring back a clear recommendation."

Scenario 5: The Inbound Lead Who Filled Out a Form

Inbound leads have self-selected, but you still need to qualify. The danger is assuming they are ready to buy when they may have only downloaded a whitepaper.

"I saw you [downloaded our guide / requested a demo / filled out our contact form]. What prompted you to look into this now? I do not want to make assumptions about where you are in the process."

---

How to Qualify (and Disqualify) on Discovery Calls

Not every discovery call should lead to a next step. One of the most valuable skills in B2B sales is disqualifying prospects who are not a fit — quickly, professionally, and without burning the relationship.

Qualification criteria: signals the deal is real

A well-qualified opportunity will show most of these signals during discovery:

• Identified pain. The prospect has articulated a specific, concrete problem — not a vague interest in "exploring options."
• Quantified impact. They can connect the problem to a business metric — revenue, cost, time, or risk.
• Urgency driver. There is a reason this matters now, not in six months.
• Budget indication. They have budget allocated, are willing to make a business case, or have indicated the investment range is realistic.
• Authority access. You know who the decision-maker is and have a path to them.
• Clear next step. The prospect agrees to a specific next action with a specific date.
• Champion identified. Someone inside the organisation wants this to happen and will advocate internally.

If you have four or more of these signals after discovery, the opportunity is worth pursuing aggressively. Track these signals in your CRM using a lead scoring approach to ensure consistency across the team.

Disqualification criteria: signals that you should walk away

Walking away from a bad-fit opportunity is not failure — it is discipline. Here are the warning signs:

• No identified pain. They cannot articulate what problem they are trying to solve. "We are just exploring" is not a reason to buy.
• No urgency. There is no compelling event, no deadline, no consequence for waiting. These deals will stall indefinitely.
• Wrong buyer. The person on the call has no influence over the decision and cannot connect you to someone who does.
• Budget mismatch. Your solution costs £50K and they are looking for something under £5K. No amount of selling will close a 10x budget gap.
• Solution mismatch. Your product genuinely does not solve their problem. Forcing a fit will create a churned customer and a bad review.
• Uncoachable prospect. They are not willing to share information, answer questions, or engage in a genuine two-way conversation.

How to disqualify gracefully

Disqualification does not mean hanging up. It means being honest, professional, and helpful — even when the answer is "we are not the right fit."

"Based on what you have shared, I want to be upfront — I do not think we are the best fit right now. Your primary need is [X], and while we do [Y], I think you would be better served by a solution that specialises in [X]. I am happy to point you in the right direction if that would help."

This builds trust (you prioritised their needs over your pipeline), saves your time for winnable deals, and creates a positive impression that may lead to referrals or a future opportunity.

---

Common Discovery Call Mistakes

After sitting in on hundreds of discovery calls across dozens of B2B companies, these are the mistakes I see most often. If you are building your SDR playbook, flag these as coaching points.

Mistake 1: Pitching too early

A prospect mentions a problem and the rep jumps straight into "well, what we do is..." That kills discovery — the prospect was about to share something valuable and you cut them off to pitch.

The fix: When you hear a pain point, respond with curiosity, not a solution. "Tell me more about that" is always the right next move.

Mistake 2: Asking questions you should already know the answer to

"So, what does your company do?" is an instant credibility killer. If the information is on their website, LinkedIn, or in your CRM, research it before the call.

The fix: Use pre-call research to skip basic situation questions. Instead of "how big is your sales team?" try "I saw you have about 30 reps on LinkedIn — is that roughly right?"

Mistake 3: Running through questions like a checklist

Reading questions off a list without connecting them to the prospect's answers turns the call into a survey. Prospects disengage because they feel like a checkbox.

The fix: Listen to each answer and let it guide your next question. Great discovery feels like a natural conversation that happens to cover the right topics.

Mistake 4: Talking too much

Gong's call analysis shows that on successful discovery calls the prospect talks roughly 57% of the time and the rep 43%. On unsuccessful calls those numbers flip.

The fix: Ask a question, then be quiet. Count to three before jumping in. The prospect will fill the silence with valuable information.

Mistake 5: Failing to quantify impact

If you do not help prospects quantify a problem, it stays abstract — and abstract problems do not create urgency. Numbers do.

The fix: Ask "what is the business impact of that?" then "can you put a rough number on it?" Even a ballpark — "probably £200K a year in lost deals" — is powerful in a proposal.

Mistake 6: Not confirming next steps

The call goes brilliantly, and then the rep says "great, I will send you an email to follow up" and hangs up. No specific next step, no date, no commitment.

The fix: Always end with a scheduled next step. "Can we book 45 minutes next Tuesday at 2pm?" beats "I will follow up" every time.

Mistake 7: Not identifying all stakeholders

You run a great discovery with a mid-level manager. They schedule a demo and bring in a VP you have never met who has completely different priorities. You are blindsided.

The fix: Always ask "who else needs to be involved?" and "who should be in the next meeting?" before you hang up. Build the relationship map early.

Mistake 8: Treating every call the same

A £10K deal does not need the same depth as a £500K deal. An inbound demo request does not need the same approach as a cold outbound prospect (booked by your SDRs or one of the best outbound sales agencies) who agreed reluctantly.

The fix: Scale discovery to the opportunity. Smaller, transactional deals can run a 15-minute discovery; enterprise deals may need multiple sessions across stakeholder groups.

---

Building Discovery into Your Sales Process

Discovery is not a standalone event — it is a muscle embedded across your entire sales process. Here is how to make it systematic.

Pre-call preparation checklist

Complete this before every dial:

• Research the company. Industry, size, recent news, funding, key challenges.
• Research the person. Role, tenure, background, LinkedIn activity, shared connections — the LinkedIn Sales blog is a good source of current best practice for social-led prep.
• Review existing data. CRM notes, previous interactions, marketing engagement (content downloads, webinar attendance, page visits).
• Prepare hypothesis. Based on your research, what do you think their top two or three challenges might be?
• Prepare questions. Choose 8-12 questions from the frameworks above that are most relevant to this prospect.
• Set a goal. What do you need to learn on this call to determine fit and propose a next step?

If you are an SDR setting up discovery calls for account executives, make sure the handoff includes all of this context. See our SDR playbook for a detailed handoff framework.

Post-call documentation

Within 30 minutes of every discovery call, the rep should document the following in the CRM:

• Key pain points. In the prospect's own words, not your interpretation.
• Quantified impact. Any numbers they shared about the cost of the problem.
• Decision process. Who is involved, what the timeline looks like, what the steps are.
• Competitive landscape. Other solutions they are evaluating, including doing nothing.
• Champion. Who is your internal advocate and what do they care about?
• Next steps. What was agreed, when, and with whom.
• Qualification score. Based on your criteria, how qualified is this opportunity?

Discovery call recording and coaching

If you are not recording and reviewing discovery calls, you are missing the biggest coaching opportunity in your sales process. Tools like Gong, Chorus, and Clari capture and analyse calls automatically. Review two calls per rep per week with specific feedback on question quality, listening, and next-step setting.

When building your cold calling programme, apply the same coaching rigour to initial conversations that you do to formal discovery — the skills transfer directly, and ZoomInfo's cold-calling research shows the connect-to-meeting conversion improves sharply when reps ask discovery-style questions on the very first call.

---

Advanced Discovery Techniques

Once your team has mastered the basics, these advanced techniques will further improve conversion rates.

The negative reverse

Instead of pushing forward, pull back. This works especially well when a prospect is guarded or when you want to test the strength of their commitment.

"Based on what you have told me, it honestly sounds like your current approach is working well enough. Why not just stick with it?"

This forces the prospect to argue for change — which is far more powerful than you arguing for it. They will articulate the reasons they need to act, in their own words, with their own conviction.

The third-party story

When prospects are reluctant to share information directly, use third-party stories to normalise the conversation and prompt them to self-identify.

"A lot of the [company type] we work with tell us their biggest challenge is [common challenge]. Some of them deal with [variation A], others struggle more with [variation B]. Does either of those resonate, or is your situation different?"

The future-pacing close

At the end of discovery, paint a picture of the future state using the prospect's own words:

"So if I am hearing you right, 12 months from now, you want [outcome 1], [outcome 2], and [outcome 3]. Your team would be spending less time on [pain point] and more time on [high-value activity]. The metrics you would track are [metric 1] and [metric 2]. Does that feel like the right vision?"

When they say yes, they have just verbally committed to the outcome your solution delivers.

The pre-mortem

Borrow this from project management. Instead of asking "what could go wrong?" reframe it as a pre-mortem:

"Let us imagine it is six months from now and this project has stalled or failed. What would have caused that?"

This gives the prospect permission to voice concerns and objections early — when you can still address them — rather than having them surface as deal-killing obstacles later in the process.

---

Frequently Asked Questions

What is a discovery call in B2B sales?

A discovery call is a structured conversation at the start of the sales process. A sales rep asks questions to understand the prospect's current situation, challenges, goals, and buying process. The purpose is to determine whether there is a fit between the prospect's needs and the seller's solution, and to gather the information needed to tailor subsequent conversations — demos, proposals, and negotiations — to the prospect's specific context. A good discovery call typically lasts 20-30 minutes and focuses primarily on listening, not pitching.

How many questions should I ask on a discovery call?

Research from Gong shows that the sweet spot is 11-14 questions per 30-minute call. Fewer than that and you are not uncovering enough information to properly qualify and position. More than that and the call starts to feel like an interrogation rather than a conversation. Quality matters more than quantity — a handful of well-placed, open-ended questions that lead to deep, layered follow-ups will always outperform a long list of superficial questions rattled off in sequence.

Should discovery and demo be the same call?

For most B2B sales, no. Combining discovery and demo into one call creates several problems: you end up rushing discovery to get to the demo, your demo is not tailored because you just learned the context minutes ago, and you lose the opportunity to prepare a customised presentation. The exception is very transactional, low-ACV sales where the buying cycle is short and prospects expect to see the product immediately. For deals above £10K ACV, separate discovery and demo into distinct meetings.

What is the difference between BANT, MEDDIC, and SPICED?

BANT (Budget, Authority, Need, Timeline) is the simplest framework and works well for mid-market transactional sales. MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is designed for complex enterprise sales with multiple stakeholders and longer cycles. SPICED (Situation, Pain, Impact, Critical Event, Decision) is a more modern framework popular in SaaS that emphasises urgency through critical events. There is no universally correct framework — choose based on your deal complexity, average contract value, and sales cycle length.

How do I get a prospect to open up on a discovery call?

Three things make prospects open up: safety, relevance, and reciprocity. Safety means setting an agenda, asking permission to ask questions, and making it clear there is no hard sell. Relevance means demonstrating through your questions that you understand their world — generic questions get generic answers. Reciprocity means sharing relevant insights or observations between questions, not just extracting information. When a prospect mentions a challenge, share a brief (10-15 second) observation about how you have seen others handle it, then ask another question. This turns the call from an interrogation into an exchange.

How do I handle a discovery call when multiple stakeholders are on the line?

Multi-stakeholder discovery calls are common in enterprise sales. The key is to acknowledge everyone, understand their individual perspectives, and manage the conversation so one person does not dominate. Start by asking each person to briefly share their role and what they are hoping to get out of the conversation. Then direct specific questions to specific people based on their role — ask the technical buyer about integration requirements, ask the business buyer about ROI expectations, and ask the end user about workflow pain points. Summarise at the end by linking each person's priorities together into a unified picture.

What should I do after a discovery call?

Within 30 minutes, send a follow-up email that summarises what you discussed — the key challenges they shared, the business impact, and the agreed next steps. This serves three purposes: it confirms you listened, it gives the prospect something they can forward to other stakeholders, and it creates a written record they can reference. Then update your CRM with detailed notes, score the opportunity against your qualification criteria, and begin preparing for the next meeting. If you agreed to share any resources or references, send them within 24 hours.

How long should a discovery call last?

Thirty minutes is the ideal length for most B2B discovery calls. It is long enough to build rapport, uncover key problems, explore impact, and set next steps — but short enough to respect the prospect's time and keep the conversation focused. Some enterprise deals with complex buying processes may need 45-60 minutes, but only if the prospect signals willingness. For high-volume, lower-ACV sales, you can run effective discovery in 15-20 minutes if your questions are sharp and your research is thorough. The worst thing you can do is let a discovery call ramble past 30 minutes without structure — you will lose the prospect's attention and your own credibility.

---

Make Discovery Your Competitive Advantage

Most B2B teams invest heavily in demos, proposals, and closing — and barely in discovery. Discovery is the foundation everything else is built on. A brilliant demo means nothing if it addresses the wrong problems.

Your action plan:

1. Adopt the 30-minute structure. Follow it until it becomes second nature.
2. Choose a framework. BANT for mid-market, MEDDIC for enterprise, SPICED for SaaS.
3. Build a question bank. Adapt the 30+ questions above to your product and industry.
4. Record and review calls. Listen to two discovery calls per rep per week with specific feedback.
5. Score every opportunity. Use consistent qualification criteria so your pipeline reflects reality.
6. Practice disqualifying. Not every discovery call should lead to a demo — only the qualified ones.

If you want help implementing a discovery framework — including customised question banks, talk tracks, call coaching, and qualification criteria — get in touch with our sales enablement team. Your next discovery call is an opportunity to win the deal before the demo even starts.