Skip to content
Spark
Writing

Adoption and strategy

Build, buy or no-code: choosing the right automation approach

Build, buy, or no-code is the wrong question until you know the workflow. Here is how we choose between them for regulated firms, weighing total cost of ownership, lock-in, and whether a regulator can inspect the result.

By Seb Lawson · 6 May 2026 · 4 min read

There is no universally right answer to build, buy, or no-code. There is only the right answer for a specific workflow, at a specific firm, at a specific stage. Get the workflow clear first and the choice usually makes itself. Pick the approach before you understand the work and you will pay for it twice.

The three options are not rivals so much as tools for different jobs. Buy an off-the-shelf product when a good one exists for a common problem. Use a no-code platform when the logic is yours but the plumbing is standard. Build custom when the workflow is core, unusual, or has to satisfy controls that a generic tool cannot. Most firms end up with a mix, and that is the correct outcome.

When buying wins

Buy when your problem is a solved problem and someone reputable has already solved it. Email security, document storage, an established KYC screening provider: you are not going to out-build a specialist, and you should not try. The trade is that you accept their roadmap, their data handling, and their limits. Read the data processing terms before you sign, especially where client data leaves the island, and check that the vendor can give you the audit evidence a supervisor will eventually ask for. If they cannot tell you how the model behaves or where the data sits, that is a reason to hesitate.

When no-code wins

No-code wins when the logic is specific to you but the building blocks are standard: move data between systems, watch an inbox, call an AI model, route the result, log it. Platforms like n8n, Make, and Zapier let you assemble that in days, not months, and change it just as fast when the process shifts. That speed is the whole point. You can ship a first version, learn from it, and iterate without a development cycle for every tweak.

For regulated firms the three are not interchangeable. Zapier is the quickest to start and the most opinionated, which is fine for light, standard integrations. Make gives you more control over complex logic at a similar level of ease. n8n is the one we most often reach for when auditability and control matter, because it can be self-hosted, which keeps data where you can see it and gives you a genuine log of every run. When client data cannot leave a controlled environment, self-hosted n8n is frequently the honest answer.

When building wins

Build custom when the workflow is core to how you make money, genuinely unusual, or bound by controls no off-the-shelf tool respects. A bespoke NAV and investor reporting pipeline, an extraction workflow tuned to your document set, an agent that has to leave a specific audit trail: these are worth owning. The upside is fit and control. You decide the data handling, the human checkpoints, the logging, and the prompt versioning, and nobody can change the rules from under you. The cost is that you own it, including the maintenance.

Total cost of ownership, honestly

The sticker price is the smallest part of the decision. What actually separates the three options over three years is this.

  • Run rate. Buying is a predictable subscription. No-code adds platform fees plus model usage. Custom adds hosting and the model usage, but no per-seat tax as you grow.
  • Change cost. No-code is cheapest to change, which matters most while a process is still moving. Bought tools change only when the vendor allows it. Custom changes cost developer time but have no ceiling.
  • Lock-in. Bought tools lock you into a vendor. Hosted no-code locks you into a platform, though self-hosted options like n8n soften that. Custom locks you into your own codebase, which at least you control.
  • Auditability. This is the one regulated firms underweight. Can you show a supervisor the input, the model and prompt version, the output, and who approved it? Some bought tools cannot. Self-hosted no-code and custom builds can, if you design for it from the start.

How we actually decide

Start no-code, prove the workflow, and build custom only where the value or the controls demand it. That sequence keeps you cheap and fast while you are still learning, and reserves the expensive option for the places it genuinely pays off. A great many workflows never need to graduate from a well-built n8n flow, and pretending otherwise is how firms overspend. This is also, quietly, one of the biggest reasons pilots stall, so it is worth reading alongside why AI pilots fail.

The honest version of this decision is not a spreadsheet, it is a conversation about one workflow and what it has to survive. If you want that call made properly, book a review and we will tell you which of the three each of your workflows actually needs.

Let’s map how your business works

A free 30-minute call with Seb or Mark. Bring the spreadsheet you hate most and we’ll tell you honestly whether a system would fix it.