Back

What Is a Qualified Meeting? Define It Before You Outsource

TL;DR — There is no industry-standard definition of a qualified meeting, and there shouldn't be. What counts as qualified for a £4,000 product is not what counts for a £400,000 one. Agree it in writing before outreach starts, specific enough that either side can look at a meeting and say plainly whether it counts. An argument about meeting quality is what it looks like when quality was never defined.

A qualified meeting is an attended conversation with a person and company matching the targeting criteria you and your provider agreed in advance, where there is a credible reason for a sales conversation. That much holds everywhere. What sits underneath it; how much seniority, budget, timing or problem fit matter, and where each threshold falls depends on what you sell and to whom. Anyone handing you a fixed definition without asking about your deal size, your sales cycle or your buying committee is describing their own convenience rather than your requirement.

At Pipeline we agree the qualification criteria with each client during onboarding, and that agreed standard defines a qualified meeting for that engagement. A workable definition covers four things: who counts, the problem test, why the meeting is happening, and what to do when one sits on the line.

Why is there no standard definition of a qualified meeting?

Because the thing being qualified changes shape with the deal.

Sell a ÂŁ4,000 subscription and a motivated operations manager can buy it: the problem is hers, the authority is hers, and her finance lead is the only other person involved. That meeting is qualified. Sell a ÂŁ400,000 platform into the same company and she becomes a useful ally who cannot sign anything. Same person, same enthusiasm, completely different meeting for the AE who has to work it.

Sales cycle does the same to timing. A prospect saying "not until next year" is worthless if your average deal closes in six weeks and exactly who you want if it closes in eleven months. The size of the buying committee does it again: one signature makes seniority the whole test, seven makes influence matter more than authority.

A definition built for one of those situations misleads you in the others.

What do the usual frameworks get wrong?

Nothing, if you are using them for what they were built for.

Budget, Authority, Need, Timeline is a sound way to qualify a deal in progress, and parts of it adapt perfectly well to earlier stages. The failure is requiring it in full before a first outbound meeting. Do that and you ask a cold prospect to have done work they have not done; costed a solution, raised it internally, formed a timeline, and you disqualify the early market, which is the part outbound exists to reach.

It also tests in the wrong direction, measuring how ready someone is to buy when the question is whether this is a person your business should be talking to at all. A prospect with budget and a live project can still be a poor fit; one with neither can be the account you most want in front of your AE, because the problem is real and nobody has told them there is an answer.

Use BANT to run a deal. Demand it in full to judge a first meeting and you will disqualify the pipeline you went outbound to find.

What should your definition actually contain?

At this point it is fair to think: this sounds like you're avoiding giving a straight answer.

The straight answer is that a provider's fixed definition would be worse for you. A standard applied across every client has to be achievable across every client, so it settles wherever the weakest market can support it: seniority thresholds drop to a level hittable anywhere, problem-fit tests loosen to survive a bad month, and when your ICP moves you have no standing to move the bar with it.

So build your own. Four things.

Who counts. Start with recent closed-won deals and read off the roles where they began. Then test that pattern against the ICP you are targeting now, the deals you lost, and any market you are trying to enter. Historical wins describe what your current team could close, which is not always where your best opportunities sit.

The problem test. What must be true at a prospect's company for your product to be relevant, phrased so a BDR can hear it in conversation rather than infer it afterwards.

Why the meeting is happening. A prospect who agreed because something landed is a different proposition from one who agreed to end the outreach. That sounds subjective, but it is assessable from call notes: did they recognise the problem, understand why the meeting was offered, and show some interest in exploring it?

‍

What should you agree before signing anything?

The pre-signature paragraph. Before you sign with anyone — us included, if you are weighing up outsourced BDRs — write one paragraph defining a qualified meeting for your business. A paragraph, not a schedule. Ask for the version they would be happy to be measured against. If the two match, you have a partner. If they don't, you have had that argument in week zero, for free.

‍

Frequently asked questions

What is a qualified meeting?

A qualified meeting is an attended conversation with a person and company matching the targeting criteria the buyer and provider agreed in advance, where there is a credible reason for a sales conversation. Beyond that baseline there is no universal standard, because what makes a meeting worth an account executive's time depends on deal size, sales cycle and how many people must agree before anything is bought. Write the criteria down before outreach begins, covering borderline cases and no-shows as well as clear passes.

What's the difference between a qualified meeting and an SQL?

An SQL — sales qualified lead — is a record that has passed a threshold and been handed to sales. A qualified meeting is an event: a conversation in a diary, with a named person who turned up. One is a status in your CRM, the other is half an hour of an account executive's day. Where a provider is paid against meetings, the meeting definition is the one to settle before you sign.

Does a booked meeting count if the prospect does not attend?

No. A conversation nobody had is not a qualified meeting, and no wording in a contract makes it one. What is negotiable is the commercial treatment: whether you pay against meetings booked or meetings held. Settle that before signing, along with the awkward cases — whether a rebooked no-show counts on the original date or the new one, and how many attempts a prospect gets before the meeting is written off.

‍

Related Articles

View all  articles