Automate the work
that slows you down
Every team has work that runs on manual every week. The same data entered, the same files pulled, the same emails rewritten. I build the systems that remove it.
Tools I work with
What I build
Where there's repetition, there's room for automation.
I build the systems that handle recurring work across sales, ops, and finance. Below are common things I get asked about, but the scope is wider than any list.
Industries I work in
Invoice Processing Automation
The bookkeeper went from 3 to 4 hours of manual work every week to a 15-minute check. The invoices still come in the same way. Nobody has to touch them.
Multilingual Content Pipeline
What used to take a full day of work per video now runs without anyone touching it. The team reviews and publishes instead of translating and reformatting.
Email Urgency Monitor
The system identifies what needs attention and surfaces it automatically. Inbox review time went from 30 minutes a day to under five, and nothing urgent slips through.
How it works
From first call to live automation in 2–3 weeks.
Discovery call
We go through your operation: where time gets absorbed, what the process looks like on a busy week, and where automation actually helps. I ask what I need to scope the work properly.
Build
I build the system: integrations, error handling, edge cases. You're kept in the loop throughout, not just handed a finished system at the end.
Ship & hand over
You get a live system, proper docs, and a walkthrough. And if something comes up in the first 30 days, I'm there.
About me
I build automation and AI systems for businesses across Europe.
The systems I build run on real code, with proper error handling and logging. When something unexpected happens in production, it surfaces quickly and clearly rather than silently doing the wrong thing for days. That makes the difference between a five-minute fix and a problem nobody notices until it's already caused damage.
Engineering background, with experience in finance and consulting. I kept seeing the same pattern across different environments: teams losing hours every week to work that followed the same structure every time. The tooling to remove it often didn't exist, or wasn't built for the actual workflow. That gap is what I work on.
Stack
It keeps running
No-code tools break when inputs arrive unexpectedly or an API quietly changes. I write real code with proper error handling, so the system is still running at 2am when nobody's looking.
Remote, async, available
I work across time zones and adapt to how your team operates. Comfortable with full async handoffs or close collaboration, depending on what the project needs.
Straight answers
The recommendation is always based on what the operation actually needs. If something isn't the right fit, I'll be upfront about it.
Let's talk
Pick a time or send a message. I respond within 24 hours.