Fractional CTO,
agency, or a hire?
Which gap?

There are four ways to get software built and kept running, and most of the comparisons written about them are written by one of the four. Here is the version that assumes you might reasonably pick something other than me.

The question is not which is best. It is which gap you actually have, and most people misidentify theirs — usually as a capacity problem when it is a decision problem.

The four options

Freelancers. Cheapest per hour, fastest to start, no commitment. You are the project manager, the architect, and the person who notices when something is wrong. Works well for bounded, well-specified pieces of work. Fails when you cannot specify the work, which is the situation most people are in when they go looking for a freelancer.

A development agency. Real capacity, a process, and continuity that survives one person getting sick. Structurally good at building a defined scope. Structurally poor at telling you the scope is wrong, and their commercial interest is the next statement of work rather than your ability to operate without them. Expensive per unit of output, and handover is the part to negotiate hard at the start, not the end.

A full-time hire. Full attention, deep context, and permanent. Also $150k to $250k plus benefits, a recruiting cycle of three to six months, and — the part that gets skipped — you have to be technical enough to evaluate the candidate. Hiring your first senior technical person when nobody in the building can assess them is genuinely difficult, and getting it wrong costs a year.

A fractional CTO. Senior judgment and ownership, part-time, starting next week rather than next quarter. Not full-time attention. Good ones tell you when you have outgrown them, which is a thing worth asking about in the first call.

Which gap do you have?

You know exactly what to build and need hands. Freelancers or an agency. Do not pay for judgment you already have.

You do not know what to build, or whether it should be built. This is a decision gap, and adding capacity to it makes it worse — you build the wrong thing faster and more expensively. Fractional CTO or advisory.

You have engineers but no direction. Very common at two to five engineers. The team is capable and nobody is choosing. A fractional CTO alongside the existing team, not instead of it.

Nobody technical is in the building at all. You need someone accountable before you need capacity. Otherwise you are the technical decision-maker by default, evaluating proposals you have no basis to evaluate.

Technical decisions arrive daily and you have a real team. Hire. Fractional is a worse version of the answer at that point.

Something is broken right now. Rescue work first, and the shape of the long-term arrangement can wait until it is stable. See your developer disappeared and you inherited a codebase.

The honest comparison

The strongest argument for an agency is continuity. An individual can get sick, take a holiday, or take a better offer, and an agency has a bench. That is a real advantage and I will not talk you out of it. The counter is that the bench is frequently more junior than the person who sold you the work, so ask who is actually writing the code and get the answer before signing.

The strongest argument for hiring is that permanent people accumulate context that no part-time arrangement can match. Also true. The counter is timing: it is a poor trade while the role is not yet full-time, and hiring badly is more expensive than hiring late.

The strongest argument against fractional is that you are buying a fraction of a person. That is exactly what it is. The reason it works at small scale is that the alternative is not a full person — it is nobody, or a full person you cannot yet keep busy.

Where I sit

I do the fractional version, hands-on. I make the technical decisions, build the software, and stay accountable for keeping it running. I build with agents, which is the reason one senior person can now own a whole technical function that used to need a small team — and it is also why I am careful to say that taste and judgment are the part that did not get automated.

I will tell you on the first call if you should be hiring instead, or if what you actually need is two freelancers and a clear spec. That is not generosity. Engagements that start with the wrong diagnosis end badly for both of us.

Common questions

What is the difference between a fractional CTO and a development agency?

An agency sells capacity: people who build what has been specified. A fractional CTO sells judgment and accountability: deciding what should be built, choosing the technology and vendors, and owning whether it keeps working afterwards. Agencies are structurally excellent at delivering a defined scope and structurally poor at telling you the scope is wrong, because the next statement of work is how they stay in business. The two are not competitors — plenty of engagements involve a fractional CTO directing an agency.

When should I hire a full-time CTO instead?

When the work is genuinely full-time and continuous: you have engineers who need daily management, technical decisions arriving faster than a part-time person can absorb, or a fundraise where investors want to meet a committed executive. Roughly, once you are past four or five engineers or the technical decisions are the business, hire. Before that a full-time CTO is usually underemployed and expensive.

Can a fractional CTO work alongside our existing developers?

That is one of the most common arrangements. Teams of two to five engineers frequently have plenty of capability and no one setting technical direction, unblocking hard calls, or owning infrastructure. The fractional CTO does that and mentors the team, rather than replacing anyone. It works badly only when the role is undefined — the team needs to know who decides what.

Is a fractional CTO just an expensive consultant?

The difference is accountability and duration. A consultant delivers a recommendation and leaves; the risk of the recommendation being wrong stays with you. A fractional CTO makes the decision, implements it, and is still there when it turns out to have been wrong, which is the only arrangement where the incentives point the same direction as yours. If someone is selling advice with no responsibility for outcomes, that is consulting, and it should cost less.