A good fractional CTO contract is short, clear and fair to both sides. It says what you are buying, how much time, what it costs, who owns what, and how either side ends it. If a proposed agreement runs to 30 pages or leaves any of those vague, be wary. Here is what should be in it, clause by clause, what I would push back on, and the three places where things go wrong.
This is practical guidance from the engagements I have run, not legal advice. Have your solicitor look at anything you sign.
Why the contract matters more than people think
Fractional relationships fail for predictable reasons. The scope was never agreed, so the client expected more and the CTO delivered less, or the reverse. The days crept up without anyone pricing it. The exit was awkward because nobody wrote down how it would work. Almost every one of those failures was avoidable on page one.
A clear contract is also a signal. A fractional CTO who proposes a tight, plain agreement is someone who has done this before and wants the relationship to work. One who sends a vague retainer letter or a 40-page template is telling you something too.
Scope, in plain words
What the role covers and what it does not. Strategy, leadership of the team, board reporting, supplier oversight, security, hiring. Say whether hands-on development is included, because for most fractional roles it is not. Say whether the CTO attends board meetings, and how many. A clear scope stops the quiet creep where a day a week becomes three and nobody agreed to it.
A useful test. If a founder and a CTO each wrote down what the role covers, would the lists match. If not, the scope is not clear enough.
Time and availability
How many days, which days if it matters, and what happens around those. Reasonable fractional contracts include some flexibility for the odd urgent call, and say how out-of-hours or extra days are handled and charged. A common and fair arrangement is a fixed day each week, a short monthly allowance for urgent calls, and extra days at the day rate by agreement.
What they should not do is promise full-time availability for a part-time fee. Nobody can deliver that honestly, and a CTO who promises it will either burn out or quietly under-deliver.
Fees and what they cover
Day rate or monthly retainer, what is included, what is extra. Expenses, travel, software. Typical UK day rates sit roughly between £1,000 and £1,600 and retainers are usually priced on one or two days a week. The fractional CTO cost page sets out the ranges. Watch for retainers that quietly assume more days than you will use, and for ‘minimum terms’ that lock you in for a year.
Payment terms should be plain. Monthly in advance or in arrears, on what date, with what notice of a rate change. A rate that can be changed at will is not a rate.
Intellectual property
Anything created for you in the engagement, plans, documents, code if any, should belong to you. This is standard and a fractional CTO who resists it is a concern. The one fair carve-out is their pre-existing tools, templates and know-how, which they keep and license you to use. Make sure that carve-out is specific. ‘All my methodologies’ is too broad. ‘The templates listed in schedule A’ is fine.
If the CTO brings in developers or a partner firm, the IP in what they build should also flow to you, and the contract should say so, because a gap here is the one that surfaces in due diligence years later.
Confidentiality and conflicts
A clear confidentiality clause, which cuts both ways. And a plain statement on conflicts. A fractional CTO works with several businesses. The contract should say they will not work with a direct competitor without telling you, and what counts as one. Define it narrowly enough to be workable. ‘Anyone in technology’ is meaningless. ‘A business selling the same product to the same customers’ is clear.
Notice and exit
One month’s notice either way is common and fair. Longer lock-ins favour the provider. The contract should also say what happens at the end, a handover of documents and access, a short written summary of where things stand, so you are not left holding the phone to someone who has moved on.
A good exit clause also covers the accidental case. If the CTO is unavailable for an extended period, what happens. Most fractional firms have a plan for cover. Ask.
Reporting and review
How progress is reported, to whom, and how often. A short written update and a monthly review conversation is enough. A review point at three months, where either side can adjust the days or stop, is sensible and shows confidence rather than the reverse. The firms that resist a three-month review are the ones that expect you to want one.
Who does the building
If the fractional CTO will bring in developers or a partner firm for delivery, the contract should say how that works and whether any referral or commercial arrangement exists. You should always know who is doing the work and whether anyone is being paid for the introduction. We state this openly in ours, and I would expect anyone you engage to do the same. Our piece on how fractional leadership works explains the two delivery models.
What this looks like in practice
A reasonable fractional CTO agreement for a growing business might run to four or five pages. Scope, one paragraph. Days and availability, one paragraph. Fees and payment, one paragraph. IP, confidentiality and conflicts, a paragraph each. Notice, exit and handover, one paragraph. Reporting and the three-month review, one paragraph. Delivery partners and disclosure, one paragraph. A schedule listing the CTO’s pre-existing templates. Signatures.
Anyone can read that in ten minutes and know exactly what they have agreed. That is the standard.
The three places things go wrong
Vague scope. ‘Technology leadership and support’ means whatever each side wants it to mean. Write down what it covers.
Open-ended retainers. A monthly fee with no stated days, no review point and a long minimum term is a subscription, not an engagement.
Silent delivery arrangements. A CTO who steers work to a partner without disclosing the relationship has a conflict, whether or not money changes hands. Insist on disclosure in writing.
The honest trade-off
A tighter contract takes a little longer to agree, perhaps a week of back and forth. That week saves months of friction. The relationships that go wrong almost always had a vague scope, an open-ended retainer or an unclear exit, and all three are avoidable on page one.
Start the conversation on our contact page if you want to see how ours is structured, or read more about fractional CTO support in general.
Frequently asked questions
How long should a fractional CTO contract be?
Short enough to read in one sitting. Scope, time, fees, IP, confidentiality, notice and review, in plain words. Four or five pages is typical. Length is a warning sign, not a comfort.
Who owns the work a fractional CTO produces?
You should. Plans, documents and any code created for you belong to your business, with a fair, specific carve-out for the CTO’s pre-existing tools and know-how.
What notice period is normal?
One month either way is common and fair. Longer lock-ins tend to serve the provider rather than the client.
Should there be a minimum term?
A short one, perhaps three months, is reasonable so the CTO can do a proper assessment. A year is not. Pair it with a three-month review where either side can adjust or stop.
What happens if the fractional CTO is unavailable?
The contract should say. Most fractional firms have cover arrangements for extended absence. Ask what they are before you sign.
Should the contract mention delivery partners?
Yes. If the CTO will bring in developers or a partner firm, the contract should say so and disclose any referral or commercial arrangement, so you know who is doing the work and why.