How I work
Three engagement modes, each designed around a specific problem. The entry point depends on where you are — not where you want to be.
Most common starting point
AI-MVP → Real Product
You built the MVP fast — probably with AI assistance, maybe with a small team or solo. It works. Users are coming. Investors are asking questions. And you're starting to see the cracks: a brittle data model, no test coverage, deployments that feel like gambling, a codebase only one person understands.
I come in, read the code honestly, and give you a clear picture of what's actually at risk. Then we fix it — systematically, without stopping everything. Architecture decisions, engineering practices, team setup, roadmap sequencing. The goal is a product that can grow without breaking every week.
This is for you if:
- · You have users or real business pressure but the codebase isn't ready for it
- · You're a non-technical founder and you need someone who can tell you the truth about your stack
- · You're about to hire engineers and you want to give them something they can work with
Fractional CTO
Your team is capable but there's no senior technical voice at the table. Decisions are made by committee or by whoever has the most context on a given day. Technical debt is accumulating faster than anyone wants to admit. You need someone who can define the direction, earn the team's trust, and hold the line on quality — without the cost or commitment of a full-time hire.
I start with a concrete delivery: fix something real in the codebase, ship something scoped. That earns the standing to propose bigger changes. From there, the engagement broadens — architecture decisions, AI tooling, team practices, whatever matters most. The approach: no generic methodology sold cold. I learn how your team actually works first.
This is for you if:
- · You have an engineering team but no technical leader with authority
- · You're refreshing the stack or shipping an adjacent service without growing the team
- · You want AI tooling actually embedded into how your engineers work — not just a pilot nobody uses
Founder Mentoring
You have a product idea — maybe several. You know the problem space. But the directions keep multiplying and the map doesn't converge. You're not blocked on execution; you're blocked on clarity.
Structured sessions focused on the Product Discovery phase: problem framing, user insight, roadmap prioritisation, honest positioning. I ask the questions that force the answer you already know but haven't said out loud. The output is one direction, clearly articulated, that you can defend to anyone.
This is for you if:
- · You have too many options and no way to choose between them
- · You're pre-product and need to pressure-test the idea before building
- · You're a technical founder who needs the product framing, not more engineering input
Not sure which fits?
Send me a short note about where you are. One message is enough to figure out if there's a fit — and if there isn't, I'll tell you that too.
Get in touch →