Ask most digital agencies what business automation costs and you'll get some version of "it depends". Which is technically true. But "it depends" without any further explanation is a way of avoiding the question, not answering it. Most agencies don't publish prices because pricing creates accountability. Orchestrix does.
The rest of this article is what "it depends" actually depends on. By the end, you'll know the rough range for a business automation project in the UK, what drives that number up, what brings it down, and whether automation is even the right answer for your specific problem.
The short answer
Here are the real numbers for business automation cost in the UK:
- A single-purpose script (one integration, one task, runs on a schedule): £500–£2,000
- A typical SMB automation project (two or three tools connected, error handling, deployment, documentation): £2,000–£8,000
- A multi-system pipeline (five or more sources, custom transformations, monitoring, alerts, potentially a UI): £8,000–£20,000
- Complex enterprise pipelines with compliance requirements, audit trails, and multi-team handoffs: £20,000+
The £2,000–£8,000 range covers the majority of what small UK businesses actually need. If a project with real scope is being quoted at £500, either the scope has been misunderstood or something important is being left out. If a simple integration is being quoted at £15,000, ask hard questions about what's in there.
What "business automation" actually means
The term gets misused constantly. Agencies stretch it to cover anything from a complex AI decision pipeline to a Zapier workflow with three steps. For the purposes of a real conversation about cost, it helps to know what you're actually buying.
In plain English, business automation is a script (or a set of scripts) that does something on your behalf so your team doesn't have to do it manually. That's it. Three examples from recent SMB engagements:
- A Python script that pulls orders from a Shopify store and writes them into Xero every night at midnight, skipping duplicates and flagging any with missing VAT data
- A webhook listener that fires when a contact form is submitted, creates a record in a CRM, sends a confirmation email to the customer, and posts a Slack notification to the sales channel
- A scheduled job that queries a stock management database at 6am, generates a formatted Excel report, and emails it to three distribution lists: one for operations, one for finance, one for the warehouse manager
Each of those took between one and three weeks to build properly. None of them required a "digital transformation strategy". They required someone who could read the existing tools' API documentation and write clean, maintainable code.
For context on how Orchestrix approaches these builds, see the business automation service page. The deliverables list there is what a properly-scoped automation engagement includes.
What drives the price up
These are the things that turn a £2,000 job into an £8,000 job:
- Number of integrated systems. Every tool you add to the pipeline is another API to understand, another authentication flow to handle, another set of rate limits to manage. Two systems is fine. Five is a different beast.
- Custom data transformations. If the data coming out of System A needs to be cleaned, reformatted, validated, or mapped to a different schema before it goes into System B, that's real engineering work, not just plumbing.
- Error handling complexity. A script that runs once and fails silently is worse than no automation at all. Proper error handling (retries, dead-letter queues, alerting when something breaks) adds time and cost, but it's the difference between something reliable and something that causes an incident at 3am.
- Live vs. scheduled vs. on-demand. A script that runs once a day is simpler and cheaper than a webhook-triggered process that needs to respond in real time. Real-time pipelines need more infrastructure, more testing, and more monitoring.
- Compliance requirements. If the data being moved is sensitive (medical information, financial records, HR data) there are additional requirements around encryption, access controls, audit trails, and sometimes GDPR documentation. That adds scope.
- Documentation and handover expectations. If you want a thorough handover document, a screen-recorded walkthrough, and a training session with the team, that's part of the cost. It's worth it (you'll be glad it's there six months later when the person who commissioned the build has left) but it's not free.
What drives the price down
These are the things that keep a project closer to the lower end of the range:
- A clearly-scoped single workflow. "Sync contacts from tool A to tool B once a day" is a scope. "Improve our data ops" is not. The tighter the brief, the faster the build.
- APIs that already exist and work. Most modern SaaS tools have solid APIs. If you're connecting two tools that both have proper REST APIs with good documentation, the integration is relatively straightforward. If one of the tools only exports data via a CSV download or an Excel file, add scope.
- No bespoke UI required. Automation that runs in the background and doesn't need a dashboard or control panel is cheaper to build than automation that also needs a web interface for your team to interact with. If a plain-English email alert is enough, it's enough.
- Willingness to run on existing infrastructure. If you already have a server or cloud account where the script can live, deployment is simpler. If you need a fresh environment set up and managed, that's additional work (or a managed hosting arrangement).
- Clean, accessible data. If the source data is structured, consistent, and reliable, the automation is simpler. If the data is messy (inconsistent formats, missing fields, duplicates) cleaning it up is work that has to happen before the automation can be reliable.
Why hourly pricing is a red flag
When an agency or freelancer quotes business automation on a day rate or an hourly basis, that's a sign that the scope hasn't been thought through properly, and that the financial risk is being transferred to you.
Hourly billing means the incentives are backwards. The longer the project runs, the more the supplier earns. Fixed-fee billing aligns the incentives: the supplier has to scope accurately, build efficiently, and deliver. If they get the estimate wrong, that's their problem, not yours.
Every Orchestrix engagement is fixed-fee. The price is agreed before a line of code is written. If something takes longer than estimated because the scope was misjudged, that's on Orchestrix, not on your invoice. The phrase used in an early proposal sums it up: trust-based delivery focused on outcomes, not timesheets.
This isn't just a sales pitch. It changes the entire dynamic of the engagement. You know what you're spending. The builder knows what they're building. Nobody's watching the clock.
What Orchestrix actually charges
Here's the published ladder for business automation work:
- Triage: Free. A 15-minute conversation to understand the workflow and confirm it's a problem automation can actually solve.
- Workflow audit: From £2,500. A paid, fixed-fee engagement where the workflow gets properly mapped, the tools get documented, and a punch list of proposals comes back. You can act on the output regardless of whether you hire Orchestrix for the build.
- Build: From £2,000 for a focused automation. Most SMB projects land between £3,000 and £8,000. Complex multi-system pipelines start at £8,000+.
- Managed retainer: Optional. Monthly fixed fee to host, monitor, patch, and evolve the automation.
No retainer is sold before a build exists. No build is started without an audit. The workflow audit fee is credited in full if you proceed to a build. It's not a sunk cost.
You can read the full breakdown of what's included in a build on the business automation service page.
When automation is the wrong answer
This is the section most agencies skip. Here it is anyway.
If your process is broken, automating it just makes the broken thing faster. If your team is manually entering data because the original intake form captures the wrong fields, building a script to auto-transfer that wrong data into your CRM doesn't fix the problem. It entrenches it. Fix the process first.
If the same decision has to be made every time a task runs, don't automate the task. Automation works when the rules are clear and consistent. If someone has to look at each record and make a judgement call about what to do with it, automation can help with the mechanical parts, but it can't make the decision for you. And if the decision is genuinely strategic, you probably don't want it automated anyway.
If your team will spend more time managing the automation than it saves them, it's not worth building. This sounds obvious but it happens. A complex pipeline that requires daily babysitting to keep running is worse than the manual process it replaced. Part of the value of a proper workflow audit is catching this before any code gets written.
If the problem is solvable with a £50/month SaaS tool, buy the SaaS tool. The audit will tell you if that's the case. A good Orchestrix audit has recommended off-the-shelf tools where they're the right answer. The goal is the best outcome, not a build for its own sake.
Start with 15 minutes
If you're trying to work out whether business automation is the right investment for a specific problem in your business, the fastest path is a free triage. You describe the workflow, get an honest answer on whether it's automatable and what it'd roughly cost, and go from there.
No pitch. No deck. If automation isn't the right answer, that's what the triage is for. Book a 15-minute triage here.