On cost: Benian publishes no price for anything, including the AI Audit, the four-week fixed-scope diagnosis most owners start with. Builds after it are quoted to the work, and the quote names what you own on day one. The rest of this page covers what owned means and what to check on any vendor, including us.
What client-owned means in practice
Every workflow we build runs on n8n, an automation tool, inside an account registered to your business. You can open it any day and see exactly what ran, when it ran, and what it touched. The connections to your other software, HubSpot, Shopify, your calendar, your inbox, are made through credentials created in accounts you control.
At handover you hold the admin login. Our access exists because you granted it, and you can revoke it in minutes without asking us first. The workflows themselves export as plain JSON files that any developer who knows n8n can read, edit, and rebuild, and n8n is common enough that hiring one is not hard.
The exit test is the whole point. Ask any vendor, including us: if I revoke your access and stop paying you today, what breaks? The honest client-owned answer is nothing. The automations keep running, the logs keep writing, and the next developer picks up where the last one left off. If the answer involves migration projects, export requests, or a wind-down period, you are renting.
Lock-in patterns to check on any vendor
Lock-in is rarely announced. It gets built in quietly, one default at a time, and most of it shows up in five patterns you can check before you sign anything.
First, the build lives in the vendor's account, so stopping payment stops the workflow. Second, the credentials, the API keys and app connections that let your systems talk to each other, are created under the vendor's emails, so leaving means re-authorizing everything from scratch. Third, the build runs on a proprietary tool with no export, so there is nothing to hand to the next developer. Fourth, pricing is per task or per execution, so the bill grows every time the automation succeeds. Fifth, there is no documentation, so even with full access nobody knows how it works but them.
Turn each pattern into a question and ask it in the sales call: whose account does this run in, whose name is on each credential, what format does the build export to, what happens to my monthly cost if volume doubles, and what documentation do I get at handover. A good vendor answers all five in plain words. Evasion on any one of them is your answer.
Why platforms price the way they do
Automation platforms charge monthly, usually per task, per seat, or per thousand executions. That is not a scam. It funds their hosting, support, and development, and for the platform it is a rational model, because revenue grows with your usage while their cost per task falls.
Look at it from your side, though: the more the automation works, the more you pay for a build that has not changed. And the harder it becomes to leave, because leaving means rebuilding, so the switching cost quietly becomes the retention strategy. Agencies that build on those platforms inherit the model, which is why so many quote a low setup fee and a permanent monthly retainer. Part of that retainer is the platform bill with a markup on top.
A client-owned build inverts the economics. You pay more up front, because you are buying the build instead of renting it, and then the running cost is your own n8n and API usage at cost, with no markup layer between you and your tools. Which model is cheaper depends on volume and lifespan: the longer an automation lives and the more it runs, the more ownership wins.
When a platform subscription is the better buy
Ownership is not always the answer, and the honest version of this page says so. If you need one simple workflow at low volume, a self-serve tool like Zapier gets you there without hiring anyone, ours included. Set it up yourself in an afternoon and skip the diagnosis entirely.
Ownership starts to pay when the automation touches revenue, runs at volume, or would hurt if it stopped. You do not need anyone in-house who can open n8n for it to matter; the point is that the next developer you hire can. The rule of thumb: rent the workflows you could lose without noticing, and own the ones your operation would miss by lunchtime.