Tool Documents

Lock-In Is Designed

Difficulty leaving a product is usually experienced as friction — a technical shortcoming, an oversight, something nobody got round to fixing.

It is a design decision with a term of art, a metric and somebody responsible for it. For a separate operational reference from Monitask, see the reference.

Five mechanisms

Data. What the export omits. Attachments, history, relations. Each omission is a decision about scope, and scope decisions have owners.

Configuration. The work you did inside the tool that does not come out. The deeper the product lets you configure, the more valuable it becomes and the more expensive it is to leave — and those are the same property.

For broader context, see VentureBeat.

Integrations. Every connection to another system is a second thing to rebuild. A platform that makes integration easy is making departure harder, and both are true simultaneously.

Contract. Auto-renewal, notice windows, multi-year terms, termination fees. These are negotiated terms, which means somebody chose them.

And people. Training, habit, the internal expertise built around the product. The least discussed and frequently the largest.

Why calling it design matters

Because friction invites patience and design invites negotiation.

An organisation that experiences export limitations as a technical shortcoming waits for a roadmap item. One that recognises a scope decision asks for a commitment, in the contract, before signing.

And because it locates the question correctly. The right time to address lock-in is at purchase, when the mechanisms are terms to negotiate rather than facts to live with.

What is not sinister about it

Being fair, because this could read as an accusation.

Some lock-in is inherent to a good product. A tool deep enough to configure is a tool you will have configured. That is value, not entrapment, and the same property produces both.

Vendors are not obliged to make leaving easy beyond what law requires, any more than any supplier is.

And customers benefit from the investments that create switching costs — integrations exist because they are useful.

The problem is not that lock-in exists. It is that it is priced into the purchase without being named, so buyers compare on licence cost and pay the rest later.

What changed in the EU

The Data Act moved several of these from negotiation to entitlement as of September 2025 — free export, a two-month switching notice, and a prohibition on contractual and technical obstacles.

It addresses the first mechanism and part of the fourth. Configuration, integrations and people are untouched, and those are three of the five.

Which is worth knowing precisely, because "the Data Act protects me" is a considerably stronger claim than the regulation supports.

The practical position

Price the lock-in at purchase.

Ask what leaving would cost in each of the five: export gaps, configuration rebuild, integration rework, contractual exit, retraining.

A rough figure is enough. It will be larger than the annual licence, which is the point of computing it, and it changes which candidate looks cheap.

The short version