Qualified is the most abused word in sales development. Left undefined, it means whatever makes this month's report look healthy, and it is the source of nearly every argument between a company and the agency it hired.
The fix is not complicated. Define it in writing before the first campaign sends, in terms specific enough that two people looking at the same meeting would reach the same verdict. What follows is how to do that, and why the frameworks most teams reach for no longer quite fit.
Why BANT stopped being enough
Budget, Authority, Need, Timeline was built for a world where one person could say yes. That world is mostly gone. A considered B2B purchase now involves several people who each have to agree, and applying BANT strictly to a first meeting disqualifies almost everyone, because at that stage there is usually no allocated budget and the person you are talking to cannot sign anything.
Used as a filter for a first conversation, BANT rejects good prospects for the crime of being early. The questions worth asking at this stage are different: does this company plausibly have the problem, is this person close enough to it to matter, have they acknowledged it in their own words, and is there any reason this becomes urgent rather than remaining interesting.
The criteria worth writing down
A workable definition has four parts, and it fits on half a page.
Company fit is the first, and it should be mechanical: size, sector, region, and whatever specific attribute predicts that your product is relevant. This part should be checkable without a conversation, because it is the part the list should already have solved.
Person fit is the second. Not necessarily the decision maker, but somebody with a real stake in the outcome. A practitioner who owns the problem is often a better first meeting than an executive who delegated it two years ago, provided they can bring the right people in later.
Acknowledged need is the third and the one that carries the most weight. The prospect has to have said something, in their own words, that indicates the problem exists for them. Agreeing to a call because the email was polite is not an acknowledged need, and a reply saying tell me more is the weakest possible version of one.
Timing is the fourth, and it should be the loosest. You are not looking for a purchase order date. You are looking for evidence that this becomes a live issue in a foreseeable window: a contract renewal, a project already funded, a deadline in their sector, a new executive with a mandate.
- Company fit: mechanical, checkable, already solved by the list
- Person fit: close enough to the problem to have an opinion about it
- Acknowledged need: stated by them, not inferred by you
- Timing: a plausible window, not a purchase date
Add the exclusions
A definition is sharper when it says what does not count. Write down the disqualifiers explicitly, because these are the meetings that generate arguments later.
Students, researchers, and consultants gathering information. Competitors doing reconnaissance, which happens more than most people expect. Existing customers whose account manager should be handling this. Job seekers. Companies in an active evaluation that closes next week, where you are being used as a third quote. And anyone who agreed to a call purely because the person booking it was persistent.
Decide what happens when a meeting fails the bar
Agree this before it happens, because it will happen and the moment is a poor time to negotiate. A reasonable arrangement is that a meeting failing the agreed criteria does not count toward any target and gets replaced, provided the objection is raised quickly and with a reason.
That last condition matters in both directions. Feedback given within a day or two, naming the criterion that failed, is a usable input that sharpens the profile. Feedback given at the end of the month as a general complaint about quality is not, and it is not a fair basis for rejecting the work either.
A weekly review of borderline cases is worth more than a dispute process. Most disagreements about qualification are really disagreements about a criterion that was written too loosely, and they resolve by tightening the wording rather than by arguing about the individual meeting.
The metric that keeps everyone honest
Meetings booked is easy to hit and easy to inflate. Meetings held is harder and much more informative. Opportunities created is the number that actually matters, but it lags by a full sales cycle, which makes it useless for managing a campaign week to week.
So track all three, and watch the ratios between them. A widening gap between booked and held suggests people are being pushed into calls they were not committed to. A healthy held number producing no opportunities means the qualification bar is set too low, whatever the definition says on paper.
One more, which is qualitative and worth more than it sounds: ask your account executives whether they were glad they took the meetings. If the honest answer is no, the definition needs work, regardless of what the dashboard shows.
Beware the guarantee
Guaranteed meeting volume is the clearest place where a definition of qualified gets quietly eroded. A commitment to fifteen meetings a month creates enormous pressure in the last week of the month, and that pressure always resolves in the same direction.
This is not an accusation of bad faith. It is an observation about incentives. If the only number that matters is a count, the standard behind the count becomes negotiable. Agreeing a realistic target after both sides have seen the market produces better meetings than a guarantee offered before anyone looked at it.
The short version
Write the definition down. Keep it to half a page. Make it specific enough that two people reading the same meeting notes would agree on the verdict, and revisit it after the first six weeks, when you have real examples to argue about rather than hypotheticals.
Everything else about an outbound engagement becomes easier to manage once that one document exists.