How to hire a fractional CTO: the playbook

How to hire a fractional CTO without buying advice you cannot use

Most founders try to hire a fractional CTO using the same checklist they would use for a full-time engineering leader. That is the first mistake. You are not assessing someone who will sit in the building every day, sit in stand-ups, and own a team over years. You are assessing someone whose accountability is a built outcome on a compressed timeline. The model is different, so the evaluation has to be different too. The questions that surface a genuine builder are not the questions that surface a good full-time hire, and the people who answer well on the full-time test are often the same advisors who will charge you a retainer and never write a line of production code. The process below is built to separate the two before you sign anything.

Define the problem before you define the role

Most job descriptions for this role list outputs: "technology vision," "engineering oversight," "AI strategy." Those are the things a good engagement produces, not the brief you hire against. The more useful starting point is the specific problem costing you revenue right now. Are you making technology decisions without the right context? Are your developer costs climbing without any matching gain in product stability? Do you have manual workflows eating team hours that should already be automated? Are you about to raise and unable to answer technical due diligence cleanly? Write down the three most expensive technology problems in the business. That list, not a generic role spec, is the brief for the person you are about to hire.

Ask what they will build in the first 30 days

This is the single most useful question in the whole evaluation. A real fractional CTO should be able to tell you, in concrete terms, what system will be live in your production environment within 30 days of starting. "A WhatsApp qualifier that handles cold inquiries in English and Arabic, routes qualified leads to your booking calendar, and logs everything to your CRM" is a specific answer. "We will develop an AI-enhanced customer engagement workflow aligned with your business objectives" is a red flag wearing a suit. If they cannot commit to a concrete deliverable before starting, ask them to walk through the first week instead: what they audit, the three candidate systems they would consider, and the decision framework for choosing which one to build first.

Check for named outcomes, not general experience

Ask for specific results from previous clients. Not sector familiarity. Results. "We moved a regional hospitality group's direct booking rate inside 60 days by building a WhatsApp qualifier" is a result you can probe. "We have worked extensively in hospitality and understand the operational challenges" is marketing copy. Anonymised specifics are acceptable. Named clients are better. Vague sector claims, with no metric attached, are the tell of someone who advised on projects rather than built them. When you hear a result, ask the follow-up: what did you personally build, and how was the number measured? The answer separates the operator from the slide deck quickly.

Evaluate the vendor conflict question

Ask directly: do you have any commercial or affiliate relationship with the tools you might recommend for this engagement? A legitimate fractional CTO will give you a clean answer. Any hesitation or qualification here is worth investigating before you go further. This matters because a fractional CTO with a financial stake in a particular platform will recommend that platform whether or not it fits your stack, and the most expensive architecture decisions usually arrive disguised as ordinary vendor choices. You want someone whose only incentive is the outcome you are paying for, not a referral fee sitting quietly behind the recommendation.

Understand the commitment structure

A genuine engagement is structured on monthly commitments with 30 days notice. That structure protects you, the client: if the first month does not produce a delivered system, you can walk. It also signals confidence from the fractional CTO that their work is visible and judged quickly. Multi-month minimums and large upfront commitments protect the consultant, not you. Be cautious about any arrangement that asks for six months of payment before you have seen a single built output. The shape of the contract tells you who the contract is really designed to protect.

The four interview questions that expose advisors

Beyond the first-30-days question, four more questions separate people who build from people who call themselves builders. Use them in order and listen for specifics, not polish.

"What was the last system you personally wrote the code for?" Someone genuinely building will have a specific, recent answer. If the last personal build was two years ago, you are talking to an advisor who has drifted out of the work.

"Walk me through the last technology decision where you recommended against a tool the client wanted." This tests whether they make independent calls or simply validate whatever the founder already prefers. A fractional CTO who only ever agrees is not doing the job you are paying for.

"What SaaS rationalisation did you do for your last client, and what did it save?" Most real engagements find redundant software spend in the first month. If they have never done this, they have never run a real audit.

"What is your process when the founder disagrees with your architecture recommendation?" The answer should explain how they present the reasoning and when they defer versus hold the line. Someone who always defers is selling you compliance, not leadership.

Pricing benchmarks for 2026

The market range for a genuine fractional CTO who actually builds code is £2,000 to £8,000 per month. Below £1,500 per month you are buying advisory calls with no build commitment attached. Above £8,000 per month you are paying near-full-time rates for part-time access. For context on where a full-time hire makes more sense, a permanent CTO earning £150,000 to £220,000 a year fits a business with enough technical surface area to need daily architecture decisions and a managed engineering team. The full breakdown of who needs which model is in our guide on the fractional CTO vs full-time CTO decision, and the wider market comparison sits in our fractional CTO cost analysis.

How twohundred approaches a fractional CTO engagement

If you want the operator view, here is how we run it at twohundred. The first week is a technology audit: the stack, the deployed systems, the vendors, the data pipelines, the backlog, the team skills, and the commercial scorecard. The second week is decisions, what to stop, what to build, what to keep, what to kill. The third week is the first live deliverable, usually a small and measurable system tied to a real revenue or cost lever. The fourth week is the review and the shape of the next 90 days. Pricing is structured so the build commitment is never theoretical: Foundation at £2,000 per month, Growth at £3,500, Dominance at £5,000, with every tier writing production code in the first month. That is the standard to hold any candidate to, ours included. You can see the full engagement model on our fractional CTO services page.

Frequently asked questions

Where do you find a good fractional CTO?

The most reliable channel is a referral from a founder who has actually worked with one and can point to a built system. Searching for "fractional CTO" on LinkedIn returns a mix of genuine builders and advisors, and the signal-to-noise ratio is poor. The faster filter is the evaluation itself: the first-30-days question and the named-outcomes question separate the two within a single call, long before you waste time on a trial month.

How long does it take to hire a fractional CTO?

If you run the evaluation above in a single 60-minute call, you can decide in the same week, and the engagement can start the following Monday. There is no recruitment funnel, no notice period, and no onboarding theatre. A legitimate fractional CTO is embedded inside your team within five working days. The speed is part of the point: the model only works if value shows up fast enough to judge inside the first billing cycle.

What happens if the fractional CTO does not deliver?

With a monthly commitment structure the exit is clean. If the first month does not produce a built system and a clear audit of the highest-impact next steps, you terminate with 30 days notice and your total exposure is one month of fees. This is exactly why you should refuse long upfront commitments. The whole advantage of the model is that you can verify the work before you keep paying for it.

How do you know the engagement is actually working?

Three signals give an honest read. First, whether built systems are live and the commercial metric they target is moving. Second, whether the team around the CTO is making better technology decisions without waiting for input. Third, whether the CTO is used more as a decision-maker and less as an executor as the months pass. If the executor share is rising instead of falling, the engagement has quietly turned into a senior contractor role, and you are paying the wrong rate for the wrong work.

Related reading

For the foundations of the role, start with our pillar on what a fractional CTO is. If you want the warning signs to watch for during evaluation, read our breakdown of fractional CTO red flags, and to confirm the timing is right for your business, see signs you need a fractional CTO.

---

Related Services

For businesses working through an AI strategy before committing to a build, AI consulting services covers the advisory and planning layer. When ready to move from strategy to deployment, AI implementation services covers the full rollout.