agentleFS
SkillMedevSkillMedev/founder-fundraising-os/skills/cap-table-manager/SKILL.md

cap-table-manager

Skill0 starsChanged 4 months agoMITView on GitHub

Use when a founder needs to understand or model ownership and dilution. Triggers on "model my cap table", "how much will I be diluted", "option pool", "SAFE conversion", "post-money vs pre-money", "what do I own after this round", "pro rata". Turns equity from a black box into a model the founder controls.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use it during [[fundraising-stage-selector]] to pressure-test dilution, before signing any SAFE or term sheet, and whenever someone says …

    line 14
  2. Distinctive:

    Start with the current fully-diluted table: founders, existing options, prior SAFEs/notes (at their caps).

    line 41
  3. Distinctive:

    Read off post-round ownership for each row and the founder total.

    line 45
  4. Distinctive:

    Keep founders meaningfully above 50% through seed if at all possible.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cap Table Manager

Founders lose more value to cap-table mistakes they did not model than to valuation they negotiated badly. This skill makes dilution legible: you should be able to state what you own after the next two rounds, and why.

When to use this skill

Use it during [[fundraising-stage-selector]] to pressure-test dilution, before signing any SAFE or term sheet, and whenever someone says "we'll just expand the pool." Pair instrument mechanics with [[safe-vs-priced-round]].

The mechanics that actually move ownership

Pre-money vs post-money

  • Post-money valuation = pre-money + new investment.
  • Investor ownership = investment ÷ post-money. ($2M into $8M pre => $10M post => 20% to investors.)
  • Modern SAFEs (post-money SAFEs) lock the investor's percentage; founders dilute around them when later money comes in. Know which kind you signed.

The option pool shuffle

  • Investors usually require the new option pool to be carved out of the pre-money - so founders, not investors, bear its dilution.
  • A "20% pool on a $10M post" can quietly cost founders several points. Model the pool inside the pre-money and negotiate its size to the actual hiring plan (see [[fundraise-team-hiring]]), not a round-number default.

SAFE stacking

  • Multiple uncapped or high-cap SAFEs feel free now and convert into a painful chunk at the priced round. Always model the fully converted table, not the cash-in-hand one.

Build the model

  1. Start with the current fully-diluted table: founders, existing options, prior SAFEs/notes (at their caps).
  2. Layer the new round: investment, pre/post, new pool top-up.
  3. Convert every SAFE at this round's terms.
  4. Read off post-round ownership for each row and the founder total.
  5. Project one round further at plausible terms to see the trajectory.

Guardrails

  • Keep founders meaningfully above 50% through seed if at all possible; the math gets unforgiving by Series A.
  • A round selling >25% is a yellow flag - too dilutive or underpriced.
  • Watch liquidation preference and participation; they change value even when they don't change percentage. See [[term-sheet-negotiation]].

Anti-patterns

  • Modeling the cash table instead of the fully-converted one.
  • Accepting the pool top-up as fixed instead of sizing it to the hiring plan.
  • Signing stacked SAFEs without ever modeling their combined conversion.

Deliverable

A fully-diluted cap table for today, post-round, and one round out, with the founder ownership trajectory, the pool's true cost, and a flagged list of any term that moves value without moving percentage.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.