“Fractional CTO” has become a crowded title. Search for it and you will find hundreds of consultants offering strategy days, architecture reviews, and roadmap sessions. Useful work. But when a business owner tells me they are considering one, my first question is always the same: who is going to do the engineering? Because in most of the conversations I have, the honest need is not a chief technology officer for a few days a month. It is a senior pair of hands that stays.
What a fractional CTO actually does
A fractional CTO is an advisory role. They help you make technology decisions: what to build versus buy, how to structure a team, whether your architecture will survive your growth plans, what to ask vendors. They typically work in sessions and documents. The good ones are worth their fee when you face genuinely strategic questions, an acquisition, a rebuild decision, a hiring plan for a product team.
What they do not do is patch your server on a Tuesday night, rebuild the automation that silently stopped running, or notice that your database has been slowing down for three weeks. Advice does not keep systems up.
What a fractional engineer does
Fractional engineering is the delivery layer. The systems themselves: built, monitored, maintained, and improved, month after month, by the same senior person. In my practice that means the infrastructure your business sits on, the website that represents it, the data that runs it, and the automations that save your team hours, all handled as one connected system with one person accountable.
Strategic questions still get answered, because a senior engineer who runs your systems has opinions grounded in your actual setup rather than a slide deck. But the reason clients stay is not the advice. It is that things work, and someone answers when they do not.
The test: what does your Tuesday need?
Strip the titles away and ask what your business needs on an ordinary Tuesday. If the answer is decisions, board-level guidance, and a technology strategy your investors will read, you want the CTO. If the answer is that the site should be fast, the backups should be real, the integrations should not silently fail, and someone competent should own all of it, you want the engineer.
A rough sizing rule from my own client work: businesses under about fifty people almost always need the engineer first. The strategy questions they face are real but occasional, and a good fractional engineer covers them as part of the retainer rather than as a separate line item.
Can you have both?
Yes, and at larger sizes it is a sensible pairing: a fractional CTO setting direction, a fractional engineer (or team) delivering it. But sequence matters. Strategy applied to systems nobody maintains is decoration. If you can only afford one, buy the one that keeps the lights on, then buy the thinking once there is something stable to think about.
The cost side of this decision is covered in the in-house comparison, and what a retainer actually covers month to month is on the Operate page. If you are not sure which role your situation calls for, that is a fine question to bring to a free 45-minute diagnostic call. If the honest answer is that you need a CTO rather than me, you will hear that on the call.