How to Run a Discovery Call: Questions, BANT and MEDDICC Explained

The purpose of a discovery call

A discovery call is a structured conversation to understand the buyer's situation, their problem, what it costs them, and how they make decisions. It is not a product demo. The buyer should talk more than you do. By the end of the call, both sides should know whether there is a real fit and what the next step is. A good discovery call also helps the buyer think more clearly about their own problem, which builds trust.

Prepare an agenda and share it at the start: 'I would like to understand how things work today, what you want to change, and how decisions get made. Then, if it makes sense, I can share how we have helped similar teams and we can agree on next steps. Does that work?' This sets expectations and makes you sound organised.

Questions that uncover real pain

Move from the current situation, to the problem, to the impact, to the desired outcome. Ask open questions, listen, and ask 'tell me more' or 'what happens then' to go deeper. Write down the buyer's exact words because you will use them in the proposal. Avoid leading questions such as 'would you like to save time?' that anyone would answer yes to. For a clinic, the impact might be lost patients or overtime at the front desk. For a US software company, it might be a delayed product launch. For a Gulf property group, it might be a project handover running late.

• Situation: 'Walk me through how a patient books an appointment today, from first call to visit.'
• Problem: 'Where does that process break down most often?'
• Impact: 'When that happens, what does it affect: revenue, staff time, patient experience?'
• Priority: 'Why is this coming up now rather than last year?'
• Outcome: 'If we spoke again in six months and this was solved, what would be different?'
• Process: 'Who else will be involved in choosing a solution, and how have you bought similar services before?'

BANT: a simple qualification checklist

BANT stands for Budget, Authority, Need and Timeline. It is a quick way to check whether a deal is worth pursuing. Budget asks whether money is set aside or can be found. Authority asks who can sign and approve. Need asks whether there is a real problem that your service solves. Timeline asks when they want to solve it and why. BANT is useful for smaller deals such as clinic websites or SMB apps, where one or two people decide.

Do not interrogate the buyer with four blunt questions. Weave them into the conversation. For budget, try 'Have you set a range for this, or would it help if I shared typical ranges for projects like this?' For authority, try 'Apart from you, who else would want a say?' For timeline, try 'Is there a date this needs to be live by?'

MEDDICC: qualification for larger deals

MEDDICC is a more detailed framework for bigger, multi stakeholder deals, such as a US mid market company or a Gulf enterprise group. Each letter is an area you must understand before you can forecast the deal with confidence. Fill in what you know after each call and treat the gaps as your next questions. A deal with no champion and no access to the economic buyer is risky, however friendly the calls feel. You do not need MEDDICC for every small deal. Use BANT for quick, simple sales and MEDDICC when several people, procurement or legal review are involved.

• Metrics: the measurable result the buyer expects, such as fewer missed appointments or faster release cycles.
• Economic buyer: the person who controls the budget and gives final approval.
• Decision criteria: what they will use to compare options, such as cost, security, references or speed.
• Decision process: the steps and people involved from evaluation to signature.
• Identify pain: the business problem and its consequences if nothing changes.
• Champion: someone inside the buyer's company who wants you to win and will sell for you internally.
• Competition: other vendors, an internal team, or simply doing nothing.

Check your understanding