Every prospect asks the same thing inside the first ten minutes. What is my day rate. For years I answered it, and the answer was a number I had triangulated from other people’s numbers. Then I ran the arithmetic on my own invoice. The median fractional CTO asks $220 an hour and works about 16 hours a week. That is $14,080 a month. Get 30% faster at the same work and the same output bills $9,856. I would have made the client better off and myself $4,224 poorer. Every month. For being good at the job.
I have priced this work three ways: by the hour, by the retained day, and by the decision. Two of those are wrong and I used both. Both price my attendance, and attendance is the input that is deflating fastest right now. The decision is the only unit that held its value, because the cost of getting a decision wrong did not fall at all.
The entire market is denominated in time
Go and read the published benchmarks. Every one of them prices a calendar.
Go Fractional’s rate page puts the median fractional CTO ask at $220 an hour, with the middle half of the market between $175 and $250. Employers post $136. Talent asks $221. That $85 gap is the whole negotiation. The typical engagement is 16 hours a week, roughly 40% of a full-time week, which lands at about $14,000 a month with retainers starting near $11,200.
Tristella’s guide, published 1 July 2026, tiers it the same way: light advisory 10 to 15 hours at $4,000 to $8,000, standard fractional 20 to 40 hours at $8,000 to $15,000, deep fractional 40 to 60 hours at $15,000 to $25,000 and up. Kompella’s 2026 guide tiers by days instead of hours: advisory at one day a week for $8,000 to $10,000, fractional at two days for $15,000 to $18,000, embedded at three or more days for $25,000 to $30,000. It notes that most B2B SaaS engagements settle at $15,000 a month for two days a week.
Read those tiers again. Not one of them describes a result. They describe a diary.
What each model does to the conversation
Hourly billing punishes the thing you are selling. I am hired because I have seen the failure mode before. Recognition is instant. Under hourly, instant recognition is a small invoice, so the honest expert is paid least for the moment they were most useful. Every efficiency gain, every tool, every year of pattern library, converts directly into a smaller bill. You cannot fix that with a higher rate, because the rate has a ceiling the market publishes and the hours do not have a floor.
The retainer is better and it fails differently. You sell two days a week for $15,000 and the first month is fine. Then the finance lead asks what they got for the money. The truthful answer is eight days. Eight days is not a result, so you start manufacturing evidence of presence. Standups you did not need to be in. A weekly deck. Slack responsiveness as a performance. The retainer quietly converts a senior operator into an attendance record, and the moment the client’s budget tightens, an attendance record is the easiest line to cut.
Both models have the same defect. They price the input. In 2026 the input is the part collapsing in cost, and the client knows it.
The third model
The market already has the shape and misnames it. Kompella’s smallest tier is project pricing: a tech debt audit at $15,000 to $25,000, a 90 day plan at $30,000 to $50,000, pre-fundraise preparation at $40,000 to $75,000, M&A integration at $50,000 to $100,000 and up. That is closer, but a project is still a scope of work. A decision is different. A decision has a date, one or two viable options, and a cost of being wrong that somebody can name.
Four decisions make up most of what I actually get hired for. Build, buy, or agency. The platform migration go or no go. The pre-raise architecture answer, which in 2026 is really the question of what happens to gross margin when the model gets cheaper. And the diligence verdict on somebody else’s technology.
Each one has a number attached to being wrong, and the number is not $15,000 a month. That is what the fee attaches to, along with the artefact that outlives the engagement: the one page scope, the model, the gate list, the thing the client still has after I leave.
This is not a theory I applied to consulting and nowhere else. D30 is forensic extraction over ASX filings, and the fee is the fact file and the eight articulation gates, not the hours spent reading the PDF. That is deliberate: the model that reads the document is replaceable and getting cheaper, and pricing the reading would have been pricing the part that goes to zero. D23 sells managed Apache Superset, where nobody pays for the software because the software is free. They pay for it to be run correctly. Same logic, applied to me.
The largest firms in the world made the same move this year
McKinsey now ties about 25% of its global fees to outcomes rather than time, reported by the Wall Street Journal on 29 June 2026. In the same period its internal assistant, Lilli, runs over 500,000 prompts a month and its consultants report time savings on knowledge work of up to 30%. BCG puts AI and tech-enabled work at roughly 20% of 2024 revenue heading toward 40% this year. Bain has it near 30% and climbing toward half.
Treat those as directional. They come from firm media events and investor briefings, not audited disclosure, and every one of them is a marketing number as much as an operating one. The direction still matters. The firms with the most to lose from abandoning the billable hour moved a quarter of their fee base off it in the same year their own tooling cut a third off the work. That is not two unrelated events.
Where this breaks
Decision pricing needs a decision. Plenty of engagements are honest capability rental: the team is competent and simply has no senior person in the room, and they need one every week for a year. There is no dated call to attach a fee to. The retainer is the correct instrument there, and pretending otherwise is a pricing model looking for a problem. Cap it and give it an exit date so it does not become tenure.
It also requires deal flow you may not have. Quoting a fee that is unanchored from your cost only works if you can absorb a no. If one client is more than a third of your revenue, you will not hold the line, and a published day rate is the more honest thing to sell.
The hardest problem is attribution. An hourly invoice settles in 30 days and nobody argues about whether the hours happened. A decision proves itself 14 months later, by which point the client remembers the outcome and not who made the call. So the fee has to land at the moment of the decision, not at the moment of the result. Charge for the outcome and you have written the client a free option on your own judgement.
What I would do on Monday
Take your last three invoices and divide each by the hours behind it. Then write down, in dollars, what the client’s cost of being wrong was on the largest call in that same period. The ratio is the argument.
Change one line in the proposal template. Delete “days per week” and put in the name of the decision and the date it has to be made by.
Name the artefact. If nothing survives your last day, you sold attendance and the invoice was correct.
Put a cap and an exit date on every retainer you currently run. Not to end them. To make renewal a decision instead of a default.
Stop answering the day rate question first. Ask what decision is waiting on you, and quote the answer to that.
The question still arrives in the first ten minutes. What is my day rate. I answer with a number now, and it is not per day.
I write this from the PADISO seat. If you need a CTO who has shipped, raised, and cleaned up after both, book a call.