When Do You Actually Need a CTO — and What a Fractional One Is

"We should hire a CTO" is usually said at the point where technology decisions have started going wrong and nobody in the room can tell whether the developer's answer is reasonable. That is a real problem, but it is worth being precise about what solves it — because a CTO is not a senior developer and not an IT manager, and hiring either one under a CTO title solves a different problem than the one you have.

What the job actually is

A CTO makes four kinds of decision that nobody else in an SME is positioned to make:

1. Build, buy or do nothing — and having the standing to say "do nothing" to an enthusiastic team.
2. Sequencing — what gets done first, given that everything cannot.
3. Risk — security, data protection, single points of failure, vendor dependency, what happens when the one person who understands the system leaves.
4. People and suppliers — who builds it, whether they are any good, and when to change.

Notice that none of these is writing code. A senior developer builds well; a CTO decides what should be built and whether it should be built at all. Those are different skills, and conflating them is why the "promote the best developer" move so often disappoints both parties.

Four signals you need that judgement

You probably need it if two or more of these are true:

• You cannot evaluate the advice you are being given. When your developer or agency says something will take three months, you have no way to know whether that is right, and you are deciding on trust rather than judgement.
• Technology spend has become significant but uncoordinated. Several tools, several vendors, overlapping functions, nobody with a view of the whole.
• A key-person risk exists that would hurt. One person understands the system, and their departure would be a crisis rather than an inconvenience.
• Technology has become how you compete, not just how you operate — your product, your pricing engine, your logistics all depend on something being built well.

If none of those is true, you likely need a good supplier and the build vs buy framework, not an executive.

What a fractional CTO is

A fractional CTO is an experienced technology leader engaged part-time and ongoing — commonly a set number of days a month — who holds the four decisions above for your business without being a full-time employee.

It works because those decisions are episodic. They need seniority and continuity, but not forty hours a week. What that arrangement typically covers:

• Reviewing and challenging vendor proposals and quotations before you sign.
• Setting the technology roadmap and its sequence.
• Interviewing and assessing technical hires you cannot assess yourself.
• Running an architecture, security and continuity review.
• Being the person your team escalates to when a technical decision has business consequences.

What it is not, and where expectations most often break: a fractional CTO is not going to write your software, is not available continuously through the working day, and cannot substitute for a delivery team. If what you need is hands on keyboards, this is the wrong hire — see hiring your first developer vs using an agency.

Cheaper things worth trying first

Be honest about which problem you have. Several are solved more cheaply.

A single independent technical review before signing a large contract is one of the highest-return purchases a small business can make. It costs a fraction of the contract and routinely changes what gets signed.

How to engage one properly

If you do go ahead, structure it so it produces decisions rather than meetings:

• Define the decisions they own, in writing. "Advises on technology" produces nothing; "approves vendor selection and the technical roadmap" produces accountability.
• Set a cadence and stick to it — a fixed day or half-day a week is more effective than "as needed", which becomes never and then everything at once.
• Give them access to the actual constraints — the real budget, the real revenue, the real deadlines. A technology leader working from a sanitised picture will give you sanitised advice.
• Agree a first-90-days deliverable. An assessment of current systems, risks and a sequenced roadmap is a reasonable one, and it tells you quickly whether the relationship works.
• Define the handover. A fractional arrangement should either end when you hire permanently or continue deliberately — not drift.

How to tell whether they are any good

Three signals that hold up well:

• They ask about your business before your technology. Someone who opens with the tech stack is solving their favourite problem, not yours.
• They tell you not to build things. A technology leader whose every answer is "yes, we can build that" is a supplier, not an advisor.
• They explain trade-offs in your language — cost, risk, time — rather than in terminology that makes the decision unauditable by you. If you cannot explain the recommendation to your accountant, it has not been explained to you properly.

Frequently asked questions

How many days a month is typical?
It varies with what you are asking them to hold, and there is no standard. What matters more than the number is that it is a fixed commitment rather than ad hoc, because the value comes from continuity of context. Agree the deliverables first, then the days needed to produce them.

Can my developer just become the CTO?
Sometimes, and it can work well — but treat it as a genuine role change with different skills, not a title upgrade. The specific risk is losing your best builder and gaining an uncertain decision-maker. If you promote internally, get them external mentoring rather than assuming the judgement arrives with the title.

Is a fractional CTO worth it for a business with no developers at all?
It can be exactly the right fit, because your risk is concentrated in vendor selection and management — which is precisely what the role does. A business with no internal technical capability is the one most exposed to a bad supplier decision.

What is the difference between a fractional CTO and a consultant?
Consulting typically delivers a piece of work and ends. A fractional arrangement is ongoing and carries accountability for decisions over time, which is the part that matters — someone who lives with the consequences of last quarter's recommendation behaves differently from someone who does not.

How do I find one?
Referral from another owner in a similar position is the most reliable route. Whatever the source, ask for references from businesses your size — experience running technology at a large company does not automatically transfer to a business with a small budget and no team, and the constraints are what the job is actually about.

Sources: this guide is a decision framework rather than a factual reference, and deliberately contains no engagement rates or salary figures — those vary widely by seniority, scope and market, and any published figure would mislead more than it would help. Get quotes for the specific scope you need.