Low commitment to start. Real accountability once we begin.

You shouldn't have to make a big bet to find out whether I can help. So the start is deliberately low-risk, and the commitment only ramps once we both know it's a fit.

01 · Discovery call​

A free 30-minute conversation. You describe the situation; I ask the questions a CTO would ask and tell you straight whether I'm the right person and how I'd approach it. If someone else is a better fit, I'll say so.

02 · Diagnostic​

A short, paid assessment of your technology, team, and roadmap. The point is to ground any recommendation in reality rather than assumptions — so the plan you get is yours, not a template. For many clients this is genuinely valuable on its own, and it's a small, contained way to see how I work before any larger commitment.

03 · Engagement​

We agree a clear scope, cadence, and the outcomes we're aiming for, then pick the engagement model that fits. Advisory and embedded work is month-to-month with no long lock-in — you can scale me up or down as the situation changes.

04 · Handover​

A fractional CTO who can't be replaced has failed. Decisions, architecture, and runbooks are documented as we go, and the team is set up to operate without me. The finish line is a function that stands on its own.

A few things that won't change​

Plain answers, not jargon. You'll always understand the trade-off you're making and why. If you can't repeat a decision to your board, I haven't explained it well enough.

Decisions tied to the business. Technology is a means, not the point. Every recommendation ladders up to runway, revenue, or risk.

Built to leave. I build durable systems and capable teams, then step back. The goal is to make myself unnecessary.

Start with the call​

Book a discovery call. It costs you half an hour and, worst case, leaves you with a clearer picture of your technical situation.