# The Data Hostage Crisis

Author: Pramod Prasanth
Published: 2026-02-20
Canonical: https://pramod.ch/essays/systems-of-record-tightening-grip
Description: The vendor that stores your transactions increasingly controls the terms under which you can reason about them.

---

*Part of the [Judgement Layer](https://pramod.ch/essays/context-graphs-are-judgement-graphs) series on decision infrastructure.*

---

The modern data stack debate (Snowflake vs. Databricks, lakehouse vs. warehouse) describes maybe 30,000 organisations globally.

SAP alone has 200,000+ customers. Add Oracle, Microsoft Dynamics, Infor, and you're looking at the vast majority of enterprises above €100M revenue. They don't have lakehouse architectures. They have ERP systems, Excel, and meetings.

For these companies, the question is simpler than any architecture debate: can we get our own data out?

## The Tightening Grip

RISE with SAP is marketed as cloud transformation. But it has a second effect: SAP manages the environment. The database sits inside SAP's cloud perimeter. The data extraction pipelines that enterprises built over the past decade need to be renegotiated, not just migrated.

This isn't adversarial. It's rational business strategy. SAP is doing what any platform does when it reaches sufficient scale: moving from selling software to selling the operating environment. Oracle is doing the same. So is Salesforce.

But for anyone trying to build an independent reasoning layer, the implications are significant. The vendor that stores your records now controls what you can know about your own business.

Every major vendor is reinforcing this position with AI features. SAP has Joule. Oracle has AI agents. Salesforce has Agentforce. Each is useful. Each is also a strategic move to ensure that AI-driven insights flow through the system of record, not around it.

The result: the vendor that stores your transactions increasingly controls the terms under which you can reason about them.

## Independence

Independence means reasoning freely across data from any source, in any combination, without asking permission from any single vendor. SAP data, Salesforce pipeline data, market feeds, internal spreadsheets: all become inputs to reasoning, none becomes the gatekeeper of it.

## The Portability Question Nobody Is Asking

The data portability debate in enterprise software is well-established. Regulators and procurement teams understand that organisations should be able to extract their transactional data. GDPR pushed this further for personal data. The conversation exists, even if execution remains difficult.

But there's a second portability question that almost nobody is raising: who owns the built-up judgement?

When an organisation has kept a decision record for two years, the most valuable asset isn't the data it drew on. It's the reasoning it holds.

That record is organisational cognition in structured form. It took hundreds of decisions to build. It cannot be reconstructed from the transactional data alone, because it captures the reasoning between the data points, not the data points themselves.

If that record is built inside the system of record vendor's perimeter, that cognition belongs to the vendor's platform. Switching ERPs has always been painful because of data migration. Switching away from a vendor that holds your built-up judgement is worse: you lose not just your data but your organisation's learned reasoning.

This is why architectural independence matters for the reasoning even more than it matters for the data. Data can be exported and reimported. Judgement, if it's entangled with a vendor's proprietary AI stack, cannot.

## The Harder Question

The industry conversation about AI in enterprise is focused on features: which copilot, which agent, which assistant. The structural question matters more.

Who gets to build the reasoning layer on top of enterprise data, without being beholden to the platform underneath?

The enterprises that answer this question with structural clarity (vendor-independent reasoning, portable judgement) will keep ownership of their decision-making capability. The ones that let their reasoning layer get absorbed into their system of record will find, in three years, that they've outsourced their organisational thinking along with their data management.

The data hostage crisis isn't about data anymore. It's about who owns the organisation's capacity to reason.
