Questions we answerTeam structure and leadership
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.
Free · a few minutes · starts from “We have a capability gap”
The short answer
A lead developer builds the product well, makes sound day-to-day technical choices and can mentor one or two others. A CTO owns technical strategy, architecture decisions that are expensive to reverse, and hiring and running a function. If the immediate need is shipping, hire the lead developer — it is a more achievable hire at a lower price and usually the right one. Hire a CTO when technical decisions have become business decisions, when a team needs building, or when the company is technically unadvised at the level where it matters.
These two roles get advertised interchangeably, and the mismatch is expensive in both directions: a CTO hired to write most of the code is bored within a year, and a lead developer given a strategy remit is unsupported in a job they did not apply for.
The distinction is not seniority. It is whether the main value is judgement about what to build and who builds it, or excellence in building it.
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 choices are now business choices, with cost and risk that outlast the current roadmap.
- You need to hire and lead engineers, not just write software.
- Nobody in the company can assess technical risk and it is starting to matter.
Signs it's something else
- There is no engineering team yet, so there is nobody to lead.
- What is needed this year is a well-built product against a reasonably clear roadmap.
- The title is wanted mostly for how it reads externally.
What's usually behind it
- A product that needs to be built well and nobody senior to build it.
- Technical decisions being made by default rather than by anyone deciding.
- Investors or customers asking who owns technology.
What people usually get wrong
- Hiring a CTO as the first engineer, and paying executive rates for individual contribution.
- Giving a lead developer a strategy remit with no support and calling it a promotion.
- Optimising for a title investors will recognise rather than for the work that needs doing.
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.
Lead developer or principal engineer
The product needs building well and technical direction is roughly settled.
CTO
Technical strategy, architecture and team-building are the constraint.
Fractional CTO alongside a builder
You need senior judgement periodically and delivery continuously.
When doing nothing is the right call
If you cannot yet tell which, a few days of an experienced technical adviser reviewing the current state will usually answer it — and will improve whichever hire you go on to make.
What the diagnostic asks
- Whether the gap is capability, capacity or both.
- How much judgement the work needs.
- How central it is to the business.
- Whether it could be done externally, and whether the 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.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
What changes the answer
- A need for direction, architecture and team-building points at a CTO.
- A need for the product to be built well points at a lead developer.
- No existing engineers to lead makes a CTO premature almost regardless of anything else.
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
- 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.
- When should a startup hire its first engineer?When there is durable technical work, someone who can judge technical quality, and enough definition for an engineer to own something rather than wait to be told.
- Should I hire in-house or use an agency for development?An agency is right for a defined build with a specification and an end. In-house is right when the product is continuous and the context has to stay.
- Should I use a fractional executive?Fractional works where you need senior judgement rather than senior capacity, and where someone internal can carry the execution between sessions.
- 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.