How much does custom software cost in the UK? A 2026 guide
The cost of custom software depends on scope, integrations and risk. Here's what moves the number, what you pay after launch and how to keep spending under control.
Automation platforms are the fastest way to connect two systems. A custom integration earns its cost when the data matters, the volume is high or the sync runs both ways.
Use an automation platform such as Zapier, Make or n8n when the flow is simple, low in volume and runs one way, and when a failed run is easy to spot and fix by hand. Build a custom integration when data has to stay in step between systems in both directions, when volume is high or when a missed or duplicated record costs you money. Many businesses end up with both, and that is usually the right answer.
This article is about connecting systems you already have. If you’re still deciding whether to buy software at all, start with our guide to building or buying custom software, which covers the wider decision.
An automation platform is a hosted service with a visual editor. You pick a trigger, such as a new deal in your CRM, and one or more actions, such as creating a customer in your accounting system. The platform supplies ready-made connectors for hundreds of applications and runs the flow for you.
A custom integration is code written for your systems. It calls each system’s API directly, holds the mapping between them and runs on infrastructure you control. It takes longer to build, and it can do anything the APIs allow.
The two overlap more than they used to. Some platforms let you add code steps, and n8n can be self-hosted on your own servers. The choice still comes down to the same questions about volume, failure and data.
Platforms are good at small, well-defined jobs between popular applications. Typical examples:
These flows have a few things in common. They run one way, they handle tens or hundreds of records a month and nobody loses money if one run fails and someone has to redo it. A person who knows the tools can build one in an afternoon and change it without a developer.
If that describes your need, use a platform. Paying for code to do the same job is hard to justify.
The case for code gets stronger as the stakes and the complexity rise. These are the signs we look for.
A one-way flow is simple: when A changes, update B. A two-way sync has to decide what happens when both sides change the same record, which change wins and how to stop an update in A triggering an update in B that triggers another update in A. Platforms can do this with care, but the logic ends up spread across several flows that are hard to read and harder to test.
Many platforms charge by usage. Zapier, for example, counts a task each time an action step in a flow runs successfully, so a flow with three actions uses three tasks per record. At a few hundred records a month that is cheap. At tens of thousands, the bill becomes a line your finance team will ask about, and you’ll be paying it every month for as long as the flow runs.
Volume also runs into API limits. Xero’s API, for example, allows 60 calls a minute for each connected organisation, plus a daily cap that depends on the app’s plan. A custom integration can batch requests, queue work and slow down when it gets close to a limit. A platform flow usually makes one call per record and fails when the limit is reached.
Every integration fails sometimes. An API is down, a token expires or a record arrives with a field missing. The question is what happens next.
On a platform, a failed run is typically logged and sometimes emailed to whoever built the flow. If that person is on holiday or has left, the failures pile up unseen. A custom integration can retry with sensible delays, park records it can’t process in a queue for review, alert an engineer and keep a full log of what was sent and received. For orders, invoices or bookings, that difference matters.
Connectors work well when the data in both systems is clean and the fields line up. Real data is rarely like that. Customer names are stored differently, product codes don’t match and one system allows values the other rejects.
Sometimes the data has to be fixed before any integration can work. On the Supersonic Phonic Friends platform, key details had been written into file titles as codes, so we turned them into proper tags and backfilled the existing library automatically before building search on top. Clean-up like that is usually done in code, before the integration itself is built.
Ready-made connectors cover the common actions of popular applications. Older systems, industry software and in-house databases often have no connector at all, and even good connectors may not expose the endpoint you need. At that point you’re writing code inside the platform, and much of the reason for using it has gone.
If personal data passes through an automation platform, such as customer names, email addresses or employee records, the platform is processing it on your behalf. Under UK GDPR that makes the vendor a processor, and the ICO says you need a written contract with any processor that covers set terms, including security, sub-processors and what happens to the data at the end. Ask the vendor for its data processing agreement, and check that it covers the data you’re sending.
Location matters too. If the vendor is established outside the UK, sending it personal data may be a restricted transfer, which needs adequacy regulations, appropriate safeguards or an exception. This is general information and not legal advice, so check your own position with a data protection specialist.
A custom integration doesn’t remove these duties, but it can reduce the number of parties involved. If the integration runs in your own cloud account, the data goes from one of your systems to another without a third service in the middle.
The costs follow a consistent pattern. A platform costs little to start and charges every month, in proportion to usage. A custom integration costs more to build, then costs hosting and maintenance, which don’t grow much with volume.
Neither is free to keep running. APIs change, fields get renamed and tokens expire. On a platform the vendor updates the connector, though you still have to fix flows that break. With code, someone has to update the integration when a supplier changes its API. Our guide to what custom software costs covers maintenance and running costs in more detail.
When you compare the two, price the platform at the volume you expect next year, and count the staff time spent fixing failed runs by hand.
| Factor | Automation platform | Custom integration |
|---|---|---|
| Time to first version | Hours or days | Weeks |
| Cost to start | Low | Higher |
| Running cost as volume grows | Rises with usage | Mostly flat |
| Two-way sync | Possible, hard to maintain | Built for it |
| Error handling | Basic logs and alerts | Retries, queues and full logs |
| API limits | Often one call per record | Batching and throttling |
| Older or in-house systems | Often no connector | Any system with an API or database |
| Who can change it | Anyone trained on the tool | A developer |
| Where the data goes | Through the vendor | Through infrastructure you choose |
Yes, and many businesses should. A sensible split is to keep the platform for small internal tasks that staff can build and change themselves, and use code for the integrations the business depends on: orders into the finance system, bookings into operations, customer records between the CRM and the product.
If you go this way, keep a simple list of every flow and integration, what it connects, who owns it and what happens when it fails. Also keep the platform account and any API credentials in your company’s name, the same advice we give for owning the code an agency builds.
A platform flow is also a cheap way to prove an integration is worth having. If a flow becomes important and starts to strain, that is the time to replace it with code, using what the flow taught you as the specification.
Most integration work starts with a look at the systems involved. How much it takes depends on how many systems there are, how good their APIs are, whether the data needs cleaning first and how often it has to sync. We look at the systems on a scoping call and give you a fixed quote before we write any code. If an off-the-shelf tool would do the job, we’ll tell you.
When we build an integration as part of our custom software development work, the code lives in your own repository from the first commit and you own it on final payment. It runs on AWS in London, in a separate AWS account inside our AWS organisation, with infrastructure set up as code and documented. Where a workflow tool is the better fit, n8n is part of the stack we use for AI integration and workflow automation.
If you have systems that need to talk to each other, tell us what you’re connecting and we’ll suggest the simplest approach that will hold up.
Keep reading
The cost of custom software depends on scope, integrations and risk. Here's what moves the number, what you pay after launch and how to keep spending under control.
In the UK, the agency owns the copyright in the code it writes unless the contract hands it to you. Here's what to check before you sign.
Most of a migration happens before the day itself. If the new platform is built, tested and rehearsed first, the switch becomes the smallest part of the job.
Tell us what you need and we'll reply within one working day. Once it's sent, you can book a free 30-minute call with Louie, our founder, and we'll follow up with a written quote.