Focus area
Zero-to-One Systems
I take new products and platforms from an idea to a working production system. That includes the architecture, technical strategy, the first technical decisions, what to build now and what to leave for later, and making sure the team can eventually take it over without me.
When to bring me in
You're starting from zero and need someone to own the technical side while working with product and business - technical strategy, architecture, delivery, and building the team.
You already have a team, but need someone to set the technical strategy, make the key architecture decisions, shape how the team grows, and work with product on priorities.
You need to move fast, but want to make pragmatic choices now without creating expensive problems for the product or the engineering team later.
You have an early version and need to turn it into a production system - with the right architecture, team, and way of working around it.
What I look at
I start with the business goals, what the product needs to do, which assumptions and expectations are still implicit, the constraints you are working with, and how quickly it needs to get into production.
From there I look at architecture, technology choices, team structure, delivery, and scope. I also work with product on what is worth building now, what can wait, and where the technical effort is not justified by the value to the business.
How I work
I work with the product team as the requirements take shape, defining the architecture, technology choices, delivery approach, and how the work should be sequenced.
I make the technical decisions around those requirements, keep the architecture appropriate for the stage of the product, and make sure the engineering work is planned in a way the team can deliver.
I stay involved through delivery. Depending on the situation, I can work hands-on with the team, help hire engineers, interview technical candidates, and adjust the technical plan as we learn more during implementation.
The aim is to get to production with a system that meets the business needs, can be operated reliably, and can be taken forward by the team.
What you should have after this
You should have a working production system, a team that understands how it works, and a technical foundation that makes sense for where the business is now.
The important architectural decisions should be understood rather than living only in one person's head. The team should know what comes next, what can wait, and which parts of the system will need attention as the product grows.
My involvement should decrease over time as the team takes ownership.
Engagement options
Zero-to-one work usually means staying involved through a meaningful part of the build, so I normally work directly with the team for several weeks or months.
If you already have a strong engineering team and mainly need senior technical input on architecture, technology choices, hiring, or difficult decisions as the build progresses, this can also work as ongoing Technical Advisory.
Ready to talk?
If you are about to build something important and the technical path is still taking shape, get in touch or book a call.
Taking on up to three new startup engagements in Q3 2026.