I build systems, not one-off automations

My work sits at the intersection of AI and workflow automation — building agents, connecting tools, and designing processes that remove manual work instead of shifting it around. I specialize in AI agents, n8n and Make.com automation, CRM and operations workflows, and the API integrations that connect them all together.

A single automated trigger is easy. The hard part — and the part I actually care about — is designing how a business's tools, data and AI models work together as one coherent system, so that a change in one place doesn't quietly break something else.

I've worked across a range of client projects — from service platforms to operational tooling — each with its own tools, constraints and priorities. That variety is why I build systems instead of isolated automations: a workflow that only works in isolation doesn't hold up once it has to interact with everything else a business runs on.

Practically, that means I spend as much time understanding how a process actually runs today as I do building the automation itself — because the right system depends entirely on getting that part right first. FreelancerOS is the clearest example: a system I built for my own work, the same way I'd build one for a client.