Hello and Welcome to the Full Stack Venturer Blog

The name is a small argument, so let me make it before I introduce myself. For twenty years the word "venture" has belonged to the people who fund companies rather than the people who build them, and yet the fund takes a portfolio bet while the founder takes the only bet they have, so if anyone in that arrangement deserves to be called a venturer, it is the person who ships the thing. This blog is written from that side of the table, by someone who has sat on both.

I wanted to build software before I knew what a career was, the way some children want to build bridges or rockets, but the path I actually took led first into finance, where I spent ten years working my way up to the CFO's chair. Those were good years and I do not regret them, because they taught me how money moves through a company, how a board thinks, what a term sheet really says underneath the language, and why so many technically excellent products die of financial causes that nobody on the engineering side ever saw coming.

At some point the childhood dream stopped being a dream and became a plan, and I went back to writing code. That meant starting over in a discipline where nobody cared about my previous title, and it meant a decade of doing the work at every layer: building at full stack, leading small teams through hard deliveries, working on the security side long enough to develop a professional suspicion of anything that promises to make a problem disappear, and eventually designing the systems rather than just implementing them. More recently that has included building with, and on top of, AI systems, including the multi-agent kind where the interesting problems are less about the model and more about the architecture around it.

What I do now is the combination of both careers, and it took me longer than I would like to admit to notice that this was the point all along. I am an independent operator who funds his own work, chooses his own projects, and answers to clients and users rather than to a board, and I can make that choice with open eyes precisely because I have spent years on the side that writes the checks. I have come to believe that independence is not a compromise but a deliberate position, one that the current state of the industry makes far more viable than it was a decade ago, and that belief is the thread running through everything I intend to write here.

"Full stack" is meant literally. The stack does not end at the deployment pipeline; it runs from the architecture decision through the team that has to execute it, through the product that has to earn money, all the way up to the question of whose money that is and what it costs to take it. Most writing about software stops at the first layer, and most writing about startups starts at the last one, and having lived in both I have never found a place that treated them as a single system with trade-offs that propagate in both directions.

So this blog will sit in the gap. Expect pieces on how to design systems that a small team can actually maintain, on what leadership looks like when you cannot hide behind headcount, on building products with AI without mistaking a demo for a business, and on the increasingly reasonable case for keeping the company you build. Some of it will be opinionated, because I think the industry has grown up and a lot of its received wisdom has not, and I would rather be argued with than agreed with politely.

I build from Ukraine, which shapes the perspective in ways I will not always spell out but will not pretend are absent either. If you are an engineer who wants to understand the layers above the code, or a founder who wants to understand the layers beneath the pitch deck, you are the reader I have in mind.