B2B Discovery Call Framework: 63% of Teams Run No Script (and It's Killing Your Close Rate)

Give the same prospect to two of your reps. Same product, same territory. You get back two discoveries that look nothing alike, two opposite verdicts, two close rates with no relationship to each other. It's not a talent problem. It's that there's no shared standard for what a good discovery looks like at your company. Everyone improvises on their own, and the first call becomes the first source of close-rate gap between people who are supposed to do the same job.

Everyone hunts for the magic list of the right questions to ask. Wrong track. Across the B2B sales teams we audit at ACROSS, 63% have no documented discovery script, no shared scoring grid, no call-review ritual. The question bank, everyone already has it. What's missing is the system that makes each rep ask the right ones at the right moment, and that lets you measure it. You think you're running one team. You're actually running eight different practices nobody ever wrote down.

A good discovery isn't asking more questions. It's shutting up and probing the prospect's HOW. That's my obsession: I don't interrogate the data, I interrogate how you do things. A discovery is exactly that move, applied to the prospect. Neil Rackham measured it across 35,000 calls in SPIN selling: in a discovery that closes, the rep talks 43% of the time, the prospect 57%. The SPIN framework, the qualification grid, the red flags, the SDR question bank, all of it exists to feed that ratio, never the reverse. Pitching before you've examined is the doctor prescribing before the diagnosis. The prospect feels it in thirty seconds. ACROSS's job, at its core, is one giant discovery on your company. So use us: we've run nos diagnostics watching what works and what breaks. Here's the method.

This guide covers the full definition of a B2B discovery call, the SPIN framework used by the highest-performing sales teams, the five phases of a structured discovery, a bank of 60 questions sorted by category, the red flags to catch in real time so you can disqualify cleanly, the qualification frameworks it pairs with, three structure formats depending on how much time you have, the fatal mistakes that sink a discovery, a scoring grid to decide objectively what comes next, a complete script template you can use as-is, and the ACROSS patterns observed across 100+ Revenue Health Score diagnostics.

Key takeaways

• The discovery's single mission: produce a binary decision, qualify or disqualify, not present the solution or convince the prospect.
• Reference framework: Neil Rackham's SPIN (Situation, Problem, Implication, Need-payoff). The only framework empirically validated across 35,000 analyzed calls.
• Standard 45-min structure: 10 min rapport and framing, 25 min deep diagnostic, 8 min next steps, 2 min mutual action plan.
• Talk ratio: 43/57 rep/prospect in a high-performing discovery (Rackham). Past 65% rep talk time, Gong observes a drop in conversion rate and win rate across 100,000+ analyzed B2B calls.
• Deal-breaker red flags: no identified business problem, prospect outside ICP, no identified sponsor, no budget or timeline. Any discovery should be disqualified if 2 of these 4 signals show up.
• Mandatory post-call deliverable: a written mutual action plan sent within 24 hours, restating the findings, the next steps, and the decision criteria agreed on with the prospect.
• ACROSS pattern: 63% of the B2B sales teams we audit have no documented discovery script, no shared scoring grid, and no qualitative call-review ritual. It's the number-one source of close-rate variance between reps on the same team.

"Most salespeople think that asking more questions improves their odds of closing. It's wrong. What matters is the type of question: most sellers ask too many Situation Questions and not enough Implication Questions, and it's exactly the reverse you need to trigger a real business conversation."

Neil Rackham, SPIN Selling (McGraw-Hill)

The discovery call's single mission: diagnose, don't convince

The discovery call isn't there to convince the prospect to buy. It's there to produce a shared conviction, rep and prospect aligned, on whether it makes sense to engage a sales cycle. These two ambitions are radically different in how they play out and in their effect on the pipeline.

A diagnosis, not a presentation

The rep who shows up to discovery with a slide deck and a pitch script reruns the same scenario as a doctor who'd prescribe treatment before examining the patient. The prospect feels it immediately, and two reactions follow: either they shut down and answer in generalities that make the rest of the call useless, or they let the pitch carry them and then vanish the next day because nothing actually hooked them. Either way the deal is already dead, even if the rep thinks otherwise.

A well-run discovery produces three measurable outputs. A written diagnosis of the prospect's business problem, quantified if possible. A list of the explicit decision criteria the prospect will use to choose a solution. A mutual action plan signed by both parties that sets the next concrete step. Any discovery that doesn't produce these three outputs is by definition a failure, whatever the apparent quality of the conversation.

The cost of a sloppy discovery

In our Revenue Health Score diagnostics run on 100+ B2B scale-ups between 10M€ and 100M€ ARR, a poorly executed discovery is consistently the number-one root cause of pipeline problems. Three symptoms show up in a cascade. Deals stall at the Qualification stage for weeks because nobody really qualified the problem, the budget, or the decision process. Product demos pile up without converting, because they're generic for lack of a discovery that would have let you tailor them. Proposals routinely get beaten by better-informed competitors, because the rep never collected the right information to differentiate the offer.

The SPIN framework: the empirical reference for B2B discovery

The SPIN framework, developed by Neil Rackham from the analysis of 35,000 B2B sales calls, remains the only discovery framework whose effectiveness has been empirically measured on a statistically significant sample. It structures the conversation around four successive question categories, each with a precise function in building the diagnosis.

The four SPIN categories

The classic mistake: too much Situation, not enough Implication

Rackham's data leaves no room for doubt. Average reps spend 60% of their discovery on Situation Questions ("what tools do you use," "how many of you are on the team," "what's your ARR"), while top performers spend only 15 to 20% there. Situation Questions are useful but dull, and most of them can be documented before the call via LinkedIn, the website, or prior outreach. The time saved must be reinvested in Implication Questions, the ones that turn an incidental problem into a quantified, urgent business pain.

A successful discovery always produces the same effect on the prospect: by the end of the call, they're convinced not that your solution is good, but that their problem is more serious than they thought when the call started. That cognitive shift is the only reliable signal that a discovery worked.

SPIN vs closed questions: the contrast

The five phases of a structured discovery call

A discovery call is structured in five successive phases, each with a precise operational goal and a target duration. This structure works regardless of the 30, 45, or 60-minute format, only the relative durations change.

Phase 1: rapport and framing

The first phase lasts 5 to 10 minutes. It has two goals at once. Create enough trust for the prospect to accept being vulnerable about their real problems, and explicitly negotiate the frame of the call. The rep who skips this phase, or reduces it to weather chit-chat, loses 30 to 40% of the informational potential of the rest of the conversation.

Explicit framing is non-negotiable. The rep has to clearly state the expected duration, the goal for the call, what they'll ask of the prospect and what they'll offer in return. This transparency immediately creates an adult-to-adult relationship rather than the seller-to-target dynamic that puts most prospects on the defensive. The anchoring line: "My goal for the next 45 minutes is to understand exactly your context and your stakes, so that together at the end of the call we decide whether there's grounds to go further or not. Does that work as a frame?"

Phase 2: context questions

The second phase lasts 5 to 8 minutes. It maps to the Situation Questions of the SPIN framework. The goal is to quickly map the organization, the tools, the processes and the people involved, without spending more than necessary on it. Most of this information should have been collected before the call; this phase is for verifying and deepening, not discovering. The rep who spends 20 minutes asking questions whose answer is on LinkedIn wastes their own time and the prospect's.

Phase 3: deep dive on the problem

The third phase lasts 15 to 25 minutes depending on the call format. It's the heart of the discovery and the only phase that separates top performers from average reps. It alternates Problem Questions and Implication Questions, with a precise sequence: surface a problem, then dig into its impact, then move on to another problem, until you identify the core business knot.

The "and what else" technique is decisive here. When a prospect raises a problem, 80% of reps jump straight to the solution or the next question. The 20% who perform stay on the problem and follow up with "and what else," "and concretely, what does that look like day to day," "give me a recent example." This persistence turns abstract problems into concrete, quantifiable pains.

Phase 4: exploring the impact

The fourth phase lasts 8 to 12 minutes. It extends phase 3 by systematizing Implication Questions on the identified problems. The goal is to quantify the business impact of each identified problem, in terms of lost revenue, operational cost, strategic risk, or missed opportunity. A problem that isn't quantified is a problem that won't get prioritized in the prospect's 2026 budget.

Phase 5: next steps and mutual action plan

The last phase lasts 8 to 12 minutes depending on the format. It closes the call with three concrete outputs. A shared verbal summary of the diagnosis, which the prospect must validate or correct live. An explicit next-step proposal with a precise date. A mutual commitment on what will be produced and exchanged before that next step. The rep who ends their discovery without these three outputs walks away with a 50% chance the deal vanishes within 7 days.

The bank of 60 discovery questions sorted by category

Questions on the current state (10 questions)

1. How do you handle [the problem your product solves] today?
2. Who's involved in this process and what's each person's role?
3. What tools are you currently using for this activity?
4. How long have you been operating this way?
5. Has this process changed over the past few months?
6. How do you measure the performance of this process today?
7. How often do you review these results with your team?
8. What triggered your thinking on this topic now?
9. Have you evaluated other solutions in the past?
10. What kept you from going with them back then?

Questions on the pain points (10 questions)

1. What isn't working in your current process?
2. What's the most frustrating thing day to day with this situation?
3. If you could change one thing tomorrow, what would it be?
4. What feedback do you get from your team on this topic?
5. What would you like to be able to do that you can't today?
6. Are there situations where the current process really cost you time?
7. What's keeping you from moving this forward internally?
8. Where in the customer or user journey does this problem show up most?
9. What workarounds have been put in place to compensate?
10. What do your competitors do better than you on this point?

Business-impact questions (10 questions)

1. What consequences does this problem have on your quarterly targets?
2. How much time does your team lose on this topic each week?
3. If you had to put a number on the annual cost of this situation, what range would you give?
4. How does this problem affect your ability to hit your revenue plan?
5. Who in the organization is most impacted by this dysfunction?
6. Has it already cost you a deal or a customer?
7. What happens if you don't fix this problem over the next twelve months?
8. What would the operational gain be if we cut that time in half?
9. How does your leadership view this topic today?
10. Is this something that shows up in your personal objectives this year?

Questions on the decision process (10 questions)

1. Who else in the organization needs to be involved in this decision?
2. How do you usually make this type of decision here?
3. Who signs the final purchase order?
4. Who can block the project once the technical decision is made?
5. Do you have a formalized vendor evaluation process?
6. What criteria will be used to compare the options?
7. Are there IT, legal, or procurement constraints I should know about right now?
8. In past projects, who had the final say?
9. What would an ideal decision cycle look like for you on this topic?
10. What could make this project fail internally?

Questions on timing (10 questions)

1. Why are you looking at this topic now rather than six months ago?
2. What's your target deadline for having a solution in place?
3. Is there an internal event forcing this thinking?
4. What needs to be true for you to start a project this quarter?
5. Is this project on your 2026 roadmap?
6. When would you like to see the first operational results?
7. How much time can you dedicate to an evaluation phase?
8. Have you already identified a window for an internal decision?
9. What other priorities could end up competing with this project?
10. If the decision isn't made within six months, what happens?

Questions on budget and resources (10 questions)

1. How is budget allocated for this type of topic?
2. Do you already have budget earmarked for this initiative?
3. What annual envelope does this type of investment usually fall into?
4. Who signs off on spend in this budget range?
5. Is there an OPEX vs CAPEX constraint to know about?
6. How do you usually justify ROI on this type of purchase?
7. Which internal team would own the project on the operational side?
8. Do you have the internal resources to deploy a solution like ours?
9. If budget had to be arbitrated at the last minute, what's your plan B?
10. What would make an investment a priority over another initiative?

Discovery red flags: knowing how to disqualify cleanly

The quality of a discovery isn't measured only by the number of deals engaged, but also by the number of deals disqualified in time. A rep who qualifies everything that moves pollutes their pipeline, misleads their managers on the forecast, and burns time on opportunities that don't exist. Knowing how to disqualify cleanly is an undervalued and yet decisive skill.

The four deal-breaker red flags

The operational rule we recommend at ACROSS: if two of these four signals appear during discovery, the deal leaves the active sales pipeline. Keeping it means lying to yourself and to your team.

Honoring the prospect's time

Disqualifying cleanly is also an act of respect toward the prospect. The rep who pushes a demo on someone with no problem, no budget, and no mandate wastes everyone's time and degrades their own close rate. The line to know how to say: "Based on what you're sharing with me, I'm not sure this is the right time to go further. I'd rather be straight with you than waste your time on a demo. Here's what I'd suggest instead."

The qualification frameworks that pair with SPIN

SPIN structures the conversation, but it isn't enough to qualify a deal in full. It needs to be combined with a qualification framework that frames the operational dimensions to validate. The three most-used B2B frameworks combine perfectly with SPIN.

For a detailed exploration of these frameworks and the choice between BANT and MEDDIC, see our guide B2B lead qualification BANT MEDDIC. A discovery properly run with SPIN naturally produces the information BANT or MEDDIC require, so there's no choosing between the two approaches, they operate on complementary planes.

Structure by duration: 30, 45, or 60 minutes

The discovery call adapts to three standard formats depending on the client segment, the prospect's maturity, and the density of the topic. The phase structure stays the same, only the durations change.

30-minute format (SMB, fast deals)

45-minute format (mid-market, standard)

60-minute format (enterprise, complex deals)

The fatal mistakes that sink a discovery

The same mistakes keep coming up in the sales teams we audit. They're not hard to fix, but they demand discipline and regular coaching from managers.

Mistake 1: pitching too early

Reps who whip out their solution before they've dug into the problem close less. Pulling the slides too soon has a price: Gong measures 17% lower odds of landing a follow-up on discoveries with a deck, versus calls without one. They confuse the urge to show their expertise with the prospect's interest. The prospect who hears a premature pitch understands the rep didn't listen, and they close the conversation mentally, even if the call keeps going on the surface.

Mistake 2: not listening actively

Listening actively means rephrasing, building on answers, digging, not just waiting for your turn to talk. Top performers use three recurring techniques. Active silence after an important answer, which pushes the prospect to elaborate. Mirror rephrasing, which checks understanding and creates psychological safety. Emotional validation, which legitimizes the frustration the prospect expresses and invites them to go deeper into confiding.

Mistake 3: not taking structured notes

A discovery without structured note-taking in real time is a discovery half done. The information collected evaporates within 24 hours, the CRM gets only a watered-down version, and the handover to the Account Executive or the deal desk becomes approximate. The SDR to Sales handover link details the consequences of a poorly documented handoff.

Mistake 4: not sending a structured follow-up

The follow-up has to go out within 24 hours of the call. It covers three things: the summary of the findings shared during the call, the proposed next step with a precise date, and the questions or documents both parties committed to producing. A follow-up that settles for "thanks for the call, I'll send the demo over" is worth nothing and feeds the massive no-show rate seen on second calls.

Mistake 5: not recording and re-listening to calls

Teams that use Gong, Chorus, or ExecVision progress two to three times faster than those working blind. Recording and re-listening, built into a weekly sales manager coaching ritual, turns every botched call into teaching material. Teams that skip it repeat the same mistakes for entire quarters without realizing it.

Scoring grid: deciding objectively what comes next

At the end of each discovery call, the rep has to fill in a standardized scoring grid that makes the engage-or-disqualify decision objective. This grid also lets the manager review discoveries on a common basis, and detect judgment gaps across the team.

A total score below 8 out of 16 triggers a disqualification or a move to nurturing. A score between 8 and 12 engages a standard sales cycle. A score above 12 activates a priority cycle with sales-manager co-piloting. This grid is to be adapted to your context, but its logic transfers to any B2B team.

Template: a discovery call script you can use as-is

This script is to be tailored to your solution and your ICP. It's structured for a 45-minute format and can be compressed to 30 minutes or extended to 60 minutes as needed.

Opening (minute 0 to 7)

"Hi [first name], thanks for taking the time. Before we start, I want to make sure you've got the full 45 minutes, is that still the case? My goal for this call is to understand exactly your context, your current stakes, and what pushed you to accept this conversation. At the end of the call, we'll decide together whether there's grounds to go further or not. If the answer is no, I'll tell you straight. Does that work as a frame? So I can be useful, can you tell me in one sentence how you'd define your current role and what's taking up the most of your time right now?"

Context questions (minute 7 to 13)

"Can you describe how your team operates today on [the topic your product addresses]? What tools do you mainly use in this area? Who else in the organization is involved in these topics? How long have you been organized this way?"

Deep dive on the problems (minute 13 to 31)

"What works well in your current setup, and what doesn't? When you say [problem raised], can you give me a recent concrete example? And what else? What's the most frustrating thing for you personally in this situation? How long has this problem existed, and why is it becoming a priority now?"

Exploring the impact (minute 31 to 39)

"If we had to put a number on the impact of this problem on your quarterly results, what range would you give? Who else in the organization is affected by this situation? What happens if nothing moves over the next twelve months? Is this something that shows up in your personal objectives this year?"

Next steps and mutual action plan (minute 39 to 45)

"If I rephrase what you've shared with me, the three key points would be [summary]. Am I representing your situation faithfully, or are there nuances to add? On that basis, I think there could be sense in [proposed next step]. Concretely, I'd suggest [date and format]. Does that work? On my side, by then, I'll send you [deliverable]. On your side, can you [requested action]? I'll send you a written recap of what we discussed today and what we agreed on, within the day."

Further resources

To go deeper on the structuring elements raised in this article, we recommend the following reads from our knowledge hub:

• B2B lead qualification BANT MEDDIC: the frameworks that pair with SPIN
• B2B sales process method: where discovery fits in the full cycle
• Deal desk B2B closing: qualification rigor extended to the late stages
• Sales manager coaching: the weekly call-review ritual
• B2B sales enablement guide: equipping teams to systematize discovery quality
• SDR to Sales handover: the post-discovery handoff
• B2B ICP ideal customer profile: the basis of the prospect fit assessed in discovery
• B2B lead scoring methods and tools: scoring upstream to discover better
• Pipeline management hygiene and forecast: pipeline discipline downstream of discovery
• Sales forecast precision: making the forecast reliable through structured discovery
• CRO 100-day plan onboarding: installing the discovery ritual when taking the role
• BDR performance KPI: upstream metrics of discovery quality
• Recruiting a VP Sales CRO criteria: the leader profile that instills this discipline
• Our revenue diagnostic methodology: the ACROSS method applied to qualification

Sources cited

• Neil Rackham, SPIN Selling, McGraw-Hill (1988), based on the analysis of 35,000 B2B sales calls
• Chris Voss, Never Split the Difference, HarperBusiness, on rephrasing and active-listening techniques
• Mark Roberge, The Sales Acceleration Formula, Wiley, on the discipline of a scalable sales process
• Gong.io research: data observed on talk ratio and discovery structure
• Proprietary ACROSS INSIGHT data from 100+ Revenue Health Score diagnostics run with B2B scale-ups between 10M€ and 100M€ ARR

Article written by Charles-Alexandre Peretz, cofounder of ACROSS INSIGHT, from the analysis of 100+ Revenue Health Score diagnostics run with hypergrowth B2B companies. Last updated: March 15, 2026.