Cap Tables, Dilution and Scenario Modeling: Executive Synthesis

Cap Tables, Dilution and Scenario Modeling: Executive Synthesis: managerial stakes

RelayOps sells B2B SaaS dispatch and relay-operations software to mid-market logistics fleets. Founded March 2024. Founders Alex (CEO), Bea (CTO), and Chen (COO) each hold 3,300,000 shares; advisors 100,000 (10,000,000 issued). June 2025 cash $640,000; gross burn ~$185,000/month; fourteen customers at $8,000 MRR ($96,000 ACV). SAFE: $1.2M at $8M post-money cap, 20% discount (Harbor Seed, Northline Angels). Note: $400K, 6% interest, 18-month maturity, $10M cap, 15% discount. Series A target: $4M at $16M pre-money, $1.60/share, 2.5M new shares.

Cap tables translate contracts into ownership percentages, voting power, and exit proceeds. Dilution (percentage ownership falling when new shares issue) is not inherently bad if capital increases total value. Fully diluted (counting options, converting instruments, and reserved pool shares) is the investor standard. RelayOps must model SAFE conversion (1,764,706 shares on cap path), note conversion (424,000 shares), option pool refresh, and Series A (2,500,000 new shares at $1.60).

Executive synthesis for RelayOps board

Integrate cash ($520K September), metrics (14→22 customers), instruments (SAFE+note), and Series A ($4M/$16M pre/$1.60/2.5M shares) into one recommendation.

Final cap table base case

Teaching approximation; pool assumptions shift rows.

Board questions

Are we recruiting twelve engineers with 15% pool? Does note extension remain unsigned? Is strategic SAFE rejected?

Cash +$3.9M net; runway 24+ months; new director; monthly reporting to Series A lead.

Check: cash walk ✓

If only $12M pre and metrics miss, founders must choose: accept terms, cut burn, or extend note.

Write CEO memo recommending Series A close at $16M pre with 15% pool and note extension pre-agreed.

Solution

Full memo with numbers, kill criteria, 30-day actions.

Check: integrates Units 4-5 ✓

Key takeaways

• Executive synthesis merges cash, metrics, cap table.
• Series A is structure and cash event.
• Scenarios drive negotiation discipline.
• Simplicity beats cap table chaos.
• RelayOps board decides with eyes open.

1. Deliver RelayOps board cap table synthesis memo.
2. Reconcile to single spreadsheet source of truth.
3. Continue to Unit 6: Financing Strategy and Investor Readiness.

Deep dive 1: RelayOps cap table and financing linkage (Unit 5, Lesson 4)

When Alex presents to the board, three numbers must reconcile every month: cash on hand from the bank statement, ARR from the billing system, and fully diluted founder ownership from the cap table model. If cash says nine months runway but the cap table shows twenty percent SAFE ownership unmodeled, the board is flying with two different instruments. Integration is not a slide; it is a reconciliation discipline.

Harbor Seed and Northline Angels will ask how $1.2 million was deployed. RelayOps should show hires funded, customers added, and gross margin maintained at seventy-eight percent. Investors forgive dilution when capital efficiency improves. They do not forgive unexplained burn without KPI movement.

Chen's operations metrics should include months of payroll covered, note maturity date, and status of Series A lead conversations. Bea's product roadmap should tie enterprise features to the $96,000 ACV promise made in sales decks. Misalignment between product delivery and revenue recognition creates diligence risk that shows up as cap table distrust: investors wonder if founders understand their own economics.

For scenario modeling, use the same customer count in the revenue model and the investor narrative. Twenty-two customers at $8,000 MRR is $176,000 MRR, or about $2.1 million ARR run-rate. At a $16 million pre-money, that is roughly 7.6x ARR multiple (valuation divided by ARR), reasonable for growing B2B SaaS with enterprise pipeline if retention is strong.

