Bespoke

Vendor lock-in: who actually owns your business data?

THINQ

Nobody finds out who owns their business systems on the day they sign up. The trial is smooth, the import works, the team adapts. You find out years later, on the day you try to leave — when the export arrives as a pile of files that do not fit together, the automations you built do not come with you, and the price of staying has quietly become the price of not being able to go.

That is vendor lock-in. It is usually discussed as a contract problem. It is really an architecture problem, and it is decided long before anyone reads the contract.

What you are actually renting

When a business runs on a rented platform, it is renting more than software. Three things quietly move into someone else's hands.

The data. Most platforms will let you export it, and that is true as far as it goes. The question is whether it comes out in a shape anything else can use — with the relationships intact, the history attached and the files still connected to the records they belong to — or as a flat spreadsheet that loses most of what made it valuable.

The process. Over time, the way your business actually works gets encoded in someone else's configuration: the pipelines, the automations, the fields, the rules about who gets notified when. None of that exports. It is often the most valuable thing you built there, and it is the thing you will rebuild from memory if you leave.

The roadmap. Your tools now change when the vendor decides they change. A feature your team depends on can be retired, moved to a more expensive tier, or reshaped around customers who look nothing like you. You get a say in none of it.

You don't find out who owns your systems when you sign up. You find out when you try to leave.

Renting is often the right call

We are not going to argue that a business should build everything it uses. That would be expensive and mostly pointless. Email, accounting, payroll — these are commodities, and the sensible thing is to rent a good one and get on with your day. Nobody's competitive edge lives in their payroll software.

The line worth drawing is between the tools that are generic and the systems that are specifically yours: the ones that hold your customer relationships, encode the way you deliver your work, or make you different from the business down the road. Those are the ones where lock-in stops being an inconvenience and starts being a constraint on the business itself.

Questions to ask before you commit

If you are about to put something important onto a platform, a short conversation now saves a painful one later.

Ask for a real export, not a description of one, and try to load it somewhere else before you depend on the platform. Ask what happens to your automations and workflows if you leave, and expect the honest answer to be that they stay behind. Ask how much of the platform you will genuinely use; if the answer is a small fraction, you are paying for a lot of someone else's roadmap. And ask what happens to your costs as you grow, because the pricing that suits a small team is not always the pricing that applies to a successful one.

What owning it looks like

This is most of what we do. The applications we run for the businesses we work with each replaced something rented, and the pattern is consistent: a business paying for a large platform, using a small part of it, and bending its own process to fit the parts it did use. We rebuild the part that matters around how the team actually works, and the business owns the result — its data, its process and its roadmap. You can see examples of that work here.

It is the same reasoning behind how we build websites. A site on a database-and-plugin stack is a small version of the same trap, where an extension you did not write can change what your own site does — sometimes even who is allowed to read it. And as more of your customers arrive through assistants rather than search, owning the place they arrive matters more, not less.

None of this means leaving every platform you use. It means knowing which of your systems you rent, which you own, and making that a decision rather than something you discover on the way out.

Something leaking?

Let us hear about it. We’d love to help.

Start a conversation →