Answers
How do I avoid getting locked into a vendor once they've built our AI systems?
Zachary King, Cofounder and CEO at Works · LinkedIn
Short answer
Make ownership concrete before you start. Code, configurations, documentation and credentials should all sit in your accounts, named in the contract. Lock-in rarely announces itself. It looks like systems running in the vendor's environment, on their tools, with credentials only they hold and documentation that never quite arrives.
Do this week
Add one clause before your next signature: on exit, all systems, access and documentation transfer, and the vendor demonstrates the handover.
Transcript
How do I avoid getting locked into a vendor once they've built our first AI systems?
Ownership is a list, not a vibe. Code, configurations, documentation, credentials in your account, named in the contract. Lock-in rarely announces itself. It looks more like systems running in the vendor's environment using their tools, credentials only they hold, and documentation that never quite arrives or is out of date. Then you want to leave, and discover that the thing that you paid for can't come with you.
So make ownership concrete before you start. Everything built lives in accounts that you control. Every credential is yours. Documentation is a deliverable, not a courtesy.
We work entirely inside our clients' own architecture. Their accounts, their systems, their credentials, everything inside their systems from day one. There's no handover problem at the end, because it never lived on our side. A build you can't take with you isn't an asset. It's a subscription with a few extra steps.
Add one clause before your next signature: on exit, all systems, access and documentation transfer, and the vendor demonstrates the handover. Anyone who resists that clause has just told you the answer.
Want this built inside your business?
Tell us where the work piles up. We will show you what it takes to ship it.
Let's talk →