How to Qualify a Prospect: Questions to Ask and BANT

Published on 26 October 2026.

Qualifying a prospect means checking, with a few questions, whether they have a real need, a timeframe, the means to buy and the power to decide. The best-known method for doing this is called BANT: Budget, Authority, Need, Timeline. For a small business's inbound requests, it works better in a different order: need and timeline first, budget last.

Here is what qualification covers, how BANT works, how to adapt it to the messages you receive, the questions to ask depending on your sector and what you are better off not asking.

Transparency: HelloDesk, the publisher of this article, develops an AI assistant that asks qualification questions as conversations unfold. The method below works with or without a tool.

What does qualifying a prospect mean?

Qualifying a prospect means sorting inbound requests to know which ones are likely to turn into sales, and therefore which to handle first. You are trying to answer a simple question: can and does this person want to buy what I sell, within a reasonable timeframe?

People often say "lead" for an inbound contact you know little about, and "qualified prospect" once you know they are a fit. Qualification is the step from one to the other. It is not an interrogation: done well, it feels like a conversation in which the customer explains what they are looking for, and you pick up the useful information along the way.

What is at stake is time. A small business that receives dozens of messages a week cannot call everyone back with the same attention. Qualifying is not about filtering people out: it is about deciding where to spend your time.

The BANT method: definition and limits

BANT is a qualification framework with four criteria: Budget (can the prospect afford it?), Authority (are they the one who decides?), Need (do they have a problem you solve?) and Timeline (when do they want to buy?). A prospect who ticks all four is considered qualified.

The framework comes from enterprise B2B sales, where it is often attributed to IBM. IBM still uses it: its BANT criteria template for partners asks, for example, for an executive-level decision maker to be named and for at least two key dates in the decision process before an opportunity is registered.

That is its limit for a small business. BANT was designed for long sales cycles, with several stakeholders and an approved budget. Someone writing to a restaurant, a tradesperson or a training centre has no buying committee and no formal budget. Asking them straight away "what is your budget?" or "are you the decision maker?" kills the conversation.

How to adapt BANT to inbound requests

For inbound requests, keep BANT's four pieces of information but change the order and the wording: start with the need, move on to the timeline, add the volume, and keep the budget for the end, often as a range or a choice between two options. Authority can usually be inferred from the context.

In practice, the four pieces of information to gather become:

1. The need: what exactly is the person looking for? It is the natural opening question, the one the customer wants to answer.
2. The timeline: by when? A specific date is the best sign of intent. "Saturday evening" or "starting in January" is worth more than "some day maybe".
3. The volume: how many? Number of people, seats, square metres, participants. It is often the first indicator of the value of the request.
4. The budget: last, and without asking it head-on. Offer two options instead ("our X package or the Y one?") or a range.

As for authority, it often shows in the request itself: a work email address, "for our team", "I need to talk to my business partner". There is no need to ask, except in B2B when the deal is significant.

Questions to ask depending on your sector

The right questions depend on what you sell. The principle is the same everywhere: two or three short questions, asked as the conversation goes, covering need, timeline and volume. Here are examples to adapt.

Sector	Need	Timeline	Volume
Restaurant	Meal, private hire, event?	What date, which service?	How many people?
Hotel, rental	Leisure, business or group stay?	Arrival and departure dates?	How many people, rooms?
Real estate	Buying, renting, valuation?	Project within what timeframe?	What type of property, what size?
Trades, services	What job, how urgent?	By when, emergency call-out?	What area, how many items?
Training	Which programme, what goal?	Which session, what start date?	How many participants?
B2B services	What problem to solve?	What deadline?	How many users, sites?

For budget, the same logic applies everywhere: offer options rather than an open question. And for a request that looks like simple curiosity ("are you open on Sunday?"), do not qualify: just answer.

Setting up your qualification in 5 steps

A qualification process that works fits on one page: the information to gather, the questions to get it, and what happens once the prospect is qualified. Here is the method.

