Teams do not get locked in because vendors trap them; they get locked in because they build their workflows directly against one vendor's proprietary features, formats, and platform services. Every convenience feature you adopt raw (vendor-specific memory, hosted agents, proprietary file stores) is a strand of rope. Individually trivial, collectively binding.
The frontier has changed leaders repeatedly in three years, on price as much as capability. The expected value of portability is therefore not hypothetical; it is the ability to capture each leap and each price war within weeks instead of quarters.
Own the harness: tool definitions, permissions, guardrails, recovery logic, written against your own interface with the model as a swappable component behind it.
Own the prompts and context: versioned in your repository like code, not living inside a vendor console.
Own the evaluation sets: your golden cases are precisely what makes switching cheap, because a candidate model earns its place in an afternoon of tests instead of a quarter of anxiety.
Own the data pipelines: retrieval, embeddings storage, and logs in systems you control.
Rent the intelligence: the model API itself, where switching costs, kept deliberately low, are your negotiating leverage at every renewal.
Once a quarter, price the question honestly: if our primary model vendor doubled prices tomorrow, how many weeks and dollars to move? If the answer exceeds one quarter of engineering, identify which owned layer has leaked into vendor coupling (harness, prompts, evals, data) and pull it back. The number is your lock-in, measured.
A practical multi-model posture is boring: one primary model family for most work, one secondary kept warm through your evaluation suite, cheap fast models for high-volume low-stakes tasks, and routing rules that assign work by cost and stakes. The goal is not diversity for its own sake; it is a live, tested alternative, which converts every vendor negotiation and every outage from a crisis into a routing change.
Run the secondary against your golden sets monthly. An alternative you have never tested is a slide, not a strategy.
Structure vendor relationships for reversibility: enterprise terms with training exclusion and data deletion, contract lengths matched to the pace of the frontier (annual, not five-year), and commercial commitments tied to per-unit prices rather than platform exclusivity. Take partner programs and credits where they are free; decline them where they require architectural entanglement. The multi-threaded version of partnership is holding real relationships with two or three labs while owning every layer that would make leaving any one of them expensive.
Own the harness, prompts, evaluation sets, and data pipelines; treat the model as a swappable component behind your own interface; and keep a tested secondary model warm. Lock-in is measured by your answer to the swap test, not by your contract.
Use one primary family for most work, a secondary validated monthly against your golden sets, and cheap models for high-volume low-stakes tasks. Multi-model means a live alternative and routing rules, not a collection.
Match contract length to the frontier's pace: annual terms with training exclusion, deletion rights, and per-unit pricing. Discounts that require architectural exclusivity usually cost more than they save within eighteen months.
Bring one AI question from this article. We will tell you what we would do, whether or not you hire us.
Book a 15-Min Chat →