How to hire a fractional CTO: a step-by-step guide for founders

Here is how to hire a fractional CTO without guessing: write down the outcomes you need, decide between hands-on and advisory help, set hours and a budget, source candidates through people you trust, shortlist on evidence, run a short paid discovery as the real interview, check references, then sign a contract that covers IP and handover.

Done properly, the whole process usually takes three to six weeks. The step founders are most tempted to skip is the paid discovery, and in my experience it tells you more than every call combined.

Step 1: Write down what you need a fractional CTO to achieve

“Help with tech” is not a job description. When a fractional CTO engagement disappoints, the cause I see most often is a fuzzy brief, not a bad person: the founder wanted delivery, the CTO thought they were hired for strategy, and nobody wrote either down.

Before you speak to anyone, write three to five outcomes for the next six months. Each one should be something a stranger could check. For example:

• Launch the first version of our booking app on iOS and Android by the end of March.
• Decide whether to keep, replace or bring in-house the agency we pay every month.
• Be ready for technical due diligence before the seed round closes.
• Hire and onboard our first two engineers.
• Ship an AI assistant that answers order-status questions in English and Arabic.

Under the outcomes, add the facts a candidate needs: what exists today (code, vendors, a team or nothing), your deadline, your rough budget and who makes the final decisions. This one page becomes the brief you send to every candidate, so you can compare them on the same problem instead of on charm.

Step 2: Choose hands-on or advisory, then set hours and budget

Fractional CTOs come in two broad kinds. An advisory CTO sets direction, makes the big technical calls and keeps an existing team or agency honest. A hands-on CTO does all of that and also writes and ships code. There is a fuller comparison of hands-on and advisory fractional CTOs, but the short version is this:

• You have no developers: you need someone who will build, or someone who will hire and lead builders from the first week.
• You have a team or an agency: advisory may be enough, as long as the person reviews real work and not just status reports.

That choice drives the hours. Advisory engagements often run around half a day to a day a week. Hands-on engagements during a build can take two to four days a week or more, then taper after launch.

Set a budget range before you see any quotes, so the quotes don't set it for you. As a rough US guide, a few hours of advice a month can cost a few thousand dollars, while a CTO who is hands-on several days a week can cost upward of $20,000 a month; market and seniority move these numbers a lot. The guide to what fractional CTOs typically charge explains the pricing models. One tip: compare the fee with your whole technology spend, not just with a full-time salary. A hands-on CTO can replace part of a development budget; an advisory one sits on top of it.

Step 3: Where to find fractional CTO candidates

The best candidates rarely come from a cold search. Here is where I would look, roughly in this order:

When you ask for a referral, ask about the rough patches, not just the highlights. A founder who says “great, but slow to reply on weekends” has told you more than one who just says “great.”

Location matters less than overlap. A CTO in another country works fine with two or three shared working hours a day and good written updates. Being in the same city matters only if you need them in the room, for example to run workshops or to interview local hires in person.

Step 4: Shortlist three candidates on evidence

Aim for five to ten names and a shortlist of three. Any more and you will end up comparing personalities instead of plans. Check each one against this list before you book a call:

• Has worked at your stage. Pre-launch, early revenue and scaling are different jobs.
• Has shipped products shaped like yours, such as a marketplace, a booking app or a B2B dashboard.
• Matches the hands-on or advisory need from step 2, with work you can actually see.
• Gives a straight answer on current clients and the hours they can offer you.
• Overlaps your working day by at least two or three hours.
• Writes clearly. Their first emails are a preview of every update you will get.
• Can put you in touch with past clients.

Then book a 45-minute call with each. Send your one-page brief in advance and ask them to bring questions, because the questions a candidate asks you are as revealing as their answers. I have written up 20 questions worth asking on that first call, with what good answers sound like, plus a separate list of warning signs that should end the process. Use the first to run the call and the second to decide whether to continue.

Step 5: Make a paid discovery the real interview

A call tests how someone talks. A paid discovery tests how they work. Before you commit to a monthly retainer, pay your top candidate (or your top two, if the budget allows) for a short, fixed-scope piece of real work, usually one to three weeks long.

A useful discovery ends with five things:

1. A written assessment of where you are today: code, vendors, costs and risks.
2. A prioritized roadmap for the next three to six months.
3. An architecture and stack recommendation, with the reasons in plain English.
4. A realistic estimate of time and cost for the next phase, with the assumptions listed.
5. The three to five biggest risks and what to do about each one.

Expect to pay a fixed fee. In my experience it is often somewhere around half to one month of the person's usual retainer, depending on how much there is to review. Make sure the agreement says you own everything the discovery produces, even if you don't continue. A good discovery is useful to you whichever way you decide.

Watch how it feels as well as what it produces. Did they ask sharp questions? Did they show up when they said they would? Did they tell you something you didn't want to hear? I start my own engagements the same way: two weeks of discovery that produce a roadmap, a system design and an honest estimate, which tests me as much as the project. You can see where it fits in my fractional CTO process, but I would recommend the same filter whoever you hire.

Step 6: Check references the useful way

Ask for two or three references from companies at a similar stage, including at least one where the engagement has ended. Current clients are still in the honeymoon period. Past clients know how the story finished.

Keep each reference call short and specific. Four questions do most of the work:

1. What did they actually deliver in the first 90 days?
2. Tell me about a time they gave you bad news. How did they handle it?
3. How did the engagement end, and was the handover clean?
4. Would you hire them again for exactly the same job?

Listen for hesitation on the last one. “Yes, for a different job” is a polite no for yours. If you share a contact with the candidate, a quiet backchannel conversation with someone who worked alongside them is worth as much as a formal reference.

Step 7: Sign a clear contract and onboard properly

The contract should turn your outcomes into a scope, fix the hours, availability and fees, assign all IP to your company, keep every account in the company's name and spell out notice and handover. If equity is on the table, it belongs in a separate grant with vesting. The guide to what a fractional CTO contract should cover walks through each clause. Because the rules differ from one country to the next, ask a qualified lawyer to read the draft before anyone signs; none of this is legal advice.

Then make the first week count:

• Give them their own login to everything: code repository, cloud hosting, analytics, vendor contracts and any agency's project tools.
• Introduce them to your team, your vendors and, if it helps, your investors.
• Agree on the rhythm: a weekly demo, a short written update and a monthly review against your outcomes.
• Turn the outcomes from step 1 into a dated plan for the first three months.

From there, a realistic plan for the first 90 days keeps both sides honest about progress.

How long does it take to hire a fractional CTO?

Typically three to six weeks from first search to signed contract. A warm referral can shorten that to two weeks; running two discoveries side by side can stretch it. A realistic sequence looks like this:

Rushing is the expensive option. A wrong hire costs the fees, plus the months it takes to notice and the work someone has to redo.

Where to start

Write the one-page brief today. It costs nothing and sharpens every conversation that follows. Then ask three founders you trust who they have worked with, and how those engagements handled the hard weeks. Shortlist on evidence, test with a paid discovery, and sign only when the contract protects your code, your accounts and your exit. That order guards against the mistake I see most often: hiring the best talker instead of the best fit.