What Counts as a Qualified Meeting? A Definition Sales Teams Can Bill On

A qualified meeting is a held conversation with a decision-maker who fits your ideal customer profile and showed genuine intent to explore a solution — not a booking on a calendar, not a no-show, not a curious tire-kicker.

That sounds obvious until money is attached to it. The moment you pay a setter, an agency, or a platform per meeting, the word "qualified" stops being a soft descriptor and becomes a contract term. We run pay-per-meeting pipelines for a living, and almost every dispute we have ever seen traces back to two sides holding different definitions in their heads. This post is our attempt to write the definition down so both sides can agree before the first invoice.

Why a shared definition matters more than the meetings

Most teams never define "qualified meeting" in writing. They know a good meeting when they see one, and they assume everyone else sees the same thing. Then the meetings start landing, and the gaps appear. The vendor counts a booking the day it hits the calendar. The buyer counts it only after the prospect shows up and turns out to be a fit. Those are different numbers, and the difference is exactly where trust breaks.

A shared, written definition does three things. It aligns incentives, because the vendor is now paid for the outcome the buyer actually wants rather than a proxy for it. It makes reporting honest, because everyone measures the same event the same way. And it protects both sides, because a disputed meeting can be checked against criteria instead of argued from memory. If you take one thing from this piece, make it this: define the meeting before you buy the meetings.

A good definition has two independent halves — who the person is (fit) and what they did (intent) — plus one delivery condition (they actually showed up). All three have to be true. A perfect-fit prospect who no-shows is not a qualified meeting. A hyper-engaged buyer at a company you would never sell to is not a qualified meeting either. Get specific on each half.

Defining ICP fit: the "who"

ICP fit is the part teams think they have handled and usually have not. "We sell to mid-market SaaS" is a market, not a qualification rule. To bill on fit, you need criteria a third party could check without reading your mind.

We usually break fit into four buckets:

• Firmographics — industry, company size, revenue band, geography. The hard filters. A 12-person shop is not mid-market no matter how nice the conversation was.
• Role and authority — is this person a decision-maker or a credible influencer for the purchase? A junior analyst who booked out of curiosity fails here even if the company is perfect.
• Situational fit — do they have the problem you solve, in a form your product addresses? A company with no outbound motion is a poor fit for an outbound tool regardless of size.
• Disqualifiers — the explicit no list. Competitors, current customers, regions you cannot service, industries you refuse. Writing these down prevents the awkward "well, technically they fit" arguments later.

The practical move is to turn these into a scorecard rather than a vibe. We lean on structured lead scoring so fit is a number with reasons behind it, and we keep the underlying profile itself explicit and versioned — that is the whole job of a good ICP definition. When fit is codified, "qualified" stops being subjective and two people looking at the same prospect reach the same verdict.

Defining intent: the "what they did"

Fit tells you the meeting is worth having. Intent tells you the prospect wanted to have it. This is where a lot of "qualified" meetings quietly fall apart, because a booked slot is not by itself evidence of intent — plenty of people accept a meeting to be polite, to get a nagging setter to stop, or because they misread what the call was about.

Real intent shows up as signals you can point to. The prospect replied with a specific question about their situation. They named a problem in their own words. They asked about pricing, timeline, or how you compare to a tool they already use. They confirmed the meeting rather than passively letting it sit on the calendar. None of these guarantees a deal, but each one separates "agreed to talk" from "wants to talk."

The honest tension here is that intent sits on a spectrum, and you have to pick a threshold. Set the bar too high and you starve the pipeline waiting for hand-raisers who were going to buy anyway. Set it too low and you pay for conversations that were never going anywhere. We tend to define the minimum bar as: the prospect has acknowledged a relevant problem and agreed to a specific time to discuss it, with at least one signal beyond the acceptance itself. That is a deliberately modest bar, because the fit half of the definition is already doing heavy filtering.

Tying the definition to pay-per-meeting billing

Once fit and intent are written down, billing gets simple in a way that surprises people. You bill on the intersection: a meeting counts, and generates a fee, only when it is ICP-fit, intent-backed, and held. Booked-but-no-show does not bill. Held-but-off-ICP does not bill. That is the model we run — flows start at $500/month plus a small fee only on meetings that clear the bar — and the reason it works is that the vendor now eats the cost of bad targeting instead of passing it to the buyer.

This changes behavior on the supply side. When a vendor is paid per booking, the rational move is to book aggressively and let the buyer sort out the mess. When a vendor is paid per held ICP-fit meeting, the rational move is to qualify hard before booking, because an off-profile meeting is wasted effort they will never be paid for. The billing model and the definition reinforce each other. This is exactly why our qualification step sits before anything gets booked, and why we treat the whole booked-meeting flow — visible across the Leaderra platform and delivered by our AI SDR — as one accountable outcome rather than a stack of vanity metrics.

A few practical clauses worth agreeing up front:

• The held condition. A meeting is "held" when both sides show and the conversation happens. Define a grace window and what counts as a reschedule versus a no-show.
• The dispute path. Give the buyer a short window to flag a meeting that did not meet the definition, with the recording or notes as evidence. Most disputes evaporate when the criteria are checkable.
• The reschedule rule. A prospect who reschedules once and then holds is usually still qualified. One that ghosts across three attempts is not. Write down which is which.
• The credit rule. Decide in advance whether a genuinely mis-qualified meeting is refunded, re-run, or credited.

None of this requires a lawyer. It requires one page that both sides read before the pipeline turns on. If you are standing up this motion for the first time, our AI appointment setting guide walks through the operational side of getting these meetings booked and held.

If you want to see how the qualify-before-you-book model actually runs, you can watch the live demo or book a meeting and put our own definition to the test on a real call.

FAQ

What is the difference between a booked meeting and a qualified meeting?

A booked meeting is simply a slot on the calendar, which someone can accept for any reason including politeness or pressure. A qualified meeting adds two conditions: the prospect fits your ideal customer profile, and they showed genuine intent to explore a solution. A qualified meeting also has to actually be held. Booking is a proxy; qualification is the real outcome.

What makes a meeting ICP-fit?

ICP fit means the prospect matches the firmographic, role, and situational criteria of the buyers you can realistically win, and does not trip any of your disqualifiers. In practice that means the right industry and company size, a decision-maker or credible influencer, and a problem your product actually solves. The cleanest way to enforce it is a written scorecard rather than a subjective judgment call.

Why should billing be tied to held, ICP-fit meetings?

Because it aligns incentives. When a vendor is paid per booking, they are rewarded for volume regardless of quality, and the buyer absorbs the cost of bad targeting. When payment depends on the meeting being ICP-fit, intent-backed, and actually held, the vendor is motivated to qualify hard before booking. The billing model and the quality definition end up reinforcing each other.

How do you measure buyer intent before a meeting?

Intent shows up as concrete signals rather than the acceptance itself. Look for the prospect naming a specific problem, asking about pricing or timeline, comparing you to a current tool, or actively confirming the meeting. You set a minimum threshold, typically an acknowledged problem plus an agreed time plus at least one additional signal. It never guarantees a deal, but it separates real interest from passive politeness.

What happens when a qualified meeting is disputed?

A good agreement gives the buyer a short window to flag a meeting that did not meet the written criteria, backed by notes or a recording. Because the definition is checkable, most disputes resolve quickly against the scorecard instead of turning into an argument from memory. You should also agree in advance whether a genuinely mis-qualified meeting is refunded, re-run, or credited, so there is no ambiguity when it happens.