SAFEs, Notes, and Equity

Instruments translate trust into cap table math

Early financing instruments are contracts about future ownership. A SAFE (simple agreement for future equity) delays price until a priced round but still dilutes on conversion. A convertible note (debt that converts to equity, often with interest and maturity) adds creditor rights until conversion. Priced equity sets ownership today. RelayOps seed plan: $1,800,000 SAFE with 20% discount and $9M valuation cap, converting at Series Seed priced round.

RelayOps is a B2B (business-to-business, selling to companies) SaaS (software as a service, subscription software delivered over the internet) venture improving dispatch and scheduling for mid-market field-service companies and the anchor venture for ENT 301. Founders Maya Chen (CEO, former dispatch manager at regional HVAC operator Summit Climate) and Jordan Okonkwo (CTO, former platform engineer) left Summit Climate in 2025 after living dispatch-center chaos firsthand. Their initial beachhead is 80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians. Discovery work confirmed 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows tied to same-day capacity loss when dispatchers rebalance schedules across phone calls, whiteboards, and legacy CRM tabs without a live view of technician skill, location, and parts. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo).

Throughout this course, RelayOps evolves from opportunity hypothesis to scaled venture. Elective depth lives in ENT 404 (Entrepreneurial Finance, SAFEs and Cap Tables) when you want a full unit on that phase. ENT 301 teaches the integrated journey so you can advise founders, invest, or launch with disciplined evidence. Cap table reconciliation is a core ENT 404 skill; ENT 301 requires founders to read outcomes, not delegate to counsel alone.

SAFE mechanics: cap, discount, MFN

SAFE investors get the better of cap or discount conversion price at qualified financing. RelayOps SAFE: $500k check, $9M cap, 20% discount. If priced round pre-money is $12M, cap price per share may win over discount depending on terms.

MFN (most favored nation, upgrade to better terms if later SAFEs improve) protects early angels. Founders should track side letter volume.

Qualified financing threshold is typically $500k to $1M; counsel sets exact definition. RelayOps uses $500k minimum priced round trigger in illustrative docs.

RelayOps illustrative SAFE terms (not legal advice):

Convertible notes versus SAFEs

Notes carry interest (often 5 to 8%) and maturity dates, creating default risk. SAFEs skip interest/maturity by design. RelayOps chooses SAFEs for speed; notes appear in bridge scenarios when investors want creditor priority.

Option pool and priced round dilution

Investors require option pool (shares reserved for hires, often 10 to 15%) before or after money. Pool timing shifts founder dilution. RelayOps plans 12% pool at seed priced round.

Pro rata rights and follow-on planning

Major SAFE investors often receive pro rata (right to invest in future rounds to maintain ownership percentage). RelayOps grants pro rata to checks above $250k. Founders must model follow-on capacity: if three angels exercise pro rata at priced round, less room exists for new lead investors.

Cap table modeling in ENT 404 includes pro rata exercise scenarios at 50%, 100%, and 0% uptake.

Side letters stack; counsel reviews aggregate investor rights before close.

Cap table reconciliation workflow

Reconciliation steps: (1) fully diluted share count pre-money, (2) add pool top-up, (3) convert SAFEs, (4) add new money, (5) verify founder percentages sum to 100%. Every step gets a check line.

Link to ENT 404

ENT 404 teaches waterfall modeling, liquidation preferences, and pro rata. ENT 301 founders must explain post-seed ownership without spreadsheets hiding 5% rounding errors.

Pre-seed: Maya 5,000,000 shares, Jordan 5,000,000 shares (50/50). Seed SAFE $1,800,000 at $9M cap. Priced round: $3M new money at $12M pre-money. Option pool 12% post-money.

Part A: Pre-conversion fully diluted

Founder shares: 10,000,000. No pool yet. Founders 100%. Check: 5M + 5M = 10M ✓

Part B: SAFE conversion at cap

Post-money cap method sketch: SAFE $1.8M on $9M cap ≈ 16.7% before new money if isolated (1.8/9 + 1.8). In priced round stack, counsel models exact share issuance; illustrative SAFE shares ≈ 2,000,000 fully diluted when priced round closes. Founders pre-new-money ~69% after SAFE conversion and pool top-up. Check: percentages reconciled in model ✓

Part C: After $3M new money

Post-money valuation ≈ $15M ($12M pre + $3M). New investor ownership ≈ $3M / $15M = 20%. Founders combined ~55%, SAFE ~15%, pool ~10%, new investor ~20% (illustrative; legal model governs). Check: sums to 100% ✓

Part D: Managerial read

