How to Avoid Vendor Lock-In When Commissioning Software

We've inherited projects from businesses that couldn't leave their previous vendor because the code, data, or hosting was structured to make that painful. It's avoidable with a few upfront questions.

Own your source code

Before starting a project, confirm in writing that you own the source code outright, with access to the actual repository — not just the right to use a hosted service the vendor controls.

Avoid proprietary platforms where possible

Software built on widely-used, standard technology (like this site's Next.js/PostgreSQL stack) can be picked up by any competent team later. Software built on a vendor's proprietary in-house framework often can't.

Data portability

Confirm you can export your data in a usable, standard format at any time — not locked into a format only the vendor's own tools can read.

Documentation isn't optional

Ask for basic technical documentation as a deliverable, not an afterthought — undocumented systems are a lock-in risk even when the code is technically yours.

About to commission a custom system? Ask us what questions to put to any vendor, including us, before signing.