We built the AI SDR we couldn't buy.
Outbound that isn't spam. Most tools sell volume. We optimize for qualified meetings you can verify.
Why we exist
Before writing a line of Rainmaker, we reverse-engineered the two most-hyped AI SDR tools in the market from inside their own apps. Not as critics. As users, trying to see if either could do what it claimed.
What we found: one paywalls you before showing a single lead. The other's demo silently fails for anonymous users, and its ICP engine returned our competitors as our ideal customers. Neither cites a source for any claim in any email. Both default to autopilot, meaning your company's name goes on emails you never approved. The observations are dated and written up in full on Rainmaker vs Gojiberry and Rainmaker vs Explee.
We built Rainmaker to be the opposite of both of those things. Founders and early sales teams get burned by tools that reward spraying more emails: burned domains, noisy inboxes, and zero trust. So every factual claim must be sourced, every send requires human approval by default, and pricing is partly tied to meetings the prospect accepts and keeps past the scheduled start. Not seats, and not sends.
What we optimize for
Meetings you can defend.
Not send volume. Not open rates. Not AI-scored leads that turn out to be a nuclear site tagged as real estate.
Every product decision we make runs through one question: does this help the user book meetings they can genuinely defend? If it optimizes for a number that isn't that, we cut it.
That is why we price on meetings booked, not seats. That is why nothing sends without your approval. That is why every factual claim in every email links to a real source, because a meeting booked on a false premise isn't a meeting, it's a time bomb.
Quality over quantity
Fewer, better-researched touches that cite real evidence. A bigger list is not a strategy.
Copilot, not autopilot
The agent drafts. You decide. Nothing leaves without approval, and autopilot is an explicit opt-in.
Verifiable outcomes
Outcome fees start only after an accepted meeting reaches its scheduled time. Never on a reply, a click, or an attendance guess.
Transparency by default
Guardrails, pricing math and sourcing logic are public and inspectable. What qualified means is written down before you pay.
How we stay honest
The guarantees are in the code, not the marketing.
“No source, no send” is not a policy. It is a function.
If the agent cannot find a verifiable source for a factual claim, the email is blocked before it ever reaches your approval queue. You cannot override it.
“Copilot by default” is not a setting.
ApprovalBatch is the default state of the system. Autopilot requires an explicit opt-in.
“Priced on meetings” is not a metaphor.
The $25 outcome fee triggers only when a meeting is booked, RSVP-accepted, not cancelled before the start time, and the start time has passed. We refused to charge on attended because calendar APIs do not expose attendance, and that is exactly the kind of unverifiable metric used to inflate numbers. We publish what qualified means because we think you should know before you pay.
The same rules that protect recipients also protect our reputation. The guardrail that blocks unsourced claims, the circuit breaker that pauses noisy campaigns, and the append-only ledger for billing are not marketing copy. They are running code. We publish the standards, we let you try the real pipeline with no signup, and we price so that our incentives align with yours.
This is not a story we tell. It is the operating system we run.
We are a small team.
We did not build Rainmaker to compete on features. We built it because the trust gap in AI outbound is real and the tools filling the space are making it worse. Every design decision in Rainmaker is a deliberate response to a documented failure in the category.
We are in public beta. We are building in public. If you want to follow the build, the changelog is public and the dispatch goes out with every release.
Subscribe to the dispatch