The number that matters
SaaStr left Marketo after 10 years because their AI agent could not work with the platform's API limits. Usable API time: roughly one hour per day. Migration time: one week. Cost: $14 in agent compute.
Jason Lemkin, SaaStr founder and former Adobe exec ($100M+ ARR from EchoSign acquisition), posted the breakdown. His team's agent was hitting Marketo's API ceiling 23 hours a day. They asked the agent what to do. It told them to leave and gave three alternatives.
Marketo wanted another 12% price increase after five straight years of hikes. They were SaaStr's most expensive vendor. Support was the worst in their stack. Nobody offered to fix the API limits or hold price at renewal.
SaaStr signed with Salesforce Marketing Cloud instead.
Why this matters for sales teams
Your tools are about to get fired by agents, not by your ops team.
When an agent hits an API limit, it does not file a support ticket. It surfaces the failure to whoever is using it. That person asks what to do. The agent, which has no loyalty to your incumbent vendor and no memory of last year's negotiation, gives a recommendation with alternatives.
No RFP. No committee. No six-month evaluation. One question, one answer, one week to migrate.
The protections vendors relied on are collapsing. Switching costs used to keep customers locked in. SaaStr moved a decade of data in seven days. Relationship equity does not apply when the decision maker is an agent. Familiarity still counts, but only if the product works when the agent tries to use it.
What vendors missed
Lemkin says Marketo could have kept the account for $20K (down from their increase ask) with higher API limits. They had multiple chances to name $25K and close it. Nobody did.
Support remains the cheapest retention lever in B2B, and most vendors are still terrible at it. If your product delivers half its value once an agent is doing the analysis work, you may need to let customers renew at half the price, at least temporarily.
API quality used to be a solutions engineering checkbox. Now it is a churn surface. Agents query your platform 10x more than humans did. A rate limit built for nightly syncs will not survive an agent that is working all day.
If your CRM, MAP, or data platform has API limits that block agents, your customers are one question away from switching. The agent will tell them where to go.