Outcome-based pricing for AI SDR tools sounds good in theory. "Pay only when it books meetings" is a compelling headline. The catch is always in the definition: what counts as a meeting?
This matters because the definition determines whether the pricing model is actually aligned with your interests - or whether it creates the appearance of alignment while charging on a metric you cannot control or verify.
Rainmaker charges $25 per qualified meeting. This post explains exactly what that means, how we chose the definition, and why we excluded the metrics most tools use.
The meeting definitions that do not work
Most B2B outbound tools that claim outcome pricing fall back on one of three proxy metrics. Each has a problem.
Reply. A reply is not a meeting. An out-of-office auto-reply is a reply. An angry "remove me from your list" is a reply. Charging on replies aligns the tool's incentive with generating responses, not with booking conversations that matter.
Click. A click on a link in an email is even further from a meeting. It measures curiosity about a piece of content, not intent to have a conversation.
Attended. This sounds closer to a real meeting. The problem is technical: calendar APIs - the standard integration for any meeting-booking tool - do not expose attendance data. Whether someone showed up to a calendar event is not in the API. A tool that charges on "attended" is either using a manual attestation from the sender (gameable), a proxy metric like "no cancellation before the meeting time" (which is what Rainmaker actually uses), or making a claim it cannot verify.
Each of these definitions creates misaligned incentives. A tool optimizing for replies sends more emails to generate more responses. A tool charging on "attended" without a reliable attendance signal has no real way to close the loop.
Rainmaker's definition of a qualified meeting
A meeting is qualified when all four of the following are true:
Booked - a calendar event has been created and the invite sent to the prospect.
RSVP-accepted - the prospect has accepted the calendar invite. (Not just received it - accepted it.) Not cancelled before the start time - neither party cancelled the event before its scheduled start.
Start time passed - the scheduled start time of the meeting has occurred.
These four conditions together define a meeting that, to the best of our ability to verify through calendar integrations, happened. The prospect agreed to the time. Nobody called it off. The clock ran past the start.
We publish this definition. It is on the pricing page. It is not buried in a terms-of-service document. If you evaluate Rainmaker and want to understand exactly when the $25 fee triggers, you can read the definition in plain English before you sign up.
Why we excluded "attended"
The most common objection to our definition is: what if the prospect accepted the invite, the meeting was not cancelled, but they were a no-show?
We excluded "attended" deliberately, not as an oversight.
Calendar APIs do not expose attendance. The only reliable signal available through standard calendar integrations is: was the event on the calendar, did the prospect accept, was it cancelled, did the start time pass? Attendance requires the prospect to have checked in through a meeting platform, or the seller to manually record a show. Neither is consistently available through an API.
We could build attendance tracking that asks sellers to confirm shows manually. We chose not to for one reason: manual attestation is gameable in both directions. A seller could mark every meeting as attended to avoid the fee. Or a seller could claim shows to hit a commission threshold. Neither outcome serves the accuracy of the definition.
The alternative - charging on a metric we cannot verify - would make the definition meaningless. We would be claiming outcome alignment while charging on an estimate.
Our position: a meeting that was booked, accepted, not cancelled, and whose start time passed is the most precise outcome we can verify reliably. That is what we charge on.
The cap: why it matters
The outcome fee is capped at 20% of your subscription charges per billing period.
This exists for one reason: to make sure the pricing cannot run away from you in a successful month.
If Rainmaker has a particularly strong month - books more meetings than you expected, and the $25 fees start stacking - the cap means the total outcome fees cannot exceed 20% of what you are paying in subscription charges. You benefit from strong performance without a surprise invoice.
The inverse is also true: if the tool does not book meetings, you pay the base fee and nothing more. The $79/ mo base exists regardless of outcomes. The $25 outcome fee only adds when the product delivers.
This is what "aligned pricing" means in practice: the tool earns more when you get more, it earns less when it underperforms, and it cannot earn disproportionately in a good month.
How this compares to the alternatives
Gojiberry charges $99/user flat. The pricing is simple and predictable. But it does not align incentives - you pay the same whether the tool books zero meetings or twenty. The tool has no financial skin in the outcome.
Explee charges $0.03 per email sent. This is usage-based, which is transparent. But it aligns the tool's incentive with sends, not meetings. More sends equals more revenue for the tool, regardless of whether the outreach is converting.
Rainmaker charges $79/mo base plus $25 per meeting, capped. The base covers the research and drafting infrastructure. The outcome fee aligns the tool's interest with yours for the output that actually matters.
No pricing model is perfect. Flat pricing is simpler. Per-email pricing is predictable. Outcome pricing introduces a variable component. What we chose to optimize for: the tool should only earn a performance premium on performance. If it does not perform, you pay less.