Fractional CTO vs full-time CTO: when each makes sense.
A fractional CTO and a full-time CTO solve different problems. Treating the choice as a price comparison gets the answer wrong almost every time. The actual decision is about company stage, decision velocity, and what is on the founder's desk this month.
TLDR
Full-time when the engineering org has 8+ engineers and people work matters. Fractional when you have 2-7 engineers and need senior judgment in 2-5 specific decisions per week. The failure mode is hiring full-time before you have something for them to manage, or fractional after the org has tipped into needing line management.
The framing that makes this question hard is that founders treat both options as fungible. They benchmark a full-time CTO at €200K-€280K total comp in the EU, a fractional CTO at €8K-€15K per month, and assume the fractional version is the cheap version of the same job.
It is not. The two seats do meaningfully different work, and which one is correct for your company depends on three things: how much engineering decision volume there actually is per week, who is currently making those decisions, and whether the next hires you make need a manager or a co-pilot.
What a full-time CTO actually does
A full-time CTO is a hiring manager, a culture owner, a 1:1 holder, a roadmap owner, a vendor relationship owner, and a board interface. About 30 to 50 percent of the role is people work. The remaining time is split between architecture, technology selection, founder support, and protecting the team from the parts of the business that should not interrupt them.
The reason a full-time CTO is the right answer when the role is the right answer is that all six of those responsibilities benefit from being in the same calendar, the same Slack channels, and the same hiring debriefs. You cannot fractional-ise the part where engineer number seven is having a tough quarter and needs a private conversation. You cannot async-ise the part where a designer is leaving and you need to decide if you backfill or restructure.
If the company already has eight to twenty engineers, a CTO is not optional. The question is who, not whether.
What a fractional CTO actually does
A fractional CTO does the senior-judgment subset of the role. Architecture review, hiring screens for senior roles, board prep on the technical narrative, vendor evaluation, the call you cannot delegate.
What a fractional CTO does not do, by design, is the day-to-day people management. Standups, performance reviews, retention work, and culture ownership all sit with the founder or with whoever the senior engineer in the room is. The fractional version is a thinking partner, not a line manager.
This makes fractional the correct shape when the company has fewer than eight engineers, when the founder is technical or technical-adjacent, and when the engineering decisions worth a senior brain happen on the order of two to five per week. Below that volume, even a fractional retainer is overkill. Above it, you need full-time presence.
The four shapes
Most companies are in one of four states. Here is which seat each one needs.
Pre-product, founder is the engineer
No team, no product, no users. The founder is in the code daily.
Post-product, 2-7 engineers, founder still in the code
Daily calls sit with the founder. Architecture review on Friday is the bottleneck. Senior hiring screens are guesswork.
8-20 engineers, growing fast
Role tips into mostly people work. Performance reviews, retention, culture, hiring debriefs. Fractional cannot hold this seat.
Mature engineering org, board-driven
VP Engineering for execution. Board observer fractional for technical narrative. Different conversation.
The failure modes
Both errors have the same root cause: pricing the seat instead of staging the seat.
Failure A: Full-time hire at stage 2
New CTO arrives, finds 3 engineers and a founder still pushing code. Nothing to manage. Spends 6 months building structure that does not earn its keep, or quietly slides into IC work. You are paying senior leader rates for senior IC output.
Failure B: Fractional at stage 3
Fractional cannot retain the team. Team feels unmanaged. Senior people leave. The retainer that was supposed to save money costs you an engineering rebuild 18 months later.
A working test
Two questions. The answer pattern tells you which seat fits.
Considering a fractional CTO retainer.
I run a fractional CTO practice through QuantaLynk. From €8K per month, six month minimum after a four week pilot. The retainer sits at the lower end of the market band above because the studio operates from Ahmedabad with a senior solo + AI delivery shape. Two retainers held at any time. If the shape fits, the first call is 30 minutes.
Read more about the retainer →