Skip to main content
Published on

Vendor lock-in: how to avoid becoming dependent on an IT supplier

Understanding vendor lock-in, spotting the warning signs and putting concrete strategies in place to preserve your technological independence.

Vendor lock-in (the situation where you become captive to a supplier), or supplier dependence, is the position a company ends up in when it is trapped with a supplier or a technology and the cost of leaving has become prohibitive. It is a risk that many smaller companies discover too late.

The warning signs

A few clues that should put a business leader on alert:

  • You hold no technical documentation: network diagrams, configurations, administrator passwords.
  • The data cannot be exported in a standard format (CSV, SQL (database language), an open API).
  • The contract has no reversibility clause: what happens when it ends?
  • A single supplier controls the whole IT estate: infrastructure, applications, support. If they disappear, everything stops.
  • Development work is done on a proprietary technology with no equivalent on the market.

Strategies to protect yourself

Favour open standards

Choose standard data formats and protocols (SQL, REST, OpenID Connect, SMTP) rather than proprietary solutions. An ERP that exports to CSV will always be easier to replace than software whose data is locked away in an opaque format.

Insist on contractual reversibility

Every contract with an IT supplier should include:

  • Ownership of the data and of any custom code
  • The arrangements for exporting the data when the contract ends
  • A notice period and support through the transition
  • Access to administrator passwords and accounts

Diversify your suppliers

Do not hand hosting, development, support and telephony to the same supplier. Diversification carries a coordination cost, but it dramatically reduces the risk of dependence.

Keep control of your critical assets

A few simple rules:

  • Domain names must be registered in the company’s name, not the supplier’s.
  • Cloud accounts (AWS, Google Cloud, etc.) must belong to the company.
  • Administrator access must be known to the management team, not just to the supplier.
  • Technical documentation must be kept up to date and accessible in-house.

Assess the cost of leaving before you sign

Before committing to a new tool or supplier, ask the question: “How much would replacing this cost in 3 years?”. If the answer is “nobody knows”, that is a warning sign.

In summary

Vendor lock-in is not inevitable. You prevent it from the selection stage onwards, through clear contractual clauses, open technology choices and a governance model that keeps the management team in charge of its own IT estate.

Go further