SaaStr's Salesforce agents raised its bill 40% with no new seats

Almost nobody at SaaStr has logged into the Salesforce UI in six months, according to SaaStr's account of the switch. Data usage across the account rose 10x over that stretch, and the Salesforce bill went up 40% with the same seat count as before.

The team built its own Claude agent, called 10K, to run Salesforce through the API. Bill, Brex and QuickBooks now route through the same layer. A small human staff works alongside more than 20 production agents doing that work full time.

Frequency explains the jump. A rep checks Salesforce a few times a day. An agent hits the API every time it needs a fact, runs a check, or takes an action. With 20-plus agents running production workflows, those calls add up fast.

SaaStr doesn't say whether Salesforce changed its pricing tiers in response. It also doesn't break out how much of the 40% increase came from Salesforce alone versus the combined load across Bill, Brex and QuickBooks.

Anyone stacking an agent layer on a seat-priced product should model API cost per agent action first. For SaaStr, going headless didn't lower the bill. It changed what the bill measures.