The Numbers
SaaStr replaced their contact form with an AI agent. For one event, the results: 614 meetings booked, $85k average ticket size, 2.25 million sessions handled, 402,000 interactions processed. Almost zero complaints. The team size: three people.
Jason Lemkin is blunt about the math. "There is no version of this we could have staffed with humans." The old flow killed deals. Prospect fills form, waits. Someone round-robins the lead. AE follows up two to three days later. By then, the lead is cold or talking to competitors.
What It Actually Does
The agent, called Amelia AI, runs on Qualified (now owned by Salesforce). She is trained on the full SaaStr site, crawls content daily, and knows the difference between self-serve ticket buyers and enterprise sponsors. Separate contexts for different events mean faster, more accurate answers.
Beyond chat, she routes leads, runs discount campaigns, and books meetings directly into calendars. No handoffs. No delay. The conversion happens while the prospect is still warm.
Why This Matters for Sales Teams
Contact form abandonment is a known problem in B2B. Forms add friction. Delays kill intent. Lemkin's data shows what happens when you remove both: qualified pipeline at scale without adding headcount.
For ANZ sales teams watching comp benchmarks, this is relevant context. SaaStr hit $5M ARR in 2024, bootstrapped, growing 90% annually to an implied $8M run rate. They are doing it with three people and agents, not a scaled BDR team. Worth noting: they are not VC-funded, which changes the unit economics calculation.
What the Comp Looks Like
No BDR comp to report here because there are no BDRs. That is the point. The agent handles qualification, booking, routing, and campaign execution. The humans handle strategy and closing.
Lemkin says this is "the most Captain Obvious move in AI go-to-market right now." He is correct. The tech exists. The ROI is clear. Most companies, including AI startups, still run contact forms and nothing else.
The takeaway for sales leaders: if your inbound process involves a form, a delay, and a round-robin, you are leaking pipeline. The fix is available. The question is whether you are willing to rebuild the flow.