AI & Workflow Automation
AI workflow automation built in n8n, Make.com, Zapier and the Claude API. Lead follow-up, order handling and data sync, with alerts when something breaks.
Custom automation built in n8n, Make.com, Zapier and the Claude API. The repetitive work in your business, running without you touching it, with alerts when something breaks.
Agencies quote automation projects at $3,000 to $15,000 and staff them with a project manager, a strategist and a junior building the actual workflow. You get the same workflow either way. Here you get it from the person who builds it, at $14 per hour.
My rate is $14 per hour. Most single workflows are a small fixed-price build. Larger multi-system automation gets scoped and quoted up front, so the number does not move unless the scope does. Platform costs are yours and paid directly: an n8n VPS runs a few dollars a month, Make.com and Zapier are priced per operation.
What I automate
Lead capture and follow-up
Form or ad to CRM to tagged sequence to notification, with nothing retyped by hand. Speed-to-lead matters more than almost anything else in local services: the first business to respond usually wins the job. I have built lead-capture pipelines in GoHighLevel for Linkup Advanced Scaffolding in Australia, where the owner is on site rather than watching an inbox.
Order, fulfilment and support workflows
Order to fulfilment to tracking to customer notification. Refunds and returns routed to the right person. Support tickets classified and triaged before a human opens them. For ecommerce this is usually where the hours actually go, not in marketing.
Data movement between systems
The spreadsheet somebody exports every Monday and pastes into another tool. That is a workflow, and it is costing you a morning a week. Sheets, CRMs, accounting (Xero, MYOB, QuickBooks), ecommerce platforms and internal databases, kept in sync on a schedule or a webhook.
Document and content processing
Invoices read into structured rows. Long documents reduced to the three fields you actually need. Drafting, classifying and summarising with the Claude or OpenAI API, wired into the place the output has to land.
Reporting that builds itself
The weekly numbers pulled, calculated and delivered to Slack or email on a schedule, instead of someone rebuilding the same spreadsheet every Monday.
n8n, Make.com or Zapier?
This is the question most automation pages avoid, because agencies have a platform they resell. I do not.
When you want to self-host, keep data in your own infrastructure, or run volume without per-operation pricing. Branching and custom code done right.
When you want it managed, the volume is moderate, and your team needs to see the scenario visually. The best visual builder of the three.
When the integration exists there and nowhere else. The most expensive per operation and the weakest at branching, but the library is unmatched.
When the workflow is simple and stable. Not everything needs a platform and a monthly fee, and I will tell you when that is the case.
How a build runs
- 01Map the process firstI want the current steps written down, including the exceptions people handle by memory. That is usually where the real complexity is hiding.
- 02Pick the platform after, not beforeThe process decides the tool.
- 03Build, then break it on purposeI test the failure paths, not just the happy path. What happens when the API is down, the field is empty, the same webhook fires twice.
- 04Hand over documentedA diagram of what runs when, where the credentials live, and what to do when an alert arrives. Your automation should not be hostage to me still answering messages.
Part of the job, not an extra
An automation that fails silently is worse than no automation, because you carry on believing the work is being done.
Every workflow ships with error handling and an alert that reaches a person, so a break is something you hear about rather than discover later.
Recent work
Before hiring
Do I need AI in my automation?
Often no, and I will say so. Rules are cheaper and more reliable for anything with a definite answer.
Can you self-host n8n for me?
Yes, on DigitalOcean or your existing server, with SSL, backups and monitoring. See hosting and server management.
Will it connect to my existing tools?
If it has an API or webhooks, yes. If it does not, I can usually build a bridge. See API and integrations.
What happens when it breaks?
You get a notification, not a silence. Fixes fall under maintenance or are billed hourly.
Can you fix an automation someone else built?
Yes. I audit what is there and tell you honestly whether it is worth repairing or rebuilding.
How is this cheaper than an agency?
Because you are not paying for account management, a sales process, or an office. The workflow is the same. See the GoHighLevel pipeline work for what that looks like in practice.
Built with this service
Other ways I can help
I build software, and I measure whether it works.
The same questions I research are the ones I ask on client builds: is it reliable, is it fast, is it easy to use, and is it secure. Those four drove satisfaction in my ICT portal study, and they shape how I scope and test every project.