Back to Blog

How to Choose a Fractional CTO for Your AI Startup

When the role genuinely helps, the three situations where it is the wrong answer, and the interview questions a candidate cannot talk their way through.

Andriy Markiv February 20, 2026 9 min read
Share LinkedIn X Facebook

 

We do this work, so take the framing with that in mind. The useful thing we can offer is not an argument for the role, it is the part of the evaluation that is hard to do from outside: what separates a fractional CTO who changes the trajectory of a company from one who produces a well received architecture document and leaves you where you started.

That difference comes down to accountability. The title is used loosely, and it covers three genuinely different things. Knowing which one you are buying is most of the decision.

What it isWhat they ownRight when
AdvisorAn opinion, a few hours a month. No decisions, no delivery.You have a capable technical lead who needs a sounding board, not a boss.
Fractional CTOTechnical decisions and their consequences. Architecture, hiring, vendors, governance.Decisions with long consequences are being made and nobody senior owns them.
Consultancy or agencyA specified deliverable, built by their team.You know what needs building and need hands to build it.

The failure mode is paying for the middle and getting the first. It is also the most common outcome, and it happens because the engagement was written in hours rather than in decisions.

First, whether you need one at all#

  1. Do you have a senior technical owner?

    Yes: you need an advisor or an engineer, not a CTO

  2. Is the spec already clear?

    Yes: you need delivery capacity, not leadership

  3. Are long-horizon decisions pending?

    Architecture, compliance posture, build versus buy

  4. Does the volume justify full time?

    Yes: hire. No: fractional is the right shape

Figure 1. The decision in order. Each question is worth answering honestly before moving right, because a yes at the first or second box means a fractional CTO is the wrong purchase and an expensive way to find out.

The signals that it is time#

  • A decision is pending that is expensive to reverseData model, tenancy model, where regulated data lives, which cloud, build or buy on something central. These are cheap to get right and very expensive to revisit.
  • You are entering a regulated marketHIPAA, GLBA, the EU AI Act, state insurance regulation, federal contracting. Compliance architecture is nearly free at the start and a rewrite later, which makes it the clearest case for senior involvement early.
  • Technical due diligence is comingSomeone will read your code, your security posture and your roadmap. Finding out what they will find before they find it is worth a quarter of senior time.
  • You are about to make your first engineering hiresThe first two hires set the standard for everyone after them. Hiring senior engineers is a skill, and getting it wrong twice costs a year.
  • Delivery has slowed with no obvious causeUsually accumulated technical debt and absent code review rather than effort. It takes someone senior a couple of weeks to find, and founders rarely diagnose it from inside.

Evaluating candidates: what to look for, and what it looks like when it is absent#

DimensionWhat good looks likeWhat to be wary of
Operating depthHas run systems in production under real constraints and can describe a specific failure and what they changed afterwards.Every example is a success. Nobody with operating experience has only those.
Regulatory experienceCan name the specific rule that shaped a design decision, and what the design would have been without it.Compliance discussed as a category rather than as named requirements.
AI implementation, not AI commentaryTalks about chunking strategy, evaluation sets, retrieval failure modes, inference cost. The unglamorous parts.Fluent on strategy and vague on how retrieval quality is measured.
Team leadershipHas hired, mentored, run code review, and let someone go. Can say what they look for in a senior engineer.A strong individual contributor record with no evidence of raising others.
TranslationExplains a technical tradeoff to you in terms of cost, risk and time without flattening it.Either impenetrable or so simplified that the tradeoff disappears.
CapacityWill tell you how many other clients they have and which days are yours.Evasiveness here. Six simultaneous engagements means you have bought an advisor.

Five questions worth asking#

