Why it shows up in your week
Vendor lock-in starts when the cost of leaving controls the decision more than the value of staying.
In plain language
Lock-in can come from contracts, data formats, proprietary features, custom code, skills only one partner has, or workflows that were never documented outside the vendor relationship.
A good vendor relationship still leaves you with usable exports, clear ownership, API access, renewal dates, and a credible exit path.
Where it bites
Vendor lock-in bites when renewal pressure arrives, pricing jumps, delivery slows, or an investor asks what it would cost to migrate. The hard part is rarely the license. It is the hidden migration work around data, integrations, permissions, and knowledge transfer.
What to check
- Can you export the data in a usable format without vendor help?
- What would stop a second team from maintaining or replacing the system?
- Which contract clause, API limit, or proprietary feature would make migration slow?
Common questions
What is vendor lock-in?
Vendor lock-in is a dependency on a provider, platform, or tool that makes switching away expensive, slow, or risky.
Is vendor lock-in always bad?
No. Some lock-in is an acceptable trade-off when the platform creates enough value. It becomes a problem when the business cannot leave even after the value drops.
What should you check first for vendor lock-in?
Start with data export, API access, contract renewal terms, proprietary features, handover documentation, and the cost of replacing the most important workflow.