How to hire a fractional CTO

What a fractional CTO does for a business like yours

A fractional CTO is a senior technology leader who works for you part time, usually on a monthly retainer. In a software startup that person designs architecture and manages developers. In an established service business the job looks different: deciding which systems to keep, connecting the ones you already pay for, choosing vendors, setting security basics, steering AI use, and making sure new tools are actually adopted by the people who have to use them.

Before you hire, write a one-page description of the decisions you want this person to own. For a 30-person accounting firm that might be: choose between keeping Karbon or consolidating into Canopy, set an AI usage policy, and fix how client documents flow from the portal into the tax software. Concrete decisions make the search much easier, because you can ask every candidate how they would handle the same three items.

Also be clear about what you do not want. Some owners want a sounding board for occasional decisions. Others want someone to run projects end to end. Both are legitimate, but they need different people and different fees, and saying so up front saves a lot of awkward conversations later.

Decide which kind you need

The title fractional CTO covers several quite different people. Most mismatches happen because an owner hires one kind when they needed another.

• Product or startup CTO: architecture, developer hiring, code quality and fundraising support. Right if you are building software you sell.
• Operations-focused technology lead: workflow priorities, vendor selection, integrations, AI adoption and measurement. Right if technology supports a service you deliver.
• vCIO from a managed IT provider: device, network and security roadmaps, often bundled with IT support. Right if your main worry is uptime and security.
• Interim CTO: a near full-time stopgap while you recruit a permanent leader. Right if you already know you need a full-time hire.

Where to find good candidates

Start with referrals from people who see inside many similar businesses: your outside accountant, your attorney, your banker, a peer group. National marketplaces are another route; GoFractional, for example, says it can match companies with pre-screened fractional executives in about three days. Local firms and independent consultants are a third. Your managed IT provider may offer a vCIO, which is worth comparing even if you choose someone else.

Whatever the source, look for evidence of work in a business like yours. A brilliant SaaS architect may have little to say about dispatch in ServiceTitan or matter intake in Clio. Ask each candidate to describe a recent decision they made for a client where the answer was to buy nothing new.

Vet them on a real decision

Interviews reward people who interview well. A better test is a short paid working session, perhaps two to four hours, on one of the decisions in your one-page brief. Give the candidate access to the relevant facts, such as current subscriptions, a sample of the workflow, and the team members involved, and ask for a written recommendation.

Judge the output on four things: did they ask about your business before talking about tools, did they say what they would measure, did they name risks and where a person must approve output, and could your operations manager understand the recommendation without help. Call two references and ask whether the person's recommendations were still in place a year later.

Also notice how candidates handle uncertainty. A good recommendation says what they would need to confirm, what could change their view, and what a cheaper fallback would be. Overconfidence about a business they met last week is a warning sign, however polished the delivery.

Agree the terms in writing

Most problems with fractional leaders come from unwritten assumptions about authority and scope. A short engagement letter should settle the following before work starts.

• Decision rights: what they can decide, what they recommend, and what the owner approves.
• Cadence: weekly or twice-monthly meetings, response times, and on-site days if any.
• Deliverables for the first 90 days, with dates, not just hours.
• Conflicts of interest: any reseller margins, referral fees or development teams they would steer work toward.
• Ownership: all accounts, documentation and credentials stay in your company's name.
• Exit: notice period and a handover document if either side ends the arrangement.

Set up the first 90 days

Once you have chosen someone, give the arrangement a defined first phase with a clear end. A sensible pattern is a month to understand the business and agree priorities, a month to deliver the first improvement, and a month to measure results and decide what comes next. Ask for a short written plan in the first two weeks that names the first workflow, the baseline, the measures and the people involved.

Prepare your side as well. Name an internal owner who will meet the fractional CTO weekly, usually the operations manager or a partner. Collect a list of every subscription with its cost and renewal date, admin access to the main systems, and two or three recent examples of the workflow that hurts most. A fractional leader who spends the first month chasing logins and invoices has less time for the work you are paying for.

At day 90, review together: what changed in the numbers, what the team actually uses, what was harder than expected, and whether the arrangement should continue, change shape or end.

What it costs, and how InTheory compares

GoFractional's published benchmark puts fractional CTOs at an average of $209 per hour, with the middle half between $150 and $250, typically around 15 hours a week, or about $9,000 to $15,000 a month. Other providers publish ranges from roughly $3,000 to $15,000 or more per month depending on time commitment.

InTheory's plans run $2,500, $5,000 and $7,000 a month for an initial 90 days. That is lower because the scope is narrower: one priority workflow at a time for a service business, with a written scope, a baseline and adoption work, rather than a part-time executive covering everything technical. If you are building a software product, managing an in-house development team, or need someone in leadership meetings every week across all of technology, a traditional fractional CTO is the better buy. If your need is choosing and getting results from the systems you run on, compare InTheory's scope against what a broader fractional CTO would actually spend those hours on.