Buyer guide
What is the difference between a tech lead and a CTO?
In short
A tech lead guides how a team builds a product: design choices, code quality and day-to-day technical decisions. A CTO sets technology direction for the whole business, manages technology risk and answers to the other leaders. Small companies often need one person for both, and many need the CTO side first.
Who is this guide for?
Founders and owners who keep hearing both titles from candidates, advisers and job boards and want to know which job they actually need to fill.
Titles are not standard
Companies use these titles loosely. In a ten-person startup, the CTO may write code every day. In a larger company, a tech lead may manage no one. So read the duties, not the title.
The UK government's digital and data role framework gives one clear set of definitions, which is a useful reference even if your business is not in government.
What a CTO does
The framework describes the chief technology officer as the organisation's technology strategist, who sets technical direction, works with other senior leaders, builds and leads a technology strategy, manages technology risk and keeps systems running and protected.
The CTO is accountable for the outcome across the business, and spends more time on decisions, people and risk than on code.
What a tech lead does
In the same framework, the lead software developer leads one or a few project teams, guides how they work and provides technical leadership. The developer role it sits in designs, runs and improves software to meet user needs.
A related role, the technical architect, provides technical leadership and architectural design, advises on design and manages architecture risk. Some tech leads take on parts of that role.
Which one do you need
If the questions are which technology to build on, whether to outsource, how to budget and how to protect the business, you need the CTO side. If the questions are how to structure the code and how to get this team to ship reliably, you need the lead side.
Many small companies need the strategy and risk side first, because choosing the wrong platform or vendor costs more than any single coding problem.
Doing both with one person
In a small business one experienced person can cover both on a part-time basis: setting direction, reviewing the work and guiding the developers. This only works if the person has time for both, and the scope says which is which.
Write down what the person owns: decisions they make, what they review, what you see each month, and what stays with you.
How do the options compare?
| Tech lead | CTO | |
|---|---|---|
| Focus | How the team builds the product | What the business does with technology |
| Typical questions | Design, code quality, delivery | Strategy, vendors, risk, budget |
| Works with | Developers on the team | Other senior leaders and the owner |
| Hands-on coding | Usually yes | Varies with company size |
| Accountable for | Technical quality of the team's output | The technology outcome for the business |
What should I check before I sign?
- You have written the problems you want solved before choosing a title.
- You know whether your needs are about direction and risk or about delivery.
- The job description lists duties, not only a title.
- You know what the person decides and what stays with you.
- You know how much hands-on work you expect.
- You know what you will see each month.
- The person has run similar products themselves.
- You have considered a part-time arrangement before a full-time hire.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
Is a CTO more senior than a tech lead?
In most companies yes, because the CTO covers the whole business. But the titles are used loosely, so check the duties.
Can one person be both?
In a small company, yes. Write down which decisions the person owns in each role.
Do I need a CTO if I outsource my development?
Someone on your side must still choose vendors, check the work and own the risk. That is the CTO job, and it can be part-time.
What about VP of Engineering?
It is another title that varies by company, usually closer to running the engineering team. Ask for the duties in writing.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
How can we work this way together?
- Fractional CTOAs a fractional CTO I look after your technology part time, month by month: I set the technical direction, review code, plan work in two-week sprints and keep releases, servers and vendors under control, and I still write code myself.
- Tech Lead on RetainerAs a tech lead on retainer I work inside your engineering team month by month: I plan the sprints, set code standards, review pull requests, unblock the developers and take the hardest tasks myself.