CTO Salary Benchmark Guide for Series A to B

CTO salary benchmark guide: how to price base, bonus, and equity at Series A to B

In 2026, CTO base pay spans roughly $183,000 to $390,000, and total compensation often clears $600,000 at funded startups and public companies once equity and bonus are part of the deal (KORE1 CTO Salary Guide 2026). City swings are just as sharp. San Francisco averages around $315,000 and can run to $456,750, while Tampa averages near $164,250 (CBT Nuggets salary table). That spread is exactly why a CTO salary benchmark can’t be a single number.

This guide walks through how to use The Art of CTO Compensation Benchmark to price your own role, and to set ranges for VP Engineering and other tech execs. The goal is straightforward. Pay should match scope, risk, and the company’s capital plan, not the title on a LinkedIn profile.

CTO Compensation Benchmark: what it is and how to use it

The CTO Compensation Benchmark is a research-backed view of salary and total compensation for CTOs and tech executives. It breaks data down by company stage, team size, and geography. That segmentation is the point. A Series A CTO leading 35 engineers has a different job than a “CTO” at a 12-person seed startup.

Where I’ve seen teams get the most value is treating the benchmark like a calibration step, not an answer key.

What the benchmark helps you compare

Base salary by stage and location
Equity ranges by join timing and role scope
Bonus patterns and how targets change as the company matures
Total compensation as a package, not a headline number

A good benchmark session ends with a written comp thesis. It should line up with the business plan, the hiring plan, and the risk profile.

CTO salary benchmark by stage and scope (Series A and B reality)

Series A and early Series B is the hardest band for a lot of CTOs I talk to. You’re still shipping. You’re still recruiting. And you’re carrying board-level risk for uptime, security, and delivery dates.

Startup CTO compensation: typical ranges by stage

Here are ranges that show up across multiple datasets and recruiter guides.

Seed to Series A CTO: $100,000 to $175,000 base and 1 to 5 percent equity (My Personal Recruiter CTO salary guide). KORE1 puts early stage base closer to $150,000 to $220,000, with 1 to 5 percent equity for a founding or first CTO hire (KORE1 CTO Salary Guide 2026).
Series A CTO: $180,000 to $240,000 base and 1 to 3 percent equity (KORE1 Series A section).
Series B to D CTO: $250,000 to $350,000 base, with total compensation often $400,000 to $650,000 after bonus and equity value assumptions (KORE1 growth stage ranges).

Those numbers assume US market norms. Geography changes the cash number fast.

Geography: why “remote” is not a single rate

Comp bands often follow local market pricing, not job value. San Francisco, Seattle, New York, and San Jose show average CTO salaries around $315,000 in one city-level dataset, with a high end near $456,750 (CBT Nuggets salary table). Other US cities sit closer to $160,000 to $200,000 averages.

Outside the US, the same title prices differently too. One executive benchmarking guide cites $280,000 to $380,000 base in San Francisco, versus £180,000 to £240,000 in London, and €160,000 to €220,000 in Berlin for comparable mid-stage roles (ArubaExec benchmarking guide).

So what should a Series A CTO do with this? Pick a comp “home market” and write it down. If the company hires in two hubs and three lower-cost regions, the comp philosophy needs to say which market anchors offers.

Founder vs non founder: the cash premium is real

Founding CTOs often take less cash and more ownership. Non-founding CTOs usually price closer to market salary.

Kruze Consulting reports a clear gap. In their dataset, founding CTOs average $139,000, while non-founding CTOs average $213,000. At Series A, founders average $177,000 and non-founders average $293,000 (Kruze Consulting startup CTO salary).

This matters for Series A and B boards. If the company wants a “professional CTO” to replace a founder, the cash budget has to match that decision. If it doesn’t, you’ll end up with a quiet mismatch that shows up later as churn, missed delivery, or both.

CTO equity benchmarks: how to value ownership after dilution

Equity is where most comp conversations go sideways. People argue about percent, then never model dilution or exit odds.

Here’s a definition teams can reuse.

The Art of CTO definition: CTO equity is payment for risk and time. It only makes sense when modeled against dilution, vesting, and the company’s funding plan.

Typical CTO equity benchmarks by join timing

These ranges show up across common startup comp guides.

Co founder CTO: often 15 to 30 percent at formation, before outside capital
First CTO hire at pre seed or seed: often 2 to 5 percent
Series A CTO: often 1 to 3 percent
Series B CTO: often 0.5 to 1.5 percent

Many guides assume a 4-year vest with a 1-year cliff. That schedule is normal. The terms around it are what change the real value.

The dilution math most CTOs skip

A percent number is not a value. A simple model keeps everyone honest.

Example:

Grant: 1.5 percent at Series A
Funding plan: Series B and Series C raise that doubles the option pool once
Dilution: assume 50 percent dilution from future rounds and pool changes
Ownership at exit: 0.75 percent

Now price outcomes:

Exit at $200M: 0.75 percent is $1.5M on paper
Exit at $1B: 0.75 percent is $7.5M on paper
No exit: $0

That spread is why CTOs should negotiate both percent and terms.

Terms that change equity value more than percent

Some terms show up in recruiter guides as common negotiation points.

Acceleration: single trigger or double trigger language can change outcomes in an acquisition (My Personal Recruiter negotiation list)
Refresh grants: annual top ups matter once the first grant is half vested
Severance: 6 to 12 months is common for exec roles, but many startups omit it until asked (My Personal Recruiter negotiation list)