Document assumptions in the spreadsheet: option pool target percent, SAFE conversion path (cap vs discount), note interest months, Series A raise amount, and pro-rata exercises. Change one assumption and the ownership column should update without manual heroics. If your spreadsheet requires manual percent overrides, you will eventually misstate founder ownership in a term sheet negotiation.

Employees granted options pre-Series A should understand that refresh at Series A may change strike prices and available pool shares. HR and finance should hold a joint session using the fully diluted table, not issued percentages. Nothing erodes culture faster than a new hire discovering founders told different stories about ownership.

Finally, connect financing strategy to kill criteria. RelayOps should define in writing: if Series A is not at least signed by month X, activate burn reduction plan Y and note extension Z. Financing without kill criteria becomes hope-based budgeting, which boards should reject.

Application layer 1: diligence questions investors will ask RelayOps

Leads will ask: Why is your SAFE cap $8 million post but you request $16 million pre Series A? Answer with customer growth, ACV, margin, and pipeline evidence, not adjectives.

They will ask: What happens if enterprise sales slips one quarter? Show a downside cap table at $12 million pre and a cash plan with delayed hires.

They will ask: Who owns what fully diluted after close? Produce a single table dated the day of the partner meeting.

They will ask: Is the note current? Show maturity date, accrued interest calculation, and extension status.

They will ask: Are there side letters? Produce the register or state none.

They will ask: How much pool remains for critical hires? Tie to hiring plan rows with names or roles, dates, and grant sizes.

They will ask: What is your net revenue retention? If below 100 percent, explain expansion revenue strategy in fleet upsells.

They will ask: CAC payback at $18,000 CAC and $96,000 ACV with seventy-eight percent margin; show the math in months.

Founders who rehearse these answers with a single source-of-truth spreadsheet project control. Founders who answer from memory contradict each other in the same meeting.

Board members should role-play these questions monthly until Series A closes. The practical exam is not this course's quiz; it is a partner meeting at 4 p.m. on a Thursday.

Technical supplement 1: arithmetic checks every RelayOps model must pass

Check 1: Issued shares sum to authorized issued count (10,000,000 pre-Series A amendments).

Check 2: Fully diluted percentages sum to 100.0% within rounding.

Check 3: Series A dollars = new shares × price per share ($4,000,000 = 2,500,000 × $1.60).

Check 4: Post-money valuation = pre-money + new money ($16M + $4M = $20M) for money-based view.

Check 5: SAFE cap path shares = 1,764,706 for $1.2M at $8M post on 10M base (15% ownership).

Check 6: Note converting amount includes stated interest period.

Check 7: Cash walk after close = prior cash + proceeds − fees.

Check 8: Option pool top-up shares solve the target percentage equation, not guessed.

Check 9: Pro-rata investment adds shares at Series A price.

Check 10: Waterfall at exit respects preferred preference language.

Any failed check blocks board distribution of the model. This sounds rigid; it prevents the classic failure mode where two board members argue from different spreadsheets and the CEO does not know which is correct.

RelayOps CFO should initial checks on a cover sheet. Alex should not sign term sheets until checks pass. Bea and Chen should receive the same PDF so engineering and operations align with financing reality.

These supplements complete the executive synthesis required for ENT 404 Units 5 and 6: cap tables are not academic; they are the numerical backbone of investor readiness and financing strategy.

Deep dive 1: RelayOps cap table and financing linkage (Unit 5, Lesson 4)

When Alex presents to the board, three numbers must reconcile every month: cash on hand from the bank statement, ARR from the billing system, and fully diluted founder ownership from the cap table model. If cash says nine months runway but the cap table shows twenty percent SAFE ownership unmodeled, the board is flying with two different instruments. Integration is not a slide; it is a reconciliation discipline.

Harbor Seed and Northline Angels will ask how $1.2 million was deployed. RelayOps should show hires funded, customers added, and gross margin maintained at seventy-eight percent. Investors forgive dilution when capital efficiency improves. They do not forgive unexplained burn without KPI movement.

