How I got here.

I have always wanted to build companies.

I studied game programming because my original plan was to start a game studio. The path there was less direct: a failed community app pulled me into React, React led unexpectedly to co-founding Blazity, and leaving Blazity eventually brought me back to games through Beramonium.

Those chapters taught me different things. Blazity taught me how to turn nothing into a functioning company: I ran it as COO for four years, growing it from zero to thirty plus people and three consecutive Deloitte Technology Fast 50 wins. Beramonium taught me what it feels like to build the company you dreamed about, leading a team of twelve through three years of weekly releases, and then nearly lose it when the market underneath it collapses.

What remained consistent was the kind of work I enjoy: entering an ambiguous situation, understanding how the business actually works, identifying what matters, and getting people moving toward something concrete. I am most useful where product, technology, business, and team decisions cannot be separated neatly.

AI captured my attention when it stopped feeling like a better tool and started changing what a small, capable team could accomplish. At the start of 2026, the best model felt like a talented mid-level developer who needed his hand held; half a year later it feels like working with a true senior. I am less interested in AI demos than in what happens when companies rebuild real workflows and software delivery around it.

I think software is becoming abundant. As implementation gets cheaper, the scarce advantages move elsewhere: judgment, context, taste, trust, and distribution.

That is the transition I want to spend the next part of my career building in.