← Back to Insights
You have a multi-cloud strategy. You are still locked in.
"89% of organizations say they have a multi-cloud strategy. 42% are considering moving workloads back on-premises to escape vendor dependency. The strategy and the reality are not the same thing. Lock-in is not a contract problem. It is an architecture problem."
89%
Of organizations have adopted a multi-cloud strategy. Most remain dependent on a single vendor's roadmap.
(BuzzClan, 2026)
(BuzzClan, 2026)
42%
Are considering moving workloads back on-premises to escape vendor dependencies.
(BuzzClan, 2026)
(BuzzClan, 2026)
THE DECISION STAKES
The contract is annual. The dependency is permanent.
"The business case for cloud was speed and agility. The hidden cost was that speed created dependency, and dependency created price leverage for the vendor." — BuzzClan, Vendor Lock-in Guide, February 2026
The exit cost of a platform you cannot leave is the real price of that platform. Most organizations have never calculated it.
Lock-in audit is not about leaving your current vendors. It is about knowing what it would cost to leave. That number is your negotiating position at every renewal.
THE DECISION TOOL
Four moves. One decision you can defend.
01
MAP
Inventory every vendor-specific dependency by platform: proprietary APIs, custom integrations, certified staff, data stored in vendor-controlled formats, and workflows that cannot run elsewhere. Most enterprises discover 3 to 4 platforms where exit would require 12 months and exceed 10M euros.
Without the map, you negotiate renewals blind. The vendor knows your exit cost. You should too.
02
SCORE
Assign an exit score to each platform: cost of migration, time, operational risk, and strategic importance. Red = trapped, high cost, no realistic alternative. Amber = high switching cost, alternatives exist. Green = portable, alternatives contractually available.
The score reveals which dependencies are strategic and which are accidents of history. Resolving accidental lock-in is the fastest path to improved negotiating leverage.
03
NEGOTIATE
Use the exit score as your negotiating tool at every renewal. A red-scored platform requires a data portability clause, a price cap, and a contractual exit pathway before signing the next multi-year agreement. Silence on exit terms is acceptance of the vendor's terms.
The organization that arrives at renewal with a calculated exit cost negotiates from a different position. The vendor who knows you cannot leave has no incentive to give you a better deal.
04
ARCHITECT
Build portability into every new architecture decision: open standards where available, abstraction layers between vendor APIs and internal systems, and data formats that do not require the vendor's tools to read. Portability is not free. It is an investment that pays at every contract renewal.
Architecture decisions made in 2026 determine your vendor leverage in 2029. Every proprietary integration you avoid now is a negotiating chip you keep.
37signals / Basecamp
SaaS product company. HEY and Basecamp. Exited AWS for owned infrastructure. 2022-2025.
$7M
Projected savings over five years from exiting cloud lock-in and returning to owned infrastructure. 37signals made the exit decision after a deliberate lock-in audit revealed cloud costs were structurally inflated by vendor dependency.
(37signals public statements, 2023-2025)
37signals ran the numbers and found their AWS bill was pricing in convenience they no longer needed and flexibility they were not using. The exit took 18 months. The result: infrastructure they own and understand, at a cost structure that compounds over time in their favor rather than the vendor's. The lesson is not that cloud is wrong. It is that a deliberate architecture review, done once, revealed dependencies that had been treated as fixed costs but were in fact a negotiating failure. The same audit logic applies at 10 times the scale, with proportionally larger savings.
The decision to exit was not technical. It was financial: calculate the exit cost, compare it to the compounding cost of staying, then decide. Most enterprises skip the calculation
Download the full case
PDF · 5 slides · Free access · Downloaded 184 times
Key questions
How many of your current platform dependencies would require more than 18 months and EUR 10M+ to exit, and does your board know?
When a vendor announces a 10% price increase on a platform you scored Red, what is the governance mechanism that triggers a migration project rather than absorption?
How do you build portability into architecture decisions made by teams who are incentivized on delivery speed rather than long-term sovereignty?
Pre-decision checklist
MAP — completed
SCORE — completed
NEGOTIATE — completed
ARCHITECT — completed
By Fabrice Macarty
This case resonates?
Map every vendor-specific dependency you cannot exit in under 12 months. Score each platform: Red, Amber, or Green. Negotiate a portability clause before the next renewal. Then build the next system for portability, not convenience.
Start the conversation