Chen's operations metrics should include months of payroll covered, note maturity date, and status of Series A lead conversations. Bea's product roadmap should tie enterprise features to the $96,000 ACV promise made in sales decks. Misalignment between product delivery and revenue recognition creates diligence risk that shows up as cap table distrust: investors wonder if founders understand their own economics.

For scenario modeling, use the same customer count in the revenue model and the investor narrative. Twenty-two customers at $8,000 MRR is $176,000 MRR, or about $2.1 million ARR run-rate. At a $16 million pre-money, that is roughly 7.6x ARR multiple (valuation divided by ARR), reasonable for growing B2B SaaS with enterprise pipeline if retention is strong.

Document assumptions in the spreadsheet: option pool target percent, SAFE conversion path (cap vs discount), note interest months, Series A raise amount, and pro-rata exercises. Change one assumption and the ownership column should update without manual heroics. If your spreadsheet requires manual percent overrides, you will eventually misstate founder ownership in a term sheet negotiation.

Employees granted options pre-Series A should understand that refresh at Series A may change strike prices and available pool shares. HR and finance should hold a joint session using the fully diluted table, not issued percentages. Nothing erodes culture faster than a new hire discovering founders told different stories about ownership.

Finally, connect financing strategy to kill criteria. RelayOps should define in writing: if Series A is not at least signed by month X, activate burn reduction plan Y and note extension Z. Financing without kill criteria becomes hope-based budgeting, which boards should reject.

Application layer 1: diligence questions investors will ask RelayOps

Leads will ask: Why is your SAFE cap $8 million post but you request $16 million pre Series A? Answer with customer growth, ACV, margin, and pipeline evidence, not adjectives.

They will ask: What happens if enterprise sales slips one quarter? Show a downside cap table at $12 million pre and a cash plan with delayed hires.

They will ask: Who owns what fully diluted after close? Produce a single table dated the day of the partner meeting.

They will ask: Is the note current? Show maturity date, accrued interest calculation, and extension status.

They will ask: Are there side letters? Produce the register or state none.

They will ask: How much pool remains for critical hires? Tie to hiring plan rows with names or roles, dates, and grant sizes.

They will ask: What is your net revenue retention? If below 100 percent, explain expansion revenue strategy in fleet upsells.

They will ask: CAC payback at $18,000 CAC and $96,000 ACV with seventy-eight percent margin; show the math in months.

Founders who rehearse these answers with a single source-of-truth spreadsheet project control. Founders who answer from memory contradict each other in the same meeting.

Board members should role-play these questions monthly until Series A closes. The practical exam is not this course's quiz; it is a partner meeting at 4 p.m. on a Thursday.

Technical supplement 1: arithmetic checks every RelayOps model must pass

Check 1: Issued shares sum to authorized issued count (10,000,000 pre-Series A amendments).

Check 2: Fully diluted percentages sum to 100.0% within rounding.

Check 3: Series A dollars = new shares × price per share ($4,000,000 = 2,500,000 × $1.60).

Check 4: Post-money valuation = pre-money + new money ($16M + $4M = $20M) for money-based view.

Check 5: SAFE cap path shares = 1,764,706 for $1.2M at $8M post on 10M base (15% ownership).

Check 6: Note converting amount includes stated interest period.

Check 7: Cash walk after close = prior cash + proceeds − fees.

Check 8: Option pool top-up shares solve the target percentage equation, not guessed.

Check 9: Pro-rata investment adds shares at Series A price.

Check 10: Waterfall at exit respects preferred preference language.

Any failed check blocks board distribution of the model. This sounds rigid; it prevents the classic failure mode where two board members argue from different spreadsheets and the CEO does not know which is correct.

RelayOps CFO should initial checks on a cover sheet. Alex should not sign term sheets until checks pass. Bea and Chen should receive the same PDF so engineering and operations align with financing reality.

These supplements complete the executive synthesis required for ENT 404 Units 5 and 6: cap tables are not academic; they are the numerical backbone of investor readiness and financing strategy.

Deep dive 1: RelayOps cap table and financing linkage (Unit 5, Lesson 4)