1. Reread your last 30 requests. Spot the ones that turned into sales and note what they had in common: a type of need, a short timeline, a minimum volume.
2. Define your qualified prospect in one sentence. For example: "a group of at least 8 people with a date within 30 days". That is your threshold.
3. Write three questions at most. One per missing piece of information, worded the way you would say them out loud. Test them on your next conversations.
4. Decide what happens next. Is a qualified prospect called back within the hour? Passed to a colleague? Do the others get a complete written answer? Without this rule, qualification is pointless.
5. Review every month. How many qualified prospects became customers? If the rate is low, your threshold is too broad; if you are missing sales, it is too strict.

What not to ask

Only ask for the information you need to handle the request. It is good sales practice, since every extra question makes prospects drop off, and it is also an obligation: the GDPR requires collecting only data that is "adequate, relevant and necessary", as France's data protection authority, the CNIL, points out.

In practice, avoid asking straight away for a postal address, a date of birth or personal information unrelated to the request. Never ask for health or sensitive information "just in case": the CNIL recommends not collecting it if you can do without. A name and a way to get back in touch are almost always enough at the qualification stage.

Small business or sales team: two uses

In a small business, qualification is mainly about not missing the requests that matter among the routine questions. The same three questions, asked for every request, are enough. The hardest part is asking them quickly, including in the evening and at weekends, when prospects write and nobody is available.

In a B2B sales team, qualification is about dividing the work: who calls back whom, in what order. There, the full BANT framework keeps its value, especially the authority question, because a large deal is often lost for not having spoken to the right person.

In both cases, part of the qualification can be handed to an AI assistant that asks the questions as the conversation goes and passes requests that clear the threshold on to the team, with the context. It is one of the uses described in our article on automating WhatsApp Business with AI, and the principle behind HelloDesk's answer, qualify, hand over feature.

Frequently asked questions

What is the BANT method?

BANT is a sales qualification framework with four criteria: Budget, Authority (decision-making power), Need and Timeline. A prospect is considered qualified when they have a need you solve, the means to buy, the power to decide and a defined timeframe. It comes from enterprise B2B sales.

What questions should you ask to qualify a prospect?

Three questions are usually enough: what exactly are you looking for (need), by when (timeline) and for how many people or units (volume). Budget comes last, as a choice between two options rather than an open question. Adapt the wording to your sector and ask them as the conversation unfolds.

Is the BANT method suitable for small businesses?

Not as it stands. BANT was designed for long sales cycles with several decision makers. For a small business's inbound requests, keep BANT's information but change the order: need, timeline, volume, then budget. Authority can generally be inferred from the context and does not need to be asked.

What is the difference between a lead and a qualified prospect?

A lead is an inbound contact you do not yet know is a fit for your offer: a message, a form, a call. A qualified prospect is a lead whose need, timeline and ability to buy have been checked, and who therefore deserves priority sales follow-up. Qualification is the step that turns one into the other.

What data are you allowed to ask a prospect for?

Only what is necessary to handle their request. The GDPR requires data to be adequate, relevant and limited to what is necessary, as the French data protection authority, the CNIL, points out. At the qualification stage, a name, a contact method and information related to the request are enough. Avoid sensitive data.

Can an AI assistant qualify prospects?

Yes, for simple inbound requests. An AI assistant can ask need, timeline and volume questions as the conversation goes, on WhatsApp, Instagram or by email, then pass requests above a defined threshold on to the team. Sales decisions and complex deals remain the team's job.

In short

Qualifying a prospect means asking the right questions at the right time to know where to spend your time. BANT gives you the framework; for inbound requests, ask in the order need, timeline, volume, budget, with three questions at most, and decide in advance what happens to qualified prospects.

If your requests come in on several channels and at all hours, HelloDesk's AI assistant asks these questions for you, 24/7, and passes on the requests that matter. Compare the HelloDesk plans or discover HelloDesk. And for the reviews left after a purchase, see our method for replying to Google reviews.