Keeping the Right to Leave: Vendor Lock-in, Explained for Small Businesses

Lock-in rarely shows up on the day you sign. It shows up the day you want to leave, as a bill in time, money and lost features. Six questions before you commit keep that bill small.

What is vendor lock-in, really?

A bill you pay later. Nobody locks a door behind you. What happens is quieter. Every month, your business puts a little more into a tool: customer records, bookings, photos, order history, and the way your staff are used to working.

The day you want to leave, all of that has to come with you. The cost of moving it is what people mean by lock-in. Amazon Web Services makes the same point in its 2021 guide, Unpicking Vendor Lock-in: lock-in is really about switching costs that make leaving difficult or risky, not about being blocked from leaving.

Those costs come in four kinds:

• Time. Weeks spent exporting, re-entering and checking data.
• Money. Exit fees, two subscriptions running at once, and someone paid to do the move.
• Features. The new tool can't do one thing the old one did, and that thing turns out to matter.
• Flexibility. While you are stuck, you can't take the better offer down the road.

Every tool you choose has some switching cost. The goal isn't zero. It is knowing the size of the bill before you sign, not after.

What should you ask before you sign?

Six questions. They work for any software your business runs on: a website builder, a booking system, a CRM, a WhatsApp tool, accounting software or a cloud host. They follow the six lock-in considerations in the AWS guide, rewritten for a business owner rather than an IT department.

1. Can I pay month to month? A long contract should be your choice, and it should buy you something, such as a lower price or guaranteed upgrades. If a 12- or 36-month term is the only option, ask why. On AWS, Savings Plans are that kind of choice; our post on why your cloud bill keeps growing covers when one pays off.
2. What exactly am I paying for? Find out whether you own what you buy or only rent the right to use it. Ask what happens to your licence if you move. Tools built on open, widely used standards usually cost less to leave.
3. How does my data get out? Ask for the file format, how long an export takes, what it costs, and how long your data is kept after you cancel. "You can download it" is not an answer until you know the format.
4. Will what I built still work somewhere else? That means your website, your booking flow or your chatbot. If it only runs inside their system, you will rebuild it from scratch when you leave.
5. Is it reliable, and is it still improving? Ask for the uptime promise in writing, and what you get back if they miss it. A tool that has stopped improving is a tool you will want to leave.
6. Have their prices gone up or down? Look at their price history. The AWS guide makes a pointed observation here: a provider with a history of raising prices is likely to make leaving harder, too.

How do you test the exit?

Ask them to show it to you. The best single test takes ten minutes, and you do it before you pay. Ask the salesperson to export a sample account while you watch, or do it yourself during the free trial. Even AWS's guide tells customers to ask providers to demo their export tools while they are still choosing.

Then open what comes out on your own computer, without their app:

• Are all your records there, including customers, orders, notes and photos, or only some of them?
• Is it in a format other tools can read, like CSV, Excel or plain HTML?
• Was it free, or did it need a paid plan or a support ticket?
• Does their help page say how long your data is kept after you cancel?

If the answer to any of these is "we'd have to check", treat that as the answer.

Is lock-in ever worth it?

Sometimes. Not every switching cost is a trap. A booking system with a feature nobody else has, or a payment provider your customers already trust, can be worth staying with. AWS makes the same argument: use the service that best meets your needs, as long as you know of no glaring cost to leaving.

Chasing perfect portability has a price of its own. The same guide warns that spreading work across several providers without a real reason tends to bring more complexity and less depth. Splitting everything across two tools "just in case" usually means more to manage and fewer useful features.

What matters is choosing the lock-in on purpose. When you sign up, write a one-page exit plan:

1. What data lives in this tool, and how you would export it.
2. What you would have to rebuild somewhere else.
3. Who would do the move, and roughly how long it would take.
4. What it would cost, including any notice period or exit fee.

Keep it in the same folder as the contract. Look at it once a year, and again whenever the price changes.

Our own answers

We built Quantum Accord around the right to leave, so it is only fair to answer the questions ourselves:

• Contract. Websites are a one-time purchase, with hosting included and no renewal. Agents and automations are monthly, with no setup fee, and you can cancel whenever you like. The Team plan for companies is billed yearly, and it is optional: you can buy sites one at a time instead.
• What you pay for. You buy the site, not a seat, and there is no monthly fee to keep it online.
• Your data and code. Once you have bought a site, it downloads as a standard HTML file you can host on any static host. Web App builds with a designed data model also come with a separate Next.js and Supabase project. Edits made with Quantum Tune are not included in the download.
• Your domain. If you buy it through us, it is registered in your name, not ours, and it goes with you if you leave. If you bought it yourself, it was always yours.

For the website side of this story, read Why Code Ownership Matters for Small Business. And whoever you choose, us included, ask them to show you the exit first.

Start building free · Talk to us