In short: The layer that encodes how a business decides is the deepest lock-in in enterprise software. It is also where the strongest growth is. The enterprise should own that record, and the contract should say so before the first workflow moves in.
Key points
- What is at stake is not data or models but the accumulated record of how the organisation decides.
- Test any platform on export in an open format, independence from its model, and record-level retention control.
- Negotiate a tested export schema, fixed-rate exit assistance, ownership of derived records and no training on your records.
- Assign the judgment record to the function whose decisions it records, with risk and compliance oversight.
- For vendors, portability can earn more durable trust than lock-in.
The one software vendor whose semantic-layer pitch is backed by hypergrowth grew US commercial revenue 149% year on year in its latest reported quarter, to $764 million. Its core product models a business as objects, links and actions, and lets agents operate over that model. The rest of the market is now copying the idea by name; one major platform explicitly describes its new layer as ontologies.
Its critics make the mirror argument. Once workflows, permissions and decision logic live inside that layer, switching becomes extremely costly. At least two European governments have declined the vendor on sovereignty grounds.
Both are right, and the tension applies to every enterprise brain, not just one vendor.
What is actually at stake
It is not the data. Data can usually be exported, and much of it is licensed from others anyway. It is not the model, which is rented and replaceable. It is the accumulated record of how the organisation decides: the definitions, the exceptions, the precedents, the conflicts resolved, the outcomes linked to decisions.
That record is built slowly, through use, by the organisation's own people. If it lives only inside a vendor's proprietary structure, the organisation's institutional judgment has become a line item the vendor can reprice at renewal.
Three tests for any platform
- Export. Can you export every decision record with its sources, history, supersession links and outcomes, in an open, documented format, without professional services?
- Model independence. Does the record survive intact if the vendor's model, memory product or agent framework is replaced?
- Control. Are retention and deletion controlled by you, record by record, with a log?
If the answer to any is no, you are building your judgment into someone else's asset.
Put it in the contract
The time to negotiate this is before the first workflow moves, not at the first renewal. Useful clauses: a documented export schema, delivered and tested annually; exit assistance at a fixed rate; explicit ownership of derived records, including summaries and links the platform generates; and no use of your decision records to train models offered to others.
Internal ownership matters too
The same question applies inside the firm. If the judgment record belongs to IT, it will be managed as infrastructure. If it belongs to the function whose decisions it records, with risk and compliance overseeing it, it will be managed as an asset. The second works better.
A note for vendors
Portability is not the enemy of retention. A vendor that makes the record easy to leave with, and keeps clients because the product around it is better, earns a kind of trust that lock-in never does. In a market where every competitor offers the same connections to the same data, that trust may be the more durable advantage.
In practice
- Run the three tests on every platform that holds decision records today.
- Add export, exit-assistance and derived-records clauses at the next negotiation.
- Test an export once a year and check that it can be read without the vendor.
- Assign ownership of the record to the accountable function, with risk oversight.
What would prove this wrong. Organisations switching platforms without material loss of decision history or capability, even where no export rights were negotiated. Then the lock-in risk is overstated.
Common questions
How do I avoid vendor lock-in with an enterprise AI or ontology platform?
Before the first workflow moves in, check you can export every decision record in an open format, that the record survives a model change, and that you control retention. Put export, exit-assistance and derived-records clauses in the contract.
What contract clauses protect a company's decision data?
A documented export schema delivered and tested annually, exit assistance at a fixed rate, explicit ownership of derived records including generated summaries and links, and no use of your records to train models offered to others.
Who inside a company should own the decision record?
The function whose decisions it records, with risk and compliance overseeing it. If IT owns it, it gets managed as infrastructure rather than as an asset.