Generic interview questions get generic answers. These are the ones where an operator and a commentator give visibly different answers.

  • Tell me about an architecture decision you got wrong.The answer should be specific, should include what it cost, and should name what they now do differently. Anyone who has operated at this level has several. A candidate who cannot produce one either has not been accountable or will not admit error, and both matter in this role.
  • How would you measure whether our AI system is working?Look for a baseline before anything else, and for measures split between retrieval and generation. An answer that goes straight to accuracy has not had to defend a system to anyone.
  • What would you tell us not to build?A good answer arrives within the first two weeks and is specific. Someone who will only ever add to your roadmap is not providing the function you are buying.
  • What does your handover look like?The role should be building toward its own redundancy: documentation, a team that understands the system, a full time successor eventually. A candidate with no answer has an incentive problem you will feel in month eight.
  • Walk me through how you would spend the first two weeks.Expect reading code, talking to the engineers, and finding out what is actually slow, before any recommendations. A candidate who already knows the answer has not understood that your situation might be particular.

Structuring the engagement#

  • Buy a paid discovery sprint firstOne to two weeks: architecture audit, team assessment, a prioritized technical roadmap. You get something useful whatever happens next, and you learn how they work before committing a quarter.
  • Write the agreement in decisions and outcomes, not hoursOwn the data architecture. Complete SOC 2 readiness. Hire two senior engineers. Hours invite timesheet arguments and let accountability sit nowhere.
  • Name the daysWhich days of the week are yours, with a defined path for urgent decisions in between. Vagueness here is how two days a week becomes a slow Slack reply.
  • Set a three month review with real criteriaAgree at the start what will be true by month three. Month to month flexibility only helps if someone is checking.
  • Plan the exit from the beginningWhat is documented, who can run the system, what triggers a full time hire. A fractional CTO engagement that cannot end has stopped being fractional.

The cost comparison, stated honestly#

Most articles on this put the saving at some large percentage. The figure is arithmetic rather than insight, and it is mostly a function of buying two days instead of five, so here is the comparison without the headline number.

FactorFractionalFull time
Monthly costCommonly $5,000 to $25,000, set by days and scope.Base plus benefits plus equity, and the equity is usually the larger number over time.
Time to productiveOne to two weeks.Three to six months to hire, then a ramp on top.
If it is not workingEnds with notice.A painful and expensive process, and a year lost.
Depth of contextLower. They are not in every conversation, which is the real tradeoff.Full. Present for everything, which is worth a great deal once there is enough to be present for.
Breadth of patternHigher. Has seen the same mistake at several companies.Narrower, deeper in your domain.

Frequently asked questions#

What is a fractional CTO?

A fractional CTO is a senior technology leader who works with your company part time, usually two to four days a week, owning architecture decisions, technical hiring, vendor evaluation and engineering governance. The distinction that matters is accountability: a fractional CTO owns outcomes and makes decisions, where an advisor offers opinions and a contractor executes someone else's plan.

How much does a fractional CTO cost?

Engagements commonly run from $5,000 to $25,000 a month, set by the number of days a week, the scope of accountability and how much regulatory complexity the role carries. The comparison people usually want is against a full time hire, where the honest answer is that the saving comes mostly from buying fewer days rather than from a cheaper rate, plus the absence of equity dilution and a shorter commitment if it is not working.

When should a startup hire a fractional CTO?

When technical decisions with long consequences are being made by people who are not equipped to make them, and the volume of such decisions does not yet justify a full time executive. The common triggers are an architecture choice that will be expensive to reverse, technical due diligence ahead of a raise, a first engineering hire, or entering a regulated market where the compliance architecture has to be right from the start.

What is the difference between a fractional CTO and a consultancy?

A consultancy sells a team and a deliverable. A fractional CTO is one accountable person inside your organization, in your stand-ups and your repositories, who makes decisions and lives with them. Consultancies suit well defined projects with a clear specification. A fractional CTO suits the situation where you do not yet know what should be built.

Looking for a fractional AI CTO?

Goatechs works with companies in regulated industries. Our principals bring thirty-plus workflow automation projects at Adobe as a Senior Technical Consultant, six years in regulated financial services at U.S. Bank, and forty years in software development spanning hardware and software. Book a free 30 minute call and we will tell you plainly whether this is the right shape of help for where you are.

Book a Strategy Call →