The other day ServiceTitan shut off Podium’s integration for roughly 1,000 shared customers after a nine-year partnership. The coverage mostly framed it as a breakup. It works better as a case study in what owning the record can and can’t do for you.
ServiceTitan delisted a partner with $100M in AI agent ARR, cut off 1,000 shared accounts, and kept essentially all of those accounts. The contractors stayed because their jobs, invoices, customer history, and technician schedules all live in ServiceTitan. Podium was the removable piece. That is what being the System of Record buys you.
What it didn’t buy was a change in the growth rate. ServiceTitan grew 25% last quarter, which is a very good number and roughly the best case for a vertical System of Record in 2026. Snowflake grew product revenue 34% with 126% net revenue retention. Databricks crossed $7B ARR growing over 80%.
Owning the record is a retention asset. The growth has to come from somewhere else, and the gap between the two is widening every quarter.
Why Being a System of Record Alone … Isn’t Enough:
- Systems of Record convert into retention, not acceleration. ServiceTitan can cut off a partner, lose nobody, and still grow 25%. Salesforce’s applications business, the actual System of Record, grew 7% in constant currency last quarter.
- Systems of Record are the most expensive databases most companies own. Salesforce’s list price for additional data storage is $125 per month per 500MB, or $3,000 per GB per year. The same gigabyte on S3 costs a fraction of a cent per month.
- Agents create, consume, and touch far more data than humans ever did. Salesforce processed 28.6 trillion tokens for customers, up 152% quarter over quarter. Data 360 ingested 52 trillion records in a single quarter, up 136% year over year. None of that is human-scale volume, and none of it is priced for.
- Salesforce already conceded the point. Of those 52 trillion records, 35 trillion came in via Zero Copy, meaning they never physically moved into Salesforce. Zero Copy volume grew 277% year over year. The fastest-growing data motion at the largest System of Record is the one where it doesn’t hold the data.
- Owning the record doesn’t win you the agent sale. Podium built $100M in AI agent ARR in under 24 months, much of it inside ServiceTitan’s own customer base. Open platforms lose agent deals to specialists. Closed ones eventually lose the customer.
- API limits bite before storage costs do. Salesforce allocates API calls per user per day. Agents don’t have users. ServiceTitan’s April 2026 API terms go further and bar AI systems from independently choosing endpoints.
#1. What the Podium fight actually proved
ServiceTitan’s Marketplace policy, published in June 2026, welcomes competitive partners as long as they aren’t using the partnership and the support that comes with it to gradually displace parts of ServiceTitan. Its API terms from April 2026 require calls to stay inside a predefined certified scope and bar AI systems from choosing endpoints on their own.
Together those two documents describe a perimeter. ServiceTitan is defending the ground around the record, and it has the leverage to do it, because the alternative for a contractor is ripping out the thing that runs their business.
That leverage is worth a lot. It shows up as high renewal rates, as pricing power, as net revenue retention above 110%. It is also almost entirely defensive. Cutting off Podium doesn’t add a dollar of new revenue to ServiceTitan. It prevents the loss of some future dollars. Those are different businesses.
Every System of Record carries the same asymmetry. The switching cost that keeps customers in is a separate asset from the thing that makes them spend more.
#2. Retention is the floor, not the engine
Look at what the Systems of Record are printing.
Salesforce reported $11.13B in Q1 FY27, up 13%. Strip out the Informatica acquisition and organic growth lands closer to 8-9%. More telling is how the company now segments itself. Agentforce Apps, which is sales, service, marketing, commerce, and Slack, came in at $6.91B and grew 7% year over year in constant currency. Data 360, Headless Platform, and Other went from $2.95B to $3.68B.
The record layer grew 7%. The data layer grew 25%. Same company, same customers, same quarter.
Veeva, one of the most locked-in Systems of Record in existence, grew 16% last quarter while running a full CRM migration underneath its customers. Salesforce management flagged lower attrition as a driver of net new order value. Retention is holding up fine.
Now the layer underneath. Snowflake: product revenue up 34%, NRR 126%, RPO up 38%, 779 customers over $1M. Databricks: over 80% growth at $7B ARR.
Customers aren’t leaving the System of Record. They’re spending their incremental dollars somewhere else.
#3. Systems of Record are extremely expensive databases
Salesforce charges roughly $125 per month for an additional 500MB of data storage. That works out to $250 per GB per month, or $3,000 per GB per year. File storage is cheaper at about $5 per GB per month, which is still $60 per GB per year.
One 2026 analysis put it at $15,000 a year for 5GB of Salesforce data storage against under $30 a year for the same 5GB on S3.
Those aren’t the same product, and Salesforce would rightly say you’re paying for a governed, permissioned, audited, workflow-attached record rather than for bytes. That’s a fair defense of the price. It stops being a defense of the architecture once agents show up.
The price was set for a world where data volume is bounded by how fast humans can type. A rep creates a few dozen records a day. A support agent logs a case. A field tech closes a job. At that volume nobody notices they’re paying four orders of magnitude over commodity storage, because the absolute number stays small.
Agents are not bounded that way.
#4. Agents produce an absurd amount of data, and much of it doesn’t have to be in a System of Record
Run a real agent workload and look at what it generates. Tool call traces. Intermediate reasoning. Embeddings. Retrieval logs. Scoring runs. Evaluation results. Failed attempts. Retries. Every one of those is data the agent creates, keeps, and reads back.
In our own Connect build, a single scoring pass writes 164,523 rows. That’s one job, on 14.5k profiles. We’re importing 250k profiles next, roughly 17x the scale. That data has to live somewhere cheap enough that I can re-run the whole thing when a scoring rule turns out to be wrong, which happens regularly.
Almost none of it is a business object. It’s the exhaust of the agent doing its job: enormous, mostly disposable, read far more often than written.
Salesforce’s own disclosures show the scale. 28.6 trillion tokens processed to date, up 152% quarter over quarter. 3.8 billion Agentic Work Units delivered, up 111% quarter over quarter. Data 360 ingesting 52 trillion records in a single quarter, up 136% year over year.
Now set that against a 7% growth rate in the applications business. Data volume moving through the platform grew 136%. System of Record revenue attached to it grew 7%.
#5. The API limit hurts before the storage bill does
Storage you can at least pay for. API access is often capped regardless.
Salesforce editions come with API call thresholds allocated per user per day. That made complete sense when API calls were a proxy for integrated human work. It breaks immediately with agents, because agents don’t have seats. The more agentic the workload, the faster the ceiling arrives, and the only lever is buying seats nobody sits in.
ServiceTitan’s April 2026 API terms are more direct. Calls must stay in a predefined certified scope, AI systems can’t independently select endpoints, and ServiceTitan reserves the right to permit AI use at all. Certified status is also contingent on paying revenue share, which sits in the same requirements list as the security terms.
So the constraint isn’t only cost. It’s permission. A customer willing to pay System of Record prices for agentic access may not be allowed to have it.
This is a policy choice rather than a physics problem. Systems of Record can change these terms whenever they want. Most of them are currently choosing to tighten.
#6. Salesforce’s answer is to stop storing the data
The number to watch in Salesforce’s quarter is Zero Copy.
Of the 52 trillion records Data 360 ingested last quarter, 35 trillion came through Zero Copy, up 277% year over year. Zero Copy means the data doesn’t move. Salesforce registers external tables from Snowflake, Databricks, BigQuery, or Redshift and queries them in place. It holds the metadata and the query path. The bytes stay in the customer’s lakehouse.
Two thirds of the data flowing into the largest System of Record in B2B never lands in it.
That’s the correct move, and Salesforce made it early. It also costs them the storage rent, the per-GB pricing, and physical possession of the data. What they buy with it is the right to stay the control plane, the place where data gets interpreted and acted on.
Snowflake is describing its ambitions in the same language from the opposite direction. Sridhar Ramaswamy called Snowflake the control plane for the Agentic Enterprise, and the company bought Natoma, an enterprise MCP platform, to govern what agents do across workflows.
Two companies converging on the same layer from opposite sides. One owns the record and is giving up the storage to get there. One owns the storage and is buying its way toward the record. That race is where the growth is, and it’s a different race than being the System of Record.
#7. Even as the System of Record, you still have to earn the agent sale
Owning the record doesn’t hand you the agent revenue. It gets your agent tried first, and that’s all it does.
Podium built $100M in AI agent ARR in under 24 months, a meaningful share of it selling to contractors already running ServiceTitan. Those customers had the incumbent’s agents available to them. They bought someone else’s. That’s what an open platform looks like in practice: the record holder is one bidder among several, and the customer picks on merit.
Which leaves two options, and both cost you something.
Stay open and you compete for the agent sale on the same terms as everyone else. You keep the retention, you keep the revenue share, and you lose a lot of agent deals to specialists who are better at one job than you are at forty.
We’re the open case, seen from the customer side. We run Salesforce headless. The humans at SaaStr barely log into it and the agents do the reads and writes through the API, which is why we now use Salesforce something like 100x more than we did when it was a browser tab three people opened. We love Agentforce, and it ran the win-back campaign that pulled 72% open rates on roughly 1,000 ghosted sponsor leads.
We also run Artisan for outbound, Monaco for the follow-up our human SDRs were too busy to chase, and Qualified for inbound, all on top of that same Salesforce. Best agent for the best job, on the System of Record. Salesforce didn’t lose by allowing it. It got 100x more usage out of us, it got our marketing automation migration, and it bought Qualified outright in April. What it never had was a monopoly on the agents running against its own record.
Close the platform and you win the agent sale by default, right up until the best agents live somewhere you can’t reach. At that point the record stops being the reason customers stay and becomes the reason they leave.
I’ve been on the customer end of the second one. Marketo was in essence our System of Record for marketing, and our agents hated it. We were one of its first 10 customers and stayed roughly 20 years, and the only thing that made leaving hard was two decades of engagement history. The record that held us that long turned out to be a file we had to remember to export on the way to Salesforce Marketing Cloud.
#8. What the record is still good for
Systems of Record don’t go away. Betting against them has been a losing trade for twenty years.
What they’re good for is narrow and durable:
- Authority. When two systems disagree about what a customer’s contract says, something has to be right. That’s a small table and it’s worth premium pricing.
- Permissions and audit. Regulated workflows need a record with a defensible chain of custody. Veeva’s whole business rests on this, and it’s why Veeva can grow 16% while migrating its customers to an entirely new CRM.
- Workflow and approvals. The place where a human says yes. Agents can prepare a decision, and in most categories they still can’t make it.
- Distribution. Being where people already work is worth a great deal, and it’s why the incumbent’s agent gets tried first.
That’s a good business with real pricing power. It’s a 10-16% growth business, and pretending otherwise is how you end up shipping AI features that don’t move the number.
#9. If you sell a System of Record
Your moat protects your base, not your growth rate. Logo retention explains the floor. Growth has to come from a unit that expands with usage, and for most Systems of Record that unit is still a seat.
Your storage pricing caps your own agentic ambitions. If your platform charges $3,000 per GB per year, your own agents can’t afford to write to it either. That’s why the incumbents’ agentic products keep getting architected on a separate data layer. You will end up building the cheap layer regardless, so decide it on purpose.
Perimeter defense buys time, but the meter is running. ServiceTitan is right that a partner shouldn’t use an integration to displace it. But delisting Podium doesn’t create a dollar of demand, it preserves an existing one. And every quarter the door stays shut, the odds go up that the agent your customer actually wants is on the other side of it. There’s a version of the next five years where every System of Record tightens API terms, holds its base, grows 10%, and watches the agentic spend route around all of them.
#10. If you build on top of one
Don’t put your agent’s working data inside someone else’s System of Record. Read from it, write the small authoritative results back to it, and keep everything else in Postgres or a lakehouse where a full re-run costs you nothing.
Read the API terms before you build anything. Not the docs, the terms. What’s your rate ceiling, is it allocated per seat, are AI-driven calls addressed explicitly, and what does the platform reserve the right to change. That’s a diligence item now, the same way security review is.
And know which side of the line your product sits on. If your value is holding the record, you’re in a retention business and should price and plan like it. If your value is activating data across systems, you’re in a consumption business, and your ceiling is set by how cheaply and quickly you can touch enormous amounts of data.
The record stays. The rent doesn’t.
Systems of Record aren’t going anywhere. The authoritative version of the customer, the contract, the job, and the invoice will keep living in them, and companies will keep paying well for that.
But the data agents create and activate runs 100x to 1,000x the volume humans generated, and the databases inside most Systems of Record are 100x to 10,000x too expensive to hold it. That math resolves the way Salesforce already resolved it with Zero Copy: keep the record, give up the storage, and go fight to be the layer that decides what happens next.
Retention keeps you in the game. The agent sale still has to be won on merit, on your own platform, against everyone else.
It was never the same thing as growth.
