An n8n consultant for UK and Irish businesses

Honest answer: it depends on volume and control. Zapier is easy to learn and expensive at scale, because every task is billed. Make costs less per operation but is still metered and cloud-only. n8n gives you far more flexibility, AI agent nodes and self-hosting for a flat cost, at the price of a steeper learning curve. A few simple Zaps? Stay on Zapier. Automation at the core of your operation? n8n, and I will show you the maths.

Self-host if your data has to stay on infrastructure you control, common in legal, health and finance, or if your execution volume makes cloud pricing silly. The trade-off is maintenance: updates, backups and monitoring become your problem, or mine. I set up self-hosted instances with automatic backups and update checks, and I document the runbook. If your volume is modest and your data is not sensitive, n8n Cloud is fine and I will say so.

Yes, and it is one of the few automation tools where agents are more than a marketing label. n8n has native agent nodes: an LLM step can decide which tools to call, query your database, draft a reply, then hand to a human for approval. The part that matters is the guardrails. I build agents with approval gates, spending limits and full execution logs, so you can see every decision the model made and roll it back.

I price by fixed project scope rather than day rate, so you know the number before work starts. Most ongoing work sits between £500 and £1,500 a month, or a custom retainer shaped around what you need. No lock-in, no surprise invoices. Book a call and I will tell you what yours needs.

Yes, and it is not an optional extra. Every build ships with a plain-English description of what each workflow does, a diagram of the triggers and paths, credential locations, and a recorded walkthrough. The test I use: could a competent freelancer who has never met me pick this up in a week? Undocumented automation is how businesses end up hostage to whoever built it, and half my rescue work starts exactly there.

Yes. This usually starts with a workflow that mostly works: an ex-employee's build, an agency handover, or something assembled from YouTube tutorials that fails silently once a week. I audit it first: read every node, map the credentials, find the failure points, and give you a written verdict on whether to repair or rebuild. Then you decide. Either way you end up with documentation, error alerts, and a workflow no single person holds hostage.

A single workflow build, connecting a CRM to two or three other tools, typically takes one to two weeks including testing. A Zapier migration depends on Zap count: a dozen Zaps is usually two to three weeks with the parallel-run period. Self-hosted setup adds a few days for the server, backups and monitoring. I give you a fixed timeline in the proposal, and the parallel run means nothing breaks while we get there.