Lock-in appears in five forms, and only one of them responds to negotiation. Buyers therefore spend their leverage on the exit clause and leave the other four untouched. This article names the five forms, gives seven tests to apply before you sign, explains why the semantic form catches most organisations, and describes what an exit looks like when the design guarantees it.
Connect with us about your exit terms · · Replies within 24 hours
Five, and they operate independently of each other.
| Form | What holds you | Does negotiation help? |
|---|---|---|
| Contractual | Notice periods, exit fees, minimum terms. | Yes. |
| Technical | A proprietary format or interface. | Partly. |
| Semantic | The meaning of your data lives in the supplier's code. | No. |
| Operational | Your processes are shaped around the product. | No. |
| Skills | Your team knows only this product. | No. |
A procurement exercise negotiates the first row well. HM Government's Technology Code of Practice and its Open Standards Principles push at the second.
Rows three, four and five receive almost no attention, and they hold you the longest.
Semantic lock-in means the meaning of your data lives in software you do not own.
Your supplier's system holds a field called status, with values 1 to 6. The rule that says 3 means an active tenancy with unpaid rent sits in the supplier's code. You export the data, and you receive the numbers.
You now hold your records and not your rules. The export is complete and the meaning did not come with it.
Apply these before signature, while you still hold leverage. Each one has a factual answer, and a supplier can answer each one in writing.
Test five deserves emphasis. The cloud guide for the public sector treats exit planning as part of a decision to buy, rather than a task for later.
Your processes shape themselves around the product you use. A team learns the screens, builds its week around the reports, and writes its procedures against the fields the product offers.
Three years later, the exit cost includes retraining, rewritten procedures and a period of reduced service. None of that appears in a contract, and all of it appears in a business case.
Operational lock-in grows with time in use, so a five-year term costs more than the licence fee difference suggests.
A supplier promise and a design guarantee differ in one way. A promise depends on the supplier existing and choosing to honour it. A guarantee holds when neither is true.
Three things make an exit a design property.
Sense Future publishes a self-host conformance package for engage.re, at version 2.0.0. It describes the interfaces and the behaviour a conforming implementation must show.
We build your system on engage.re, and each of the five forms of lock-in has a specific answer.
| Form | What your system gives you |
|---|---|
| Semantic | Your meaning is held as data in a shared dictionary, so an export carries the definitions with the records. |
| Technical | Six interfaces over JSON, from any language, described in a published conformance package. |
| Contractual | You may host it yourself. A published specification lets a third party build a conforming replacement. |
| Operational | The system fits your process, because we build it to your process rather than the reverse. |
| Skills | Your team learns your own vocabulary and standard interfaces, not a supplier's screens. |
You hold your own encryption keys. Sense Future built engage.re, and it has run in production since December 2025.
A council signs a ten-year contract for a housing management system. The exit clause is strong, and the meaning of every field lives in the supplier's code. Year eight arrives, the council runs a re-procurement, and the migration takes three years because nobody can state what the data means. The contract was never the constraint.
A care home group signs a three-year contract for a records system. The group holds no leverage on price, and it can still apply all seven tests, because each one asks for a fact rather than a concession.
The care home software and estate agency software pages set out the sector detail. Our guides to off-the-shelf against bespoke for care homes and software subscription price rises cover what lock-in costs once it exists.
Five. Contractual lock-in comes from notice periods and exit fees. Technical lock-in comes from proprietary formats. Semantic lock-in means the meaning of your data lives in the supplier's code. Operational lock-in means your processes are shaped around the product. Skills lock-in means your team knows only that product. Negotiation helps with the first, and barely touches the others.
The meaning of your data lives in software you do not own. Your supplier's system holds a status field with values 1 to 6, and the rule that says 3 means an active tenancy with unpaid rent sits in the supplier's code. You export the data and receive the numbers, so you hold your records and not your rules.
Only against technical lock-in. A file of status codes is structured, commonly used and machine-readable, so it satisfies a portability requirement. A person still has to rediscover what each code means, and that work is the real cost of leaving.
Seven questions. Ask for a real sample export with field definitions. Ask where the meaning of the data is written down. Ask what the interface is. Ask who holds the encryption keys. Ask whether you can run the system yourself. Ask for the exit runbook. Ask what happens to your audit trail.
Three properties that hold without the supplier's cooperation. Your meaning is held as data, so an export carries the definitions. A published specification lets a third party build a conforming replacement. You hold your own encryption keys, so your access does not depend on anybody else.
We build your system on engage.re. Your meaning is data in a shared dictionary, six interfaces over JSON are described in a published conformance package at version 2.0.0, you may host the platform yourself, and you hold your own encryption keys.
Connect with us about your exit terms · · Replies within 24 hours