What a fractional CTO is, and when interim or part-time is the better fit

Key takeaways

• A fractional CTO is a senior technology executive who works for your company part of the week, on contract, usually alongside one or two other clients. You get CTO-level judgment without a CTO-level salary, equity grant or search.
• The label covers three different engagements: advisory (10 to 15 hours a month, a sounding board), active fractional (20 to 40 hours a month, a real member of the leadership team) and interim (near full-time for a defined window). Buying one when you need another is the most common mistake.
• Interim fits a gap with an end date: a CTO left, a search is running, a due-diligence deadline is fixed. Part-time or advisory fits an ongoing need that doesn't fill a week. Active fractional fits a company with a strong engineering lead who needs a technical executive above them.
• Decision rights matter more than hours. A fractional CTO with authority over architecture, hiring and vendor spend behaves like an executive. One without it is a consultant with a better title.
• Evaluate on the work sample, the reference from a company they've left, and their current client load. Cost ranges by structure live in the fractional CTO rates guide.

Why this question matters

You're reading this because something changed: a technical co-founder is leaving, an investor asked who owns the architecture, the engineering team passed ten people and nobody is making the calls that need making, or a full-time CTO search came back with a comp number the board won't approve yet. A fractional CTO is one answer to each of those, and a different answer to each. The engagement that covers a departure is not the one that coaches a founder through a Series A build, and vendors who sell fractional CTO services rarely tell you which one they're quoting. This guide separates them so you can name what you need before you talk to anyone.

The frame: Three structures under one label

Every fractional CTO engagement lands in one of three structures. The rates guide prices them; this guide defines them.

The structures aren't tiers of the same product. An advisory CTO working 12 hours a month can't unblock a team that needs someone in the standup, and an interim CTO at 45 hours a week is wasted on a company that needs a monthly architecture review. Pick the structure from the trigger, then go shopping.

What is a fractional CTO, exactly?

A fractional CTO is an experienced chief technology officer who takes on your company as one of a small number of clients, working a set number of hours a week or month on a contract rather than as an employee. Gergely Orosz and Sergio Pereira's Pragmatic Engineer piece defines the role as a CTO working part time for several companies in parallel, and that "in parallel" is the operative word. The person is a practicing executive splitting their calendar, so you get someone whose judgment is being tested at two or three companies at once, and you share their attention.

The Fractional Work Report 2026, published by Fractional Jobs, puts the typical fractional CTO commitment at 10 to 25 hours a week per client and counts roughly 150,000 fractional workers in the US, with hiring demand up 149% year over year in Q1 2026. The same report says 87% of fractional workers have 11 or more years of experience. That's the point of the model. You're buying seniority in small units, and the market has grown because the unit size finally matches what a 12-person engineering team needs.

What a fractional CTO does depends on the structure above, but the work clusters into five areas: technical strategy and architecture decisions, the engineering hiring bar and org design, vendor and build-versus-buy calls, technical due diligence and board communication, and, at the active and interim levels, the standards the team ships to. What they don't do, at any level short of interim, is write most of the code or run the sprint. If the job description is "senior engineer who also makes decisions", the role you want is an architect or a staff engineer, priced and scoped differently.

Fractional, interim, part-time, temporary: Do the labels mean different things?

Mostly yes, and the market uses them loosely enough that you should ask what a vendor means before you compare quotes.

The one distinction that changes the contract is fractional versus interim. A fractional CTO expects to hold other clients and won't drop them for you. An interim CTO expects to be yours for the window and expects the window to close. If you need someone in the building four days a week for the next five months, say "interim" and price it that way. Calling it fractional will get you candidates whose calendars can't do it.

When is an interim or part-time CTO the better fit?

The honest test is whether the need has an end date and how many hours a week it takes. A hypothetical shows how the same company can need two different structures a few months apart.

Suppose a Series A company loses its technical co-founder in the spring. The CEO's first instinct is a fractional CTO, because that's the phrase the board uses and the comp is manageable. The first two conversations are with fractional CTOs who work 15 hours a week across three clients. Both are strong. Neither can do what the company needs in month one, which is to be in the standup every day while two senior engineers who reported to the co-founder decide whether to stay, and to sit across from the auditor in a SOC 2 review already on the calendar.

