What a Cap Table Tells You
A cap table reveals the ownership structure of a startup: common shares (founders, employees), preferred shares (investors), and the option pool (reserved for future hires).
The cap table tells you who controls the company, how much dilution future rounds will cause, and whether the company has raised too much or too little.
GitDealFlow's engineering data adds a dynamic layer: startups with rising commit velocity and a clean cap table (reasonable founder ownership, no toxic terms) are the strongest investment candidates.
Key Cap Table Metrics
Founder ownership: should be 50-70% post-seed. Below 40% is a red flag.
Option pool: 10-20% total. If it's been mostly granted, future hiring will require a new pool (which means dilution).
Investor ownership: 20-40% post-Series A. Too much investor ownership means the cap is stacked against new investors.
Convertible instruments: SAFEs, notes, and warrants that haven't converted yet complicate the cap table. Request a 'fully diluted' view.
Red Flags on a Cap Table
Excessive founder dilution (<40% before Series A) suggests either over-raising or weak negotiating.
Too many angel investors (15+ on the cap table) makes future rounds complicated.
Aggressive liquidation preferences (2x+) can mean employees and founders see nothing in a modest exit.
Context: Where This Fits
This explainer is part of a library built on a single dataset: public engineering activity across 350+ startup GitHub organizations, 15 sectors, refreshed weekly. The through-line is that deal flow signal is earliest in code: breakout teams appear 21 to 47 days before their round is public. Concepts on this page are defined precisely because imprecise vocabulary is what makes sourcing decisions unfalsifiable.
Continue Learning
- What is commit velocity
- Code-Side Sourcing: the named category
- Glossary: every term in the library
- Learn hub: all explainers
A practical read-through of How to Read a Cap Table Like a VC: the dataset behind this page refreshes weekly across 350+ organizations and 15 sectors, and every figure shown traces to a public GitHub REST API pull. That matters for two reasons. Reproducibility: any number here can be re-derived from primary sources, which is the standard the published methodology sets for itself. Timeliness: engineering acceleration precedes announcements, so this page follows the data cadence rather than the news cycle, and the freshness endpoint always reports the exact pull date.
Frequently Asked Questions
What's a healthy cap table look like?
Founders: 50-70%, Option pool: 10-20%, Investors: 20-40% post-seed. Clean, no outstanding convertible instruments. GitDealFlow's momentum data helps justify better cap table terms.
How often should founders update the cap table?
After every transaction: fundraise, option grant, option exercise, or conversion. A stale cap table is a legal and financial risk.
What tools are used for cap table management?
Pulley, Carta, Shareworks, and LTSE Equity. Most use Carta. GitDealFlow's engineering data complements cap table analysis by showing whether the team delivering the cap table value is performing.