A key account management plan that changes next Tuesday
A key account management plan on one page: share of wallet with its source, the time budget most plans omit, and ninety day actions, not objectives.
ReadIt reads like the only honest pricing in the category, because you pay for output rather than effort. The catch is in the definition of the output, and there is published research on exactly what happens when you reward the easy half of a job.
A vendor sends a one line proposal: two hundred and fifty dollars per meeting, no retainer, you only pay for what you get. It reads like the first honest pricing you have seen in this category, because every other quote in the folder asks for money before anything happens.
Then the meetings start arriving and you notice something. They are real meetings. Somebody turns up. And almost none of them should have been in your calendar.
That is not a vendor behaving badly. It is the pricing model doing exactly what it was designed to do, which is produce meetings. Nobody was ever paid to produce the thing you actually wanted.
Everything about whether this model works for you is decided by one definition, and in most proposals that definition is missing. Before anything else, write down what a meeting is. Specifically:
If the proposal does not define these, the vendor's definition applies by default, and their definition is the one that pays them.
There is a general version of this problem and it is better documented than the sales literature suggests. Burton Weisbrod's working paper Why Strong Rewards in Government and Nonprofit Programs Don't Work: A Social Heisenberg Principle (Institute for Policy Research, Northwestern University, WP-25-1, January 2025) is about public services rather than B2B sales, and the mechanism transfers exactly.
His statement of it is blunt: "the stronger the reward is for the more easily observed dimensions of performance, the greater is the worker's incentive is to disregard the unrewarded and the poorly rewarded, dimensions of performance; small rewards for the observables make sense."
Read that against a per meeting fee. The meeting is the easily observed dimension. Fit, timing, budget authority and genuine intent are the dimensions nobody is paying for, and they are harder to observe at the moment the invoice is raised. The model does not make a vendor dishonest. It makes the unmeasured half of the job unrewarded, and unrewarded work gets less attention from everyone, including people acting in good faith.
Weisbrod also sets out the conditions under which paying for performance works rather than fails: the system has to reward what is easy to measure, it has to also reward what is costly to measure, and it has to avoid encouraging gaming that produces what "appears to be better performance, but actually is not". A single per meeting rate satisfies the first condition and neither of the other two.
These are not hypotheticals. They are what the incentive predicts, in the order they usually show up.
Seniority drift. Meetings get booked one layer below where they need to be, because that layer says yes faster. The call is pleasant, the person has no budget, and the follow up dies quietly.
Interest inflation. The pitch that books the meeting is not the pitch that sells your product. It is the pitch that gets a yes to thirty minutes. Those are different sentences, and the gap between them is the reason your conversion rate from these meetings is lower than from your own pipeline.
List exhaustion dressed as volume. A vendor paid per meeting works the easiest part of your market first. That is rational. It also means month four looks nothing like month one, and the ramp you planned off early numbers was measuring the cream of a finite list.
Pay per meeting is one of three structures, and the honest comparison is not about price. It is about who carries which risk and what each one quietly encourages.
| Model | Who carries the risk | What it rewards | Fits when |
|---|---|---|---|
| Retainer | You | Effort and continuity, not outcomes | The market is unproven and you need learning, not volume |
| Pay per meeting | Shared, tilted to the vendor | Bookings, which is a proxy | Your qualification criteria are written down and enforceable |
| Pay per qualified opportunity | Mostly the vendor | Something closer to the real outcome | You can define "qualified" without argument, and will arbitrate it |
The third row looks strictly better and often is not available, because a vendor cannot price a definition you control and can change. When it is available it costs considerably more per unit, which is the correct price of moving risk off your side of the table. The cash flow consequences of the first two are a separate question, worked through in B2B retainer versus project pricing.
There is a close cousin of this problem on the agency side of marketing, where the standard model takes a percentage of advertising spend and therefore rewards spending rather than results. Khaled Badr sets out the conflict and why he refuses the model in why we don't take a cut of ad spend. Same structure, different industry, and worth reading because the argument is made by someone turning down the money.
If you are going to buy this way, these are the clauses that decide whether it works. None of them is unusual and most vendors will accept them, which is itself a useful test.
Pay per meeting earns its place in two situations. The first is a market you already understand, where your qualification criteria are specific enough to be written on one page and you are willing to enforce them. The model then buys you capacity without a hiring decision, and the proxy is close enough to the outcome to be useful.
The second is a time boxed push with a known target list, where the job really is to get in front of people and you are not asking the vendor to judge fit. Pre-event booking is the clearest example, and it has its own window and rhythm, set out in booking meetings before a trade show.
If neither describes you, the question underneath is usually not pricing at all. It is whether to buy this capability or build it, and that comparison is in outsourced BD versus hiring a salesperson.
The research is not about sales. Weisbrod's paper examines pay for performance in public and nonprofit service industries: schools, hospitals, higher education, courts. Nobody has run the equivalent analysis on outsourced appointment setting, and we are carrying a mechanism across contexts. We think the carry is sound, because the mechanism is about measurement and reward rather than about any particular industry, but you should know that is what it is.
We have quoted no market rate. Per meeting prices circulate in this category, and the numbers we have seen come from vendor pages and forum posts with no disclosed sample, no definition of a meeting and no geography attached. A rate is meaningless without the definition it is attached to, so we would rather give you the definition and let you collect your own quotes.
A good vendor can beat a bad model. This is a post about what a pricing structure encourages, not a prediction about any individual firm. Plenty of people hold a higher standard than their contract requires. The point is that you are then relying on their character rather than on the agreement, and you should know which one you are relying on.
None of this fixes a qualification problem you have not solved. If you cannot say in writing which meetings you want, no pricing model will produce them, and a per meeting rate will simply convert your vagueness into volume. That work comes first, and it is yours.
Send us the proposal, the qualification standard you would hold it to, and the roles you need in the room. We will come back with where the definition is loose enough to bill against, which clause is missing, and whether the model fits your market at all.
Book a Free Consultation