Reporting that assembles itself from the tools already in the stack.
- Make
- n8n
View project
Delivery Automation
I build workflows that remove repetitive operational work from your team’s plate, using the tools you already run.
Workflows already in place
A sample of the builds, named where the client approved it.
One SME interview becomes a month of assets without a PM chasing checklists.
- n8n
- LLM
View project
Automated lead sourcing and outreach system built to reduce manual prospecting work.
- n8n
- Apify
- OpenAI
- Google Sheets
- CRM
View project
Every team carries work that follows the same shape every week: the same report assembled by hand, the same onboarding steps typed again, the same file moved from one place to another. None of it is hard. Together it is where the hours go.
I build the workflows that take that work off your team, on the tools you already run, with the SOPs and documentation your team needs to own the system after I’m gone. Handover is part of the build, not a favour at the end of it.
This is not automation for its own sake, and it is not AI added because it is available. If the underlying process is broken, automating it just produces the wrong result faster, and I will say that before I build anything.
What’s included
- Process review before anything is built
- Workflow build on your existing stack
- Testing against real cases, not happy paths
- SOPs and documentation
- Handover so your team can run and change it
His systematic approach and clear documentation made it both affordable and maintainable.
Workflows I build most often
Named jobs with a named output, rather than a general promise to make things more efficient.
Client reporting that assembles itself
Numbers pulled from the places they already live, written into the format your clients expect, on the day of the month you agreed. The reporting week stops being a week.
Onboarding without a PM chasing checklists
A new client triggers the accounts, the folders, the kickoff documents and the reminders. Your PM checks the exceptions instead of typing the same twelve steps again.
Brief-to-draft content pipelines
An approved brief moves itself into research, drafting and review, arriving with the right person at the right stage rather than sitting in someone’s inbox.
Repurposing engines from a single SME interview
One recorded conversation with an expert becomes the source for a month of assets, cut and routed automatically to whoever publishes them.
How a build runs
Find the repetitive work
I look at what your team does every week that follows the same shape every time, and what it costs you in hours.
Decide whether automation fits
Some of it should be automated. Some of it needs the process fixed first, and automating it as-is would just make a broken thing faster. I will tell you which one you have.
Build it on your tools
Workflows run on the stack you already pay for wherever possible, so this adds capability rather than another subscription and another login.
Document and hand over
SOPs and documentation written for the people who will actually run it, so the system survives me leaving and survives the person who used to own it changing jobs.
Typical stack: Make · n8n · HubSpot · Google Workspace · Slack · your existing tools. Adding a tool is a decision with a reason behind it, not the default.
Bring me your messiest bottleneck
You talk, I listen and recommend a solution. Yes, I’d also tell you straight if I’m not the right fit.
Prefer async? Ask me anything →