Interim CTO
We lead engineering full time while you recruit a permanent CTO or work through a transition. We agree the term and the decisions we’ll own before we start.

Your incoming CTO gets a written record of what we decided, why we decided it and what needs attention next.
The exit is the point
An interim CTO who becomes indispensable has failed.
-
What we agree with the board
Which decisions we’ll own, which work must keep moving and what the incoming CTO will need from us at handover.
-
An interim mandate is exclusive and full-time
while it runs, this seat is the job.
-
The term is fixed
the handover document is a first-class deliverable, and success is measured by how little the incoming CTO has to reverse-engineer.
When this is the right instrument
The CTO left, and the search will take two quarters you cannot afford to lose.
- A transition (merger, carve-out, replatforming) needs an executive who has done it before and leaves when it is done.
- The board needs technology represented now by someone with no interest in keeping the seat.
The deliverable
An engineering organization that kept running, and a written handover the incoming CTO can execute from day one: architecture, roadmap, team, vendors, and the decisions made in the interim, with reasons.

Between CTOs, or about to be?
A 30-minute call on the transition: what must not stall, what the term should be, and whether an interim seat is even the right instrument.
