Most companies hire a fractional CTO the way they would hire a full-time one, only smaller. Two days a week instead of five. Same job description, same expectations, a fraction of the salary.
Then, a few months later, they wonder why it is not working.
The problem is not the person, and it is rarely the number of days. The problem is the model. A fractional CTO is not a part-time CTO. It is a different role, with a different contract, and it only works when both sides design it that way.
Hours Are Not the Product
When a company buys "two days a week of CTO," it is buying time. But time is not what it actually needs.
What it needs is decisions. Which architecture will carry the next two years. Whether to rebuild the payments module or isolate it. Who to hire first, and who not to hire at all. Which vendor promises are real. What "done" means for the team.
A full-time CTO makes these decisions in the gaps between meetings, in hallway conversations, in the hundred small moments of being present. A fractional CTO does not have those moments. If the role is designed around presence, it will always feel thin.
So the question changes. Not "how many days?" but "which decisions does this role own, and how will we know they were made well?"
The Three Ways It Fails
I see the same patterns again and again when fractional leadership does not deliver.
The Expensive Advisor The fractional CTO attends meetings, gives opinions, and writes recommendations. Nobody is obliged to follow them. The team listens politely, the founder nods, and the real decisions are still made by whoever was in the room on Tuesday. Advice without decision rights rarely survives contact with delivery pressure.
The Part-Time Firefighter Every week starts with a list of urgent problems. The fractional CTO spends the time fixing them, because that is what is visible. Nothing structural changes. After six months, the company has paid for a senior engineer on call, not for leadership.
The Shadow CTO Someone inside the company, often the strongest senior developer, keeps making the real technical calls between visits. The fractional CTO arrives, finds decisions already made, and either reverses them, which damages trust, or accepts them, which makes the role decorative. Two leaders, one direction, constant friction.
All three have the same root cause. Nobody wrote down what the role is accountable for.
Decision Rights, Written Down
The single most useful document in a fractional engagement is short. It lists the decisions the role owns, the decisions it advises on, and the decisions it stays out of.
Owns Technical direction, architecture decisions above a certain cost, the delivery process, engineering hiring criteria. These are decided by the CTO, with the reasoning recorded.
Advises Product priorities, budget, vendor contracts, organisational changes. The CTO's view is heard and recorded, but someone else decides.
Stays out Day-to-day task assignment, code-level choices inside agreed standards, anything the team lead already owns well.
This sounds bureaucratic. It is the opposite. Once it is written, nobody has to negotiate authority in every meeting. The senior developer knows what they decide alone. The founder knows when to escalate. The fractional CTO knows where to spend scarce time.
It also protects the people inside the company. A strong team lead does not lose authority when an outside leader arrives. Their space is named, not taken.
Asynchronous by Design
A fractional leader cannot run the team through meetings. There are not enough of them. The role has to work in writing.
That means a short decision log, so every important choice has a date, a reason, and an owner. It means architecture notes that the team can read without a call. It means a clear channel for questions, with an agreed response time, so the team is never blocked waiting for Thursday.
Done well, this has a side effect that full-time leadership often misses. The company ends up with its technical reasoning on paper. When the fractional engagement ends, the knowledge stays. Nobody has to rebuild why the system looks the way it does.
Measured Against a Baseline
The last piece is the one most engagements skip. How will anyone know it worked?
Before the first decision, write down where things stand. How long it takes to ship a small change. How often releases need fixing. How much of the team's time goes to unplanned work. How long it takes a new developer to deliver something real. You do not need perfect numbers. You need honest ones, taken at the start.
Then report against them, in writing, every month. Not activity, not hours, not a list of meetings attended. What changed, what did not, and what is planned next.
A monthly written report keeps both sides honest. The company sees whether it is getting leadership or just presence. The fractional CTO has to show progress, not effort. If nothing moves after three months, that is a real signal, and it is far better to see it then than after a year.
When It Is the Right Model
A fractional CTO is not a cheaper substitute for a full-time hire. It is the right model in specific situations:
- Before the first senior technical hire, when the company needs direction now and the hiring decision itself needs expert input.
- During a major change, such as a modernisation, a new platform, or a merger of two codebases, when the existing leaders need experienced help carrying it through.
- When the team has outgrown its founder's technical role, and the founder needs time to step back without leaving a gap.
- When a full-time CTO would be underused, because the real need is a few high-stakes decisions per month, not daily management.
In each of these, the value comes from judgment applied at the right moments. Not from hours spent in the building.
The Contract Is the Role
If you are considering fractional technical leadership, start with three questions before you talk about days or rates:
- Which decisions will this person own?
- How will the team reach them between visits?
- What will we measure at the start, and review every month?
If you cannot answer them, you are not ready to hire anyone yet, fractional or full-time.
If you can, you will find that a few well-designed days a month can change the direction of a company. Not because the person works harder, but because the role was built to lead.
