A fractional CTO proposal arrives with an unusual pricing line: instead of a flat retainer, the fee is a percentage of your monthly engineering spend, payroll plus contractors plus agency plus cloud. The pitch is that the fee grows with the company and shrinks if you cut back, so it always fits. It sounds aligned. It is worth slowing down before you sign it.
The short answer: pricing a fractional CTO as a percentage of engineering spend creates a quiet incentive for the spend to grow, and the person paid that way is often the one recommending hires, vendors, and infrastructure. Most of the time the advisor is honest and the incentive never bites. But you are buying judgment, and the one judgment that matters most early on is when not to spend. A flat retainer, adjusted at review points, keeps that judgment clean.
Why the model exists
The appeal is real on both sides. For the fractional CTO, it is a simple way to scale fees with responsibility: managing a $40,000-a-month engineering budget is genuinely less work than managing a $200,000 one. For the founder, it feels like the fee can never be wildly out of proportion to the company.
Agencies and some managed-service firms use versions of it, and it borrows from older models where a project manager took a percentage of the build cost. So it is not unusual or sinister on its face.
Where the incentive points
Think about the decisions a fractional CTO actually influences in an early-stage company:
- Whether to hire the next engineer now or in two quarters.
- Whether to keep the agency or bring the work in-house.
- Whether to move to a more expensive cloud setup, or commit to a reserved-capacity deal.
- Whether to buy a tool or build it.
- Whether to rewrite or refactor.
Every one of those has a "spend more" answer and a "spend less" answer. Under a percentage model, the advisor earns more when the answer is "spend more." A good person will still give you the right answer most of the time. But you will never quite know, and neither will your board, and you have paid for advice that is harder to trust.
The worst version I have seen tied the fee to total vendor spend, including the agency the fractional CTO had recommended. The fees were not outrageous, but nobody in the room could tell whether the recommendation to expand the agency team was about the product or the invoice.
The problem runs the other way too
A percentage fee also punishes the fractional CTO for doing one of the most valuable things they can do: cut waste. If they find $8,000 a month of idle cloud capacity, or a contractor who is not delivering, or a tool nobody uses, the fix reduces their fee. Most will still do it. Asking them to do it against their own pay is not a fair setup, and over time it changes what gets looked at. The engineering tool bill nobody owns is exactly the sort of review a percentage model quietly discourages.
What fair scaling looks like instead
You can get the "fee grows with the company" benefit without the incentive problem.
Flat retainer, reviewed at milestones
Set a flat monthly fee for a defined scope. Review it at agreed points: after a raise, when the team doubles, or every six months. The fee goes up because the job got bigger, and that is a conversation, not an automatic formula.
Tiers tied to scope, not spend
Define two or three scope tiers, for example advisory, working, and team-leading, with a fixed price for each. Moving between tiers is a decision you both make. What a fractional CTO retainer actually buys each month is a good way to define what each tier should contain.
Disclosure of any vendor interest
Whatever the pricing, the contract should require disclosure of any referral fee, equity, or other interest in a vendor they recommend. That one clause removes most of the conflict risk in any model.
If you are already on a percentage model
You do not need to tear it up. Three practical steps:
- Separate recommendation from approval. Major spend decisions, a new hire, a new vendor, a cloud commitment, get a short written case that you or a board member approves.
- Cap the fee. Agree a ceiling so that a large hiring round does not automatically produce a large fee jump.
- Convert at the next review. Use the next renewal to move to a flat retainer at roughly the current level, and say why: you want advice that is clearly independent of the budget.
None of this assumes bad faith. It is the same reason audit firms are not paid a percentage of the revenue they audit. The structure should make honesty easy, not heroic.
How I price it
I use flat retainers tied to scope, reviewed at agreed points, and I disclose any relationship with a vendor I recommend, which in practice is none. My own terms are on the pricing page. If you are looking at a proposal with an unusual fee structure and want a second view, comparing two fractional CTO proposals walks through the rest of the checklist, or book a call and we can go through it together.
FAQ
Is it common to pay a fractional CTO a percentage of engineering spend?
It is uncommon. Most fractional CTOs charge a flat monthly retainer or a day rate. Percentage models appear more often with agencies and managed-service firms.
Why is a percentage-of-spend fee a problem?
It ties the advisor's income to how much you spend on engineering, while they are advising you on hiring, vendors, and infrastructure. It also reduces their fee when they cut waste.
How should a fractional CTO's fee scale as we grow?
Through a flat retainer reviewed at milestones, such as a raise or the team doubling, or through fixed-price scope tiers you move between deliberately.
What clause should any fractional CTO contract include about vendors?
A requirement to disclose any referral fee, equity, or financial interest in a vendor they recommend.