The proposal looks reasonable until you hit the last paragraph: a three-month minimum commitment, paid whether or not it works out. Your instinct is to push back. You have not worked with this person, you do not know if the fit is right, and now they want a quarter of your runway locked up before you have seen a single thing shipped. So is the minimum a fair ask, or a red flag?
The short answer: a short minimum is normal and usually in your interest. A long one, or one with no exit, is where you push back. The length and the exit terms matter far more than the existence of a minimum at all.
Why a minimum exists in the first place
A fractional CTO is not selling hours. They are selling the ramp-up cost of understanding your business, your codebase, your team, and your decisions well enough to be useful. That ramp is real and it is front-loaded.
In practice the first month is mostly learning. They are reading the code, sitting in on your calls, mapping who does what, and finding the fires. The output in month one is thin on purpose, because a fractional CTO who starts making big calls in week two without understanding the context is the more dangerous hire, not the safer one. The value shows up in months two and three, once the context is loaded.
If there were no minimum, the incentive structure breaks. A founder could hire, extract the month-one audit, and leave before paying for any of the judgment that the audit was supposed to inform. Good operators have been burned by exactly that, so they price a floor in. A three-month minimum is them saying: give me long enough to actually be worth the money.
There is also a scheduling reality. A fractional CTO runs a small number of engagements at once, often three or four. Taking you on means turning down or delaying someone else. A one-month tryout that evaporates leaves a hole in their book they cannot easily refill. The minimum compensates for that risk.
What a fair minimum looks like
Length is the first thing to check. Three months is standard and defensible. Six months as a hard minimum is aggressive for a first engagement and worth negotiating down. Twelve months with no exit is a full-time contract wearing a fractional label, and you should treat it as one.
The exit terms matter more than the number. A fair three-month minimum still has a way out if things are clearly wrong. Look for one of these:
A notice period instead of a hard wall. Many engagements use a 30-day notice rather than a locked term. You can leave any time, you just pay for the next 30 days. That is cleaner than a fixed minimum because it protects both sides without trapping either.
A defined off-ramp inside the minimum. Some contracts keep the three-month term but add a two-week or 30-day mutual break clause for cause, so a genuine bad fit is not a hostage situation.
A paid pilot before the minimum starts. A two-week or one-month paid trial that precedes the longer term lets you both test fit before committing the quarter. If a fractional CTO offers a paid trial, take it over arguing about the minimum. It solves the same problem with less friction, and it is a good sign about how they work.
What you do not want: a long minimum, full payment up front, and no exit clause of any kind. That combination transfers all the risk to you and tells you the person is more worried about locking in revenue than about earning the renewal. The best operators expect to earn month four by being useful in months one through three, not by contract.
How to negotiate it
Do not argue the minimum away. Reshape it. Three moves work:
First, ask for a paid trial in front of the term. "Happy to commit to three months. Can we do a paid two-week pilot first so we both know the fit is right?" A confident operator says yes.
Second, convert a hard minimum into a notice period. "Instead of a locked three months, can we do a rolling engagement with 30 days notice either way?" This gives them revenue predictability and gives you an exit.
Third, tie the commitment to a deliverable, not just time. If the first month is an audit and a plan, agree that the minimum only continues if that plan lands and you both agree it is worth executing. That reframes the minimum as a checkpoint, not a cage.
If the answer to all three is a flat no, that is information. A fractional engagement is a relationship built on the person wanting to keep earning your business. Someone who needs a long lock with no exit is not betting on their own value, and that is the opposite of what you are paying for. Before you sign anything, it is worth a short call to pressure-test the terms and the person behind them; a conversation about the exit clause tells you more than the rate does. You can book a call to talk it through or read how we scope a fractional engagement so the term and the work actually match.
FAQ
Is a three-month minimum for a fractional CTO normal?
Yes. Three months is the most common minimum and is usually reasonable, because the first month is mostly ramp-up and the value lands in months two and three. Six months or longer as a first commitment is worth negotiating down, and twelve months with no exit is effectively a full-time contract.
Can I get out of the minimum if it is not working?
It depends on the exit terms, which matter more than the length. Look for a notice period, a mutual break-for-cause clause, or a paid pilot in front of the term. Avoid any deal that combines a long minimum, full up-front payment, and no exit clause.
Should I pay the full minimum up front?
No, not as a rule. Standard practice is monthly billing across the minimum, not a lump sum. Full payment up front shifts all the risk to you and removes the operator's incentive to keep earning the engagement each month. See how payment terms usually work.
What if they offer a paid trial instead?
Take it. A paid two-week or one-month trial before the minimum solves the fit-risk problem more cleanly than arguing about term length, and an operator who offers one is showing confidence in the work.