If your fractional CTO is not working out, the engagement ends one of four ways: you fix it, you restructure the scope, you replace the person, or you hire a full-time CTO. Most of the time the first or second is enough, and ending it is the last resort. One disclosure: HighCircl places this kind of role, so we have an interest in the replace option. We'll say plainly when it isn't the right one. Nothing here is legal advice. For the wider set of decisions at this stage, see our startup scaling guides.
How do you tell a failing engagement from a slow one?
Look for what you can observe without reading a line of code. The table below is our judgment, built partly on symptoms published by others and attributed where they come from.
| Symptom | What it usually means | First test |
|---|---|---|
| Nothing you can name shipped in the last 30 days | Advisory-only engagement, or too few hours | Ask for the last three things delivered, with dates |
| Advice and documents, no working software | Delivery was never assigned to anyone | Ask who owns delivery of each recommendation |
| Rescheduled calls, slow replies | Overcommitted to other clients | Check the hours in your agreement against hours worked |
| Reluctance to define success metrics | No accountability, or no clear scope | Ask for three reviewable measures for the next 90 days |
| They are the only one who understands the system | Dependence on them instead of your team | Ask for the architecture written down |
| Your team gets blamed for missed milestones | A gap between strategy and execution | Ask the team separately what blocked them |
| Nobody else reviews their technical decisions | No independent check | See step 3 below |
Get A Fractional, an advisory site, lists unavailability, overcommitment, avoiding accountability metrics, all talk and no deliverables, creating dependency, and blaming your team as its red flags. EltexSoft, which sells a competing model (CTO-as-a-Service), calls an advisory-only engagement "an expensive opinion": documents, no shipped software, and a title without accountability. Eric Brown's guide to when to hire a fractional CTO adds a warning sign you can test in one meeting: vague answers on hours, deliverables and handoff.
Fractional CTOs usually lead rather than write production code, so the question is who owns delivery.
One symptom isn't a verdict. Three of them together, with dates, is a pattern.
Is it the person, the scope or the contract?
Most failures we'd expect to see are scope failures, not person failures. That's our judgment, not a measured rate, and we found no published failure statistic we could verify. Before you blame the person, test four things.
Hours against the work. Amazing CTO, a fractional CTO vendor, says on its fractional CTO page that most engagements begin at one day a week, scaling to two or three for launches or due diligence, and lists EUR 6-20k a month. A founder who expects a full-time CTO's output from one day a week has a scope problem, and swapping the person won't fix it.
Authority. Can they cut scope, say no to a feature or reassign work? A CTO with accountability but no authority will look like a bad CTO.
Availability. If your outages happen at 2am and their calls happen on Thursdays, write the response window into the agreement.
Conflict of interest. If they also sell development services or have ties to the agency building your product, their recommendations aren't neutral. That one is about the person, and it may justify ending the engagement, depending on your contract and whether it was disclosed.
How to run the fix, from diagnosis to handover
The five steps below run in order. Steps 1 to 3 take about 30 days, which is the window Get A Fractional recommends giving someone after you raise the problem.
1. Diagnose with a dated log
Write down what was promised, what was delivered and when, for the last two months. Use the table above. If you can't produce a log, you have a feeling, and a feeling doesn't survive a hard conversation. Also pull out your contract and find three things: the notice period, the hours, and who owns the work product.
2. Have the milestone conversation
In week 1, talk directly, with the written list in front of you. Lead with the pattern, then ask what's in the way. The answer sorts the problem into hours, authority, skill or commitment, and each needs a different fix.
In weeks 1-2, agree three milestones with a visible result, a date and an owner. "Staging environment rebuilt and documented by the 14th" can be met or missed. "Improve engineering velocity" can't. Get them in writing and send them as a follow-up email.
3. Get an independent check
You can't tell whether a milestone was really met, so have someone who can. Commission a scoped one-off technical review from a senior engineer with no stake in the outcome, and ask for a short written report: is working software shipping, are the architecture decisions sensible for your size, and could someone else pick this up tomorrow? Tell your fractional CTO the review is happening. Doing it behind their back turns a delivery question into a trust question. The same 30-day approach for a co-founder uses the same move, minus the equity questions that don't apply to a contractor.
In weeks 3-4, review against the milestones: met, partly met, missed. Two met and one partly met is a recovery. Three missed, matching your log, is an answer.
4. Choose: exit or restructure
If the review shows real work and the problem was hours or scope, restructure (more days, a narrower remit, an engineer to carry the build). If it shows little happening, end it.
For the exit, Get A Fractional's sequence is to use the termination clause, ideally 30 days' notice. It also lists reasons to end an engagement immediately: a confidentiality breach, misrepresented qualifications, an ethical lapse or conflict of interest, and repeated missed commitments. Whether you can do either depends on your contract. Check the notice period and the termination triggers before you speak to them, and ask a lawyer if the wording is unclear. Exit terms for an interim CTO cover what to write into the next agreement.
5. Secure the handover
Before you give notice, get admin access in your company's name, not theirs:
- the code repositories and the cloud account
- DNS and domain registrar
- CI/CD, monitoring and the password manager
Then rotate credentials on the day the engagement ends, and check what your contract says about who owns what they built. Ask for a handover document covering architecture, deployment, open decisions and vendor accounts, and keep a one-week overlap if the notice period allows. If the contract is silent on ownership of their work, treat that as a gap to close now, with a lawyer.
Should you replace them, restructure or hire full-time?
| Situation | Option |
|---|---|
| Right job, wrong person (misrepresented skills, conflict of interest, no ownership) | Replace |
| Wrong hours or wrong scope, person is sound | Restructure |
| You can now fill 30+ hours a week of CTO-level work, or need someone daily | Hire full-time |
| Product is stable, engineering team is growing, you need someone in the room daily | Hire full-time |
| Nothing shipped and your team can't say what they'd do differently | Fix the brief first, then decide |
In our judgment, restructuring is often enough. A new fractional CTO on the same vague brief will produce the same result with a different name on the invoice.
Going full-time is the planned outcome of many engagements rather than a failure. Amazing CTO says the goal is to grow internal leadership or hire a full-time CTO, and TechCXO, another vendor, says a fractional CTO can help define the job spec for the permanent hire. TechCXO also claims a fractional CTO starts in days, against a six-month executive search for a full-time one. Treat that as a vendor claim, but the direction is sound: you may need cover while the search runs.
What this means for your team and hiring decision
Don't sign another retainer until you can name the job it must do and the output you expect in 90 days. The figures below show what waiting can cost. EltexSoft's illustrative example is about $300 an hour for four hours a week, roughly $14,000 a quarter with no shipped product. It's the author's example, not a survey. Our arithmetic, not Amazing CTO's figure: three months at the bottom of its listed EUR 6-20k a month range is EUR 18,000, and up to EUR 60,000 at the top, before the product time lost.
Keep technical access in your name regardless of who you hire next. If you've outgrown the model, the next decision is a permanent leader, and hiring a full-time CTO walks through it.
Hiring a fractional CTO through HighCircl
HighCircl doesn't publish fractional CTO rates or notice terms, so we don't quote any here. For senior engineers we shortlist 3-5 candidates within 72 hours, from roughly 1 in 10 applicants who pass four vetting stages run by senior engineers. There's no subscription, no recruitment fee and no minimum hour commitment. For senior-engineer engagements, if it isn't working we replace the engineer at no additional recruitment cost; we haven't published separate terms for fractional CTOs. See the fractional CTO hiring page.
FAQ
How long should I give a fractional CTO to improve?
About 30 days after you raise the issue (put it in writing, which is our advice). That's Get A Fractional's window, and we agree with it. Agree three dated milestones at the start and judge by those, not by how the month felt.
Can I end a fractional CTO contract early?
It depends on your notice clause, so read it before the conversation, not after. Get A Fractional recommends a 30-day notice clause and says to consider immediate termination for serious breaches such as breach of confidentiality. Your contract may differ. This is not legal advice.
What should a fractional CTO hand over when they leave?
Admin access to repositories, cloud, DNS, CI/CD and monitoring in your company's name, a document on architecture and deployment, a list of open decisions and vendor accounts, and ideally a week of overlap with whoever takes over. Rotate credentials on the last day.
Is it worth switching to a full-time CTO?
If you could now fill a full week of CTO-level work, or the team needs someone in the room daily, yes. If the problem was scope or hours, a full-time hire costs more than a fractional retainer and doesn't fix the brief, so fix the scope first.
Why do fractional CTO engagements fail?
Mostly because the brief was vague: too few hours for the work, no authority to cut scope, no defined deliverables or metrics. That's our judgment, not a measured statistic. Conflicts of interest and overcommitted advisers are the person-side causes.