Negotiating CTO Equity Package vs Salary: Scripts for Pre‑Seed Startup Offers
TL;DR
A pre‑seed CTO must prioritize equity signal over headline salary because early‑stage risk is the real cost. The decisive judgment is to anchor negotiations on ownership growth rather than cash compensation. Use the scripts below to lock in a dilution‑protected equity grant, a market‑aligned salary floor, and a milestone‑based vesting cadence.
Who This Is For
You are a senior engineer or product leader with 8‑12 years of full‑stack experience, currently earning $180k‑$210k base at a mid‑size tech firm, and you have received a CTO title from a seed‑stage startup that just closed a $3M round. You are comfortable with product leadership but have never structured an equity package, and you need a concrete judgment on how to balance cash versus ownership before you sign.
How should a CTO evaluate equity versus salary in a pre‑seed offer?
The answer is to treat equity as the primary lever of compensation; salary becomes a secondary safety net. In a Q2 debrief, the hiring committee argued that a $190k salary looked generous, but the hiring manager reminded us that the real value lies in the equity grant’s anti‑dilution clause. The committee’s judgment: equity determines long‑term upside, salary only mitigates immediate cash flow concerns.
The first counter‑intuitive truth is that “higher cash does not equal lower risk.” Early‑stage risk is borne by the ownership stake, not the paycheck. An equity grant of 1.2 % with a 20 % anti‑dilution provision will outperform a $30k salary bump over a five‑year horizon if the company reaches a $150M exit. The framework we use is the Ownership‑Risk Matrix, which plots cash on the X‑axis and equity protection on the Y‑axis. A CTO should aim for the upper‑right quadrant: high protection, modest cash.
Script – opening the equity conversation:
> “I’m excited about the vision, and I see the CTO role as a partnership. To align incentives, I need a grant that includes a 20 % anti‑dilution clause and a vesting schedule tied to product milestones rather than a static four‑year timeline.”
The judgment is clear: demand protective equity terms first; negotiate salary only after the equity package is locked.
What specific equity clauses should a CTO demand in a pre‑seed agreement?
The answer is three clauses: anti‑dilution protection, double‑trigger acceleration, and a performance‑based vesting schedule. In a hiring‑manager conversation after the third interview round, the manager tried to brush off anti‑dilution as “standard for founders only.” I reminded her that the board’s legal counsel had just rejected a similar clause for a senior engineer, citing the same risk profile. The judgment: any CTO who concedes on these clauses is signaling low confidence in the company’s future.
- Anti‑dilution protection (e.g., 20 % price‑adjustment on future rounds).
- Double‑trigger acceleration (full vesting upon change of control and termination without cause).
- Milestone‑based vesting (e.g., 25 % after MVP launch, 25 % after Series A, remainder over 24 months).
Not “just a grant,” but “a grant with protective mechanics.” This signals to investors that the CTO is treating the role as a true co‑founder.
Script – requesting the clause:
> “Given the pre‑seed stage, I need a 20 % anti‑dilution provision that adjusts my grant price on the next financing round. Additionally, I would like double‑trigger acceleration tied to a change‑of‑control event, and vesting that accelerates on the MVP delivery milestone.”
The judgment is to embed these clauses in the term sheet before any salary discussion.
How can a CTO negotiate a realistic salary floor without jeopardizing equity talks?
The answer is to anchor the salary at a market‑based floor and then frame it as a “risk‑adjusted cash component.” In a hiring‑committee debrief after the fourth interview, the senior engineer on the panel suggested a $210k base, but the CTO‑to‑be argued that the cash component should reflect the cost of living in San Francisco plus a 10 % risk premium. The judgment: the salary is a concession, not a lever; it must be justified by market data, not by personal need.
Use a three‑point script:
- Cite industry benchmarks (e.g., $190k‑$210k for CTOs at $3M‑$5M pre‑seed stage).
- Add a risk premium (“I’m taking on product‑delivery risk, so I need a $20k risk premium”).
- Tie salary to a review clause (“Let’s revisit compensation after Series A when the runway extends beyond 12 months”).
Not “just a number,” but “a data‑driven floor with a built‑in review.” This keeps the negotiation focused on equity protection while still securing a livable cash baseline.
Script – salary anchor:
> “Based on current market data for CTOs at pre‑seed companies, a base salary of $200k is appropriate. I propose we embed a six‑month review tied to the Series A close to adjust cash compensation as the risk profile changes.”
The judgment: set a firm floor, then use the review clause to revisit cash later.
When is it appropriate to ask for a signing bonus versus a larger equity grant?
The answer is only when the startup’s cash runway is insufficient to meet the salary floor; otherwise, a signing bonus dilutes the equity pool and signals misaligned risk appetite. In a Q1 board meeting, the CFO argued for a $25k signing bonus to sweeten the offer, but the lead investor pushed back, stating that any cash outlay reduces runway and escalates dilution. The judgment: a signing bonus is a red flag that the company is low on cash and the CTO should demand more equity, not cash.
If the company can’t meet a $190k base, request a larger grant (e.g., increase from 1.2 % to 1.5 %). If cash is available, a modest signing bonus (no more than $10k) can be used to cover relocation expenses, not as compensation for risk.
Script – refusing a signing bonus:
> “I appreciate the offer of a $25k signing bonus, but given the runway constraints, I’d prefer to increase my equity grant to 1.5 % with the same protective clauses. This aligns my incentives with the company’s growth without straining cash resources.”
The judgment is to treat a signing bonus as a negotiation lever only when cash is scarce; otherwise, replace it with equity.
How should a CTO handle vesting schedule negotiations to protect against founder turnover?
The answer is to demand a hybrid vesting schedule that combines time‑based and milestone‑based components, with a clause for accelerated vesting upon founder exit. In a post‑interview debrief, the CEO tried to lock the CTO into a straight‑line four‑year schedule, but the hiring manager cited a recent case where a CTO lost 0.8 % ownership when the founder left after 12 months. The judgment: a pure time‑based schedule is a risk to the CTO; a hybrid schedule mitigates that risk.
Proposed schedule:
- 25 % vested upon successful MVP launch (Month 6).
- 25 % vested at Series A close (Month 12).
- Remaining 50 % vesting monthly over the next 24 months, with double‑trigger acceleration if the CEO departs without cause.
Not “standard 4‑year,” but “a schedule that ties vesting to product milestones and founder stability.”
Script – vesting negotiation:
> “I propose a vesting structure where 25 % vests on MVP delivery, another 25 % at Series A, and the balance vests monthly over two years, with double‑trigger acceleration if the founding team exits without cause. This aligns my equity with company milestones and protects against founder turnover.”
The judgment: embed milestone triggers and protective acceleration to safeguard ownership.
Preparation Checklist
- Review recent pre‑seed CTO term sheets from comparable companies (Series A valuation $30‑$45 M, equity grants 1‑1.5 %).
- Compile market salary data for CTOs in the Bay Area (base $190k‑$210k, risk premium +10 %).
- Draft a one‑page equity protection summary (anti‑dilution, acceleration, milestone vesting).
- Prepare a negotiation script that opens with equity clauses before mentioning cash.
- Anticipate founder concerns about dilution; have a dilution‑impact calculator ready.
- Align your ask with the company’s runway (e.g., 12‑month cash runway after Series A).
- Work through a structured preparation system (the PM Interview Playbook covers equity negotiation with real debrief examples and scripts).
Mistakes to Avoid
BAD: “I’ll take whatever salary you can afford; equity is secondary.” GOOD: “Equity is the primary lever; I’ll accept a modest cash floor only if protective clauses are in place.” The first approach signals low confidence and invites cash‑only offers.
BAD: Accepting a standard four‑year vesting schedule without milestones. GOOD: Negotiating a hybrid schedule that vests on MVP launch and Series A, then monthly thereafter. The latter protects against founder turnover and aligns incentives with product success.
BAD: Ignoring anti‑dilution and assuming the grant will stay constant. GOOD: Demanding a 20 % anti‑dilution clause and modeling dilution scenarios. The latter prevents unexpected ownership erosion in future rounds.
FAQ
What is a reasonable equity percentage for a CTO at a $3M pre‑seed startup?
The judgment is 1.0 %‑1.5 % with anti‑dilution protection; anything below 0.8 % is a red flag that the company undervalues the role.
How long should the salary negotiation take before signing the term sheet?
The judgment is no more than three business days after the offer; any longer signals indecision and gives the founder leverage to retract.
Should I ask for a higher signing bonus if the startup’s cash runway is limited?
The judgment is to refuse a signing bonus when cash is scarce and instead ask for a larger equity grant; a bonus in that scenario merely reduces runway and increases dilution.
The 0→1 PM Interview Playbook (2026 Edition) — view on Amazon →