By Keith Rull ·
Hire an interim CTO when the CTO seat is empty and releases, incidents, and hiring still need someone with authority this week. Hire a fractional CTO when the team can build, and a defined set of technology decisions needs an owner on a regular cadence. The shape of the gap decides it. The number of hours does not.
Here is how to tell the two apart, and how either one hands the work to a permanent leader.
What is different about the authority?
A fractional CTO provides ongoing part-time leadership for decisions you list in the scope. The company often does not have a full-time CTO, and it does not need one yet. The fractional CTO page is the short definition of that role: architecture direction, hiring, budgets, vendors, and how technology risk is reported.
An interim CTO steps into a vacant CTO seat. The authority is temporary and broad: releases, incidents, hiring, and vendor commitments that cannot wait for the search. The interim CTO page describes the first days: make that authority visible, capture work in flight, and keep the organization shipping.
| Fractional CTO | Interim CTO | |
|---|---|---|
| Fits when | The team can build, and recurring decisions have no owner | The CTO has left or is leaving, and the business cannot wait |
| Authority | A written set of decisions | Temporary authority over the vacant seat |
| Cadence | A regular part-time rhythm | Inside the week, for as long as the seat is empty |
| Typical trigger | Direction, hiring, or vendor choices keep returning to the leadership meeting | A departure, with releases and incidents still live |
| Ends when | The scope changes, or a full-time CTO is the right next hire | A permanent CTO has started and the handoff is done |
One decision, with a clear owner already inside the company, is a different engagement. That is CTO consulting: a written recommendation on a rebuild, a vendor renewal, or a team-structure question, and then a stop. It is not a standing CTO role.
A transformation that is stuck between teams is a different shape again. That work sits with a Forward Deployed CTO, embedded until the receiving team can run the result. The comparison lives on Forward Deployed CTO versus fractional CTO, and the operating version is what a Forward Deployed CTO does inside a stuck workflow.
If the company can already decide, and the missing piece is people to build the next release, that is not a CTO seat. Staff augmentation adds capacity to a team that has a lead. How those engagements start from a single architecture question is on work with Keith.
When does the gap need interim cover?
Use interim cover when the seat itself is empty and the calendar will not wait.
The signs are practical. A release is dated, and nobody can pause it. An incident path names a CTO who has already left. A vendor renewal or a hiring offer needs a signature this month. The search for a permanent leader is real, and it is slower than those deadlines.
The first days are about authority, not a new strategy deck. Confirm who can pause a release, who handles an escalation, and which supplier or staffing decisions cannot wait. Write that down where engineering and the executive team can both see it. Capture work in flight and every decision that has a deadline. Mark choices you make during the gap as provisional, so the incoming CTO can confirm them or reverse them.
I have run an independent fractional CTO practice since 2007, alongside other leadership work. Interim cover is the same judgment applied to a vacancy: temporary authority, a visible owner, and a planned exit. I would not invent a long roadmap in week one. I would make the next release and the next incident safe to own.
When is fractional enough?
Fractional is enough when someone is already shipping, and the missing piece is a senior decision on a cadence.
The signs match the ones on the fractional page. Roadmap commitments slip, and nobody can say which technical risk is behind it. Engineering leads disagree, and the disagreement needs a call. Investors or customers are asking technical questions the founders cannot yet answer. None of that requires a person in the office every day. It requires an owner for a defined list, on weeks you can put on a calendar.
Agree which decisions the fractional CTO makes, which stay with the founder, and which stay with the engineering lead. Also agree what happens on a day the fractional CTO is not available. An urgent production call needs a path that does not depend on a part-time calendar. If that path is “wait until Thursday,” the seat is interim or full-time, and the fractional scope is the wrong tool.
A single architecture review before a release can be the cadence. A weekly working session can be the cadence while the company chooses a hiring plan. Match the cadence to the decisions. Matching it to a round number of hours is how the scope goes fuzzy.
How does either role hand the work on?
Both roles should leave artifacts the company keeps. The handoff is the point, not a closing meeting.
For interim cover, the handoff is a log: unresolved decisions, owners, and deadlines. Provisional changes are marked for the incoming CTO to confirm or reverse. The search itself can be part of the work. Defining the role, sitting in the technical interviews, and planning the first month are normal interim tasks. The engagement ends when that person has started and can run a release without the interim in the room.
For a fractional engagement, the handoff is a decision log, a hiring plan when you need one, and a leadership summary of technology risk. It also names the trigger that would change the shape: daily decisions, a larger team, or a fundraise that needs a full-time technology executive. What a fractional CTO owns week to week goes further on decision rights and cadence. When those triggers are already true, start with interim or a full-time search, not with a part-time scope you will outgrow in a month.
You can choose between these without outside help when the gap is obvious: an empty seat, or a list of decisions and a team that can build. Talk it through when the seat is half-empty, the founder is still the de facto CTO, and the team disagrees about which decisions are stuck.
FAQ
How long does an interim CTO stay?
For as long as the written scope says the seat is empty, and not longer than the handoff needs. There is no standard length that fits every search. Put the review date in the scope, and end the engagement when the permanent CTO can run releases, incidents, and hiring. Extending out of habit turns temporary authority into an unclear role.
Can an interim CTO run the search for a permanent CTO?
Yes. Defining the role, assessing candidates on the technical bar, and planning the handoff are part of interim leadership. The interim should say, in writing, whether they are a candidate for the permanent seat. Mixing those two roles without saying so is how the search loses trust.
When does a fractional engagement become a full-time hire?
When technology decisions are needed continuously, the team needs daily leadership, or the role has become central to fundraising and strategy. A fractional engagement can write that job, run the interview loop, and stay through the overlap. It should not pretend to be the full-time seat once the calendar is already full.
Can one person do both for the same company?
Sometimes, in sequence. Interim cover through a vacancy, then a fractional scope once a permanent leader is in place and only a few decisions remain, is a clean sequence. Doing both at once, with no line between the vacant seat and a part-time list, is how authority gets muddy. Write which hat is on, and when it comes off.
If you’re deciding what kind of CTO cover you need, talk to us.