Discovery Call Structure for Consultative Sellers

A discovery call structure for consultative sellers should work like a diagnosis. Research supplies context, the opening tests a hypothesis, questions establish business impact, and the close secures a committed next step. Helping the buyer understand what needs to change and why earns the right to recommend.

Why the discovery call is structurally harder than it used to be

Buyers come with views of their own, a shortlist of competitors, and research held by people on a committee the seller may never meet. They have already done a large share of their independent research, so the conversation does not begin on neutral ground. The seller must uncover what the buyer believes as well as what the buyer needs. A generic script ignores that head start and makes the buyer pay for the seller’s lack of preparation. In a 30-minute call, that is an expensive way to say hello.

Discovery therefore has to do several jobs at once. It must uncover pain, work with existing views, and show that the rep can be trusted to guide the discussion. The questions need to demonstrate an understanding of the account while helping the buyer see the problem more clearly. That requires following the meaning of an answer. A checklist can organize the facts, but it cannot carry the conversation.

Why BANT fails consultative sellers and what replaced it

BANT puts budget first, which creates a mismatch for consultative selling. In modern B2B buying, budget is often allocated after pain has been acknowledged and quantified. An account without a budget line may have a business case that still needs work. Disqualifying it too early ends the diagnosis before the seller has established the cost of the problem.

Diagnostic frameworks reverse that order by starting with the facts and their consequences before moving to a recommendation. SPIN follows Situation, Problem, Implication, and Need-Payoff, while Sandler shares the principle of understanding before prescribing. MEDDIC and MEDDPICC cover similar ground and remain in use. For a 30-minute call, SPICED offers an economical structure through Situation, Pain, Impact, Critical Event, and Decision. Its sequence gives the conversation a spine, moving from context to pain, from pain to impact, and then to the timing and mechanics of a decision.

Pre-call research as the first diagnostic act

The Tomba consultative sales playbook describes six stages, which are research, connect, discover, diagnose, recommend, and commit. Its exit criterion for research is that the rep can name the probable pain and the people who feel it before making contact. Preparation should cover recent company news, trigger events, the organization and likely stakeholders, the tech stack, the current workflow, and industry pressures. These facts matter because they support a useful hypothesis about the buyer’s situation. Collecting them is not the same as knowing the answer.

Trigger events need a close look because they can explain why a problem matters now. Funding rounds, leadership changes, product launches, contract renewals, and competitor pricing changes can all supply urgency to test during the call. None proves that a particular pain exists. Instead, a trigger gives the seller a specific assumption to offer and the buyer something concrete to correct. Public answers, including those on the website or in an RFP, should already be part of that preparation.

Intent signals add context about where the buyer may be in the process. These include spikes in searches for competitor brands, research into the category, or the use of comparison keywords. A buyer already comparing alternatives is further into the process, so the opening should acknowledge that. Otherwise, the seller risks teaching the first lesson to someone who has already reached the exam.

Opening the call: agenda, hypothesis, and earning the right to question

The first three minutes establish whether the call will be a joint diagnosis or a vendor pitch the buyer has to survive. Start by confirming the agenda so the buyer knows what the conversation will cover and can change its direction. Then offer the hypothesis developed through research. Ask the buyer to correct it, giving them room to confirm the suspected pain or choose another starting point.

The hypothesis should link to something specific, such as a recent trigger or a known competitor the buyer is weighing up. A relevant insight published by the seller’s company can also establish credibility when it speaks directly to that context. It belongs in the opening because it helps explain the buyer’s situation. Make the diagnostic intent plain by explaining that understanding comes before any account of the offering. The buyer should know why the questions come first.

From minutes three to eight, move into SPICED’s Situation stage. Confirm the current state, tools, team size, workflow, and volume needed to understand the problem. Begin with what is already known rather than asking the buyer to recite public information. These checks give the later pain questions a sound footing and let the buyer correct assumptions before more rests on them.

The question architecture that moves from surface pain to business impact

SPIN’s four layers help shape the questions asked as the call moves through SPICED. Situation questions ask how the team handles the process now, while Problem questions ask where it breaks down most often. A description of the workflow supplies context, and an account of its recurring failure begins to name the pain. Each answer should determine what needs exploring next.

