Skills / Raising the round / SAFE stacking math

How many SAFEs can I stack before dilution surprises me at conversion?

Every name on your cap table is also a customer, an acquirer, or a disclosure problem.

safe-stacking-math

SKILL.md · 1,923 words

Verified Sept 2026

Download the folder
What your agent reads.
name
safe-stacking-math
description
SAFE stacking and conversion math for cybersecurity founders. Post-money SAFEs at several valuation caps, what lands on the day the stack converts at the Series A (pro rata side letters, the option-pool increase, an uncapped MFN, a cap the round prices at or under), the bridge or extension as the base case, and who holds a security company's SAFEs (sitting CISO angels, CISO syndicates, customers or design partners asking for equity, corporate venture arms, specialist cyber funds) and what each does at conversion. Use when a founder signs another SAFE, grants a side letter or MFN, sets or defends a cap, models dilution before a priced round, is stacking SAFEs to defer pricing the company, is asked why the cap table carries several caps, or plans a bridge or extension. Not round size or the Series A bar (see cyber-seed-benchmarks). Not whose money to take (see who-leads-cyber-seed). Not what to pay CISO advisors (see ciso-advisor-equity). Not whether to take CVC or customer money (see strategic-and-cvc-money).
title
SAFE stacking math
question
How many SAFEs can I stack before dilution surprises me at conversion?
subtitle
Every name on your cap table is also a customer, an acquirer, or a disclosure problem.
summary
You will not be surprised by the arithmetic of a SAFE, because it is simple. You will be surprised on the day the whole stack converts at once, when every side letter, option grant, and cap you deferred lands in the same week, and by who is holding the paper, because in a security company your angels are also your buyers and your acquirers.
group
raise
verified
2026-09-09
order
26

1023 / 1024 characters

This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.

You will not be surprised by the arithmetic. A post-money SAFE sells a percentage equal to the purchase amount divided by the cap, a stack of them adds up, and the standard forms are published with a worked example for every case below. The surprise arrives on the day the stack converts, when everything you deferred lands at once: the side letters, the increase in the option pool, a cap that turns out to be a ceiling, and the bridge round nobody put in the deck. You are the person who has to walk each of those back to the investors who backed you first, and in a security company those investors are often your buyers and your acquirers.

A SAFE was built for a company too early to price.

You are using an instrument invented for one narrow situation. You and an investor both want to do the deal, the company is genuinely too early to price, and neither of you wants to spend six weeks and two lawyers arguing about a number that is a guess either way. So you skip the argument. The cap and the discount stand in for a price, and they are rough stand-ins.

That is the honest use, and it has drifted. SAFEs now run the whole length of a company's fundraising, and one common reason is to avoid re-pricing a company whose last valuation has started to look too high. Deferring a price does not fix a price. It moves the conversation to the day the stack converts, and turns it into someone else's condition of closing.

So know how your stack reads. A seed-stage company with several SAFEs at different caps raises questions before it raises money, and those questions are slow ones: what was promised, at what price, to whom, and why the price moved. Hold the cleanest cap table you can at every stage. Cap tables get complicated on their own as a company ages; starting complicated spends time you do not have.

Keep a ledger, not a list of caps.

You keep one ledger with every instrument on it, showing the amount, the cap, the discount, any most-favored-nation clause, any side letter, and who holds it, and you read your ownership off that ledger and never off the most recent cap. Each post-money SAFE fixes its holder's percentage against its own cap, and the percentages add together. A later SAFE with a higher cap does not reduce an earlier one with a lower cap. It sits beside it. Nothing you grant before the priced round dilutes the SAFE holders, so every option you hand out in between comes out of the founders and the pool that already existed. Stack enough of them against one cap and you have sold the whole company.

Amount divided by cap is the rule for cap-only paper and only for cap-only paper. A SAFE that carries both a cap and a discount converts on whichever is better for its holder, so carry it as a range until a price exists. Read the form before you add the row, because a SAFE with both a cap and a discount is not the standard form, and someone drafted it that way for a reason.

The most important column in the ledger is who holds the paper, not what the cap is.

Everything you deferred converts on the same day.

You will renegotiate every term you were told was simple, in one week, against the people who backed you first, and the new lead investor will make it a condition of closing. SAFEs are sold as the instrument that lets you defer the argument. They do not remove the argument. They postpone it to the moment when you have the least leverage, because conversion stays abstract until a price exists and the lead has no interest in inheriting any of it. Signing is cheap. Conversion is where counsel earns the fee.

A pro rata right buys a seat at the allocation conversation, not the allocation itself. The lead negotiates its ownership target first, the round size is fixed, so every adjustment lands on the existing investors, and they get cut to a fraction of what their side letters promised. We have watched that happen in competitive round after competitive round, and the existing investors notice. Ration the right before you grant it, by setting a minimum check size, and remember that your earliest backers are the people you will need in the next hard moment.

The option pool splits in two. The increase the lead requires at the Series A dilutes the SAFE holders and the founders alike. Every option you granted between the first SAFE and the Series A dilutes only the founders, and in a security company those grants are the CISO advisors you collected along the way. And an uncapped most-favored-nation clause inherits the worst paper you ever issue, including a side letter. Never give one to a holder you would be embarrassed to hand your bridge terms to.

