The full story

I started coding at 15, a World of Warcraft site that got DDoS'd on day one; by 18 I was building bots and learning how production systems survive contact with the outside world. After university I took the regulated path: three years at Finologee writing Java for the banking sector, where every deployment is audited and every mistake has legal consequences. That's where production-grade stopped being a feature and became a discipline.

In 2020 I co-founded kodehyve as CTO and built the operating system for real estate developers: one platform spanning project management, CRM, finance, compliance, and the investor lifecycle. I was sole developer for the first year, then scaled the team past 20, with the CI/CD, code review, and onboarding to match.

I introduced event-driven architecture, a shared design system, and led a full platform rebuild when we outgrew the first one. On the side I shipped a fully eIDAS-compliant eSignature platform on Luxembourg's national trust infrastructure (LuxTrust), still used by 100+ agencies today.

Five years from sole developer to a team of 20+ taught me the thing that still drives how I build: every foundational decision compounds. The ones you get right carry you; the ones you get wrong haunt you.

And then AI arrived. Starting in 2025, I spent entire days testing, not building demos, but trying to find out: can it really replace a developer? What kind of developer? Is it hype, or is it actually as wild as people say? The answer: without guardrails, it creates beautiful chaos. With solid foundations and defined patterns, it becomes the most powerful tool I've ever used.

And that's when it hit me: it's like having employees who can do anything. But you have to explain everything to them. The best employee in the world, except they don't give a damn about your business. And because they love you, you're always right.

That's where ITzWorking started: an AI-native dev agency, where the years I spent shipping production systems become the frame AI doesn't have on its own. I spent months isolating the pillars that turn an LLM from a 2x intern into a 10x senior. I wrote them down, clarified them, stress-tested them on real projects.

From those pillars, two processes emerged: one to integrate AI-assisted development into an existing codebase, another to ship a complete project alone in seven days, work that would have taken five developers six months. Real numbers.

What I learned along the way: every piece of software faces the same underlying problems. You only recognize them once you've lived them. Read more at itzworking.io...

Coming out of kodehyve, I had something rare: a CTO's view of what actually slows a company down, and the execution speed of an AI-native agency. Watching whole teams burn out on repetitive work, the realization landed: most of that work can be encoded and handed to AI. Not by stacking ten SaaS tools. By building software shaped around how the business already runs.

I proved it on myself first, with Nexus, the internal OS that runs ITzWorking. The first version was basic: ingest information, categorize it with AI. Then I started feeding it everything I still did by hand, one piece at a time, using my HRE Framework to switch each task from a human to an AI.

Step by step, Nexus absorbed the work. Today around 90% of the agency runs inside it. The last 10% stays human on purpose: it's what makes this a premium agency, not the cheap, forgettable AI everyone is already tired of. It's also, selfishly, where we find the next place to add a real "wow" to what we deliver, because as of 2026, AI still isn't a convincing source of ideas for people. We could automate that 10% too. We choose not to.

That's what I mean by artisanal AI. Not an assembly line, and not a generic tool resold to everyone, but a system shaped from how one business actually works. You'll see similar shapes from one client to the next, never the same build. That's the work. The case studies, the offers, and the framework live at ITzWorking.