A fractional CTO owns execution alongside the team. An engineering counsel owns the decision before the team executes. The two roles are priced similarly, are often offered by the same kinds of people, and are called in by the same kinds of founders — and they are, nevertheless, different jobs.
The confusion is not an accident. The phrase fractional CTO is, by now, the shorthand operators reach for when they know they need a senior technical voice and do not yet know what shape the engagement should take. The phrase engineering counsel is newer, narrower, and less familiar. The decision about which one to ask for is usually made inside the first conversation — sometimes before — and it tends to be made on intuition rather than on a clean definition of the two.
This note is the clean definition we wish we could hand to every founder who writes in saying, we think we need a fractional CTO, can you tell us if we do?
What a fractional CTO does
A fractional CTO carries a standing responsibility, for a fixed portion of the week, inside an operating company. The engagement has the texture of an employment — regular standups, ownership of a roadmap, participation in hiring, standing meetings with the commercial side of the house. The fractional CTO is sometimes named to investors. The fractional CTO is almost always the person a junior engineer escalates to when a release is about to go badly.
The work is, in the ordinary sense, operational. It is the work of an in-house head of engineering, delivered part-time because the company is either not yet large enough to sustain a full-time head or deliberately choosing not to hire one. The engagement is open-ended. It resembles, and is intended to resemble, a member of the leadership team.
This is a legitimate and sometimes excellent shape of engagement. It is the right shape when the company has engineers, has code, has customers, and needs someone senior carrying the weekly responsibility of making the engineering function work.
What engineering counsel does
Engineering counsel is a single senior technical judgment, delivered in writing, on a specific decision. The engagement is scoped — one question, one architecture, one diligence, one read — and it closes. The counsel is not named to investors. The counsel does not carry a roadmap. The counsel does not sit in standups, and is not the escalation point for a junior engineer in a release. The counsel is the person a principal calls when a decision is about to be made that the principal suspects will shape the next three years of the company and does not want to decide without a senior external reader.
The engagement has the texture of legal counsel, not of employment. A retainer, a scoped read, or a single call. A written memo. A closed deliverable. The studio that provides it does not stay unless asked, and prefers not to be the one that builds what follows.
This is a different job. It is the right shape when the company has, in front of it, one or two decisions whose cost of being wrong is higher than the cost of commissioning an independent senior read.
Where the two shapes diverge
Three differences are worth naming.
The first is ownership. A fractional CTO owns the execution. The engineering counsel does not. If the engineering counsel's memo is wrong, the team that decides to follow it is still the team that owns the outcome. This is not a loophole — it is the point. The counsel is paid to read the decision clearly. The team is paid to make it.
The second is cadence. A fractional CTO engagement is, by design, open-ended. It is intended to continue as long as the company finds it useful. An engineering counsel engagement is, by design, closed. It begins, it delivers a named artefact, and it ends. If the company needs another read later, it commissions another engagement, under a fresh engagement letter.
The third is distance. A fractional CTO is inside the room. A counsel is outside it. The value of the counsel's read comes specifically from having not been in the meetings that led to the decision in question. The counsel has not watched the team argue. The counsel is not friends with the vendor. The counsel has no investment in the outcome beyond the quality of the written memo. The clients who find the distinction most useful are the ones who have lived through the limits of the alternative.
Which one a founder actually needs
Three situations help sort the choice.
If the company does not yet have engineers and the question is who will run engineering as we build the team, the shape is fractional CTO. An engineering counsel cannot carry weekly engineering leadership. The counsel will not take that engagement, and should not.
If the company has engineers and a working system and the question is this one decision, sitting in front of us, is about to harden — is the plan the right plan?, the shape is engineering counsel. A fractional CTO can answer it, but only by temporarily stepping out of the operational role into an advisory one, which tends to blur the accountability on both sides.
If the question is we need a senior technical person to sit beside our team for the next eight months through the AI deployment, the honest answer depends on a follow-up. If sit beside means own the engineering weekly, the shape is fractional CTO. If it means review the decisions as they are made, in writing, without owning the build, the shape is a senior coaching engagement — which is a format of engineering counsel, not of fractional-CTO work.
A fractional CTO that only writes memos is a counsel in the wrong contract. An engineering counsel that runs standups is a fractional CTO in the wrong contract. The shape of the engagement follows from the shape of the question.
What this means for the studio
We are an engineering counsel. The distinction matters to us because it is the one that keeps the work honest.
We decline fractional-CTO engagements not because the work is less valuable — it is sometimes more valuable — but because it is a different discipline, with different rhythms, and we would do it less well than firms whose entire practice is organised around it. We also decline engagements that begin as counsel and quietly turn into a fractional-CTO arrangement by accretion. Either the engagement is the counsel we were asked to deliver, or it is an employment, and employments deserve to be treated as such — with a proper letter, a proper scope, and a proper acknowledgement that the shape of the work has changed.
If a principal writes to us asking for a fractional CTO, we will usually say so plainly — the fit is not right here, and the fit is likely to be better at one of the practices we trust to do that work — and, if the question underneath the ask turns out to be a counsel question, we will say that too. The first conversation is unpaid. Its job is to get the shape right.
The most expensive version of this particular mistake is to hire a fractional CTO for a question that wanted a counsel, then spend nine months waiting for the part-time operator to deliver an artefact the engagement was never shaped to produce. The second most expensive version is the other way around. Either mistake is avoidable. It is avoided by naming, in writing, which of the two shapes the engagement is — before the work begins.