Playbook · The CTO role

Updated

What does a CTO do in a startup?

A CTO in a startup decides how the product gets built and makes sure it does: the architecture, the team, the vendors and the technical risks. The job changes with each stage, from writing most of the code before launch to hiring and leading engineers after the first round.

The average CTO at a US seed-stage startup is paid $155,000 a year in cash. At Series A it is $196,000, and at Series B $238,000. That is before payroll tax, benefits and equity.
Source: Kruze Consulting, 10 Aug 2026

From my work

At Peeps, an Overwolf app, I planned the project and ran it in sprints with a team of three: one QA, one backend developer, and me on full-stack. We built on Overwolf’s API and its app starters to save time. Then the investors wanted the deadline moved from six months to four. We cut features to meet it and moved them to after launch.

At Mom Software I led a five-person team. A normal week was a sprint plan, tickets assigned, my teammates’ merge requests reviewed, and my own tickets done. The decision that changed that project was to stop patching the old Angular 10 code. It had no clear pattern, a lot of dead code and unused libraries. We started again on a Fuse template and moved the legacy code over one module at a time.

Before the product exists

The CTO is mostly a builder. The work is picking a stack the team can hire for (boring is a feature here), writing a large share of the code, and cutting the scope down to the one feature that proves the idea. The most useful thing a CTO says at this stage is often “not yet”.

From MVP to first customers

Now the job is shipping without breaking things. A CTO sets up deploys you can roll back, backups, error tracking and basic security, and keeps a short list of the shortcuts taken so they get paid back later. By now there is a new feature request every week, and each one is urgent. Someone has to say which ones wait until after launch.

After a seed round

  • Hiring: the job spec, the interviews and the first engineers.
  • Process: sprints, code review and a release routine the team keeps without being chased.
  • Vendors: which tools and agencies to pay for, and which to drop.
  • Investors: answering the technical questions in a round, and owning the roadmap the board sees.

Series A and later

The CTO writes less code and makes fewer, bigger decisions: architecture that will hold for the next few years, security, and the shape of the engineering team. Expect more meetings than merge requests. Many companies hire a VP of Engineering around here to run delivery, so the CTO can focus on technical direction.

What I look for when I hire engineers

I interviewed engineers at Wi-Mobi. I spent less time on the tech stack and more on how a person reasons. I asked how they handled past projects, or gave them a made-up scenario and asked what they would do. Frameworks can be learned in weeks. Judgment takes longer.

Do you need a full-time CTO yet?

Not always. If the company needs CTO decisions but not yet a full-time CTO, a fractional CTO costs a fraction of the salaries above. If you are so early that there is nothing technical to decide, or you need a technical lead in the room every day, a part-time CTO is the wrong fit. Hire full-time, or wait. A CTO with nothing to decide is an expensive spectator.

Read next

Sources

Start

Tell me where the product is stuck.

In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.

How the call goes

  1. 01You tell me about the product, the team and the next 6 months.
  2. 02I ask about the code, the stack and what keeps breaking.
  3. 03We pick the option that fits, or agree that none does.

09:00 to 20:00 CET

Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.