Technical review
Two weeks, fixed. A written assessment of the stack, the team and the risks, with the three things to fix first.
Fractional CTO
Ship what matters. Retire what does not.
I run engineering for founder-led companies two days a week: the roadmap, the architecture calls, and the hiring, without the full-time seat.
15 years building product teams
Seed to Series B
From two days a month
What I own
The scope, written down.
| Architecture | The decisions that are expensive to reverse, made deliberately and documented in plain language your board can read. |
|---|---|
| Delivery | A roadmap with dates that hold, and a weekly rhythm the team runs without me chasing it. |
| Hiring | Scorecards, interview loops and the first two senior hires, so the team survives my exit. |
| Security and compliance | The baseline your enterprise customers ask for, in the order that unblocks revenue first. |
| Not included Be clear | Hands-on feature work. I direct the team and review the hard parts, I am not a contract developer. |
Engagements
01
02
03
Three ways to work together.
Fractional CTO
Two days a week. Architecture, delivery and hiring owned end to end, with me in your leadership meeting.
Build sprint
Ninety days to get a product out of the doldrums and into customers' hands, then a handover your team can run.
“He killed two projects in the first month and shipped the third. Nobody had been willing to make that call.”Sample testimonial · Founder, Series A SaaS
Tell me what is stuck.
A 30-minute call. If the answer is a contractor rather than a CTO, I will say so.
Book a call