Almost every founder we meet started with the same cap table: a Google Sheet with a founder tab, an angels tab, an option pool tab, and a fully-diluted total at the bottom that is off by a few basis points nobody has time to fix. It works. Until it doesn't.
The moment it stops working is almost always the same: the first priced round. A term sheet arrives, the lead's counsel asks for the fully-diluted table, and the founder discovers three things at once — the SAFEs do not convert cleanly, the option pool math depends on which pre-money you use, and the side letter granted to an angel last summer changes the pro-rata calculation on this round.
This is not a spreadsheet skill problem. It is a data-model problem. Cap tables are graphs, not tables, and a Series A is where the graph shape starts to matter.
Where the spreadsheet actually breaks
1. SAFE and note conversion
A SAFE is not a row. It is a set of conditional promises: convert at the lower of a cap and a discount, on the first qualifying priced round, into the same class as new money, sometimes with an MFN clause that references the terms of other SAFEs. Modeling that in cells means writing conditional logic that only the person who wrote it can maintain, and re-writing it every time a new SAFE is signed.
The failure mode is silent. The sheet returns a number. The number is wrong by two percent. Two percent of a Series A is real ownership.
2. Option pool sizing
The Series A almost always includes a pool refresh, and the refresh is almost always sized out of the pre-money. Which means every point you add to the pool comes out of the founders and existing investors, not the new lead. Which means the founders need to model at least four scenarios: unchanged pool, 10 percent post, 12 percent post, and whatever the lead actually asks for. In a spreadsheet, each scenario is a copy-paste that quietly drifts.
3. Waterfalls and preferences
As soon as you have a priced round you have a preference stack. As soon as you have a preference stack you have a waterfall. And as soon as you have a waterfall, an exit at any given valuation returns wildly different numbers to different holders depending on liquidation preference, participation and seniority. Founders who cannot show this waterfall to a prospective acquirer or a departing employee lose credibility fast.
4. Side letters and MFNs
Most seed rounds accumulate a handful of side letters — extra information rights, pro-rata guarantees, most-favored-nation clauses. None of them live in the cap table. All of them affect it. When the Series A closes and one angel discovers their MFN was ignored, the founder is the one who eats the cleanup.
The spreadsheet cap table does not fail loudly. It fails silently and then embarrassingly, usually in front of the person you were trying to impress.
What a real cap table looks like
A cap table that survives Series A has four properties.
It is instrument-aware. A SAFE is a SAFE, a note is a note, a share is a share, and each type carries its own conversion, vesting and preference logic. The system knows what a post-money SAFE with a 15 percent discount does when a priced round clears at a given pre-money.
It is scenario-native. Every question a founder gets — 'what happens if we take the higher pre-money with a bigger pool', 'what if we accept the tender at eighty percent' — resolves in seconds because the underlying graph runs the math, not a copy of the sheet.
It is shared. The founder, the lead's counsel, the CFO and eventually the auditors all read the same object. No one is emailing screenshots. When something changes, everyone sees the change.
It is auditable. Every issuance, transfer, cancellation and repricing is a dated event with a document behind it. When someone asks 'why does this angel own 0.42 percent', the answer is a link, not a memory.
How to migrate without losing a week
Migration sounds heavy. It does not have to be. The order that works is the reverse of what most founders try.
Start with the current fully-diluted state, not the history. Load the current holders, the current instruments and the current pool. Reconcile that against the last agreed number from the spreadsheet. If they match, you have a working baseline.
Then, and only then, layer in the historical events — the founder issuances, the seed SAFE, the pool grants, the leavers. History is nice to have for audit; it is not what the Series A lead is going to look at first.
Then model the round itself as a scenario on top of the baseline. Pre-money, new money, pool refresh, SAFE conversion, side letters. The output is the pro forma table the lead's counsel will actually ask for.
The whole exercise, done in this order, takes an afternoon for a typical seed-stage company. Doing it in the wrong order — trying to reconstruct three years of history before you have a baseline — is what costs a week.
Where Equavion fits
Equity in Equavion is instrument-aware from day one. SAFEs, notes, options, RSUs and priced shares are first-class objects with their own conversion and vesting behavior. The Scenario Modeler runs any 'what if' — pool size, pre-money, waterfall — against the live graph and returns a pro forma table you can share with the lead's counsel. Every event has a document behind it. When the Series A closes, the numbers everyone signed are the numbers you already had.
Takeaways
- The spreadsheet cap table breaks at Series A, not before, and it breaks silently.
- The four common failure points are SAFE conversion, pool refresh math, waterfalls and side letters.
- A real cap table is instrument-aware, scenario-native, shared and auditable.
- Migrate by baselining the current state first, then layering in history, then modeling the round.
