Automations that work for you
I start with where your company loses time. Then I build the solution, deploy it on your side, and stay long enough for it to run without me.
Repetitive work is eating your team
Someone retypes the same data every day, from an email into the system, from the system into a spreadsheet, then once more into an invoice. Nobody enjoys that work and it is where mistakes happen most easily.
I build automations on n8n and Make.com, and connect systems over APIs and webhooks. Orders, documents, invoices and reports stop needing a person to click them through.
- Workflow automation and system integrations
- Document and data processing
- Notifications and reports that run themselves
From practice
For an online store I built a Chrome extension that shows full order data pulled from the store API right next to a customer email the moment it opens. The backend runs on n8n. Email handling got about 70 percent shorter. From the same shelf is an automation where invoices generate themselves every month from Google Ads data.
Enquiries and customer service are outgrowing your people
The same questions come back over and over, and enquiries arrive from five channels at once. The team answers instead of working, and some cases still fall through.
I deploy AI agents and chatbots that answer repetitive questions, qualify enquiries and route them to the right person. People stay on the cases that genuinely need them.
- Chatbots and AI agents for handling enquiries
- Qualifying and routing tickets
- Voice assistants
From practice
I built a system where a support agent sees the caller's details, their orders and status before picking up the phone. A mobile app sends the data through a webhook into n8n, and from there into a browser extension. Separately, an AI agent with vector memory on MongoDB drafts replies to social media comments, taking the brand's earlier messages into account.
Work and data scattered across spreadsheets, inboxes and systems
One piece of information sits in a spreadsheet, another in an inbox, a third in the head of the person currently on holiday. Nobody knows which version is current, and pulling a report takes half a day.
I organise the work in one system and connect it to the rest of the tools you already use. Usually Monday.com or Airtable, chosen for how you actually work rather than for a vendor's price list.
- Monday.com and Airtable setup and configuration
- Tidying up processes and team workflow
- Connecting the system to email, your store and the rest of your tools
From practice
Day to day I work as an AI & Automation Specialist at a renewable energy company of about 150 people, where I build and maintain automations in production and administer the CRM. I know what such a system looks like when several dozen people use it, not three.
How I work
Process diagnosis
A free half hour call, after which you leave with a list of two or three things to automate, regardless of whether you decide to work with me.
Planning
I write up the scope, the order and a date, and along with them you get a list of what I will need from you, before we sign anything.
Delivery
I build on your accounts and with your keys, testing on real anonymised data, because that is where the exceptions to the rule show up.
Handover and growth
You are left with documentation and a working system you develop yourself or with me, without being tied to me.
Why me
I build and maintain automations in production, not only in demos. The difference shows when something breaks at two in the morning.
I will say plainly when you do not need AI, just order in the process. Sometimes the best solution is something simpler and cheaper than what you came to buy.
I set everything up on your accounts and your keys. When the work ends you are not left with something that only runs as long as I have access.
You work with me, not with an account manager. The same person runs the call, builds the thing and then maintains it.
Frequently asked questions
A single process is usually a few days to two weeks. A larger rollout covering several processes and integrations with systems you already have takes four to eight weeks. I give a specific date after the diagnosis, because most of it depends on what access we have on the side of your tools.
Yes. I build on your n8n or Make.com account, with your API keys and your access. When the work ends nothing stays tied to my side and you do not pay me to keep the system running.
No. If you do not, I pick the tool for your case and help get it running. Simpler processes are fine on Make.com, while larger and more unusual ones usually work out better on self-hosted n8n.
I quote after the free diagnosis, because only then is it clear how many processes are in scope and what needs integrating. I bill for hours worked, and on larger projects we can agree a fixed price for delivery.
Often not. Plenty of things people want to solve with AI only need the process put in order and connected with ordinary automation. It comes out cheaper and breaks less. If that is the case for you, I will say so plainly at the diagnosis.
Let us find where the time goes
A free call, thirty minutes. We walk through your process and you leave with a concrete list of what can be automated fastest and roughly how long it will take.
No obligations and no slide deck.
Book a free analysis