The Kind of CTO You Need at Each Stage
The CTO who takes you from zero to one is rarely the one who scales you to a hundred. A field guide to matching the leader to the moment.
Founders ask me whether they need a CTO. The better question is which kind, and for how long. The role is really three different jobs wearing the same title, and the skills rarely live in one person across all three stages.
Zero to one: the builder
Early on you need someone who ships. The job is to find product-market fit before the money runs out, which means writing code, making brutal scope cuts, and keeping architecture simple enough to change tomorrow. Process here is mostly waste.
One to ten: the team-builder
Once it works, the bottleneck shifts from the product to the organization. Now you need someone who hires well, installs just enough process to be predictable, and turns a few heroes into a system. This is where most early CTOs struggle, the skills that got you here actively fight the skills you now need.
Ten to a hundred: the executive
At scale the CTO is a business leader who happens to own technology, managing managers, aligning engineering to the P&L, and answering to a board. Different job again.
Why fractional and interim works
You don't always need to hire permanently for the stage you're in, especially through a transition. A fractional or interim CTO can carry you across the gap, build the team and the process, and hand off to the right permanent leader once the shape of the job is clear. I've done exactly that for more than 30 companies since 2018.
- Bridge a sudden departure without a panic hire.
- Stand up engineering leadership before you can justify a full-time exec.
- Stabilize after an acquisition while you search for the permanent CTO.
- Get senior judgment in the room for the decisions that don't get a second try.