We sell fractional CTO services, so read this chapter with that in mind. It's still going to tell you when you don't need us — because a wrong-fit engagement is bad for everyone, and because the fastest way to earn your trust is to argue against our own invoice where it's warranted.
What a CTO actually does
Strip the title down and the job is owning technical judgment: what to build, what to buy, what to ignore, who to hire, when the architecture is about to become the bottleneck. It is not primarily writing code. A great senior engineer and a CTO are different jobs that happen to share a keyboard.
When you need nobody (yet)
- You're pre-product, exploring, and a no-code tool or an AI-assisted prototype answers your current question
- Your product is one technical founder's expertise and you're under ~5 people
- Your technical decisions are genuinely reversible and cheap — you'd pay a CTO to supervise decisions that don't matter yet
Spending on technical leadership before there's anything to lead is the technical equivalent of hiring a CFO to manage your checking account.
When fractional is the right call
The fractional window is real, and it's wide. You're in it when:
- You're non-technical and making expensive technical decisions blind — vendor selection, agency oversight, first engineering hires
- You have engineers but no judgment layer — good builders, nobody deciding what not to build
- You're between 2 and ~25 engineers — enough surface area for real CTO problems, not enough for a full-time CTO's workload
- A specific high-stakes moment is coming — a fundraise with technical diligence, a platform decision, a scaling wall
- You need a translator — between your board and your dev team, or between you and the agency building your product
What you're buying is senior judgment at the hours the judgment is needed — which at this stage is genuinely not forty a week.
When you need full-time — and fractional is the wrong call
Be suspicious of any fractional CTO who won't say this part out loud:
- Past ~25–30 engineers, the job becomes daily: org design, career ladders, incident culture, cross-team architecture. Part-time attention starts costing you.
- When technology is the company's core bet — deep tech, infrastructure, novel ML — the technical vision needs a full-time owner with real skin in the game.
- When the team needs a leader, not an advisor. Engineers at scale need someone present for the Tuesday-afternoon decisions, not a weekly review.
At that point, the fractional CTO's last job is running the search for their replacement — writing the spec, screening finalists, and handing off cleanly. If your fractional partner resists that transition, you've learned something important about them.
The honest heuristic
Count the technical decisions you made last quarter that you couldn't confidently evaluate. Zero to two: you're fine — phone a friend when one comes up. A handful, or a big one approaching: that's the fractional window; rent the judgment. It's a daily stream and the team is growing: hire full-time, and use fractional only as the bridge and the search partner.
Wherever you land: the expensive mistake isn't picking the wrong tier. It's having nobody own technical judgment while the decisions pile up and compound. That's the one configuration that always ends badly.