From writing code to owning the outcome
I started as a programmer, building web applications with Next.js and the Node ecosystem. The work was the usual kind: someone describes a feature, you build it, you move on to the next one.
Then AI changed what that work is worth. Writing code became fast and cheap. What stayed expensive was everything around it: deciding what should be built, how the parts fit together, what happens when traffic doubles, and what the product should do for the person using it.
I moved there on purpose. I studied system architecture and design, then product and user experience, until I could take a business goal and work out the whole system behind it, down to what each screen should show and why.
What I do now
I work as a systems architect and fractional CTO for ecommerce and SaaS founders. In practice I make the technical decisions, build or lead the build, and stay accountable for the result. You get one person to ask, and one person who answers.
The clearest example is an enterprise B2C ecommerce platform I designed and built end to end: the storefront customers buy from, and the backend that runs orders, catalogue and payments. It is live, and you can read how it was built.
Who I work best with
Owners and founders who have a business to run and would rather not spend their week on technical questions. You know your customers and your market. I make sure the software underneath keeps up, and I explain every decision in terms of cost, risk and time.
