What Counts as a Qualified Meeting at Recursive Scale
The acceptance criteria are written before launch as a named list of titles. What makes a meeting billable, who decides, and what happens when the two sides disagree.
In short
- Recursive Scale agrees the acceptance criteria in writing before the first message sends, as a named list of titles or a substantially equivalent role reasonably relevant to the client's offering.
- A meeting is billable only when a person meeting that written standard attends and takes part, so a calendar entry that nobody honours produces no invoice.
- Of thirty B2B outbound agencies read on their own sites on 17 September 2026, five publish qualification criteria a buyer could argue from and fourteen use the word qualified without defining it anywhere.
- Pricing is quoted per engagement, typically $200 to $800 per attended meeting depending on ICP and deal value, with no setup fee, no retainer and no minimum.
A meeting is qualified at Recursive Scale when a person holding one of the titles agreed before launch, or a substantially equivalent role reasonably relevant to your offering, attends the meeting and takes part. That definition is written down before the first message sends. Pricing is quoted per engagement, typically $200 to $800 per attended meeting depending on ICP and deal value.
The definition comes first, not last
Every pay-per-meeting arrangement has one operative term, and it is this one. The rate, the channel mix and the volume all follow from whether a given meeting counts.
Most of this market settles that afterwards. Thirty B2B outbound agencies were read on their own sites on 17 September 2026. Fourteen use the word qualified against a meeting or a lead and publish no criteria anywhere. Five publish something a buyer could actually argue from. One publishes a deadline for rejecting a meeting.
A standard agreed after the meetings start arriving is not a standard. It is a monthly negotiation in which the party holding the invoice has the stronger position.
What is agreed before launch
Three things are written down before anything sends.
The titles. A named list, agreed with you. Not a seniority band, not a description of a decision-maker, a list. Where a real job title sits outside the list but covers the same responsibility, the standard reads “a substantially equivalent role reasonably relevant to your offering”, which is there to stop a Head of Revenue Operations being refused because the list said VP RevOps.
The market. The companies the programme will work, agreed as a definition rather than a sample. A meeting with a perfect title at a company outside the agreed market is not billable.
The exclusions. Existing customers, live opportunities and any account you name are suppressed before outreach begins. A meeting with a company already in your pipeline is not a meeting Recursive Scale produced.
You approve all three, plus the messaging and the sender names, before the first send.
Attendance is inside the definition
A booking is not a meeting. The distinction decides the invoice and most of this market leaves it ambiguous.
| The event | Billable at Recursive Scale |
|---|---|
| A calendar entry is created | No |
| The prospect confirms the slot | No |
| The prospect does not appear | No |
| The prospect reschedules and does not attend the new slot | No |
| The prospect attends and takes part | Yes |
| The prospect attends but holds a title outside the agreed list | No |
| The prospect attends at a company you had already excluded | No |
Nine of the thirty agencies read trigger on attendance in some form, using five different words between them. Three trigger on a booking and publish no rule at all for what happens when the prospect does not turn up, which means a no-show is billable on their published terms.
What happens when we disagree
Disagreements happen and the structure decides how they end.
Because the criteria are titles and a market definition rather than an assessment of intent, most disputes resolve by reading the list. A title is on it or it is not. A company is inside the agreed market or it is not.
Where a role is genuinely borderline, your view settles it. The reason is commercial rather than generous: a provider paid only when a prospect attends has no way to profit from a meeting that should not have happened, and an argument about a single invoice costs more than the invoice.
Where a meeting was clearly outside the standard, it is not billed and it does not need a claim form to establish that.
Why the definition and the billing trigger belong together
An agency paid a retainer never has to define a qualified meeting, because the invoice arrives whether or not one occurs. Definitions are expensive to write and constrain the writer, so a provider with no commercial reason to write one usually does not.
Billing on an attended meeting forces the issue. Recursive Scale cannot raise an invoice without pointing at a person, a title and a conversation that happened, which means the standard has to exist before the work starts and has to be specific enough to apply.
The same logic removes the floor underneath the rest of the arrangement. No setup fee, no retainer, no minimum, no tooling charge. A month in which no qualified prospect attends anything produces no invoice, so there is nothing to argue about in a quiet month either.
Who this is not for
The model does not suit everyone and the cases where it does not are predictable.
Markets under roughly 10,000 reachable buyers. Below that, a full pass produces too few meetings for the arithmetic to work, and the constraint is the market rather than the price. Say so early and the answer is usually that outbound is the wrong channel rather than that the rate is wrong.
Annual contract values under roughly $10,000. At $200 to $800 per attended meeting, a deal worth less than about ten thousand cannot absorb the cost of the meetings it takes to win one.
No working sales process. Recursive Scale produces attended meetings with people holding titles you named. Converting those into revenue is your side of the arrangement, and a programme that fills a calendar nobody works is an expensive way to discover that.
A requirement to own the sending domains. Outreach runs on Recursive Scale’s own domains and inboxes so your primary domain is never exposed to complaint risk. If you need the sending estate in your own name, this is the wrong provider.
A need for the definition to stay flexible. The standard is fixed before launch and changed by agreement rather than by the month. Teams that want to redefine a qualified meeting as they go will find the arrangement rigid, which is the point of it.
What to ask any provider, including this one
Four questions, each answerable with a document rather than a conversation.
- Write down the titles that make a meeting billable. A list settles a dispute. An adjective does not.
- Does the invoice require the prospect to have been there? Ask for the exact word and what it means.
- What happens if the prospect reschedules? Twenty-nine of thirty agencies publish nothing on this.
- What do I owe in a month with no qualified meetings? The answer here is nothing. It is not nothing everywhere.
Open-ended term, 14 days’ notice. You keep the target data and the reply history.
Questions this raises
- What is a qualified meeting?
- At Recursive Scale, a meeting with someone holding a title on the list agreed before launch, or a substantially equivalent role reasonably relevant to your offering, who attended and took part. Attendance is part of the definition, not a separate condition.
- Who decides whether a meeting was qualified?
- The written list does. Because the criteria are titles rather than judgements, both sides read the same document and reach the same answer. Where a role is genuinely borderline, the client's view settles it.
- Do you charge for a meeting the prospect does not attend?
- No. Attendance is built into the standard, so a booking nobody honours is not a qualified meeting and produces no invoice. Nothing is owed before a qualified prospect attends.