Fractional CTO vs. full-time: a decision framework that doesn't lie

This is the question I get on most discovery calls, usually phrased some variant of: we know we need senior engineering leadership, we just are not sure if we need a full-time one yet.

There is no single right answer. But there is a framework that, over dozens of these conversations, has held up better than the usual “it depends.” The framework has three buckets — hire full-time, hire fractional, or wait — plus the failure mode of each, because the failure mode is usually what you actually need to hear.

Start with what the role is for #

Before any of this is useful, get one thing clear in your own head: what is the work this person needs to do in the next two quarters?

Not “be the CTO.” Not “own engineering.” The actual list of decisions and outputs that, if they do not happen, will hurt the business in the next 180 days.

The list usually falls into one of three shapes:

Build mode. You have product-market fit signals and need to ship faster and hire well. The work is mostly recruiting, sequencing, and removing technical blockers.
Fix mode. Something is broken — velocity, quality, the team’s morale, or all three. The work is mostly leadership: clarity, structure, hiring up or out, sometimes architectural surgery.
Direction mode. You do not yet know what to build, or you know but you cannot articulate the technical bet. The work is mostly strategy and writing — usually with the CEO, not the team.

Each shape rewards a different hire. Most failed CTO hires I have seen are not bad hires; they are good hires for the wrong shape of work.

Hire full-time when #

A full-time CTO is the right move when all of the following are true:

You have a defined product strategy that requires sustained execution over twelve to thirty-six months. Not a vision deck — a strategy, with bets, and a rough roadmap to validate them.
The company can afford the loaded cost. In the EU that is realistically €200k–€350k cash plus equity, depending on stage and geography. Loaded with benefits, taxes, and the people they will need to hire to be effective, it is materially more.
You can credibly recruit a strong candidate. Meaning your story, your market, and your funding are all defensible under sharp questions from a senior leader who has done this before. If you cannot, the search will drag, you will compromise on the third candidate who said yes, and you will spend the next year managing out that compromise.
You need an executive in the room with the founders, not a contractor. Equity, brand, weight in the market, identifying as employee #1 of the technology — these all matter, and only a full-time hire credibly carries them.

If any one of those four is missing, full-time is the wrong move right now, and forcing it almost always wastes a year.

The full-time failure mode #

The most common failure mode of a full-time CTO hire at this stage is hiring eighteen months too early. The signs:

The first 90 days produce a strategy document but no shipping.
Hiring becomes the main activity, but the team has nothing scoped for new engineers to do.
The CEO starts privately complaining about velocity. The CTO starts privately complaining about clarity. Both are right.

That is not a bad hire. That is a hire the company was not yet structurally ready for.

Hire fractional when #

A fractional CTO is the right move when one or more of the following is true:

You are pre-product-market-fit and the technical strategy is changing monthly. Buying twelve months of executive presence to refine a strategy that will be different in six is a poor use of capital. Fractional buys you the senior judgment without locking in the bet.
The work is bursty. One quarter of intense architecture, hiring, and platform decisions; then steady state for the next two. A fractional engagement compresses cleanly to match this shape; a full-time hire creates the work to justify their continued presence, whether it is needed or not.
You need senior judgment more than full-time presence. This is the most common case in pre-Series-A companies. The team has one or two strong engineers; what they lack is someone in the room when the founders make irreversible technical decisions. Two days a week of the right person beats five days a week of the wrong one.
You cannot yet afford — or attract — a full-time CTO at the level you actually need. Fractional engagements let you work with people three seniority tiers above what your cap table would otherwise stretch to. That is a real edge, especially for a first technical leader hire.

A useful test: if I imagine this person joining full-time today, can I name three specific things I would expect them to deliver in the first 90 days? If you cannot, fractional is almost certainly the right next step — because the engagement itself will surface what those three things are.

The fractional failure mode #

The most common failure mode of a fractional engagement is treating it as a permanent state. Fractional CTOs work best as a structured bridge: out of a chaotic moment, into the right next shape. That shape might be a full-time CTO, a strong VP of Engineering reporting to the CEO, or a staff engineer plus a hands-off advisor.

If, six months into a fractional engagement, the answer to what is this evolving into is more of the same, something has gone wrong on one side of the table. Usually it is that the engagement has become comfortable for both parties, which is not the same as useful.

Wait when #

The third bucket — and the one founders are most reluctant to hear — is wait. Wait is the right move when:

You do not yet have an engineering team large enough to require either. A strong staff engineer plus the founder is often the right answer at five engineers or fewer. Adding a fractional CTO at this size can dilute responsibility instead of concentrating it.
The decision is being driven by investor pressure rather than an operational gap. Hiring a CTO to satisfy a board is one of the more reliable ways to spend money badly. Investors are usually right that you will need senior technical leadership eventually; they are often wrong about when.
You have not yet had the hard internal conversation about what you actually want this person to own. If you and your co-founders cannot describe the role in plain language, no candidate will be able to either, and the search will produce mostly noise.

Waiting is not a strategy by itself; it is a strategy if you use the time to figure out the questions above. Three months of deliberate clarification is almost always cheaper than nine months of a misaligned hire.

A short heuristic #

If you want to compress this whole essay into something you can use on a Tuesday afternoon:

Hire full-time when you have a defined strategy, the budget, the magnetism to attract the right person, and the need for an executive — not a contractor.

Hire fractional when the work is bursty, the strategy is still being written, or you need judgment more than presence.

Wait when the team is too small, the pressure is external, or the question of what this person should own is still unanswered.

And if you are not sure which bucket you are in, that itself is usually the signal: hire fractional for a quarter and use the time to figure it out. The cost of being wrong is bounded; the cost of being wrong about a full-time hire is not.

If you are weighing this decision right now, I am happy to be a sounding board for thirty minutes. Send me the situation and I will tell you honestly which of the three buckets I think you are in — even when the answer is wait and is not work for me. Or read how I think about engineering reviews if that shape feels closer to what you need.