Equity also needs an internal system. Ravio describes equity banding as a way to keep grants consistent by level, and to support refresh grants and promotion increases (Ravio equity compensation guide). The same idea works for CTO and VP Engineering grants, even if the numbers differ.

VP engineering compensation data and the CTO to VP split

Series A and B companies often blur CTO and VP Engineering. That’s where comp gets weird fast.

Here’s the rule of thumb I use. CTO comp should price for external risk and cross-company scope. VP Engineering comp should price for delivery, hiring, and org health.

A quick comparison table for Series A to B

Dimension	CTO (Series A to B)	VP Engineering (Series A to B)
Primary scope	Tech strategy, architecture, risk, exec alignment	Execution, delivery, hiring, org design
Board exposure	High	Medium
Equity expectation	Higher, tied to company risk	Lower, tied to execution scope
Common failure mode	Too hands on, no delegation	Great delivery, weak tech direction

This split matters for comp because the job is different. It also matters for career ladders. Our guide to engineering career ladders and leveling should match the comp bands, or people will spot the mismatch fast.

For teams that want to formalize the split, pair this guide with:

Internal link: our guide to org design for platform and product teams.
Internal link: our guide to engineering manager and director leveling.
Internal link: our guide to building a staff plus engineering track.

(Those topics keep comp tied to scope, not personality.)

Tech executive salary ranges: base, bonus, and the metrics trap

A lot of CTOs focus on base and equity, then treat bonus like an afterthought. That fails at Series B and beyond, because bonus is where boards try to “pay for outcomes.”

Riviera Partners notes a shift toward blended packages with more performance-based incentives, tied to measurable outcomes like platform modernization and cost goals (Riviera Partners executive compensation trends 2025). Public company placements in their report show bonuses as standard.

Bonus patterns show up in adjacent exec roles too. The L Suite reports 73 percent of legal exec respondents were bonus eligible, with median target bonuses of 20 to 25 percent of base at Series D and earlier, and 30 to 35 percent at Series E and later (The L Suite GC comp trends 2025). CTO bonus targets often follow a similar maturity curve, even if the exact numbers differ.

The metrics trap

The catch is that CTO bonus metrics can punish good engineering. You can hit the numbers and still wreck the system.

Bad metric set:

Ship dates only
Headcount growth only
Cloud cost down only

Good metric set:

Availability and latency tied to customer impact
Security posture milestones tied to audit dates
Delivery predictability tied to planning accuracy

This is where CTOs need to connect bonus design to engineering systems. Use DORA metrics carefully. Pair them with product outcomes. Our Engineering Metrics Dashboard tool and guide can help teams track lead time and deploy frequency without turning them into a weapon.

Enterprise implications for Series A and B CTOs

Comp feels personal, but it changes company outcomes.

Hiring plan risk: Underpaying the CTO role forces “hero mode” and slows hiring. At 10 to 100 engineers, that delay can cost a full quarter of roadmap.
Retention risk: Mispriced equity and no refresh grants create a cliff at year two. People leave right as systems get complex.
Governance risk: If the CTO package ignores security and reliability scope, the company pays later in incidents. Tie comp to ownership of SLOs and incident response.
Internal equity risk: A VP Engineering paid above the CTO, or a director paid near the VP, creates politics. Fixing it later costs more.

For governance, teams can track comp decisions like any other risk. The Art of CTO Command Center can hold the record of role scope, comp bands, and the rationale, next to incidents and tech debt.

CTO recommendations: how to use the benchmark in real negotiations

Immediate actions

Write the role scope. List systems owned, team size, and board exposure. Tie it to the next 12 months plan.
Pick a home market. Decide which city or region anchors cash. Document remote adjustments.
Model dilution. Build a one-page cap table scenario with two future rounds and an option pool increase.
Ask for terms, not just percent. Push on acceleration, refresh grants, and severance language.

Policy framework for Series A to B companies

Comp philosophy. State target percentile and market anchor. State how remote pay works.
Equity bands. Define bands by level and role family. Use ownership percent or grant value, but pick one.
Refresh policy. Set a cadence, often annual, with triggers like promotion or scope change.
Offer review loop. Require CEO, CFO, and board comp committee review for exec offers.

For build versus buy decisions that affect scope and comp, use our Build vs Buy Matrix tool. A CTO running a heavy build plan carries more delivery risk than a CTO buying a mature platform.

Architecture principles that connect to compensation

Risk priced into scope. If the CTO owns security and uptime, comp should reflect it.
Systems ownership clarity. Tie equity and bonus to clear ownership boundaries.
Operational maturity targets. Set SLOs and incident response expectations. Then tie bonus to outcomes.

For incident-driven bonus metrics, pair this with our guide to incident postmortems and the Incident Postmortem tool. It keeps the company honest about what “good” looks like.

Bigger picture: comp is a strategy tool, not a perk

Executive pay is shifting toward measurable outcomes and mixed cash plus equity packages, especially in VC-backed and public companies (Riviera Partners executive compensation trends 2025). At the same time, geography keeps fragmenting pay bands, even for the same job (ArubaExec benchmarking guide).

For Series A and B CTOs, the real work is alignment. The package needs to match the company’s risk appetite, the funding plan, and the operating model. If the company wants a CTO to run a platform rebuild, the equity and bonus plan should say that out loud.

If the company’s comp philosophy is fuzzy, people fill the gap with rumors. Then leaders start negotiating against each other.

The question is simple: does the company pay for the outcomes it claims to value, or does it pay for titles and hope for the best?

Use the CTO Compensation Benchmark tool

CTO Salary Benchmark Guide: How to Price Base, Bonus, and Equity at Series A to B