Maya's investor FAQ: "Why SAFE not priced?" Speed and fewer immediate governance terms while milestones are still volatile. Priced round follows ARR and retention gates.

LedgerLift founders thought they owned 70% post-seed but forgot 8% uncapped advisor grants and 4% note interest conversion. RelayOps maintains a single fully diluted sheet updated within 48 hours of any grant.

RelayOps issues 10,000,000 founder shares. Seed SAFE $1,800,000 converts at $9M post-money cap using post-money SAFE shorthand (ownership ≈ investment / cap). Approximate SAFE ownership percent. If founders had 100% pre-SAFE, what is founder percent post-SAFE before new round? Show check.

Solution

SAFE ownership ≈ 1.8 / 9 = 20%. Founders ≈ 80%. Check: 20% + 80% = 100% ✓. Note: priced round and pool will dilute further.

Two reasons RelayOps prefers SAFE over convertible note for seed angels.

Solution

No maturity/default overhang and simpler docs for fast close. Angels still get cap and discount economics.

Key takeaways

• SAFEs convert to ownership; they are not free money.
• Cap table reconciliation requires check lines every step.
• Option pool timing shifts founder dilution materially.
• RelayOps seed: $1.8M SAFE at $9M cap with 20% discount (illustrative).
• ENT 404 owns waterfall depth; founders must read outcomes.

1. Build a simplified post-SAFE ownership table for RelayOps.
2. List three documents investors request besides the pitch deck.
3. Continue to Lesson 5: Preparing for Investor Conversations.

Applying SAFEs, Notes, and Equity at RelayOps

When RelayOps applies safes, notes, and equity, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.

Consider how startup finance, runway, and fundraising instruments changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why safes, notes, and equity is a CEO-level skill, not a brainstorming exercise.

Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.

Extended RelayOps scenario: cross-functional read

Imagine RelayOps's quarterly review for safes, notes, and equity. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak startup finance, runway, and fundraising instruments answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.

Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.

Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. SAFEs, Notes, and Equity gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.

For deeper study on this unit's specialty, see ENT 404 (Entrepreneurial Finance, SAFEs and Cap Tables). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.

Technical mechanics and checks (RelayOps patterns)

For safes, notes, and equity, show work the way finance shows reconciliations. Opportunity scorecards print weighted criteria and explicit kill rules. Interview synthesis tables show code frequency with qualified denominators only. MVP scorecards list assumption rank, build weeks, runway share, and kill criteria. Cap tables after SAFE conversion show pre-money, post-money, and founder ownership with check lines.

Use plain-language hypotheses before instruments. Example: "If fewer than six of ten operations leaders rank same-day rebalance in top-three pains, RelayOps deprioritizes hypothesis H1." That hypothesis is falsifiable without code. Weak hypotheses hide inside feature roadmaps.

Spreadsheet grain matters. Customer-level tables suit funnel conversion; logo-month tables suit retention; assumption-level tables suit experiment backlogs. RelayOps forbids ambiguous metrics like "engagement" without operational definitions tied to dispatch jobs routed per active day.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "How sure are we?" maps to evidence labels (exploratory, descriptive, causal), not bravado. "What is the dollar impact?" maps to overtime saved, slots recovered, or MRR with stated assumptions. "Can we ship faster?" maps to risk of untested adoption during live emergencies. "Why not copy ServiceTitan?" maps to wedge focus and beachhead economics, not feature envy.

RelayOps's credible answer format for safes, notes, and equity is three bullets: recommendation, evidence strength, and next test if limitations matter. A fourth bullet states what would falsify the recommendation within 60 days. That discipline prevents founders from becoming either bottlenecks or rubber stamps for investor narratives.

Judgment under uncertainty (RelayOps decision log)

Founders who master safes, notes, and equity keep a decision log: date, decision, evidence at time, dissent captured, review date. When RelayOps chose emergency-queue MVP over full suite parity, the log recorded HeatRoute's LOI-to-active failure mode as contrast case. When Phoenix beat Dallas on retention, the log triggered segment screener review rather than blaming sales tone.

Your workbook should mirror that log format for one venture you follow. If you cannot write dissent and kill criteria, you have a story, not a decision. SAFEs, Notes, and Equity is how teams convert stories into capital-efficient learning.

Applying SAFEs, Notes, and Equity at RelayOps

When RelayOps applies safes, notes, and equity, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.

Consider how startup finance, runway, and fundraising instruments changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why safes, notes, and equity is a CEO-level skill, not a brainstorming exercise.

Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.

Extended RelayOps scenario: cross-functional read

