Choosing a Fractional CTO

Choose around the responsibility your business needs someone to take. A convincing conversation is a start. You still need evidence that this person can make the decisions, lead the people and carry the work through.

Start with the gap

Describe the business problem before choosing the title. A slipping launch, capable developers without direction and a substantial investment needing scrutiny call for different arrangements.

If direction and delivery already work, retain that leadership and add specific expertise. A fractional CTO can also work alongside an agency or strengthen a good team.

Explore the Missing CTO situation.

Ask for decisions, then examine the reasoning

Go beyond “Tell me about a similar project”:

• What did you initially believe, and what changed your mind?
• Which options did you reject, and why?
• What did you personally decide and lead?
• Who implemented it?
• What changed for the business, and how was that measured?

A rebuild recommendation should explain the constraint and transition risk. A hiring plan should connect roles to actual work. An AI proposal should explain useful behaviour, evaluation and operation.

In one engagement, I chose an internal build over an agency delivery organisation. The scope stayed the same; I owned technical decisions and led one engineer, retaining product knowledge inside the venture. Read the delivery decision. or the team decision behind a SaaS turnaround.

Test how they approach uncertainty

A prospective CTO should ask about customers, revenue, commitments and the people involved. Technical questions should inform a business decision.

Ask: “What would you need to see before recommending a course of action?” Look for specific evidence, a clear decision and a distinction between known facts and assumptions. A long issue list without priorities is not enough.

Make ownership explicit

Establish who owns decisions, who implements them, who accepts quality and how progress, spending and risk become visible. A meeting schedule alone does not establish delivery responsibility.

I agree authority directly with founders and lead execution through existing engineers or development partners. See the working relationship.

Match the evidence to the responsibility

Founder references reveal commercial judgement and trust. Engineer references reveal leadership and technical decisions. A substantial personal build supports engineering depth. Each answers a different question.

After a client's unsuccessful CTO hire, I assessed candidates against its actual commercial, architecture and leadership constraints. Read the appointment case.

Compare the complete arrangement

Consider leadership, development capacity, specialist work and operations together. Read the cost guide.