The answer to what does a startup CTO do depends less on the company than on the size of the engineering team. With two engineers, the CTO is the best programmer in the building. With twenty-five, the same person may not have merged a pull request in a month, and whether that's a problem depends on which kind of CTO they want to be.
So this page is organized around team size. It covers the versions of the job, what the CTO owns at each stage, how to tell you need one, what the options cost, and how the CTO differs from a VP of engineering. The Nautis section near the end is about the admin around engineering, which is the part software can actually help with.
What does a startup CTO do at pre-seed, seed and Series A?
Pre-seed: build it
The CTO is usually a cofounder and writes most of the code. The jobs are choosing a stack the team can hire for, shipping a first version fast enough to learn from, and making a few decisions that are expensive to undo later: how authentication works, where data lives, who holds the production keys. If you're a non-technical founder deciding whether you need this person at all, read how to find a technical cofounder first.
Seed: build it and hire for it
A knowledge-base article from the Martin Trust Center for MIT Entrepreneurship describes the early hacker-CTO as someone who should take on both the management and the technical work. In practice that means interviewing engineers, reviewing their code, setting up on-call and still shipping features. That usually means a week split between shipping and making other people productive, and both halves suffer a little.
Series A: choose a version of the job
The MIT article says that as headcount passes 15 or 20, project and people management start to dominate, and the CTO ends up doing a lot they don't enjoy, with little time for technical exploration. That's the moment to bring in a VP of engineering and decide what the CTO's job becomes.
Three versions of the CTO job once the team grows
In 2014, Greg Brockman, then CTO of Stripe, wrote about trying to define the role. He expected CTOs to be chief architects, but in about 20 conversations with other CTOs he found only one who fit that description. Most saw the job as making the technology organization work: connecting senior engineers, mentoring, unblocking. One acted as the head of product. Another had gone back to coding, focusing on the work he was best at.
Brockman's own path is a useful example. At Stripe he hired Marc Hedlund as VP of engineering, who took over one-to-ones and, over time, recruiting. Brockman later went back to writing code, partly because it gave him a direct view of the organization again. He quoted another CTO's line that the job isn't about time management but about energy management.
Our view: decide which version you're aiming for before you hire the VP of engineering, and tell them. A VP who expects to inherit the whole team will clash with a CTO who wants to keep the architecture team, and that conflict is avoidable.
- Architect. Owns the technical design and the hardest systems. Rare, by Brockman's count.
- Organization builder. Owns how engineering works: hiring, levels, process. This is close to the VP of engineering job, which is why the two get confused.
- Product CTO. Owns what gets built, sitting between customers and the team.
Signals you need a CTO, or a VP of engineering under one
- You're a non-technical founder paying an agency, and nobody inside the company can judge whether the code is any good.
- An investor's diligence call asks about architecture, security or scaling, and no one on your side can answer.
- The current technical lead hasn't written code in two months, misses it, and is spending the week in one-to-ones.
- Engineering hiring has stalled because the only person who can run interviews is also on call.
- The same class of outage keeps happening and nobody owns the fix.
The first two point to a CTO, either as a cofounder or a fractional hire to start. The last three point to a VP of engineering underneath an existing CTO. The full comparison is in CTO vs VP of engineering.
What a CTO costs: cofounder, fractional or hired
Two very different published numbers exist for Series A, and both are worth seeing. Kruze Consulting's payroll data from venture-backed clients is what CTOs at those companies actually earn. A.Team, a talent marketplace, prices what it costs to recruit an outside CTO.
| Option | Published figure | Source |
|---|---|---|
| CTO on payroll, seed | $155,000 average cash pay | Kruze Consulting, 2026 |
| CTO on payroll, Series A | $196,000 average cash pay | Kruze Consulting, 2026 |
| CTO on payroll, Series B | $238,000 average cash pay; overall median $166,000 | Kruze Consulting, 2026 |
| Advisory fractional CTO, 10 to 15 hours a month | $4,000 to $10,000 a month | A.Team, 2026 |
| Active fractional CTO, 20 to 40 hours a month | $10,000 to $25,000 a month, about $15,000 on average | A.Team, 2026 |
| Interim or near full-time fractional, 40+ hours a month | $20,000 to $40,000 a month | A.Team, 2026 |
| Hired CTO, Series A, US | $250,000 to $350,000 base, 1% to 3% equity, $325,000 to $490,000 first-year cash including a $40,000 to $80,000 recruiting fee | A.Team, 2026 |
| Computer and information systems managers, all US employers | $175,140 median wage, May 2025 | BLS |
The gap between $196,000 and a $250,000 base is large. A likely reason is that payroll averages include founder CTOs who pay themselves below market, while A.Team prices an outside hire. If you're recruiting, budget for the higher number. A.Team also says fractional is most cost-efficient from seed to Series A, that the crossover to full-time tends to come at 15 to 25 engineers, and that by Series B complexity usually warrants a full-time CTO. The BLS line is a broader category that lists CTO among its titles, so use it for scale only.
CTO compared with VP of engineering, lead engineer and fractional CTO
| Role | Main focus | Manages people? | Typical stage |
|---|---|---|---|
| Technical cofounder | Building the first version and owning early technical risk | Rarely at first | Pre-seed |
| CTO | Technology direction: architecture, product or the engineering organization | Early on yes, later by choice | Seed onward |
| VP of engineering | Execution: delivery, hiring, process and engineering management | Yes, it's the core of the job | Past about 15 to 20 people on the team |
| Lead or staff engineer | The hardest technical work on one area | Usually no | Seed onward |
| Fractional CTO | Technical judgment and oversight a few days a month | Sometimes, lightly | Pre-seed to Series A |
How Nautis takes admin off a CTO, and what stays technical
Nautis won't review code or design systems. Where it helps a CTO is the admin around engineering: connecting tools for the company's agents, keeping shared secrets in one place, and running technical hiring.
GitHub and Linear, with approval
GitHub and Linear connect through the managed integrations catalog, and you sign in on the provider's own screen. Connecting and enabling a tool for agents are separate steps. Each tool's page lists its actions, tagged Read or Write, and an admin can switch individual actions off. Writes, such as creating a Linear issue from a customer bug report, wait in the Approval Center unless an admin sets connected app actions to Run without asking. A delete in a connected app counts as a write, so switch off delete actions you never want an agent to take. Nothing is synced or mirrored into Nautis; agents call the tool on demand.
Shared secrets in one vault
The Credentials vault stores API keys, database credentials, SSH keys, certificates, tokens and client secrets, encrypted at rest with AES-256. Each credential has its own Shared Access list, folders can separate production from staging, and you can import CSVs from 1Password, Bitwarden, LastPass or a browser. Only owners and admins can export, each export asks for your password, and the workspace owner gets an email about every one. When someone leaves, removing them from the organization ends their access, and the guide's advice to rotate the underlying secret is worth following. It's a place for the team to keep and share secrets; the guide describes no link to deploy pipelines.
Hiring engineers
Jobs and recruitment drafts a job description with Generate, publishes it to a careers page that applicants use without an account, and runs candidates from Applied to Hired with interviews, panel feedback and offers. A hire converts into an employee record in one step. One limit for technical hiring: there aren't custom screening questions yet, so take-home tasks and coding tests run elsewhere.
Big technical calls, like a database migration or a rewrite, can go into Decision Loop under the Tech category with a 90-day review, so you find out later whether your confidence was justified.
The rest stays with the CTO: architecture, code review, security, incident response, and deciding what not to build. Nautis isn't an issue tracker, a CI system or a monitoring tool, and its breadth means dedicated engineering tools will go deeper. It's also a young product, publicly launched in July 2026. If you want to look, there's a 14-day trial and the plans are on the pricing page.
FAQ
What does a startup CTO do if they don't write code anymore?
They usually own one of three things: the architecture, the engineering organization, or the product direction. Greg Brockman found most CTOs he spoke to focused on making the technology organization work. Some, including him at Stripe, later went back to coding by choice.
Should a startup hire a CTO or a VP of engineering first?
A CTO first, often as a cofounder, because someone has to own technical direction from the start. A VP of engineering comes when management starts to take over the CTO's week, which the MIT entrepreneurship center puts at a team of about 15 to 20.
How much equity does a startup CTO get?
For an outside CTO hired at Series A in the US, A.Team's 2026 guide gives 1% to 3%, vesting over four years, alongside a $250,000 to $350,000 base. A cofounder CTO's stake comes from the founders' split, not from hiring benchmarks.
Is a fractional CTO worth it?
Often, before Series A. A.Team prices an active fractional CTO at about $15,000 a month on average and calls the model most cost-efficient from seed to Series A. It works best when you have engineers who need direction, not when you need someone to write the product.