In our experience, vendor lock-in rarely announces itself. You pick a capable platform, the project succeeds, and three years later you realise your data, your processes, and your institutional knowledge all live inside one supplier’s world. The renewal quote reflects exactly how trapped you are.
For government and public-sector buyers this is a strategic risk, not just a commercial one. A locked-in critical system is a single point of failure for a national service. It quietly erodes the negotiating leverage you’ll need at every renewal for the next decade.
Lock-in comes in four flavours, and you should price all of them.
- Data lock-in. Your information sits in proprietary formats that are hard to export.
- Skills lock-in. Only the vendor’s people understand the system.
- Process lock-in. Your operations have reshaped themselves around the tool.
- Contractual lock-in. Pricing, exit terms, and IP clauses that punish you for leaving.
Picture all four feeding into one question, the only question that really matters here.
flowchart TD
A(["Data lock-in: proprietary formats you can't export"]) --> Q{"What would it cost to leave in three years?"}
B(["Skills lock-in: only the vendor's people get it"]) --> Q
C(["Process lock-in: operations reshaped around the tool"]) --> Q
D(["Contractual lock-in: exit terms that punish leaving"]) --> Q
Q --> E(["That number is your real leverage"])
Design for exit before you sign. The single most useful question in any procurement: “If we wanted to leave in three years, what would it cost and how long would it take?” The answer tells you more about your future leverage than any feature list.
Practical defences:
- Insist on data portability. Open, documented export formats, and the right to your own data at any time.
- Favour open standards and interoperability so components can be replaced one at a time instead of all at once.
- Keep integration layers vendor-neutral so swapping one system doesn’t cascade through ten others.
- Nail down IP and source-code terms up front, especially for anything custom-built.
- Retain internal knowledge so you’re never wholly dependent on one supplier’s staff.
None of this means avoiding capable commercial platforms. It means going in with your eyes open, pricing the exit, and keeping the architecture modular enough that a single bad supplier can’t hold an entire program hostage.
Worried a critical system is becoming a trap? SDCG reviews contracts and architectures for lock-in risk and designs exit strategies that keep your leverage intact. Independently, with no stake in the incumbent. Book a free 30-minute review.