How to Define a Qualified Meeting That Actually Converts

What is a qualified meeting?

A qualified meeting is a conversation with a buyer who has an active situation your product addresses, a reason that situation is live now, and the standing to discuss it. Job title, company size, and stated interest describe fit. They don't establish that anything is happening.

Three states get used interchangeably in contracts and reporting, and separating them is the first practical step:

Booked. A slot exists in a calendar. Someone accepted an invitation.

Held. Both parties attended and stayed for a defined minimum. This is what most appointment-setting arrangements actually pay on.

Qualified. A live situation was present and discussable. This is the only one of the three that predicts anything about pipeline.

Almost every commercial arrangement I've seen prices and measures on the first two. That isn't dishonesty on anyone's part — booked and held are easy to verify and hard to dispute, which is exactly why they end up in contracts.

But if you're paying on held and hoping for qualified, you've written an agreement that doesn't describe what you want.

‍

Why qualified meetings still don't convert

Open your qualification criteria and read them as a list. Most organizations find some version of this:

• Job title or seniority level
• Company size, by headcount or revenue
• Industry or vertical
• Budget authority or influence
• Sometimes: stated interest in the category

Every one of those describes who the person is. None of them describes what is happening to them.

Here is what that produces, and I've watched it more times than I can count. A director of infrastructure at a 5,000-person company, with budget influence and a stated interest in storage, takes a meeting.

On paper this is a textbook qualified meeting. In the room there is no scoped project, no date that anything has to happen by, and nothing making the current arrangement untenable. The conversation is pleasant. The seller does a good job. Nothing moves, because there was nothing to move.

That meeting satisfied the criteria completely. The criteria were measuring fit and the client was buying conversion.

Two pieces of published evidence are worth putting next to this, with their limits stated.

RAIN Group's Top Performance in Sales Prospecting study surveyed 488 buyers representing several billion dollars of purchases and found that 58% of sales meetings are not valuable to buyers.

It's a perception survey rather than an outcome study, and it's from 2018, so I'd treat it as directional rather than current. It's still the clearest published signal that a large share of meetings that met someone's criteria did nothing for the person sitting in them.

Gartner's B2B buying research puts the typical buying group for a complex solution at six to ten decision makers, with 77% of buyers describing their most recent purchase as very complex or difficult.

Read that against a criteria set that screens on a single named contact's title and authority. Even when you have the right individual, one person with a job title is not a qualified situation.

There's a third thing worth saying about evidence here, because it bears directly on the argument. If you go looking for a benchmark conversion rate from marketing-qualified to sales-qualified, you'll find published figures ranging from the low teens to above fifty percent.

The most widely circulated number — around 13% — comes from a 2018 analysis and is now flagged as obsolete by the people who used to cite it. Those figures don't disagree because the data is bad. They disagree because the definitions disagree. Which is the argument of this article, arriving from a different direction.

‍

Which qualification criteria actually predict conversion?

The distinction that matters isn't between good criteria and bad criteria. It's between criteria that describe a buyer and criteria that describe a situation.

‍

Both matter. Buyer criteria stop you selling to the wrong companies. But they're a filter, not a forecast, and most organizations have written a filter and called it a specification.

Four situational signals are worth defining operationally, because "situational" on its own is as vague as "consultative."

Now the asymmetry that explains why almost nobody writes criteria this way.

Buyer criteria are cheap to verify. You can confirm a title and a headcount from a database, at scale, without speaking to anyone, and you can audit them afterward without dispute. Situational criteria require an actual conversation with the buyer, and they require whoever has that conversation to be capable of judging what they heard.

So criteria drift toward buyer attributes not because anyone believes they predict better, but because they're auditable without talking to anyone. That's a procurement convenience that became a specification, and it's the root of the problem.

‍

Is BANT still useful for enterprise technology deals?

Partly, and less than its persistence would suggest.

BANT screens on Budget, Authority, Need, and Timeline. Three of those four are buyer attributes. Only Timeline reaches for a situation, and in practice it's asked as a question rather than verified as a fact — the buyer offers a date, the date goes in the record, and nobody establishes what forces it.

The critique isn't new and it isn't mine. Informa TechTarget has argued at length that BANT is an inefficient way of establishing demand for most enterprise technology providers, and similar arguments have come from HubSpot, ANNUITAS, and a number of practitioners over the past decade. Budget-first qualification made sense when buyers approached vendors with a budget already allocated. It maps poorly onto a market where buyers do most of their evaluation before anyone from your company is involved.

It's worth looking at the main frameworks specifically for what they leave out at the layer this article is about:

‍

The pattern is the point. Every one of these is a tool for a seller qualifying a deal in front of them. None of them is written as a specification for what a supplier must deliver. That's the gap, and it's why organizations with a well-adopted methodology still buy meetings that don't convert — the methodology governs what the rep does after the meeting arrives, and says nothing about what should have arrived.

