To hire a fractional CTO, start with the decisions you want owned, not the hours you want filled. Write down the one outcome the first month must deliver. Ask each candidate what they would decide, what they would leave alone, and what you would hold in writing at the end. Agree a capped scope before anyone starts. Walk away from anyone selling developer hours under a CTO title.
That last point matters more than it sounds. A lot of what is sold as “CTO as a service” is a development company’s sales channel: the CTO time is how they sell you a team. A fractional CTO you can trust is the one who will sometimes tell you not to build anything at all.
Do you need a fractional CTO?
You probably need one if technology decisions keep landing on your desk and you are not sure you are making them well. Typical signs:
- You have developers or an agency, but nobody decides what they build next. The team waits for you, or builds what is easiest.
- A build is late, over budget or fragile, and adding more people hasn’t helped.
- You are about to buy or build something significant, such as a CRM, a platform or an AI tool, and want an independent view first.
- Tools have piled up, costs keep rising and nothing quite connects.
- Investors, buyers or a big customer ask technical questions you can’t yet answer with confidence.
You probably don’t need one yet if you have one simple website and a standard tool for each job, and none of it is causing problems. You may need a good developer, not a CTO. And if your software is the product and technical decisions arrive every day, you may need a full-time CTO, not a fractional one. More on that below.
Where to find a fractional CTO
Most good fractional CTOs are found through people you trust: other founders, your accountant, an investor or an adviser. Beyond referrals, LinkedIn and fractional-executive directories let you see a person’s background and what they write about.
Wherever you find them, check which of three kinds of provider you are talking to. Each has a place, but they make money in different ways.
| Provider | How they make money | Best when |
|---|---|---|
| Independent fractional CTO | Their own time and judgement | You need decisions made and someone accountable for them, without a build team attached |
| Development company offering “CTO as a service” | Mostly the developer hours that follow | You have already decided to build and want one supplier to run it |
| Recruiter or marketplace | A placement fee or margin on the hours | You want a shortlist quickly and will judge the people yourself |
None of these is wrong. The risk is not knowing which one you are dealing with, because advice from someone who earns more when you build more is not neutral advice about whether to build.
Ten questions to ask before you hire a fractional CTO
- What would you decide in the first month, and what would I have in writing at the end of it? You want a clear answer, not “it depends on discovery”.
- Do you or your company sell development work? If yes, ask how they keep the advice independent.
- Tell me about a time you advised a client not to build or buy something. A good answer names the decision and the reason.
- Which decisions have you owned yourself, start to finish? Ask for the outcome and what changed, not a list of technologies.
- How do you price, and is there a cap? Hours, a day rate or a retainer can all work, if you know the maximum before you commit.
- What is the minimum term and the notice period?
- How many hours a month would my situation need, and why?
- How will you work with my existing developers, agency or suppliers? A fractional CTO should make them more effective, not replace them by default.
- Who will own the accounts, code, documents and passwords you create or change? The only good answer is “you do”.
- What would make you tell me I don’t need you any more, or that I need a full-time CTO?
Fractional CTO red flags: when to walk away
Most fractional CTOs are honest. When a hire goes wrong, though, the warning signs were usually there before the contract was signed:
- The CTO title is a front for developer hours. Every problem leads to “our team can build that”.
- No written output from the first piece of work. If a month ends with meetings but no decisions on paper, you can’t judge what you paid for.
- No cap, or a long lock-in. An open-ended monthly retainer with a three- or six-month minimum before you have seen any work.
- They won’t say what they would leave alone. Someone who never recommends doing less is unlikely to be working in your interest.
- They can’t show decisions they have made. Titles and tool lists, but no example of a decision and what it changed.
- They want to hold your accounts or your code. Domains, cloud accounts, repositories and admin logins should be in the business’s name, with access given to them, not the other way round.
- Pressure to commit before a scope exists. “Sign the retainer and we’ll work out the details” is the wrong order.
None of these needs a long investigation. Ask the ten questions, and the answers will usually tell you.
The first-month scope you can copy
Before you sign, agree one page like this. It works as a fractional CTO scope of work, and it is what any contract should attach. Copy it, fill in the middle column, and ask each candidate to complete it with you.
| Item | Write down | Example |
|---|---|---|
| Outcome | The one result the first month must deliver | A decision on whether to rebuild the booking system or fix the current one |
| Decisions owned | What the fractional CTO decides, and what stays with you | They recommend the option and the supplier; you approve the spend |
| Written outputs | What you hold at the end, in writing | A one-page decision with the reasons, a fix-first list, and a brief your developers can build from |
| Hours and cap | Estimated hours, the rate, and the maximum you will pay | 15 hours estimated, capped at 18 |
| Access needed | The systems, people and documents they need, in your name | Read access to the code repository and hosting account; an hour with the lead developer |
| Your contact | Who on your side answers questions and approves decisions | The founder, with the operations manager for day-to-day questions |
| Review date | When you will look at the outputs together and decide what comes next | Four weeks from the start date |
| Exit terms | Notice period, and what is handed back when the work ends | No minimum term; all documents and access handed back within a week |
If a candidate can’t help you fill this in, or resists putting a cap on the hours, you have learned something important before spending anything. Bring your draft to a free 30-minute review, and within a few hours you get a written list of what to fix first.
What a fractional CTO costs
Fractional CTOs charge by the hour, by the day or by monthly retainer, and published rates vary widely by market. For current UK and India ranges, and how they compare with a full-time hire, see what a fractional CTO costs in India and the UK.
At Your Tech Chief, you pay for the hours your scope needs: ₹5,000 an hour in India or £100 an hour in the UK. After a free 30-minute review, you get a written fix-first list and a fixed, capped quote for the first fix, so you know the maximum before you commit. After that, you pay for the hours you use, with no retainer and no minimum term.
From fractional to full-time
A good fractional engagement should leave you free to stop, carry on, or turn it into something bigger. In 2022 I was brought in as an external CTO on a UK council children’s-services platform that had stopped moving. It reached a secure production release in about three months, and the client’s CEO then hired me as Head of IT.
That is the path to look for: start with one scoped piece of work, judge it on what it delivered, and decide from there. I have led technology for 10+ years, as a CTO in India from 2017 to 2024 and then for UK public-sector and AI platforms. More about how I work.
When this doesn’t apply
If your software is the product, you have a growing engineering team, and technical decisions arrive every day, a fractional CTO is a stopgap at best. Hire a full-time CTO, or look for a technical co-founder. A fractional CTO can still help you write the role and interview candidates, but shouldn’t be the long-term answer.
And if what you are really deciding is whether to buy one piece of software, you may not need a CTO at all yet. Start with the decision itself: what to automate in your business, and what not to.
Questions founders ask about hiring a fractional CTO
How do I hire a fractional CTO?
Decide the one outcome the first month must deliver, then talk to two or three candidates found through referrals, LinkedIn or fractional directories. Ask what they would decide, what they would leave alone and what you would hold in writing, check whether they sell development work, and agree a capped first-month scope before you sign.
What should a fractional CTO contract include?
A clear scope: the outcome, the decisions the CTO owns, the written outputs, the estimated hours with a cap, the access needed, a review date and the exit terms. It should also say that all accounts, code and documents belong to your business, and set a short notice period with no long minimum term.
What are the red flags when hiring a fractional CTO?
Watch for a CTO title used to sell developer hours, no written output from the first piece of work, no cap or a long lock-in, unwillingness to say what they would leave alone, no examples of decisions they have owned, and any request to hold your accounts or code in their own name.
How many hours a month does a fractional CTO need?
It depends on the scope, so ask for an estimate with a reason. A first piece of work often takes 10 to 20 hours. Ongoing months vary with the decisions in front of you, which is why a monthly cap agreed in advance is more useful than a fixed number of days.
Should I hire a fractional CTO or a full-time CTO?
Hire a fractional CTO while technology decisions come in bursts and you need senior judgement without a full-time salary. Hire a full-time CTO once your software is the product, your engineering team is growing and decisions arrive every day.