Questions we answerTeam structure and leadership
Do I need a CTO?
Not always, and not always yet. The question is what technical leadership the business needs over the next year or two — and whether that is a permanent seat, a fractional or interim leader, or capability grown from inside.
Free · a few minutes · starts from “We have a capability gap”
The short answer
Probably not yet, if what you need is someone to build the product. A CTO is a leadership role — technical strategy, architecture decisions you cannot easily reverse, and hiring and running a team. If the immediate need is code shipped, a lead engineer or a strong senior developer is usually the better and more achievable hire. The question to settle first is whether the gap is technical judgement at the top or technical delivery, because they are different hires at very different prices.
A CTO is a specific answer to a range of problems: no one owning technical direction, a founder out of their depth on architecture or hiring, an engineering team without a leader, or investors expecting a title. Each points at a different kind of person, and some do not need a permanent one.
The diagnostic treats this as a capability gap and asks how durable and how central the need is, whether anyone internally could grow into it, how soon it matters and whether a senior permanent hire is fundable.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- Technical decisions are made by whoever is free, and nobody is accountable for the result.
- The engineering team has grown past what the founder can lead as a side task.
- You cannot assess the technical hires you need to make.
Signs it's something else
- The need is one decision — an architecture, a migration, a due-diligence exercise — with an end date.
- The team is small and technically strong, and what is missing is prioritisation rather than leadership.
- The title is being asked for by someone outside the business rather than needed inside it.
What's usually behind it
- Technical decisions being made by whoever is nearest, with nobody accountable for them.
- A growing engineering team with no one to lead, hire and set standards for it.
- A one-off need — an architecture decision, a due-diligence process, a platform migration — that feels permanent because it is urgent.
What people usually get wrong
- Recruiting a CTO to write code, or a lead engineer to set strategy, and being disappointed by both.
- Giving the title to the first engineer as a retention device, without the remit that goes with it.
- Recruiting a senior technical leader when nobody in the business can judge the candidates.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Recruit a permanent CTO
Technology is central, the need is durable, and there is a team and a roadmap to lead.
Fractional or interim leadership
The need is real but part-time, or urgent enough that recruiting would be too slow.
Promote and support an internal lead
Someone has the judgement and the context, and needs backing rather than replacing.
A specialist for the one decision
What you actually need is an answer to a specific technical question.
When doing nothing is the right call
If technology is not yet central to how the business competes, and the current team is shipping, the honest answer may be not yet. Name the trigger — the size of the engineering team, a platform decision, a funding round — and revisit it then.
What the diagnostic asks
- Whether the need is growing, steady or temporary.
- Whether someone in the team could grow into the role, and how much judgement it needs.
- How soon it matters, how central technology is to what the business does, and whether a senior permanent hire is fundable.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Specialist support
Bring in a freelancer, consultant or specialist for a defined piece of work.
Develop
Build the capability in someone already in the team, with time and support.
Outsource
Hand a defined, ongoing scope of work to an external provider.
What changes the answer
- A temporary or one-off need, or a deadline this month, points at a fractional or interim leader rather than a permanent CTO.
- A growing, core, judgement-heavy need with nobody close internally is the case for a permanent senior hire.
- Someone internally who could grow into it, with time, is cheaper and more durable than either.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- What should my next hire be?Start from the constraint rather than the wish list. The right next hire is the one that releases the most work or removes the largest risk — which is often not the role that feels most overdue.
- We have a skills gap. Should I train, hire or bring someone in?It depends on how long you need the skill, how soon, and whether anyone in the team is close to it. Each answer points at a different route.
- Do I need another manager?Only if the problem is span of attention rather than unclear ownership. A manager helps when there are more people than one person can support properly; added to fuzzy roles, a manager adds a layer to the confusion.
- Do I need a CTO or a lead developer?One sets technical direction and builds a team; the other builds the product well. Most early companies need the second and advertise for the first.
- Is my team too small?Team size only means something against the work. The useful question is whether what is being asked of the team is achievable by the people in it, arranged the way they are.
- When should a startup hire a COO?When operational load is genuinely holding the business back and there is a defined remit to own — not when a founder wants to stop doing the parts of the job they dislike.