What a fractional CTO actually costs
Published rates for fractional CTO work in the US spread from about $150 to $500 an hour, and monthly retainers from roughly $3,000 to $15,000. That range is wide because the label covers two different jobs. Advisory work — a weekly call, a second opinion on architecture, an introduction to a candidate — sits at the bottom. Hands-on leadership, where someone owns delivery, runs your engineers and is accountable for what ships, sits at the top.
The comparison that matters is not hourly rate against hourly rate. A full-time CTO in a US market costs $250,000 to $400,000 all-in once equity, benefits, payroll tax and recruiting fees are counted, and takes four to six months to hire. The question is not whether fractional is cheaper per hour. It is whether the fraction you buy covers the decisions you actually need made.
The three engagements founders actually ask for
Nearly every enquiry we take is one of three shapes, and they price very differently.
| Technical due diligence | Fixed fee. A raise or acquisition is in motion and someone needs an independent read on the codebase, the team and the risk. Two to three weeks, delivered as a written report you can hand to an investor. |
|---|---|
| Interim technical leadership | Monthly retainer. The technical founder has left, or was never there. Someone has to own architecture, unblock the team, and be accountable for the roadmap until a permanent hire lands. |
| Ongoing fractional CTO | Monthly retainer, smaller. The team ships fine but there is nobody senior to decide build-versus-buy, review a vendor contract, or say no to the wrong architecture. Typically one day a week. |
When a fractional CTO is the wrong answer
We turn down more of this work than we take, and it is worth being direct about why.
If you need code written, you need engineers, not a CTO. Paying leadership rates for implementation is the most common way this engagement wastes money. If your engineering team is more than about fifteen people, the coordination load alone justifies someone full-time and present. And if the real problem is that the founders disagree about the product, no technical hire of any kind resolves that — it surfaces as an architecture argument, but it is not one.
What the first ninety days look like
A fractional engagement that starts with a strategy deck has usually already failed. The first month is diagnostic and mostly listening: reading the code, sitting in standups, talking to every engineer individually, and finding out what the team already knows is broken. Almost always they know.
Month two produces the first written artefact — a technical assessment that names the three things most likely to hurt you in the next two quarters, with an honest cost against each. Month three is execution on whichever of those you choose to fund. By the end of the quarter you should have a roadmap your engineers believe in, and enough evidence to judge whether the engagement is worth continuing.
How to evaluate anyone offering this service
- Ask what they would do in the first thirty days. Anyone who answers with a framework rather than a question has a template, not a method.
- Ask for a reference from an engagement that ended. Everyone can produce a happy current client; how someone leaves tells you more.
- Ask who does the work. In many firms the person who scopes the engagement is not the person who shows up on Monday.
- Ask what they will not do. A senior operator has clear limits and states them early. Omnicompetence is a sales posture, not a capability.
- Ask how they measure the engagement. If there is no answer beyond hours delivered, there is no accountability.
Fractional CTO versus the alternatives
A technical advisor gives you a sounding board for a few hours a month and equity-light terms, but no accountability for delivery. A development agency gives you throughput but has a structural interest in the project continuing. A full-time CTO gives you complete ownership, at a cost and hiring timeline most companies under thirty people cannot justify.
Fractional leadership sits between those deliberately: enough authority and time to own technical decisions, without the cost structure of a permanent executive. It is the right answer when the decisions are hard but not yet continuous. When they become continuous, hire someone — and a good fractional CTO will tell you when that point arrives, and help you hire your own replacement.