Implication questions turn that failure into a business consequence. They ask what a breakdown costs in close rate, team hours, or revenue. The Tomba consultative sales playbook identifies this layer as the hinge between a stated problem and a quantified business case. Without it, the buyer can leave with a well-described complaint that still cannot justify spending. A sore point is not yet a budget argument.

Ask for an estimate in dollars or hours even when the buyer cannot give an exact figure. A rough order of magnitude, such as whether the cost is closer to tens of thousands or hundreds of thousands, is firmer ground than “a lot.” Need-Payoff questions then ask what fixing the problem would change for the quarter. This lets the buyer describe the value of a solution in terms that matter to the business.

The Tomba consultative sales playbook says top performers talk roughly half the time and points to call recording tools such as Gong as a way to measure that balance. Talk ratio is a proxy, but a rep who dominates leaves little room for discovery. Listen for problems the buyer had not fully articulated before the conversation. A shift from “your product” or “your platform” toward language about using the solution or fixing the workflow signals that the buyer is beginning to internalize it. These are moments a rep can explore and a manager can coach.

Mapping the decision process and stakeholders before the call ends

Once the business impact is clear, the seller needs to find out how the buyer will make the purchase. SPICED’s Critical Event stage establishes the deadline, while its Decision stage establishes how a choice gets made. Ask what outside event makes the problem important to solve by a set date, such as a board review, contract renewal, or regulatory change. That gives urgency a basis outside the seller’s desire to close. Without it, a deadline may be wishful thinking wearing a calendar invite.

The decision discussion should establish who makes the final call, how the decision is structured, and what the formal evaluation involves. Before the call ends, identify by name the champion who will advocate internally and the economic buyer with budget authority. Also identify the end users whose pain was diagnosed and any likely blocker. Procurement, IT, legal, or something else the company needs to do may change how the deal moves forward. Knowing the pain without knowing these roles leaves the seller with only part of the diagnosis.

Some committee members who have a say will never attend a sales meeting. What these hidden buyers read may shape their views, their RFP invitation lists, and the suppliers they back internally. Surface who they are, equip the champion with a relevant, shareable insight, and plan outreach across the stakeholders who can be reached. Thought leadership can inform people beyond the meeting without requiring a direct conversation with each of them. The discovery call therefore needs to account for influence beyond the people on it.

Closing the call with a committed next step, not an open-ended follow-up

The close starts with one last check of the diagnosis before the seller moves into selling. Reflect the problem and its impact back in the buyer’s own words, then leave room for correction. If the buyer changes the summary, resolve that difference before agreeing on what happens next. Agreement about the problem gives the next step its purpose.

If the economic buyer was absent, arrange the next discovery meeting to include them. Agree on the follow-up artifact before leaving the call, whether it is a personalized summary, a relevant insight, or a tailored demo. Send it the same day, while the conversation is fresh, before it fades over two days. The artifact should support an agreed action.

A successful outcome is either a booked next meeting with defined participants or a mutual decision not to advance. An indefinite promise to think about it leaves neither party with a clear commitment. A doctor does not finish a diagnosis by vaguely offering pamphlets, and a consultative seller should not either. The prescription is a mutual action plan that spells out the next steps, names who will take part, and sets dates that fit the buyer’s decision process. That turns shared understanding into something both sides have agreed to do.

Making the diagnostic approach repeatable across a team

Even with a good structure, pipeline quality varies when every rep uses it in a different way. Standardizing the approach gives managers something concrete to coach without turning the call back into a questionnaire. Recordings and talk-ratio analysis through Gong can show whether the questions get to Pain and Impact, whether the rep leaves room for answers, and whether both sides agree to a next step. The coaching target is the quality of the diagnosis. A question asked earns little credit if its answer goes unexplored.

Capture the buyer’s own description of the pain, the quantified impact, the stakeholder map, and the critical event in the CRM so they can inform preparation for similar accounts in the same industry. Move what the team learns about competitors from a static battlecard into a live competitive intelligence program. The alternatives buyers consider and the criteria competitors have shaped are useful signals when captured. When the same pain keeps coming up, marketing should use it to make content about problems buyers say they have, including content for hidden committee members.

The Tomba consultative sales playbook names discovery-to-proposal conversion rate, average deal size, and win rate as team-level measures of the consultative process. These measures show how coaching and what the team shares with one another tie to sales results. The standard is a diagnosis strong enough to support a recommendation and a next step the buyer has reason to take.