n8n and Make automation, built and handed over working.
Order flows, invoice pipelines, data syncs between the tools you already pay for. Built by one UK operator who runs this exact machinery on his own businesses every day.
What this actually is
Most automation projects die in the gap between the diagram and the running thing. I do not sell diagrams. You get a workflow running in your own n8n or Make account, moving your real data, with the failure paths handled: what happens when the API times out, when the spreadsheet has a blank row, when someone renames a column.
The systems on my work page are not client anonymised screenshots. They are my own operation: a store that fulfils itself, invoices that read themselves into the books, a content pipeline that publishes on schedule across nine brands. The same patterns, pointed at your tools.
When I will tell you not to automate
If a spreadsheet and ten minutes a week solves your problem, I will say so and you keep your money. Automation nobody needed is the most expensive kind: it breaks quietly, and then somebody pays twice.
What lands on your desk
- A working workflow in your own account, not a subscription to mine
- The failure paths handled and documented, not just the happy path
- A written walkthrough and a handover call, so it keeps running without me
- n8n, Make or Zapier, chosen for the job rather than by habit
Open the proof
These are published case studies of running systems, not slides. Each links to the thing itself.
Start with a brief
One line is enough. You get an honest answer on fit, and a number rather than a discovery call.
Start a brief