How to avoid AI consulting lock-in

Almost nobody gets locked in by signing something obviously bad. It happens through accumulation: a system running on a vendor's infrastructure, keys nobody on your side holds, logic that exists only in the head of the person who wrote it, and eventually leaving costs more than staying.

By then the negotiation is over and you did not attend it. Everything below is cheap to require at the start and expensive to retrofit.

Own the accounts

The single most effective protection, and the one most often skipped for convenience.

Every third-party service the solution depends on should be registered to your company, paid on your card, with an administrator login your side holds. Model providers, automation platforms, messaging services, hosting, databases.

The common alternative is that the vendor runs everything under their own accounts and bills you for it. Convenient at setup and it means you cannot leave, because the thing does not exist anywhere you can reach. If a vendor resists this, ask why, and treat a vague answer as the answer.

Insist it runs somewhere you control

Related and distinct. Accounts are ownership; hosting is possession.

If the automation runs on infrastructure the vendor owns, your operations depend on their continued goodwill and continued existence. That is a real risk with small firms, ours included. Ask directly: if we parted ways on bad terms tomorrow, what would still be running on Monday?

The good answer is everything, because it is in your environment and they merely have access. Access can be revoked. Possession cannot.

Get the prompts and the logic in writing

The intellectual property question in AI work is not really about code, it is about configuration. The prompts, the rules, the escalation conditions, the decision thresholds, the list of things the system must never do. That is the actual product, and it is often nowhere except inside a platform the vendor administers.

Require it exported and delivered in readable form, and require it kept current rather than delivered once at handover. If somebody tells you their prompts are proprietary, understand what that means: they are proposing that the thing running your operation is not yours.

Write the exit into the agreement while everyone is friendly

Name it before you start. What you receive on termination, in what format, within how many days, and at what cost. The answer to the last one should be nothing.

Also settle who owns what is produced. The default in a lot of consulting agreements is that the supplier keeps the tooling and licenses it to you, which may be acceptable if you know that is the deal. It usually is not what the client thinks they agreed to.

And put a notice period on it that you can actually use. Twelve-month terms with a ninety-day exit window are a lock-in mechanism wearing a contract's clothes. What else belongs in the contract.

Require documentation aimed at your replacement

Not a handover call. Something written, sufficient for a competent person who has never met the vendor to understand what runs, when, on what trigger, and what to do when it breaks.

The honest test: could you hand this folder to a new hire and have them maintain it? If the answer depends on a conversation with the original builder, you have documentation in name only. This is also the thing most likely to be promised and least likely to be delivered, so make a payment milestone depend on it.

Keep diagnosis and build as separate decisions

The structural version of all of the above.

If the roadmap only makes sense when the firm that wrote it builds it, the advice and the sales pitch were the same document. What you want is a diagnosis specific enough that any competent builder could execute it, which means you can shop the build, which means the recommendation had to stand on its own merits.

Paying separately for the two also gives you a clean stopping point after the cheaper half, when you know a lot more about whether you want to work with these people.

Where we stand, since we are one of them

We build the agents we recommend, so we have the same incentive every other firm in this category has, and you should assume it.

What we do about it: the roadmap is written to be executed by anyone and we say so before you pay for it. Accounts are registered to you where the work touches third-party services. You get the configuration in readable form. Building it with us is an option and never an obligation, which is on the consulting page in those words because it is the term that makes the advice trustworthy.

The uncomfortable part of writing this is that a client who follows the list is easier to lose. That is the point of the list.

If you want the wider set of warning signs, the red flags is the companion piece.