When Alex presents to the board, three numbers must reconcile every month: cash on hand from the bank statement, ARR from the billing system, and fully diluted founder ownership from the cap table model. If cash says nine months runway but the cap table shows twenty percent SAFE ownership unmodeled, the board is flying with two different instruments. Integration is not a slide; it is a reconciliation discipline.

Harbor Seed and Northline Angels will ask how $1.2 million was deployed. RelayOps should show hires funded, customers added, and gross margin maintained at seventy-eight percent. Investors forgive dilution when capital efficiency improves. They do not forgive unexplained burn without KPI movement.

Chen's operations metrics should include months of payroll covered, note maturity date, and status of Series A lead conversations. Bea's product roadmap should tie enterprise features to the $96,000 ACV promise made in sales decks. Misalignment between product delivery and revenue recognition creates diligence risk that shows up as cap table distrust: investors wonder if founders understand their own economics.

For scenario modeling, use the same customer count in the revenue model and the investor narrative. Twenty-two customers at $8,000 MRR is $176,000 MRR, or about $2.1 million ARR run-rate. At a $16 million pre-money, that is roughly 7.6x ARR multiple (valuation divided by ARR), reasonable for growing B2B SaaS with enterprise pipeline if retention is strong.

Document assumptions in the spreadsheet: option pool target percent, SAFE conversion path (cap vs discount), note interest months, Series A raise amount, and pro-rata exercises. Change one assumption and the ownership column should update without manual heroics. If your spreadsheet requires manual percent overrides, you will eventually misstate founder ownership in a term sheet negotiation.

Employees granted options pre-Series A should understand that refresh at Series A may change strike prices and available pool shares. HR and finance should hold a joint session using the fully diluted table, not issued percentages. Nothing erodes culture faster than a new hire discovering founders told different stories about ownership.

Finally, connect financing strategy to kill criteria. RelayOps should define in writing: if Series A is not at least signed by month X, activate burn reduction plan Y and note extension Z. Financing without kill criteria becomes hope-based budgeting, which boards should reject.

Application layer 1: diligence questions investors will ask RelayOps

Leads will ask: Why is your SAFE cap $8 million post but you request $16 million pre Series A? Answer with customer growth, ACV, margin, and pipeline evidence, not adjectives.

They will ask: What happens if enterprise sales slips one quarter? Show a downside cap table at $12 million pre and a cash plan with delayed hires.

They will ask: Who owns what fully diluted after close? Produce a single table dated the day of the partner meeting.

They will ask: Is the note current? Show maturity date, accrued interest calculation, and extension status.

They will ask: Are there side letters? Produce the register or state none.

They will ask: How much pool remains for critical hires? Tie to hiring plan rows with names or roles, dates, and grant sizes.

They will ask: What is your net revenue retention? If below 100 percent, explain expansion revenue strategy in fleet upsells.

They will ask: CAC payback at $18,000 CAC and $96,000 ACV with seventy-eight percent margin; show the math in months.

Founders who rehearse these answers with a single source-of-truth spreadsheet project control. Founders who answer from memory contradict each other in the same meeting.

Board members should role-play these questions monthly until Series A closes. The practical exam is not this course's quiz; it is a partner meeting at 4 p.m. on a Thursday.

Technical supplement 1: arithmetic checks every RelayOps model must pass

Check 1: Issued shares sum to authorized issued count (10,000,000 pre-Series A amendments).

Check 2: Fully diluted percentages sum to 100.0% within rounding.

Check 3: Series A dollars = new shares × price per share ($4,000,000 = 2,500,000 × $1.60).

Check 4: Post-money valuation = pre-money + new money ($16M + $4M = $20M) for money-based view.

Check 5: SAFE cap path shares = 1,764,706 for $1.2M at $8M post on 10M base (15% ownership).

Check 6: Note converting amount includes stated interest period.

Check 7: Cash walk after close = prior cash + proceeds − fees.