Imagine RelayOps's quarterly review for safes, notes, and equity. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak startup finance, runway, and fundraising instruments answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.

Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.

Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. SAFEs, Notes, and Equity gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.

For deeper study on this unit's specialty, see ENT 404 (Entrepreneurial Finance, SAFEs and Cap Tables). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.

Technical mechanics and checks (RelayOps patterns)

For safes, notes, and equity, show work the way finance shows reconciliations. Opportunity scorecards print weighted criteria and explicit kill rules. Interview synthesis tables show code frequency with qualified denominators only. MVP scorecards list assumption rank, build weeks, runway share, and kill criteria. Cap tables after SAFE conversion show pre-money, post-money, and founder ownership with check lines.

Use plain-language hypotheses before instruments. Example: "If fewer than six of ten operations leaders rank same-day rebalance in top-three pains, RelayOps deprioritizes hypothesis H1." That hypothesis is falsifiable without code. Weak hypotheses hide inside feature roadmaps.

Spreadsheet grain matters. Customer-level tables suit funnel conversion; logo-month tables suit retention; assumption-level tables suit experiment backlogs. RelayOps forbids ambiguous metrics like "engagement" without operational definitions tied to dispatch jobs routed per active day.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "How sure are we?" maps to evidence labels (exploratory, descriptive, causal), not bravado. "What is the dollar impact?" maps to overtime saved, slots recovered, or MRR with stated assumptions. "Can we ship faster?" maps to risk of untested adoption during live emergencies. "Why not copy ServiceTitan?" maps to wedge focus and beachhead economics, not feature envy.

RelayOps's credible answer format for safes, notes, and equity is three bullets: recommendation, evidence strength, and next test if limitations matter. A fourth bullet states what would falsify the recommendation within 60 days. That discipline prevents founders from becoming either bottlenecks or rubber stamps for investor narratives.

Judgment under uncertainty (RelayOps decision log)

Founders who master safes, notes, and equity keep a decision log: date, decision, evidence at time, dissent captured, review date. When RelayOps chose emergency-queue MVP over full suite parity, the log recorded HeatRoute's LOI-to-active failure mode as contrast case. When Phoenix beat Dallas on retention, the log triggered segment screener review rather than blaming sales tone.

Your workbook should mirror that log format for one venture you follow. If you cannot write dissent and kill criteria, you have a story, not a decision. SAFEs, Notes, and Equity is how teams convert stories into capital-efficient learning.

Applying SAFEs, Notes, and Equity at RelayOps

When RelayOps applies safes, notes, and equity, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.

Consider how startup finance, runway, and fundraising instruments changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why safes, notes, and equity is a CEO-level skill, not a brainstorming exercise.

Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.

Extended RelayOps scenario: cross-functional read

Imagine RelayOps's quarterly review for safes, notes, and equity. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak startup finance, runway, and fundraising instruments answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.

Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.

Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. SAFEs, Notes, and Equity gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.

For deeper study on this unit's specialty, see ENT 404 (Entrepreneurial Finance, SAFEs and Cap Tables). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.

Technical mechanics and checks (RelayOps patterns)

For safes, notes, and equity, show work the way finance shows reconciliations. Opportunity scorecards print weighted criteria and explicit kill rules. Interview synthesis tables show code frequency with qualified denominators only. MVP scorecards list assumption rank, build weeks, runway share, and kill criteria. Cap tables after SAFE conversion show pre-money, post-money, and founder ownership with check lines.

Use plain-language hypotheses before instruments. Example: "If fewer than six of ten operations leaders rank same-day rebalance in top-three pains, RelayOps deprioritizes hypothesis H1." That hypothesis is falsifiable without code. Weak hypotheses hide inside feature roadmaps.

Spreadsheet grain matters. Customer-level tables suit funnel conversion; logo-month tables suit retention; assumption-level tables suit experiment backlogs. RelayOps forbids ambiguous metrics like "engagement" without operational definitions tied to dispatch jobs routed per active day.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "How sure are we?" maps to evidence labels (exploratory, descriptive, causal), not bravado. "What is the dollar impact?" maps to overtime saved, slots recovered, or MRR with stated assumptions. "Can we ship faster?" maps to risk of untested adoption during live emergencies. "Why not copy ServiceTitan?" maps to wedge focus and beachhead economics, not feature envy.

RelayOps's credible answer format for safes, notes, and equity is three bullets: recommendation, evidence strength, and next test if limitations matter. A fourth bullet states what would falsify the recommendation within 60 days. That discipline prevents founders from becoming either bottlenecks or rubber stamps for investor narratives.