Fractional CTO & product
For teams without a full-time CTO, I make the technical calls, help hire and set priorities, all while writing code. It usually starts with a product that needs a technical lead, a team that has stopped shipping, or a system your product has outgrown.
What I build for
Requirements before code
Before anyone writes code, I work out with you and your team what the product needs, write it down as requirements engineers can build against, and cut what doesn't earn its place.Decisions you can explain
Every technical decision should be one you could explain to your board or investors: what it costs, what it risks and what it rules out later. That goes for architecture, build or buy, and which problems to leave alone for now.A team that ships
When a team stops shipping, I look first at how work is planned, reviewed and released, because that's usually where it stalls. Then I fix it, and help hire and onboard the engineers you need next.Rescue before rewrite
Before anyone talks about a rewrite, I measure where the system actually fails, make change safe with tests and test environments, and fix the worst bottleneck first, so it improves while it keeps running.Project management built in
I track requirements, plans, progress and tests as the work happens, with AI agents doing much of the bookkeeping. You can see where things stand, and there's no project manager billed on top.From client work
All case studies →Questions
What does a fractional CTO actually do?
A fractional CTO is a part-time CTO. They own the technical side of the company: which decisions to make and when, what the engineers work on first, and who to hire next. You have one person who answers for those calls and sees them through. In my case, it also means writing code with your team, with AI agents that multiply what I can build.
Shouldn't we just hire a full-time CTO?
Once there's a full-time job for one, yes: usually when leading the engineering team takes someone's whole week. Before that, what matters most is a handful of early decisions, such as the database, the cloud provider and how users sign in. They look small when you make them, but every feature you build afterward depends on them and makes them more expensive to change. A part-time CTO can get those right while you work out what kind of full-time leader you'll need.
Our team ships faster than ever with AI, but the product keeps getting worse. Why?
Because code now comes faster than anyone decides what the product should be. AI tools fed more context than anyone has curated turn out more of it, the product fills up with proofs of concept nobody finished or removed, and the parts customers actually use stop getting the care that makes them fast and polished. Green automated checks only tell you what those checks covered. So I start with what the product is for: walk through it with the team, cut what doesn't earn its place, and make sure the checks actually run.
Our product has outgrown the system it was built on. How do we keep adding features without it falling apart?
Decide what the system should look like for the product you have now, then move it there a change at a time. Most systems were shaped by the product they first served, and every feature since was fitted in wherever it would go, so each new one has to work around all the others. Reading the code is the quick part now, with AI tools. The slow part is the judgment: which parts still fit, which to reshape, and where new work should go so the next feature is easier, not harder. Each feature then lands on the new shape, and the system improves while it keeps running.
The agencies we talked to include a project manager. Will we need one?
Not with me. An agency usually puts a project manager between you and its engineers and bills for both, so the people building your product hear what you need second-hand. You work with me directly. I gather the requirements with you, decide what matters most and break big work into pieces your engineers and my AI agents can build in parallel. The bookkeeping (plans, progress, tests) runs on AI systems I built for it, which keeps my time on the engineering while it stays tied to what you asked for.
Tell me what you're building
A free 30-minute call with me, not a sales team. Bring the diagram or the prototype. My engagements run long and personal, so I'd rather know we fit first. Either way, you'll get a Slack Connect invite for later questions.
Book a call