Iorier All articles
Artificial Intelligence

When Your Data Checks Into a Hotel That Never Lets You Leave

Iorier
When Your Data Checks Into a Hotel That Never Lets You Leave

Photo: MarkBuckawicki, CC0, via Wikimedia Commons

There is a particular flavor of dread familiar to any chief technology officer who has tried to migrate off a long-tenured software platform: the discovery that the data you assumed you owned is, for practical purposes, trapped. Export tools are missing or crippled. The API that could automate an extraction is gated behind an enterprise tier priced as though it were a different product. Proprietary formats have quietly absorbed years of business logic that no other system can parse.

Vendor lock-in is often described as an unfortunate side effect of software design. More often, it is a deliberate architectural decision — one of the most consequential and least examined in modern business technology.

Lock-In as Strategy, Not Accident

The economics are simple. Acquiring a new customer is expensive; keeping an existing one through genuine product excellence is expensive too. Keeping one through friction is nearly free. A vendor who makes departure painful can raise prices year over year, deprioritize support, and degrade the product, secure in the knowledge that the cost of switching exceeds the cost of staying.

The tactics are well documented across the industry. Proprietary file formats that no competitor can read. Export functions capped at a few thousand records per day. API access bundled into premium pricing tiers. Contract terms with punitive early-termination clauses. Some platforms go further, embedding workflow logic — custom fields, automation rules, calculated metrics — in structures that exist nowhere in the export at all. You can leave with your data. You cannot leave with your configuration.

The rise of AI has raised the stakes considerably. Companies that fed years of documents, conversations, and customer records into an AI platform have effectively trained models on their institutional knowledge. Whether and how that intelligence can be extracted — the fine-tuned model, the embeddings, the learned behaviors — is rarely addressed in standard contracts. For many US enterprises, their most valuable proprietary asset is now sitting inside someone else's infrastructure.

What Captivity Actually Costs

The visible costs are the ones on the invoice: annual price increases that outpace inflation, premium tiers purchased solely to unlock export or API capabilities, and professional services fees for integrations that exist mainly to deepen dependence.

The invisible costs are larger. Locked-in customers under-negotiate, because they know renewal is a foregone conclusion. They forgo better tools because migration is unthinkable. Their engineers spend weeks building workarounds for limitations a portable system would not have. And their data — the raw material for AI-driven decision-making — appreciates in value everywhere except in their own hands.

A useful thought experiment: if your vendor raised prices forty percent tomorrow and froze all feature development, how many of your critical workflows would survive a migration inside twelve months? For a surprising number of American companies, the honest answer is none.

A Pre-Purchase Checklist for Evaluating Exit Risk

Before signing any significant software or AI agreement, procurement teams should be able to answer the following:

Vendors with confident answers to these questions are signaling that they expect to retain customers on merit. Vendors who deflect are telling you, in the most reliable way possible, how they plan to behave later.

The Leverage Is in the Question

Lock-in risk is cheapest to evaluate before the signature and most expensive to discover after. The questions above cost nothing to ask and take an afternoon to answer. Companies that ask them consistently will find the market slowly reorganizing around them, as vendors who compete on portability and honest data ownership begin to win the deals that smooth-talking incumbents used to take for granted.

Your data checked into the hotel. The only question that matters is whether you read the checkout policy before you unpacked.

All Articles

Related Articles

Small Pipes, Big Business: The Quiet Rise of Companies Built to Be Plugged In

Small Pipes, Big Business: The Quiet Rise of Companies Built to Be Plugged In

Shipping in Silence: The Retention Channel Nobody Uses

Shipping in Silence: The Retention Channel Nobody Uses

The Zombie Subscription Audit: Reclaiming Budget From Software Your Team Forgot

The Zombie Subscription Audit: Reclaiming Budget From Software Your Team Forgot