On this page
How do no-code and custom compare?
No-code is faster and cheaper to begin with. Custom fits better and belongs to you.
| Compared | No-code tools | Custom build |
|---|---|---|
| Speed | Quick to a first working version. You can test an idea the same week you have it. | Slower to start. It needs a written scope, a build and testing, and the scope sets the timeline. |
| Cost shape | Low to begin, then a subscription that tends to rise with usage, users or features. | A one-off build price, then running costs paid to providers and optional support. |
| Limits | You work inside what the tool allows. Anything outside it needs a workaround or a second tool. | Built around your process, including the awkward exceptions. |
| Ownership | You rent access. Your process lives in the vendor's account and format. | Built in your accounts. You own the code and the data. |
| As volume grows | Usage-based plans cost more, and long chains of steps get harder to follow and fix. | Running costs rise with usage too, paid directly to hosting and software providers. |
| Who can change it | Anyone on your team who learns the tool. This is its biggest strength. | A developer. Changes need us, your own developer or a retainer. |
The last row is the one owners underrate. If your process changes every month, the ability to change it yourself is worth more than a perfect fit.
What happens to a usage-priced tool as you grow?
Many no-code automation tools charge by usage, so it pays to know how usage is counted. Zapier's help centre sets out how it measures task usage: each successful action step counts as a task, while triggers, filters and paths do not. At the plan limit, new runs are held unless extra tasks are paid for.
That is a fair model, and it is cheap at low volume. The point for a growing business is that the bill follows the number of action steps multiplied by the number of runs. Count both before you assume your current plan will hold.
Our comparison of Zapier and custom automation goes through that decision on its own. For the wider question of renting software or owning it, see custom software vs SaaS.
Which of our solutions replace a stack of tools?
A custom build is not one thing. These are the three solutions we would look at for a business that has outgrown its no-code setup, and you may only need one.
Workflow automation
Workflow automation moves details between your tools when something happens, such as a new order or a signed form. It checks the result and flags a failure to a person. Levers: time back and money kept, because retyping stops and so do its mistakes.
Internal tools
An internal tool gives your team one screen for the work that is spread across spreadsheets and apps today. Our guide to spreadsheets that should be software lists the signs. Lever: time back, so the same team handles more clients before the next hire.
CRM setup and migration
CRM setup and migration puts every enquiry and client in one record with an owner and a next step, and moves your history across from the old tools. Lever: more clients, because fewer enquiries are left with nobody responsible.
What that looked like for one client
TMMB Academy, a TikTok Shop academy, came to us with fragmented funnel and operating processes, rising software subscriptions and no single system. We built one portal with role-specific workspaces for admins, coaches, creators, sales, assistants and brands. TMMB was able to take on greater capacity, improve scalability and retention, and reports generating six figures within roughly two to three months (client-reported, shared with permission).
What are the workarounds costing? Do the sum
The leak, in an owner's words: "We have five tools, and one person's job is copying details from one to the next." Here is what a fix does, whichever route builds it.
- A new job, order or booking in one tool starts the automation.
- The system writes the same details into each of the other tools.
- It checks that each write worked.
- It sends a person only the cases that failed or need a decision.
The sum has two parts: the copying, and the mistakes copying causes.
| Line | Example figure | Running total |
|---|---|---|
| Copy steps per job | 4 | |
| Minutes per step | 5 | 20 minutes a job |
| Jobs a week | 30 | 10 hours a week |
| Hourly cost of the person doing it | £18 | £180 a week |
| Weeks in a year | 52 | £9,360 a year |
| Retyping mistakes a month | 2 | |
| Cost to put each one right | £150 | £3,600 a year |
| Both parts together | £12,960 a year |
Example figures. Swap in your own. We made these round numbers up to show the method. They are not a result or a forecast. The hours only count as money if you use them: a hire you no longer need, or the same team taking on more work.
For your own number, pick one job and follow it through every tool. Count the times someone retypes something, time one of them, and count last month's corrections. Or work out your own figure with our ROI calculator.
A tidier no-code setup or a custom build can both remove these steps, and the sum tells you how much either is worth paying for. For a proper price, book a call: it leads to a paid audit whose report prices each problem for a year.
When no-code is enough
Stay with no-code tools, and do not let anyone sell you a build, when:
- The process is still changing. Settle how you work first. Building around a process that moves every month wastes the build.
- Volume is low. If the plan you are on covers your runs comfortably, the subscription is the cheap option.
- You are testing an idea. Prove that customers want the thing before you pay to build it properly.
- The connection already exists. Two tools with a ready-made link between them do not need custom code.
- Someone on your team looks after it. A documented setup with a named owner can run for years.
What does a custom build cost?
We start with a paid audit at £3,000 plus VAT (US $5,000). The written report arrives within 10 working days, and the fee is credited against the build when the build deposit is paid within 14 days of the report. Before the audit you get a range, not an exact price.
Scoped builds run from £5,000 to £20,000 (US $10,000 to $30,000). Where yours sits depends on how many tools are connected, how much data moves across and how many people use it. Our custom software pricing page sets out what moves the figure.
After launch, hosting and software are paid directly to the providers from your own accounts. Support is optional, from £1,000 a month.
Frequently asked questions
How much does a custom build cost compared with no-code tools?
More at the start. Our scoped builds run from £5,000 to £20,000 after a £3,000 plus VAT audit, where a no-code tool starts with a small subscription. The comparison that matters is the build price against what the workarounds cost you each year.
Can we keep some of our no-code tools?
Yes. We keep what works and build only where the gaps are. A custom build often sits beside tools you already pay for and connects them.
Who can change a custom build after launch?
A developer. That can be us on a monthly retainer, or your own developer, because the code sits in your accounts with documentation. Your team cannot edit it the way they edit a no-code tool, and that is a real trade-off.
Do we own a custom build?
With us, yes. Everything is built in your own accounts, and you own the code and the data.
What happens to the data in our current tools?
It is moved across as part of the scope. Duplicates and missing fields are cleaned first, and messy data adds to the work, so the audit checks it before we price anything.
How do we know we have outgrown no-code?
Three signs: someone's job has become moving details between tools, runs are being held at a plan limit, and nobody can explain how the whole setup fits together.