What Is a Qualified Meeting? Meaning, Criteria and Who Decides

Every meeting a provider books is a meeting; a qualified meeting is one that was worth booking. The word qualified carries the whole weight of appointment setting and SDR contracts, because it is the unit that gets paid for and reported, and it is the unit buyers and providers argue about when a calendar fills up without the pipeline following.

The term has no fixed industry definition, which is the point of this entry: the definition is something each buyer and provider must agree, in writing, before the first email is sent.

For the wider subject of meeting-led services, see the B2B lead generation topic hub.

Five recur in well-run agreements.

1. Company fit. The company matches the agreed profile: industry, size band, geography. The ICP is the reference document.
2. Role fit. The person has a named part in a decision like this: they decide, hold budget, evaluate or will use what you sell.
3. A problem acknowledged. Some version of the problem was discussed before booking, not discovered in the meeting.
4. Informed consent. The person knew what the meeting was about when they accepted. A calendar invite accepted out of politeness fails this test.
5. Held, not booked. A meeting that does not take place is not counted, and a no-show is not half a meeting.

A worked example, which is illustrative: Quaywise, which sells warehouse software, defines a qualified meeting as a 30-minute call, held, with a named person at a logistics company of 200 or more staff who owns warehouse operations or IT, who knew the subject when they accepted. One sentence, five tests, no room for argument.

The lead qualification checklist, account edition adds the account-level questions to the usual ones.

Whoever wrote the definition down first, which should be both parties, together, before the contract is signed. The practical steps are short: write the criteria as a numbered list, attach it to the agreement as an annex, name who judges borderline cases and how disputes are settled, and state plainly that no-shows and meetings taken to be polite do not count.

Our qualified meeting definition sheet is a fill-in version built to be attached to a contract. Doing this before work starts is cheap. Doing it in month two, with an invoice on the table, is not.

Because the incentive runs against the definition. A provider paid per meeting earns from volume, so every loose word in the criteria drifts towards more billable meetings: the person was senior enough, the company was nearly in profile, the no-show can be rebooked so it half counts. The buyer, reading the same words, sees a calendar of polite conversations and an invoice.

Neither side is dishonest. The words were loose, and loose words settle in favour of whoever counts them. This is the single most common argument in pay per meeting engagements, and our post pay per meeting vs retainer covers how the pricing model shapes it.

An SQL (sales qualified lead) is a person sales has checked and agreed to pursue; a qualified meeting is a conversation with such a person that actually took place. One is a name in the CRM, the other is half an hour in a diary. Both share the same limit: each is a one-person unit, and in a large deal one person is a start, not a decision.

No. A purchase in a large account is agreed by a buying committee: someone who decides, someone who pays, evaluators, users and functions that can block. A qualified meeting engages one of them. If that person moves on, loses interest or loses the internal argument, the account closes behind them.

That is why we treat the qualified meeting as the floor, not the goal. The goal is an inroad: more than one person in conversation, a problem named in the buyer's words and a next step that adds someone new. The lesson Why One Meeting Is Not an Inroad opens our appointment setting course with exactly this gap.