Fool me twice, shame on me

The cloud taught enterprises what it costs to leave. Agents are about to teach the lesson again, this time with the business logic a company runs on.

By Gilad Ben-Nahum, President5 min read

Anyone who has replaced a core system knows the moment. The contract was signed years ago, the data is plainly yours, and only on the way out do you learn what leaving costs.

That lesson was expensive enough to reach the regulators. In July 2025, the UK’s competition authority found that egress fees and weak interoperability were limiting customer choice in cloud.1 The EU went further: from January 12, 2027, its Data Act bars cloud providers from charging customers to switch, egress included.2

That was the first time. It is worth noticing how the second one begins.

A reasonable decision, and a signal

In September, a leading CRM vendor told customers it will meter every call a registered AI agent makes to its platform, over MCP or a direct API, and bill it in consumption credits.34 No rate has been published, metering waits on 30 days’ notice, and existing integrations keep their current pricing.4

The logic is hard to fault. Gartner estimates that up to $234 billion of enterprise application spending is exposed by 2030 as agents do work across systems without anyone logging in.5 A business priced per person has to find something else to price once the person stops showing up.

What deserves attention is what the decision reveals. Gartner put it in one line in April: in the execution era, “control of enterprise context is economic power.”6 Read from the buyer’s seat, that sentence is a warning. Whoever holds your context sets the terms on which you use it.

What has to move this time

The first time, the hard thing to move was data. This time it is judgment.

An agent acting for you has to know what correct means in your company: who approves, which exceptions apply, when to stop and ask. That knowledge gets written down somewhere, and it tends to settle wherever the agent was built, in a platform’s configuration, a workflow designer, or code an implementation team left behind.

Take an illustrative piece of business logic, for discount approval. Anything above 15% goes to the regional VP, unless the deal is a renewal and margin holds above the floor; non-standard payment terms go to finance first. For years, logic like that lived in a policy page and in the heads of the few people who knew why it existed. Build an agent around it inside one platform, and the logic quietly becomes part of that platform. Nothing about the moment feels like a commitment. You notice only later, when you want a different agent, a cheaper model, or the price changes.

Gartner expects that by 2028, 70% of enterprises will abandon agentic AI built by vendors’ forward-deployed engineers, citing soaring costs and an inability to evolve those systems on their own.7 The failure it describes is one of ownership. The customer could not change what had been built for it.

Why the second time costs more

Moving data was painful, but a record arrives on the other side as recognizably the same record.

Business logic travels differently. Export a configuration and you hold text, with no evidence that another system will decide the same case the same way. Moving logic means rebuilding it, then earning back the confidence that it is right. Open protocols help agents reach systems; they carry no understanding of what your logic means.

The meter, meanwhile, runs on access. Analysts following the CRM change note that its cost will depend as much on how agents are built as on how many you run, and that teams using outside AI tools will pay their model provider and the platform at once.8 How many calls a task takes is settled by whoever built the agent, rarely by whoever owns the budget.

The fair objection

Every vendor charges, the argument goes, and wherever you keep your business logic becomes the next dependency.

There is truth in that. Paying for work is fair, and anything worth running costs money to run, including whatever holds your business logic. The question was never whether to pay. It is what you are paying for, and whether you can leave with what is yours.

The CRM vendor’s change also carries real progress. Agents get their own registered identity and narrower permissions instead of borrowing a person’s login, which is how it should work everywhere.34 It is simply worth seeing that the registration that makes an agent governable is the same one that makes it billable.3

So the case here is narrower than it may sound. It concerns where the definition of how your business runs is kept, and on whose terms.

A test for sovereignty

Sovereignty, in this sense, has nothing to do with where servers sit, and it does not mean building everything yourself. It means four things hold for the assets your business cannot run without.

Readable without a toll. Your teams and agents can read your own business logic and records without paying each time they look.

Portable in working form. Your business logic moves to another agent, model or platform in a form that runs, rather than as a description of what used to.

Changeable by the people who own them. A domain owner can revise the logic without a services ticket, and every agent picks up the change.

On your own record. You can show which version of your business logic an agent followed on a given decision, from records you keep rather than rent.

Pass that test and much else follows. Renewal conversations change, because a credible exit keeps pricing honest whether or not you ever use it. A new model becomes something to try on Monday rather than a project for next quarter. And the people who spent years learning why the logic exists remain the ones who decide what it says.

Questions to ask your team this week

  1. For our three most important agentic workflows, where does the business logic live today, and who could change it tomorrow?
  2. If the platform hosting one of them published a per-call price next month, could we forecast the bill, and could we move?
  3. Could we hand that logic to a different agent in a form it could run? Have we tried?
  4. For a decision an agent made last month, can we show which version of the logic it followed, from records we hold?
  5. Do our contracts cover exit and portability for configuration and logic, or only for raw data?

Fool me twice

The first time, it was our data, and it took regulators to make leaving affordable. Waiting for a Data Act that covers the logic our agents run on would be the second mistake. The decision is being made now, in the first few workflows, and mostly by default.

If you replaced every agent you run next quarter, what would you lose that you thought you owned?

Sources

  1. Competition and Markets Authority, “Cloud services market investigation: Summary of final decision,” July 31, 2025. assets.publishing.service.gov.uk
  2. Pinsent Masons, “Switching and porting rules under the EU Data Act,” Out-Law guide, on Article 29 of Regulation (EU) 2023/2854. www.pinsentmasons.com
  3. Vantage Point, “Salesforce Will Meter Agentic MCP and API Calls,” summarizing Salesforce Help article 005360285, “Understand AIforce Impact” (September 17, 2026). vantagepoint.io
  4. Salesforce Ben, “Salesforce Will Charge Flex Credits for Agentic MCP and API Calls,” September 24, 2026. www.salesforceben.com
  5. Gartner, “Gartner Says $234 Billion in Enterprise Application Software Spend Is at Risk from Agentic AI,” press release, July 1, 2026. www.gartner.com
  6. Gartner, “Gartner Expects Most Enterprises to Abandon Assistive AI for Outcome-Focused Workflow by 2028,” press release, April 2, 2026 (Alastair Woolcock, VP Analyst). www.gartner.com
  7. Gartner, “Gartner Predicts 70% of Enterprises Will Abandon Agentic AI Built by Vendor Forward-Deployed Engineering by 2028,” press release, September 29, 2026. www.gartner.com
  8. 2Data, “Salesforce Will Soon Charge When Your AI Agents Call It,” October 19, 2026. 2-data.com

All posts

Next step

Ready to build your Rulebook?

Book a demo and see one of your processes as a Rulebook.

Book a demo

Book a demo

See your process Factified.

A 30-minute session with our team on one of your real processes: where its rules live today, where they conflict, and what it looks like sealed. Leave your work email and we’ll set up a time.

No deck, no pitch. One of your processes, live.