Writing · Leadership
I have been a full-time CTO and I work as a fractional one, so I have no neutral corner here. What I do have is the failure modes of both, seen from inside. That is the part the comparison articles written by marketing teams leave out.
Hire a full-time CTO when the technology is the company: when architecture decisions happen weekly, the engineering team is past roughly ten people and growing, and the technical roadmap is inseparable from the company strategy. A team that ships daily needs leadership that is present daily. No fractional arrangement replaces that.
The full-time failure mode is hiring this person too early. A five-person company that hires a CTO to manage two engineers has bought an expensive title, not capacity. The most common version I see: a strong senior engineer promoted into the title, doing architecture reviews for a team that does not exist yet, while the actual constraint sits in sales or delivery.
A fractional CTO fits when the company needs senior technical judgment and direction but does not generate a full-time executive workload: growth-stage companies with a capable team that lacks technical leadership, non-technical founders making consequential technical decisions, AI or automation programmes that need an owner, or an interim period after a departure.
The distinction that matters is not hours. It is operator versus advisor. An advisor gives opinions from a distance and owns nothing. The version of fractional work I consider legitimate enters the machine: owns the architecture, the delivery, and the result. If a fractional CTO cannot open the codebase, they are a consultant with a better title.
The fractional failure mode is buying strategy theatre: slide decks, steering committees, and technology recommendations from someone who has never operated under the consequences of their own advice. The check is simple. Ask what they have personally shipped and run in production, and ask who fixes it when it breaks.
Before hiring either, verify that technical leadership is actually the constraint. A sales problem, a technical problem, and a cash problem are usually the same problem wearing three costumes. Companies regularly hire a CTO to fix what is really an unclear offer or a broken delivery model, and the new executive spends a year discovering that.
That verification is what the two-week operating diagnostic exists for. When it shows the constraint is leadership-shaped, I sometimes take the seat myself: the scope of that work is described under the CV, and delivered outcomes are in the case studies. When the decision is about someone else's CTO, team, or technical claims before an investment or acquisition, that is technical due diligence.
Describe the company and the decision. A free 30-minute conversation will tell you whether the constraint is leadership-shaped at all, and if so, which version fits.
Book the conversation →