What that company needs for the next four months is an interim CTO: one client, near full-time, a defined window that ends when the executive search fills. The search itself takes three to six months, which is the reason the gap exists. Reframe the engagement as interim and the candidate pool changes. The people who take interim roles are between operating jobs or run interim as a practice, and they're used to walking in on day one with no context and stabilizing a team that's watching the exits. A well-run interim engagement ends with the interim CTO on the hiring panel for their own replacement and a written architecture record the permanent hire doesn't have to reverse-engineer.

Now suppose the same company, six months on, has a full-time CTO and a different problem. The CTO is strong on the product side and light on infrastructure, and the platform is moving to a multi-region setup nobody on the team has run before. This is where the advisory structure earns its keep: a fractional CTO with two other clients, 12 hours a month, reviewing the migration plan and joining the monthly architecture review. No standups, no decision rights, no presence in the org chart. The company would waste money buying that at 40 hours a week in month one, and it would fail buying the interim engagement at 12 hours a month.

Part-time or active fractional sits between these two. It fits when the need is ongoing and the team already has a strong engineering lead who runs the week. The fractional CTO at 25 to 35 hours a month owns the architecture direction and the hiring bar, joins the leadership meeting, talks to the board quarterly, and leaves the sprint to the lead. This is the structure most of the fractional CTO services market sells by default, and it works when that lead exists. Without one, the fractional CTO becomes the engineering manager by gravity, the hours balloon, and you've bought an interim at a fractional price with a fractional CTO's other clients still on their calendar.

Three signals point at interim rather than fractional: the need has a known end (a search, a diligence process, a migration cutover); the team needs someone present daily to hold together; and the work includes things only a seated executive can do, like signing off on a security audit or being the named technical officer in a financing. Three signals point the other way: the need is a recurring decision cadence rather than daily presence; a competent engineering lead already runs the week; and the budget is approved as a monthly line rather than a role.

How do you find and evaluate a fractional CTO?

Five channels supply most fractional CTOs, and they differ on who holds the contract and what you pay for the introduction.

Boutique fractional-CTO firms (Ten Mile Square, CTOx and their peers) employ or contract a bench of CTOs and sell them on a monthly retainer through the firm; the Fractional Jobs listicle puts CTOx at roughly $3,000 to $15,000 a month, quoted per engagement. Fractional-executive marketplaces (Fractional Jobs, GoFractional) introduce you to independents for a one-time placement fee, $3,000 to $8,000 at Fractional Jobs as of September 2026, after which you contract directly. Talent networks that vet for seniority place fractional leaders under the same paper as senior individual builders; at A.Team that's one MSA with the leader on their own service order at one all-in rate and no managing-partner fee, the same structure as any senior builder. Toptal's team product offers a self-led tier and a Teams Advanced tier with a dedicated team manager, which is a different thing from a CTO and worth knowing when someone offers you "technical leadership" as a line item. Your investors' networks and direct outreach to operators on LinkedIn round out the list, at zero fee and with zero vetting other than your own.

Whichever channel, evaluate the same three ways. Give them a work sample: your current architecture document or your last two post-mortems, and 45 minutes to tell you what they'd change first and what they'd leave alone. A strong fractional CTO will find the decision you've been avoiding within the hour. Take a reference from a company they've finished with, not a current client; ask what the handover looked like and whether the permanent hire kept their decisions. And ask for their current client count and weekly hours, then do the arithmetic against the hours you need. A fractional CTO at three clients and 40 hours a week has 13 for you. If your trigger needs 30, you've found a good advisor and the wrong structure.

The marketplace evaluation guide covers the vendor-side questions (vetting depth, replacement terms, pricing transparency) that apply here as much as to any senior placement.

What to do next

Write down the trigger in one sentence, then the number of hours a week the trigger needs and whether it has an end date. That sentence tells you the structure. Take it to the rates guide to price it, and to the fractional versus full-time decision framework if you're not sure the role should be fractional at all. When you're ready to talk to a network, a scoping call that names the structure up front is what gets you a matched shortlist within 72 hours of the scoping call rather than a week of clarifying emails. Hire expert talent is where that call starts.