How fractional CTO engagements are structured and priced

The first question I get from a founder is usually "what does it cost." The honest answer is that it depends on the shape of the engagement, and the shape matters more than the number. Two fractional CTOs can quote the same monthly figure for completely different amounts of work and accountability. This post explains the structures I use and see, what moves the price inside each one, and how to read a proposal so you are comparing the right things.

I am not going to publish rates here. Pricing for my own engagements is in the written proposal, because it depends on scope. What follows is the general shape of the market as I have experienced it from both sides.

The four common models

Days per week, scoped by the quarter

This is the default for ongoing fractional CTO work and the one I use most. You agree on a fixed number of days per week, typically one to three, on a fixed schedule. The engagement is scoped for a quarter with a 90-day plan, and it renews if the results say it should.

What you get is a leader who is predictably present. Engineers know which days the CTO is in. Leadership meetings have a technical executive in the room. Decisions do not wait two weeks for a call. The 90-day plan has owners and checkpoints, so both sides can tell whether it is working.

Pricing is normally a flat monthly amount tied to the number of days. More days costs more, and the daily rate often drops a little as days go up because the context switching cost goes down.

Monthly retainer for availability

A retainer buys access rather than fixed days. The company pays a flat monthly fee, and the fractional CTO is available for a set range of hours, meetings and reviews, with a cap. This suits companies that need a senior technical voice on call: reviewing a vendor contract, sitting in on a board prep, pressure testing a hire, answering the question that would otherwise sit unanswered for a week.

The risk with retainers is that they drift. Either the company underuses it and resents the fee, or overuses it and the fractional CTO resents the hours. Good retainers define what is included, what triggers additional billing, and a monthly check on whether the shape still fits.

Project based

A defined outcome with a start and an end. Technical due diligence before a raise or acquisition. A 90-day stabilization plan for a team in trouble. An architecture review and migration plan. A SOC 2 readiness program. Setting up AI and agentic engineering practices across a team.

Projects are priced as a fixed fee or a fixed fee per phase, with scope written down tightly. The advantage is clarity: you know what you are buying and what it costs. The disadvantage is that real engineering problems rarely stay inside the box, so good project proposals say what happens when the scope changes.

I describe the project and advisory side of my own practice on the CTO consulting page.

Advisory hours

A few hours a month with a founder or an engineering leader. No operational authority, no team management, just a standing conversation with someone who has done the job. This is the lightest and cheapest model and it is often the right one for a technical founder who does not need a CTO but wants a peer.

Advisory is usually a flat monthly fee for a small block of hours, or a package of sessions. Expect it to be clearly bounded, because the moment an advisor starts running meetings and reviewing pull requests, it has become something else and should be priced as such.

Interim is priced differently

An interim CTO or VP of Engineering is full time on a fixed term, usually covering a departure. It is priced closer to a full-time executive on a monthly or daily basis, often with a premium for the short notice and the exclusivity. If your head of engineering just left and you have forty engineers, this is the shape you need, and fractional pricing will not describe it. I covered how to tell the two apart in fractional CTO vs full-time CTO vs VP of Engineering.

What moves the price

Inside any of these models, a handful of things drive the number.

Days and hours. The obvious one. Three days a week is roughly three times one day, with some discount for continuity.

Scope of authority. Owning decisions and managing people costs more than advising. If the fractional CTO is accountable for hiring, delivery and reliability, they are carrying executive risk and will price it that way.

Team size and complexity. A five-person team on one product is a different job from a forty-person org across three codebases with a compliance deadline. The second needs more preparation time outside the billed days.

Urgency and state. A team in a stable state with a clear roadmap is cheaper to lead than one in the middle of an outage streak or a failed migration. Turnarounds take more hours than the schedule says.

Hands-on expectation. If you want the fractional CTO writing production code and reviewing every significant pull request, say so, because it changes the hours and the kind of person you need. I do both, and it is in my proposals explicitly.

Experience. Someone who has run a 100-person org and been through diligence, acquisitions and compliance programs will cost more than someone two years out of their first lead role. Whether that premium is worth it depends on whether you expect to face those situations.

Equity

Some fractional CTOs take part of their fee in equity, usually at early stage. My view is that equity should be a supplement for a real commitment, not a replacement for cash, because a fractional leader who is paid mostly in equity has every incentive to spend their time on the clients who pay cash. If equity is on the table, keep the cash component honest and treat the equity as alignment, with vesting and a clear definition of what the role is.

What a good proposal contains

Whatever the model, a proposal you can evaluate has these parts in writing.

1. The goal of the engagement in one or two sentences, in business terms.
2. Scope: which decisions the fractional CTO owns, which they advise on, and which stay with the founder or team.
3. Cadence: days or hours, which days, and how urgent issues outside those days are handled.
4. The 90-day plan or the project phases, with owners and checkpoints.
5. The metrics both sides will look at when deciding whether to renew.
6. Price, billing cadence, and what triggers a change in price.
7. Term, notice period, and how handoff works when it ends.

If a proposal is a number and a paragraph, ask for the rest. The missing parts are where engagements go wrong.

How to compare two offers

Do not compare monthly totals. Compare three things.

Accountability. What is each person actually on the hook for. "Available for questions" and "owns delivery and hiring" can cost the same and are not the same.

Mechanisms. Does the proposal describe what the team will have at the end that it does not have now: an operating rhythm, a plan, release discipline, dashboards, a hiring loop. A fractional CTO who is not there every day has to leave mechanisms behind, and the proposal should say which ones.

Exit. What happens in month four if you want to hire full time. The right answer is that the fractional CTO helps you hire and hands off. If the proposal makes leaving hard, that tells you something.

How I structure mine

For the record: my ongoing engagements are one to three days a week, scoped by the quarter, with a 90-day plan written in the first two weeks. Project work is fixed scope with a written definition of done. Advisory is a small monthly block of hours. Every engagement starts with a short written proposal that covers scope, cadence and pricing before any work begins, and every engagement has a clear handoff path to a full-time leader when the company is ready. The details are on the fractional CTO page, the background is on my resume, and the fastest way to get a proposal is to send the goal and the constraint through the contact page.

Frequently asked questions

How are fractional CTOs usually paid?

Most commonly a flat monthly fee tied to a set number of days per week, billed monthly. Project work is usually a fixed fee or a fee per phase. Advisory is a smaller monthly fee for a block of hours. Hourly billing exists but is less common for ongoing leadership work because it rewards time rather than outcomes.

How long does a fractional CTO engagement last?

Ongoing engagements are typically scoped by the quarter and renew as long as the results justify it. Many run for a year or more. Project engagements run for the length of the project, often one to three months. A good engagement also has a defined handoff when the company is ready for a full-time leader.

Do fractional CTOs take equity?

Some do, usually at early stage and usually as a supplement to cash rather than a replacement for it. If equity is part of the deal, keep the cash component realistic, define vesting, and write down what the role actually is so the equity is tied to a real commitment.

What should be in a fractional CTO proposal?

The goal in business terms, the scope of decisions the CTO owns, the cadence, a 90-day plan or project phases with owners and checkpoints, the metrics used to judge renewal, the price and billing terms, and how the engagement ends and hands off.