SaaStr Says One Agent Does Most of Four Marketers' Work

In a post about a Wall Street Journal CMO Today feature, SaaStr founder Jason Lemkin wrote that one in-house agent, called 10K, does more work than any of SaaStr's other agents. Lemkin wrote that most of what a VP of Marketing would do now runs through 10K.

SaaStr says it runs on three humans and more than 20 agents. 10K makes about 35,000 Salesforce API calls a day, with a record of 45,000, and SaaStr says its Salesforce bill is up about 40% in 2026 because of agent usage.

The salaries come off the payroll line of the P&L. What replaces them is a metered bill, and its size depends on two things, how the agent is built and what vendors decide to charge for its calls. A GTM leader controls the first one. The vendor controls the second.

The agent's costs are evolving

SaaStr says 10K estimates its own metered cost at about $10,000 a month. The figure is the agent's own estimate, and no invoice has been published. Lemkin wrote, "That's still far less than four marketing salaries, but it isn't free." SaaStr also set a $100-a-day cap on AI spend, and the post says the agent broke through it.

The $10,000 is a moment in time. The same post reports that SaaStr reduced 10K’s Salesforce calls by about 90% from a September peak. It did that by moving heavy work onto its own stack while staying on Salesforce. The post doesn’t say whether the estimate comes before or after that reduction.

SaaStr's own accounting of what its agents cost has changed over time. In a post announcing Episode #005 of The Agents, SaaStr said 10K’s Replit bill was about $80 for the previous month, covering Replit’s platform alone. The same post put the fully burdened cost of 10K and its customer-success agent, QBee, together at $500 to $800 a month. The $10,000 is a metered estimate the newer post doesn't break down, so the three figures aren't a before and after.

Salesforce calls drive the cost

A separate SaaStr post on running Salesforce headless shows how the CRM line item moves. SaaStr’s data usage against Salesforce rose about 10 times while its seat count stayed flat, and the bill rose about 40%. SaaStr wrote, “That’s OK, but it’s approaching our limit.” It said it would store less in Salesforce if costs kept rising. The 90% reduction is what that looked like in practice.

Seats didn't move. A CRM forecast built on seat count would have missed the increase, because it tracked the agent's activity while logins stayed flat.

Salesforce plans to price agent calls directly. Salesforce Ben reports that successful MCP and API calls by registered agents will consume Flex Credits. The multiplier isn’t published, metering hasn’t started, and customers get 30 days’ notice. Existing integrations keep current pricing. Salesforce Ben noted that “customers cannot yet calculate the cost impact.” We covered the change when Salesforce first laid out agent metering.

Salesforce told the outlet that consumption depends on how the agent is built. That splits the bill into two variables. Buyers control how their agent is built, as SaaStr’s 90% drop shows. The rate on every call that remains is Salesforce’s call.

The meter can be engineered down

SaaStr is the best evidence that the bill can be managed. It dropped its calls about 90% without leaving Salesforce. Falk Gottlob ran product at Salesforce and now runs Falkster.AI. Gottlob argues that a per-call meter stacked on the seat pushes customers to sync records to their own database and read from there, the same workaround Lemkin first described. In Gottlob’s telling, agent traffic drops, the metered revenue never shows up and seats shrink at renewal. “A meter on the call is the seat model refusing to move,” Gottlob wrote.

Gottlob shares Lemkin's estimate that the agent rate could cost 60 to 1,200 times the integration API rate. Both are estimating, since Salesforce hasn't published a rate.

If pricing climbs sharply, customers will build around it, as SaaStr already did. But the fix was a project. SaaStr moved its work onto a separate stack that it now has to run itself. Each architecture change and each vendor repricing resets the number, so the agent line moves the way usage spend does while payroll held steady.

Every number here is SaaStr's own and unaudited. SaaStr sells an agents playbook and promotes running a company this way. By SaaStr's own account, a human still publishes ads and Marketing Cloud segments, so the swap is partial.

Salesforce’s Flex Credit multiplier for agent calls is still unpublished, and metering starts only after 30 days’ notice. Until it lands, the $10,000 is the agent’s guess at a bill the vendor hasn’t finished writing.

Cutting the roles is the entry point. Owning the meter is the job.

Salesforce charged SaaStr for seats, and the seats didn’t move while the agent’s calls rose tenfold. Now it plans to charge for the calls, the sequence Gottlob describes as the seat model refusing to move. SaaStr has published what that looks like from the buyer’s side.

If the pattern holds, the headcount a GTM leader cuts for an agent returns as usage spend, priced by the vendor and reset with each architecture change and each new rate card. The saving is real until the meter starts, and nobody has seen the meter yet.

That's still far less than four marketing salaries, but it isn't free.

By Business of GTM