The cap is a milestone.

The advice is to take the highest cap you can get, as if the cap were a free option. A cap is a ceiling on what the holder pays, not a floor on what you keep. If the priced round lands at or below the cap, the SAFE converts at the round price and takes more of the company than the cap implied. The trap is not the down round. The trap is a flat round against a cap set in a hot quarter, a cap that looked like a discount to the Series A and turns out to be the Series A.

We have watched founders raise the smallest amount at the highest price that covered the plan, and then miss the plan by two quarters. The financing that followed cost them far more than the money they turned down at the start. Minimizing dilution at the seed is treated as basic hygiene. It is a bet that the plan works to the quarter, and the instrument that rescues a founder who lost that bet is priced against their lack of alternatives. Take a lower clean cap over a higher one with a discount or side letters attached, and negotiate what happens on a miss before you sign.

The bridge round is the normal outcome.

You are more likely to raise a bridge than to raise the Series A on the schedule in your seed deck. In the seed-stage security companies we have watched, the bridge or the inside round has been the usual path between a seed and a priced round, and the standard model still presents it as a failure. If you treat it as an aberration, you will meet it unprepared and late.

The milestones a priced round requires take longer than the runway a seed buys, and in a security company the gap is wider, because the security review and the proof-of-concept process sit between a signed pilot and the revenue a lead wants to see. Your next investor is most often the investors you already have. Plan your financing around your existing cap table, because those are the people you will be negotiating with.

A bridge is not a fundraise.

The temptation is to run the bridge like a round and create competitive tension. The consent rules make that impossible. Existing preferred investors can block anything senior to their position, and your claim of soft-circled outside money is not a credible alternative to people who can see your bank balance. Trying to create tension damages the one relationship the bridge depends on.

A bridge is usually a convertible note, and a note ranks senior to every SAFE you signed. The discount, the warrant, or the extra layer of preference you accept to close it quickly is a price cut deferred with interest, payable at the exit, where a buyer prices the company and not the cap table. In a modest outcome the whole stack has to collapse before anything closes at all, and that negotiation happens among your own investors while you have no leverage. Consent is also mechanical. The board must formally agree before any SAFE is issued, and once preferred stock exists your charter may require more. Read it before you promise anyone a wire date.

The ledger is a list of buyers.

You are stacking relationships, not caps. In this industry the angel list is people who run security reviews, sit on procurement committees, and work in corporate development at the platforms that will one day bid for you. Every row is a customer, an acquirer, or a disclosure problem, and the Series A lead will read it that way.

A sitting CISO on your cap table is ordinary at conversion and a disclosure event in your own security review at their employer. Put the disclosure in writing where their procurement team can see it, never bundle the SAFE with a pilot, and treat that account as a reference rather than as recurring revenue. A CISO investment syndicate is money, not deal flow. A customer asking for equity instead of paying is structure plus a disclosure problem inside their own procurement, so keep the commercial contract and the investment on separate paper, each with its own end date. A corporate venture arm is a wire, not a relationship, and from the day you sign it narrows your acquirer list to buyers comfortable owning what a rival holds. A specialist cyber fund will usually ask for the pro rata side letter, so decide before you grant it how you will ration it, because the same fund is the one you will need at the bridge. An uncapped most-favored-nation holder is in the room for every SAFE you sign afterward.

An acquisition can arrive before any priced round, and in security it often does. On a sale, each holder takes the greater of their money back or their converted share, so the total purchase amount on the ledger is a floor the price has to clear before founders and common stock see anything. An acquirer is buying that floor and the disclosures beside it, and prices both.

Working the question.

  1. Write the ledger: every instrument, with amount, cap, discount, most-favored-nation clause, side letter, and the type of holder.
  2. Add up the ownership sold, amount divided by cap for every cap-only instrument, and add every option granted since the first SAFE. Carry any cap-plus-discount paper as a range.
  3. Work backward to the pro rata from the Series A ownership you will accept, less the lead's target and the pool increase it will require. Decide now, by minimum check size, who keeps the side letter.
  4. Stress the cap three ways: the round at the cap, below it, and comfortably above it.
  5. Plan the bridge as the base case: who writes it, what they will ask for, who has to consent, and what the lead will want cleaned up.
  6. Tag each holder for the buyer and acquirer test, and move customers, sitting CISOs, and corporates onto paper separate from the commercial relationship.
  7. Run the model again before every signature.

Working with an agent.

Give your agent every instrument you have signed. Ask it for one ledger carrying the amount, the cap, the discount, any side letter and the holder on each row, and then the total ownership you have already sold. That total is your ownership. The most recent cap is not.

Install the skill.

You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.

mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/safe-stacking-math.zip && unzip -oq safe-stacking-math.zip && rm safe-stacking-math.zip

safe-stacking-math/SKILL.md

No terminal? Download safe-stacking-math.zip and drop into your assistant’s project files.

Kevin Skapinetz

Tell us what you see.

Whether you’re thinking about starting a company, building one in stealth, or raising a round: send Kevin or Dan what you see on LinkedIn, in your words.