Founders almost always open the pricing conversation the same way: how many days a month do we need? It is the wrong first question, but it is wrong in a useful way, because the right answer tells you a lot about your stage. Days are an output of the engagement, not an input to it. Start with what you need decided and the days fall out of that.
Why days are the wrong unit
A day of a fractional CTO is not a day of work in the way a day of an engineer is. Much of the value is decisions, reviews, and direction, which take little calendar time but carry enormous weight. Two well-placed days a month spent on the right architecture call and the right hire can be worth more than twenty days of someone present but not deciding anything.
If you anchor on days, you end up buying availability and then trying to fill it, which is how a focused engagement turns into expensive busywork. Anchor on the decisions and the cadence the work actually requires, and the number of days becomes a consequence rather than a guess.
What actually drives the number
Three things set how much of a fractional CTO you need: the decision load, the team's maturity, and the phase you are in.
Decision load
How many consequential technical decisions are in front of you in the next quarter? A company that has settled its architecture, has a steady roadmap, and just needs a senior sounding board has a light decision load. A company mid-platform-migration, hiring three engineers, and answering investor diligence has a heavy one. The heavier the load, the more days, because each real decision needs context, framing, and follow-through, not just a verdict in a meeting.
Team maturity
A team with a strong senior engineer who can execute needs the fractional CTO mostly for direction and the occasional hard call. A team of capable but junior builders needs more hands-on involvement, because direction without enough support does not turn into shipped work. The gap between what the team can run on its own and what the moment demands is most of what you are filling.
Phase
Engagements are heaviest at the start and around big events. The first month is always more intensive, because the fractional CTO is building context, auditing what exists, and setting direction. A fundraise, a migration, or a key hire spikes the load too. A steady-state advisory relationship between those events is lighter. Sizing for the average instead of the peaks, with room to flex up when an event hits, is usually the right structure.
The ranges I see in practice
With the caveat that the decisions drive it, here is the rough shape of the market in 2026.
Light: advisory and sounding board
Roughly one day a week, often less, in the range of a few thousand dollars a month up to around $8,000. This fits a company with a solid team that needs senior judgment on the occasional big decision and a steady hand to check direction. The value is concentrated in a few high-stakes moments rather than spread across the week.
Standard: embedded part-time leadership
Around two days a week, commonly landing near $10,000 to $15,000 a month, which is where most growth-stage B2B engagements settle. The fractional CTO owns technical direction, is in the room for the decisions that matter, manages vendor relationships, and is close enough to the team to keep delivery honest. This is the most common shape because it covers the real leadership load without paying for a full-time seat.
Heavy: near-full-time, usually temporary
Three to four days a week, priced accordingly. This is right during an intense phase, a migration, a turnaround, a fundraise, or while you search for a permanent hire. It is rarely the right steady state. If you genuinely need someone four days a week indefinitely, that is often the signal you have outgrown fractional and need a full-time CTO, which I wrote about in you're not ready for a full-time CTO, here's how to know.
The honest way to size the retainer is to describe the next quarter, list the decisions and events in it, and let that set the cadence. Then revisit it, because the right number changes as you move between phases. That flexibility is the whole point of the model, and it is part of why I bill the way I do rather than by the hour, which I explain in why I don't bill by the hour.
If you want help translating your next quarter into the right cadence and a fair number, that is a short conversation worth having.
FAQ
What is the most common engagement size?
About two days a week, often priced near $10,000 to $15,000 a month for growth-stage companies. It covers technical direction, the decisions that matter, and vendor oversight without paying for a full-time seat.
Should the first month be bigger?
Almost always. The opening weeks carry the heaviest load because the fractional CTO is building context, auditing what exists, and setting direction. Plan for a more intensive start that settles into a lighter steady state.
What if my needs change month to month?
Build flex into the agreement so the cadence can rise around events like a fundraise or migration and fall in steady periods. Sizing for the peaks wastes money; sizing for the average with room to flex is usually right.
When do days stop being the right model?
When you genuinely need someone three to four days a week with no end in sight. At that point you are paying near full-time money for a part-time arrangement, and a permanent CTO is usually the better answer.