I called the fractional CTO a myth. Now I'm selling one and here's what changed.
A while back I wrote a fairly skeptical piece on the fractional CTO model. The argument, in short: surface appeal aside, most fractional engagements fail to deliver what companies actually need from technology leadership, and founders should approach them with eyes wide open.
I still believe every word of that critique.
I am also, as of this month, offering Fractional CTO services to SME founders through Actinwise.
If that sounds like the kind of intellectual U-turn consultants make when they switch from writing about a market to selling into it, I understand. So let me explain what changed, and what didn't.
The five traps still exist. They're sharper than I wrote.
Reading the original piece again, the critique held up. There are five things that go wrong in most "fractional CTO" engagements:
- Depth vs. breadth. A part-time engagement can't substitute for the immersion a full-time leader brings. Not for any company actually trying to do something hard.
- Cookie-cutter solutions. Breadth of experience cuts both ways. A leader who's seen 30 companies can pattern-match. They can also flatten everything into the same three recommendations.
- Conflicts of interest. A fractional leader serving competing firms is conflicted, whether they admit it or not.
- Availability gaps. When the system goes down or a vendor disappears, you need someone on the call. Not someone scheduling a call for Tuesday.
- Short-term bias. Engagements paid by the hour, billed monthly, and optimized for "next month's renewal" tend to produce short-term hands, not long-term thinking.
These aren't theoretical. I've seen all five up close. So has anyone who's bought consulting at any scale.
But these are failure modes of one shape, not the model itself.
Here's what I missed in the original article: I treated the dominant market shape of fractional CTO as if it were the only possible shape.
That dominant shape (and I mean this descriptively, not pejoratively) is something like: 4–8 hours per week, 5–8 concurrent clients, monthly retainer with vague deliverables, advisory-only, no execution authority. It's engineered by both sides to maximize revenue per hour while minimizing commitment. It produces every trap I listed.
But it isn't the only shape available. It's just the one that scales easiest for the seller. A different engagement shape, designed around the failure modes, produces a different outcome.
This is the difference between being a fractional CTO and running a fractional CTO engagement. They sound the same.
They aren't.
What shape actually works
Engineer around each trap and a usable shape emerges. Here's the version I'd defend:
On depth: one to two days a week, not four hours
Most fractional CTOs sell hours per week. That's not leadership; it's office hours. Real engagement starts at one full working day per week as a floor, ideally two for the first 90 days. That's enough time to be in the standups that matter, read the documents nobody else reads, and be present when decisions get made. If a company can't justify that level of commitment, they don't need a fractional CTO. They need an advisor, which is a different product.
On generic solutions: scope the outcome, not the role
The trap of cookie-cutter strategy comes from selling "be CTO" as the deliverable. That's an open-ended brief, and open-ended briefs produce generic answers. The fix is to scope each engagement to a specific outcome: an executive-ready AI strategy, a vendor selection for a critical platform, oversight of a modernization program. The fractional CTO is the person leading that outcome. Generic recommendations don't survive contact with a specific outcome you've signed up to deliver.
On conflicts of interest: declare the roster, exclude the rivals
Most fractional CTOs maximize client count for revenue. That's the conflict, not some abstract loyalty problem. The fix is structural: a small concurrent roster (three clients maximum, in my case), declared exclusions for sector
competitors on request, and a written conflict policy that survives the sales call. If you're not willing to say no to a client because they compete with one you already have, you're not running a fractional engagement. You're running a freelance practice.
On availability gaps: real on-call, not scheduled meetings
A fractional CTO who can't answer the phone when the system is down isn't a CTO. The fix is contractual: a defined on-call window, the same as any senior engineer would have, with explicit response-time commitments for the kinds of crisis that warrant it. If a fractional leader can't offer that, they should be honest about it and call themselves something else.
On short-term bias: longer engagements, real outcomes
Monthly retainers with vague deliverables are designed to be re-sold every month, which is why the work optimizes for the next renewal. The fix is at the contract layer: 3, 6 or 12-month engagements scoped around real outcomes (a working AI strategy, a successful platform modernization, a clean board handover). Time-boxed, not open-ended. When the outcome is delivered, the engagement either ends or renegotiates around the next outcome. Both are honest. An indefinite monthly retainer is not.
Why I'm comfortable with this version
The fractional CTO model isn't broken. The default market shape of it is. The shape I've put into the Actinwise offering is the one I'd want as a buyer:
- One to two days per week of genuine engagement
- Scoped to a specific outcome, not "be CTO"
- Small roster, declared exclusions
- Real on-call commitment
- 3, 6 or 12-month terms, not perpetual retainer
That's the offering I'd hire. So that's the offering I'm selling. If a founder reads this and decides the version I'm describing is still not what they need, that's the right answer for them, and I'd rather they figure that out from this article than from a sales call.
The original critique stands. The version I'd actually build looks different. Both are true.
If you're thinking about a fractional CTO and want to compare what you've been pitched against the shape I describe here, I wrote up the offering on the Actinwise site: https://actinwise.com/services.