One note on the surrounding literature: you'll find confident claims that adopting a given framework lifts win rates by twenty or thirty percent. I couldn't trace any of them to a primary study, and the figures are inconsistent between sources that cite the same origin. Treat them as marketing.

‍

How to write qualification criteria as a supplier specification

Here's the structure I'd use. It works whether the meetings come from an agency, an internal SDR team, a channel partner, or an event.

Situation. What must be true about the buyer's circumstances — not who they must be. Written as a condition, not a preference.

Evidence. What the qualifier must be able to state, in the buyer's own words, to claim the situation exists. This line does more work than any other. It converts a judgment into something checkable.

Timeline, with the cause. The date, and the thing forcing it. A timeline without a cause is a guess the buyer made to be helpful.

Stakeholders. Who else has to agree, identified by role. Not a full buying group map — enough to know whether the person you're meeting can move anything.

Disqualifiers. Explicit. What should be rejected even when fit is perfect. Most criteria sets omit this entirely, and it's the omission that lets a specification quietly become a preference. If nothing is disqualifying, everything qualifies.

Verification. How the receiving seller confirms the criteria were met, and within what window. Without this you have a standard nobody applies.

Two pieces of practical advice about producing it.

Write it with whoever generates your meetings, not for them. Criteria handed down are criteria worked around. I've been on the receiving end of enough of them to say that plainly. When the people doing the qualifying help write the standard, they tend to enforce it, because they understand what it's for.

Derive it from your own converted meetings, not from a methodology. Pull the last thirty first meetings that became qualified opportunities. Read what was true in all of them, and what was absent from the ones that didn't convert. That's your specification, and it will be more accurate than anything you adopt off the shelf — including from us.

‍

Should you pay per meeting booked or per meeting qualified?

Per qualified, and the reason is about incentives rather than fairness.

When an arrangement pays on meetings booked or held, the supplier's obligation ends the moment the meeting happens. There is no commercial reason for them to know or care what came of it. That's not a character flaw in appointment setters — it's what the contract asked for.

So change what you hold them to.

Ask for conversion by cohort. What proportion of the meetings delivered last quarter became qualified opportunities in your CRM. Not a case study, not a testimonial from a different client — the actual rate on the meetings they gave you. If a supplier can't answer that question, that is itself the finding. A supplier who tracks only delivery has no visibility into whether their qualification is working, which means they can't improve it.

Some pay-per-qualified-appointment models already exist, and a few providers distinguish between scheduled, held, and qualified-and-held in their pricing. That's a genuine improvement. What almost none of them do is report a downstream conversion rate on delivered meetings back to the client, which is the number that would actually tell you whether the criteria are working.

What belongs in the agreement:

• The qualified-meeting definition, in full, as the specification above
• A verification window — how long the receiving seller has to assess and dispute
• Rejection and replacement terms, with a named ceiling so neither side is exposed to open-ended disputes
• A reported converted-meeting rate by cohort, on an agreed cadence

That last clause is the one that changes behavior. Everything above it is hygiene.

‍

Does tighter qualification mean fewer meetings?

Yes. This isn't a caveat, it's arithmetic. Criteria that require an active project, a caused timeline, a named constraint, and a trigger event will disqualify buyers that looser criteria would have passed. Volume falls.

I'll state what that means for us, since it's the obvious objection. We sell meetings. Tighter criteria reduce the number we can deliver per client, and therefore what we invoice. That's a real cost to our business and I'd rather name it than have you notice it.

The reason I'd still argue for it: a smaller number of converting meetings costs less per opportunity than a larger number that don't, and only one of those two arrangements survives a budget review. If your cost per meeting looks efficient and your cost per opportunity doesn't, you already have the answer.

There's also a floor, and it's worth knowing where it is. Criteria strict enough to guarantee conversion produce almost no meetings, and a program delivering four meetings a quarter can't be evaluated, can't be improved, and won't be renewed. The goal isn't criteria that certify. It's criteria that predict — tight enough to exclude the meetings that were never going to move, loose enough to keep enough volume that you can read a result.

‍

How to hold a meeting supplier accountable, including us

Two questions. Ask them of anyone who sells you meetings, and ask them of us.

What proportion of the meetings you delivered to clients like me last quarter became qualified opportunities?

What do your qualification criteria actually screen for — buyer attributes, or situation?

If we can't answer both, we've failed the standard this article just asked you to apply to everyone else.

On our own products: Evolve Edge, which is live, carries qualification information into the brief the seller reads before the meeting — so what the buyer told us during qualification reaches the person who has to act on it. Evolve Coach is next. Neither writes your criteria for you. That's a decision about your own business and no software makes it.

And if you're not sure specification is your problem: the diagnostic here will tell you whether your conversion varies more by lead source or by seller. If it varies by seller, your criteria are probably fine and the work is elsewhere.