Workflow Automation
Repetitive tasks like copying data between systems, chasing approvals, routing leads and publishing content, made to happen on their own. Fewer things fall through the cracks, and your team stops doing work a machine can do. You get valuable time back every week.
Who it suits, what it includes, what you own
- Who it suits
- Small businesses whose tools don't talk to each other. If someone on your team copies data from one system into another, chases the same approvals every week, or exports a CSV to get leads where they need to go, this is for you.
- What it includes
-
- A map of where your team spends time on manual, repeatable work.
- A written plan: what gets automated, what happens if a step fails, and how you'll know it's working.
- The workflows themselves, built on n8n and connected to the tools you already use.
- Go-live with run logs, so you can see each run and what it did.
- Weekly updates while it's being built.
- How it starts
- A free 30-minute call. You tell me what's slow or broken. I tell you whether I can fix it, then send a fixed quote before any work starts. No day rates.
- What you own
- Everything I build. Full source, full documentation, full handover. No vendor lock-in, and no monthly retainer unless you want one. Accounts can sit in your name or mine, whichever suits you; we agree it in the scope.
- Ongoing costs
- Depends on the platforms involved. n8n, any AI models and any hosting have their own subscriptions. I set them out in the quote so there are no surprises.
- Limits
- An automation is only as reliable as the systems it connects. If a tool has no API, or changes without notice, the workflow will need looking after. I say so in the plan rather than after the fact.
What this looks like in practice
Illustrative scenarios. What gets built depends on your tools and where the time goes.
-
Lead routing
A new enquiry is checked against your CRM, given the details you care about, and sent to the right person in under a minute. Nobody forwards it by hand.
-
Content publishing
One approved draft goes out to each of your channels without anyone copy-pasting it.
-
Invoices and records
When an invoice is paid, the CRM and the accounting records are updated from the same event, so the same fact isn't typed in twice.
-
Data between platforms
Information entered once flows to the other systems that need it. The aim is to remove re-keying.
Tools and platforms
I build automations mainly on n8n, a workflow platform that connects to most business tools. ChatGPT and Claude handle the steps that need language, and Supabase stores data. It all connects to the tools your team already uses: CRMs, email, spreadsheets, accounting software and more.
How it works
-
Audit
I map where your team spends the most time on manual, repeatable work.
-
Design
You get a clear plan showing what gets automated, what breaks if something fails, and how you'll know it's working.
-
Deploy
Your automations go live with run logs, so you can see each run and what it did.
One example
Techtorium, a tertiary IT training institute in Auckland, used to process every enquiry from a hand-exported CSV. I'm replacing that with enquiries routed into the tools the team already uses. The work is in build.
Which task should stop being manual?
Tell me what's slow, disconnected or still only an idea. We'll work out whether I'm the right person to help.
Based in Reading, England.
Working with people in the UK and New Zealand.
Calls from 11am to 11pm UK time, Monday to Friday.