SaaStr runs Salesforce headless for six months: usage 10x, bill up 40%
Jason Lemkin's team stopped treating the CRM screen as the way in and pointed AI agents at the API instead. The consumption bill is the part founders should read twice.
For six-plus months, almost nobody at SaaStr has logged into Salesforce. The subscription is still paid and the data still sits there. The interface simply stopped being the way anyone reaches it.
Jason Lemkin, who runs SaaStr, set out what the team did in a post on the company's site. There is no clever workaround in it. They used the Salesforce API, then built an agent on top of that API using Claude. Internally they call the setup Claudeforce and the agent 10K.
The reason was arithmetic. Lemkin says SaaStr now runs on a very small number of humans and more than 20 production AI agents, with revenue up 47% year on year after being down 19%. At that ratio, he argues, the question is not whether the CRM screen is good. It is whether the agents can reach the data.
More than 10 of those 20-plus agents now touch the CRM layer. Some were built in-house, several are third-party agents pointed at the same API. Lemkin's claim is that once the system of record is headless, adding the eleventh agent is a config change rather than a project, with no waiting for a vendor to ship an integration.
The part he says he underestimated was the join. CRM data sat in one place, marketing data in another, and the financial picture in Bill, Brex and QuickBooks. With API access to all of them at once, he says a single question — has this account paid, what have they opened this month, where is the renewal — gets one answer. That used to take three people and a spreadsheet.
They also built a quote-to-cash agent that runs from contract to signature to collection, and an "AI VP of Revenue" that pushes pipeline changes and closed deals into Slack in real time rather than waiting to be asked.
Then the bill. SaaStr's data usage against Salesforce is up roughly 10x, according to Lemkin, and he expects it to reach 100x. The invoice is already up about 40%. His account count did not change at all.
He says that is close to the limit. If consumption rises much further, the team will store less data in Salesforce. Agents do not check the CRM twice a day like a rep; they hit it constantly, because doing so costs them nothing.
That is the trade a founder considering this should price first. Going headless does not reduce vendor spend. It converts a seat bill into a consumption bill, and consumption is the line that moves.
The other finding is less about tooling than about people. SaaStr's sales lead still uses the classic Salesforce record view all day. Lemkin reads Slack. Amelia talks to 10K for an hour each morning. Four people, four surfaces, one set of data.
The practical takeaway: the interface you buy is one surface among several, and the thing worth checking before you commit is whether the platform lets you build on the API without asking permission — and what it charges you when your agents start reading everything, all the time.
More: SaaStr