---
title: "Your SaaS stack is a rental agreement"
url: "https://barbairians.com/blog/your-saas-stack-is-a-rental-agreement"
description: "Nobody budgets for the exit, which is why the exit never happens. How to price lock-in before the renewal instead of discovering it during one."
---

# Your SaaS stack is a rental agreement

July 16, 2026·3 min read·BarbAIrianS

Every SaaS contract has a price you negotiate and a price you do not: what it would take to leave. The first is on the invoice and gets scrutinised annually. The second is invisible, grows every month you stay, and is the actual reason renewals get signed. If you have never calculated it, your vendor has.

## Switching cost was sold to you as a feature

Read the pitch again. “Deep integration with your existing tools.” “Your data enriched across the platform.” “Workflows tailored to how you work.”

Every one of those is a description of increased switching cost, phrased as a benefit. And they are benefits — right up to the moment your interests and the vendor’s diverge, which happens on a schedule: the price increase, the feature you depend on moving to a higher tier, the acquisition, the roadmap that goes somewhere you were not going.

At that point the depth of integration is the reason you cannot respond. A moat was dug. It faces you.

## How to actually price it

The number is not a licence fee. It is weeks of work, and it has five components:

1.  **Export.** Can you get everything out, in a schema that means something without the vendor’s UI to interpret it? Test this. Most teams discover the export is missing the relations that made the data useful.
2.  **Re-integration.** Everything that reads from or writes to this system has to point somewhere else. Count the integrations, including the spreadsheet somebody built.
3.  **Process rewrite.** The parts of your operation that exist because the tool works that way. This is usually the largest number and the one nobody estimates.
4.  **Retraining.** People, and now also whatever automation you built on top.
5.  **Parallel run.** The weeks of running both while you prove the new one.

Add it up per system. That total is what you are paying, invisibly, to keep the option of leaving alive — and it is the number that should sit next to the licence cost in every renewal discussion.

## The regulation changed one of these

The EU Data Act turned cloud switching from a commercial favour into a regulated process, including obligations around data portability and the phasing out of the egress charges that made moving large datasets quietly unaffordable.

That does not solve items 2 through 5 on the list. It solves part of item 1, and it does so specifically for cloud and data-processing services. Worth knowing, worth using at the negotiating table — and worth verifying against the current text, because the details in this area have moved.

## What a lower-lock-in stack looks like

Not heroic self-hosting. Boring choices, made deliberately:

-   **Data in a store you control**, with applications reading from it — rather than data living inside each application.
-   **Open formats and documented schemas.** If an export needs the vendor to interpret it, it is not an export.
-   **Short contracts.** Multi-year discounts are the price of your optionality; sometimes worth it, but price it honestly.
-   **An exit tested once a year.** Not planned — tested. Pull the export, load it somewhere, see what breaks. A day of work that turns an unknown into a number.
-   **The core process owned.** If a workflow is what makes you money, it should not live inside somebody else’s product.

## The question worth asking before the next renewal

Not “is this tool good?” — it probably is. Ask: **if this vendor doubled the price tomorrow, what would we do?**

If the answer is “pay it”, you are not a customer. You are a tenant, and the rent is set by someone whose business model depends on you never checking what else is available.

-   lock-in
-   SaaS
-   exit cost
-   procurement

## Keep reading

-   [The barbarians are already inside the gate](https://barbairians.com/blog/barbarians-at-the-gate-of-enterprise-software)
-   [Sovereign AI is procurement, not patriotism](https://barbairians.com/blog/sovereign-ai-is-procurement-not-patriotism)