01What you are really locked into
Most people picture lock-in as a vendor shutting down. That is the rare case. The common one is quieter: your booking, follow-up and invoicing logic exists only as screens inside one product, in that product's own format, under an account nobody checked the owner of. Then the price or the billing unit changes. Our October comparison showed that Zapier counts tasks, Make counts credits and n8n counts whole runs, so a bill from one cannot be read against another. Your options become paying or rebuilding from memory. The tool is replaceable. Knowing what each flow was meant to do is not, and that is the part to protect.
- Logic: the rules sit inside the tool, in its own format
- Billing unit: tasks, credits or executions, so one bill does not map onto another
- Account: the login and the connected apps belong to whoever created them
- Knowledge: one person knows why the flow does what it does
02Four checks before you build in one tool
Ask these before the first flow, not after the tenth. Can the work be exported? n8n's documentation says it stores workflows as JSON and lets you download them as a file (docs.n8n.io/workflows/export-import). That file describes n8n's own nodes, and we did not look for another tool that reads it, so treat it as a backup, not an escape route. Whose name is on the account? Is each flow written down in plain words that a new person could follow? And what would a rebuild cost in hours? We hold no figure for that, so make your own estimate from the written description.
- Export: download one flow now and see what you actually get
- Account: create it under your own email, never a freelancer's or an agency's
- Description: one page per flow with the trigger, the steps and the rule at each decision
- Rebuild: estimate the hours from that page, so the cost of leaving is a number
03Custom code is not automatically the way out
Custom code removes the subscription but adds a different dependency: the person who wrote it. Code only its author understands locks you in as firmly as a vendor does, just with a name attached. PROOF48 builds with custom code, API integrations and workflow tools, depending on the job, and documents the system so anyone on your team can understand what runs and why. Ownership is the open point. Our terms give you the website files, design and content after full payment. They say nothing about automations built under AUTOMATE, so ask us in writing what you receive and when, before you sign.
- A subscription ties you to a vendor, code ties you to whoever understands it
- Documentation is what turns either one into something you can hand over
- Our terms cover website files, design and content, and are silent on automations
- Get the handover in writing before you pay for the build
04Where PROOF48 is the wrong choice
If you need one or two simple flows, a form into a CRM or an order into a confirmation, buy a subscription and run it yourself. Our posts on custom versus off-the-shelf and on Zapier, Make and n8n explain how to choose. AUTOMATE costs 2,997 EUR a month and covers site chat, DM and email auto-responders, booking automation with a CRM and two custom automations a month. WhatsApp and phone are not among its listed channels; a WhatsApp or voice build is a custom project, priced on request. It is also a monthly arrangement, which is its own dependency, although the plans page says you can cancel anytime. A team that cannot yet write its rules down is not ready for us either.
- One or two simple flows you can run yourself: buy the tool, skip AUTOMATE
- WhatsApp and phone workflows: not among AUTOMATE's listed channels, a custom project priced on request
- A process nobody has written down: map it first, then decide
- AUTOMATE is monthly, and the plans page says you can cancel anytime
A restaurant that moved off a platform that owned its customers
Rotiseria Baba Novac sold through a delivery aggregator that took a cut of every order and owned the customer relationship. PROOF48 built them their own ordering system at rotiseria.ro: menu, cart, Stripe checkout, pickup slots and an email confirmation on every order. The case study says the restaurant keeps its orders in full. It does not say the automations can be moved to another builder, so we make no portability claim, and we hold no order volume to quote.
See the build: Rotiseria Baba NovacQuestions, answered
Is n8n safer than Zapier against lock-in?
Only partly. n8n's documentation says workflows export as JSON, and our October comparison notes a self-hosted version on GitHub. Self-hosting adds a server someone must keep running. Who owns the account and whether the logic is written down matter more than the brand.
Should I avoid automation tools to stay independent?
No. For standard flows a subscription is often the right answer. Keep the account in your name and a written description of each flow, and leaving stays possible.
What should I write down for each flow?
The trigger, each step in order, the rule at every decision, the accounts it touches and who is told when it fails. One page in plain words is enough for someone new to rebuild it.
Do I own what PROOF48 builds under AUTOMATE?
Our terms cover website files, design and content after full payment and say nothing on automations. Ask us in writing what you receive and when before you sign.
Where PROOF48 fits
Lock-in is rarely a vendor vanishing. It is logic, accounts and knowledge that live in one place. Write each flow down in plain words, keep the account in your name and test an export before you depend on a tool. PROOF48's AUTOMATE, at 2,997 EUR a month, documents what it builds; ask in writing what you own before you sign.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.