Check 8: Option pool top-up shares solve the target percentage equation, not guessed.

Check 9: Pro-rata investment adds shares at Series A price.

Check 10: Waterfall at exit respects preferred preference language.

Any failed check blocks board distribution of the model. This sounds rigid; it prevents the classic failure mode where two board members argue from different spreadsheets and the CEO does not know which is correct.

RelayOps CFO should initial checks on a cover sheet. Alex should not sign term sheets until checks pass. Bea and Chen should receive the same PDF so engineering and operations align with financing reality.

These supplements complete the executive synthesis required for ENT 404 Units 5 and 6: cap tables are not academic; they are the numerical backbone of investor readiness and financing strategy.

Deep dive 1: RelayOps cap table and financing linkage (Unit 5, Lesson 4)

When Alex presents to the board, three numbers must reconcile every month: cash on hand from the bank statement, ARR from the billing system, and fully diluted founder ownership from the cap table model. If cash says nine months runway but the cap table shows twenty percent SAFE ownership unmodeled, the board is flying with two different instruments. Integration is not a slide; it is a reconciliation discipline.

Harbor Seed and Northline Angels will ask how $1.2 million was deployed. RelayOps should show hires funded, customers added, and gross margin maintained at seventy-eight percent. Investors forgive dilution when capital efficiency improves. They do not forgive unexplained burn without KPI movement.

Chen's operations metrics should include months of payroll covered, note maturity date, and status of Series A lead conversations. Bea's product roadmap should tie enterprise features to the $96,000 ACV promise made in sales decks. Misalignment between product delivery and revenue recognition creates diligence risk that shows up as cap table distrust: investors wonder if founders understand their own economics.

For scenario modeling, use the same customer count in the revenue model and the investor narrative. Twenty-two customers at $8,000 MRR is $176,000 MRR, or about $2.1 million ARR run-rate. At a $16 million pre-money, that is roughly 7.6x ARR multiple (valuation divided by ARR), reasonable for growing B2B SaaS with enterprise pipeline if retention is strong.

Document assumptions in the spreadsheet: option pool target percent, SAFE conversion path (cap vs discount), note interest months, Series A raise amount, and pro-rata exercises. Change one assumption and the ownership column should update without manual heroics. If your spreadsheet requires manual percent overrides, you will eventually misstate founder ownership in a term sheet negotiation.

Employees granted options pre-Series A should understand that refresh at Series A may change strike prices and available pool shares. HR and finance should hold a joint session using the fully diluted table, not issued percentages. Nothing erodes culture faster than a new hire discovering founders told different stories about ownership.

Finally, connect financing strategy to kill criteria. RelayOps should define in writing: if Series A is not at least signed by month X, activate burn reduction plan Y and note extension Z. Financing without kill criteria becomes hope-based budgeting, which boards should reject.

Application layer 1: diligence questions investors will ask RelayOps

Leads will ask: Why is your SAFE cap $8 million post but you request $16 million pre Series A? Answer with customer growth, ACV, margin, and pipeline evidence, not adjectives.

They will ask: What happens if enterprise sales slips one quarter? Show a downside cap table at $12 million pre and a cash plan with delayed hires.

They will ask: Who owns what fully diluted after close? Produce a single table dated the day of the partner meeting.

They will ask: Is the note current? Show maturity date, accrued interest calculation, and extension status.

They will ask: Are there side letters? Produce the register or state none.

They will ask: How much pool remains for critical hires? Tie to hiring plan rows with names or roles, dates, and grant sizes.

They will ask: What is your net revenue retention? If below 100 percent, explain expansion revenue strategy in fleet upsells.

They will ask: CAC payback at $18,000 CAC and $96,000 ACV with seventy-eight percent margin; show the math in months.

Founders who rehearse these answers with a single source-of-truth spreadsheet project control. Founders who answer from memory contradict each other in the same meeting.

Board members should role-play these questions monthly until Series A closes. The practical exam is not this course's quiz; it is a partner meeting at 4 p.m. on a Thursday.