Hire an agency when your Ops Director's time is worth more than £150/hour, when you need production-grade automations live in under a month, or when the workflows touch billing, compliance, or customer data. Learn n8n in-house when the workflows are internal, low-risk, and your Ops Director has 8–12 weeks of runway to build a real skill. Most £2M–£25M businesses do both: agency builds the first three critical flows, Ops Director learns to maintain and extend them.
The short answer
Hire an agency when the automations touch money, compliance, or customer data, or when you need them live in under a month. Learn n8n in-house when the workflows are internal, low-risk, and your Ops Director has real runway to build the skill.
Most operations leaders we speak to end up doing both. The agency builds the first three flows properly. The Ops Director learns to own them from there.
This piece is written for a specific person: the COO or Ops Director of a UK B2B business doing between £2M and £25M revenue, who has already opened n8n, already watched two YouTube tutorials, and is now trying to work out whether to keep going or hand it off.
What actually costs money (and what doesn't)
The tool itself is cheap. That's not the decision.
n8n Cloud starts at £20/month for the Starter plan. Self-hosting on a small VPS is closer to £0–£10/month. If you want to be careful about data residency (a UK-based server, no US traffic), self-hosting on Hetzner or a small AWS instance is standard.
The real cost is people-time. Not the licence.
Cost line — In-house (Ops Director learns) vs Agency build:
Software licence: In-house £0–£20/month · Agency £0–£240/year
Setup + first three flows: In-house 60–120 hours of Ops Director time · Agency £4,000–£15,000 fixed
Ongoing maintenance: In-house 2–5 hours/week · Agency £500–£2,000/month retainer
Time to first working flow: In-house 4–8 weeks · Agency 1–3 weeks
Break-when-Ops-Director-leaves risk: In-house high · Agency low (documented, handed over)
A UK Ops Director on £70k–£100k with pension, NI, and overhead sits around £150–£250 an hour loaded. Sixty hours of learning n8n is £9,000–£15,000 of their time. That's the actual comparison. Not the licence fee.
When learning n8n in-house is the right call
There are four situations where I'd tell an Ops Director to learn it themselves.
The workflows are internal and low-stakes. Sending a Slack ping when a Notion page updates. Auto-tagging inbound leads. Pulling weekly metrics into a Google Sheet. If the worst-case failure is "we manually re-run it," learn it.
You have quiet quarter with real slack. Twelve weeks of genuine capacity, not "I'll do an hour on Fridays." An Ops Director learning n8n while running the business full-time will build fragile automations they later have to rip out.
The Ops Director is technical already. Comfortable with JSON, has written a bit of SQL, has used Zapier or Make in anger. They're not learning automation, they're learning a new tool. Cuts the runway roughly in half.
You want automation as a permanent internal capability. Not a project. A muscle. Then the money spent on their learning is training, not cost.
For all four, n8n is a genuinely brilliant tool to learn. Open-source, well-documented, active community. It is not the wrong choice.
When hiring an agency is the right call
The other four situations. These are the ones I see most often at £2M–£25M.
The workflow touches billing, compliance, or customer data. A bad HubSpot sync doesn't just annoy people. It loses deals, corrupts CRM records, and takes weeks to unpick. A bad invoicing automation gets you a call from your accountant. This is not the moment to be learning on the job.
You need it live in under a month. The board wants numbers by end of quarter. The client is threatening to churn. Six weeks of tutorials is not the answer.
The integration is genuinely hard. OAuth flows, webhook signatures, rate limits, retry logic, error handling that doesn't silently swallow failures. Building a two-way HubSpot sync across 23,000 contacts (which is the scope we run for HubSync) is not a first-project n8n exercise. It is production engineering.
The Ops Director's time is worth more elsewhere. If they're the person negotiating renewals, running the leadership sync, and hiring the next five roles, sixty hours in n8n tutorials is not what you're paying them for.
The hybrid that actually works
The pattern I keep recommending, especially to comms and ops leaders running lean teams:
Agency builds the first two or three critical automations properly. Production-grade, error-handled, documented.
Ops Director sits in on the build. Not driving, but watching, asking, keeping the recording.
Agency hands over. Ops Director owns extensions, tweaks, and new low-risk flows from there.
Agency retainer keeps a few hours a month for the workflows that break, change, or need to scale.
This is roughly what we ran with HubSync. The two-way HubSpot sync, the newsletter workflow, the Sales Navigator automation. All built to production standard. Then the internal team keeps extending. That's how you get automation as a permanent capability without your Ops Director spending three months as a junior n8n developer.
Real prices for UK £2M–£25M businesses
Prices are the thing every article dodges. I won't.
A single flow, well built. £2,000–£4,000. Example: Sales Navigator lead into HubSpot, enriched, routed to the right owner, Slack notification.
A three-flow starter pack. £6,000–£12,000. Two connected systems, maybe a shared data model, proper error handling and monitoring.
A full ops automation build. £15,000–£25,000. Multiple systems, custom logic, a small internal dashboard, documented handover, staff training. This is the HubSync-scale engagement.
Ongoing retainer. £500–£2,000/month depending on hours. Covers monitoring, updates when APIs change, and adding small flows on request.
If someone quotes you £50,000 for three n8n workflows, walk. If someone quotes you £500 for a two-way CRM sync, walk faster.
What actually breaks in DIY n8n builds
I've inherited enough of these to have a shortlist.
Error handling that just… doesn't. A workflow that "worked in testing" fails silently in production for six weeks. Nobody notices until a customer asks where their onboarding email is.
No environment separation. Development, staging, and production all run on the same instance. First real change breaks live data.
Credentials in plain text. Copy-pasted API keys inside workflow nodes, no vault, no rotation. When someone leaves, nobody knows what to rotate.
No monitoring. No log destination, no alerting, no health-check pings to something external. If n8n goes down, you find out from the client.
Nothing documented. When the Ops Director who built it leaves in 18 months, nobody knows what any of it does. Everything gets rebuilt. Every business we've rescued this pattern from has paid twice.
None of these are hard to get right. They just don't get done when someone is learning the tool and running their day job at the same time.
What good looks like
A production n8n build should have all of these on day one, not day 180.
Separate dev, staging, and production instances (or at least clean environment variables)
Credentials in a vault, not in workflow JSON
Error workflows that raise real alerts (Slack, PagerDuty, email)
Retry logic with exponential backoff on external API calls
Monitoring on both the n8n instance and each critical workflow
A README per workflow: what it does, who owns it, how to test it, what to do when it breaks
Version control on workflow JSON, ideally in Git
This isn't optional if the automation touches money or customer data. This is the difference between an automation that saves your Ops Director five hours a week and one that costs you three weekends a quarter.
The Goodspeed take
We run a lot of these builds. Two things we consistently see.
The first: the Ops Director who tries to learn n8n while running ops full-time almost always builds something they later regret. Not because they're not smart. Because they don't have the runway. n8n is not the wrong tool for them. The timing is.
The second: businesses that pay to get the foundation right, then take ownership of extensions, get compounding value. The first three flows unlock the next thirty. That's when automation becomes a permanent capability, not a project.
If you're an Ops Director staring at a whiteboard of manual processes and wondering which side of this article you're on, the honest answer is usually: get help with the first three, own the rest.
Goodspeed runs a fixed-scope Discovery Sprint for exactly this kind of question. Two weeks, fixed price, money-back guarantee if the output isn't useful. You get a working prototype of one automation, a costed roadmap for the rest, and a clear read on whether you're a hire-in-house or hire-an-agency shape.
Harish Malhi
Founder of Goodspeed
Harish Malhi is the founder of Goodspeed, one of the top-rated Bubble agencies globally and winner of Bubble’s Agency of the Year award in 2024. He left Google to launch his first app, Diaspo, built entirely on Bubble, which gained press coverage from the BBC, ITV and more. Since then, he has helped ship over 200 products using Bubble, Framer, n8n and more - from internal tools to full-scale SaaS platforms. Harish now leads a team that helps founders and operators replace clunky workflows with fast, flexible software without writing a line of code.
Frequently Asked Questions (FAQs)
Is n8n hard to learn for a non-developer?
The basics are easy — HTTP nodes, conditional logic, and simple data transforms are learnable in a weekend. Production-grade error handling, credential management, and multi-system integrations are not. Expect 8–12 weeks of real practice before an Ops Director is genuinely useful for anything customer-facing.
How much does it cost to hire an n8n agency in the UK?
A single well-built workflow costs £2,000–£4,000. A three-flow starter pack runs £6,000–£12,000. A full ops build with multiple systems, handover, and staff training runs £15,000–£25,000. Ongoing retainers for monitoring and small changes sit at £500–£2,000/month.
n8n vs Zapier — which is better for a UK B2B SMB?
Zapier is faster to start and better if you never want to touch code. n8n is significantly cheaper at volume, self-hostable for data residency, and handles complex logic Zapier can't. Above roughly 5,000 tasks a month, n8n is dramatically cheaper. Below that, Zapier is often the sensible call.
Can our Ops Director maintain automations an agency built?
Yes, if they were built with handover in mind: documented workflows, clear naming, credentials in a vault, and a proper README per flow. Ask any agency this before signing. If they can't answer it clearly, don't hire them.
What's the risk of self-hosted n8n going down?
Low if hosted properly — managed VPS, automated backups, uptime monitoring. Higher if hosted on a single unmonitored server. n8n Cloud is the safer default for most SMBs; self-hosting makes sense once you need UK data residency or process more than 100,000 tasks a month.
How do we know if we actually need automation?
Count the manual jobs each person on your team does every week. Anything that's the same steps in the same order across systems is a candidate. If your team is losing more than 5 hours a week to copy-paste between tools, automation pays back inside a quarter.
Should we start with n8n or a bigger platform like Workato?
For £2M–£25M businesses, n8n almost always. Workato and MuleSoft are priced for enterprise (£30k+ a year is normal) and add complexity you don't need. n8n gets you to production without the seat-tax model.
