How to read a startup cap table as a founder

How to read a cap table is a different skill from knowing what one is. Definitions live in What is a startup cap table. This post is a founder reading order: which screen to open first, which numbers to trust for a partner call, and which red flags mean you stop quoting ownership until counsel or the ledger catches up. It uses Cap Table labels (checked 31 Oct 2026). It is operator guidance, not legal, tax, or accounting advice.

How to read a cap table before you speak ownership

Never open with a remembered percentage. Open the live ledger. In Nautis, click Cap Table, land on Overview, hit Refresh, then read issued shares, authorized shares, fully diluted shares, and the option pool before you say anything on a call. If Overview and your slide deck disagree, the deck loses until you update it.

Reading is a sequence. Skimming Equity for one investor while ignoring fully diluted totals is how founders accidentally promise a percentage that only exists on a pre-dilution fantasy. Treat the tabs as an interrogation script, not a museum tour.

Reading order by tab

Move top to bottom. Do not jump to Scenarios to "make the number look fine" before Overview and Equity agree with Documents. If first-time setup is still incomplete (currency, total authorized shares, par value, initial shareholders), finish Complete Setup before you treat Overview as gospel. An unfinished setup produces empty confidence. Time-box the full pass: ten minutes for Overview and pie basis, ten for Equity versus Documents on the two largest instruments, five for a named Scenario you will not confuse with current state. If any block overruns because rows are missing, the meeting prep outcome is a fix list, not a fake percentage.

Overview numbers, the pie, and the four checks

Overview is the at-a-glance dashboard: ownership pie by stakeholder; totals for issued, authorized, fully diluted, and the option pool; breakdown by Founders vs Investors vs ESOP; recent transactions and alerts (for example issuing more than authorized). Refresh pulls the latest. Export All Data (JSON) backups the table; Import All Data restores a prior export.

Four checks to say aloud

1. Issued versus authorized: are you approaching a limit that needs a board fix before more grants?
2. Fully diluted versus the pie you memorized: are convertibles and options already in the diluted view?
3. Option pool: does the remaining pool cover the hires you just promised in the pitch?
4. Alerts: is Overview already telling you something is inconsistent?

If you cannot answer those four, you are not ready to quote ownership to an investor. Write the four answers in CRM Notes on the active round if helpful, so co-founders stop improvising different percentages in separate threads.

Pie chart literacy without false comfort

The Overview pie is a communication aid, not a substitute for the totals row. Read the pie for stakeholder mix, then verify the same story in the numeric totals. If the pie looks founder-heavy but fully diluted tells a different story because of a large pool or stacked convertibles, believe fully diluted for outside conversations. When an investor asks what founders own, answer with the basis: issued only or fully diluted. Say which Overview number you used. Silence on basis is how two honest people leave a call with different percentages.

Stakeholders, Equity, Documents, and CRM cross-reads

Stakeholders lists people and entities. Add Stakeholder when someone new appears; types include Founder, Investor, Employee, Advisor, Consultant, or Other. Before a diligence week, search for duplicate names and empty types. Ghost stakeholders make pie charts lie.

Equity is where instruments live. Create Instrument for priced preferred, SAFEs, convertible notes, options, and related forms. For SAFEs and notes, principal, discount, and valuation cap belong on the instrument; Conversions comes later when they become shares. Every Won wire in Fundraising CRM should have a matching Equity row the same day. Orphan wires are how ownership fights start. When you read Equity, scan by instrument type so SAFEs, notes, and preferred do not blur into one "investors" blob. Blurred blobs are fine for storytelling; they are fatal for diligence.

Documents should hold the signed PDFs and board consents that justify Equity rows. Pick one material investor and confirm the PDF terms match the instrument fields. If they do not, stop the narrative and fix the row before the meeting continues.

For SAFE conversion vocabulary without reteaching the whole instrument, see SAFE note explained for startups. Keep CRM stages honest so Raised does not imply Cap Table rows that do not exist. During an active raise, pair Monday Overview four-checks with a quick CRM pass: every Won convertible should appear on Equity. That cross-read catches the most common pre-call lie: celebrating money that never reached the ledger. If CRM shows Won and Equity is empty, the read failed even if Overview still "looks fine" from founder shares alone.

Scenarios, Conversions, and futures versus current truth

Scenarios answer forward questions: what if we take this SAFE, expand the pool, or price a round. Read Scenarios only after Overview is clean and Equity matches Documents. Save named scenarios with dates. Do not screenshot an unsaved sandbox and paste it into a partner email as current ownership.

When a SAFE or note converts, reading does not stop at Equity history. Open Conversions (or the converted share rows counsel directs you to record), confirm the resulting preferred or other shares appear, then return to Overview fully diluted. If Documents still only show the old SAFE and Overview never moved, you are mid-migration: do not brief the board as if conversion finished. Archive or relabel pre-conversion Scenarios so nobody forwards yesterday's sandbox as today's cap. Conversion week is mostly reconciliation: PDF, Conversions, Overview, and CRM Notes with the conversion date.

How to read a cap table on a calm week and on conversion week uses the same rule: futures live in Scenarios; current truth lives in Overview plus Documents.

Illustrative pre-call reading pass and red flags

The pass below is a composite illustrative example, not a real company.

Illustrative fifteen-minute prep: Founder opens Cap Table, Refresh on Overview, notes fully diluted and pool. Opens Equity, confirms two SAFEs show caps that match Documents. Opens Scenarios, runs one named "Lead check $1.5M", sees founder ownership after the check, closes the scenario without treating it as current. Opens CRM only to confirm those SAFE deals are Won with Files attached. On the call they quote Overview fully diluted, not a remembered seed-pitch number. The illustrative point is that reading order beats charisma because the ledger was interrogated first.

Stop conditions while you read

Stop and escalate if Overview shows issued above authorized. Stop if a SAFE or note in CRM Files is missing on Equity. Stop if two stakeholders share a name and split ownership by accident. Stop if the option pool cannot cover offers already verbalized. Stop if Scenarios are the only place a promised percentage exists. Also stop if someone asks you to "just say about X percent" while convertible instruments are still outstanding and you have not looked at fully diluted. How to read a cap table includes saying "I will confirm from Overview after this call" instead of inventing comfort.

Ownership of the reading habit

One founder owns the live ledger. A second person should complete the Overview four-checks without the owner in the room. Keep the first reading checklist on one page with a named owner and a Monday review during raises. Stop expanding parallel spreadsheets until those two people can run Overview four-checks and an Equity-versus-Files spot-check cold. Counsel still owns instrument language and authorization mechanics. Your reading job is to notice mismatches early, not to improvise legal fixes on a video call. When the second reader finds a mismatch the owner missed, treat that as success: the habit worked. Log the fix in Notes with the date so the same error does not return on the next partner call.

Close the loop while the tabs are still open. If Overview required a correction, make it before Slack continues the old number. If Equity needed a new instrument, Create Instrument before the celebration thread. If Documents were missing a consent, file it or schedule counsel the same day. When Overview, Equity, and Documents agree, update the deck ownership slide the same day. When they disagree, fix Cap Table first. Export All Data after material changes so diligence is not a scavenger hunt. Import only when you intend to restore a known snapshot.

How to read a cap table, practiced this way, turns ownership from a vibe into a repeatable interrogation: Refresh, four Overview checks, Stakeholders hygiene, Equity versus Files, Documents spot-check, Scenarios only for futures, Conversions when paper becomes stock. Point newcomers to the what-is explainer for vocabulary; use this page when the meeting starts in ten minutes and the numbers have to be true.