Startup Financial Statements and Cash Planning: Applied Business Decisions

When spreadsheets become policy

Lessons 1 through 3 gave RelayOps a shared language and operating frameworks. Lesson 1 connected cash, accrual profit, and balance-sheet articulation. Lesson 2 defined MRR (monthly recurring revenue), ARR (annual recurring revenue), burn multiple, gross margin, deferred revenue, APIC (additional paid-in capital), and working capital timing. Lesson 3 installed the 13-week cash forecast, scenario planning (base, downside, and upside cases), and board reporting rhythm. This lesson closes Unit 1 by applying those tools to four decisions every seed CEO faces: when to hire, how to negotiate vendor terms (payment timing and conditions with suppliers), when to start fundraising (raising outside equity or convertible capital), and how to choose among tradeoffs under cash pressure.

The managerial standard is not "model looks fine." The standard is: name the decision, state the cash and accrual impact, show the scenario trigger, and document the board or founder approval. RelayOps in the first half of 2025 sits between a $1.2M SAFE, fourteen customers, $640,000 cash in June, and a planned Series A (first priced venture round typically after seed traction) at $16M pre-money. Wrong hire timing or sloppy vendor float can burn two months of runway. Waiting too long to fundraise can convert a strong story into a distressed note. This lesson walks those forks with numbers that reconcile.

Hiring timing: cash weeks vs ARR quarters

Headcount is the largest line item for RelayOps: roughly $110,000 of the $185,000 gross burn in early 2025 is people. A new engineer at $160,000 base plus 25% benefits loads ~$16,667 per month fully loaded, or about $8,333 per biweekly payroll. On the accrual P&L (profit and loss statement), that cost starts the first day of employment. On cash, it starts the first payroll run, often two weeks later. Founders who model hires on the first of the month forget the payroll lag and overstate near-term cash.

The hire decision framework has four gates. Gate 1: MRR capacity. Does the roadmap require this role to unblock revenue or reduce COGS (cost of goods sold) enough to matter within two quarters? A second SDR (sales development representative) without pipeline may add $18,000 CAC (customer acquisition cost) spend before MRR moves. Gate 2: cash weeks. Insert the fully loaded payroll into weeks 1-13 of the forecast. RelayOps delaying an engineer eight weeks preserves about $66,664 cash before benefits adjustments. Gate 3: scenario survival. Run the hire in base and downside. If downside week-13 cash drops below the board floor ($500,000 for RelayOps), tie approval to a signed customer LOE (letter of engagement) or financing milestone. Gate 4: accrual burn multiple. Will this hire improve net new ARR enough to lower burn multiple within twelve months? If not, the hire is a bet on fundraising, not on unit economics.

Part-time and contractor paths deserve the same gates. A fractional CFO at $8,000 per month improves statement quality but does not fix product delivery. A contract engineer at $120 per hour for twenty hours weekly may cost $10,400 monthly with less commitment than a full-time hire. Model both in the forecast with end dates so they do not silently become permanent headcount without board visibility.

Hiring also hits equity (ownership). Each offer consumes option pool shares. RelayOps reserved 15% for options at incorporation. Issuing 100,000 advisor shares per relayops.js facts dilutes founders slightly but does not hit cash until stock-based compensation (non-cash expense spreading option fair value over vesting) accrues. Investors track pool remaining; operators track cash. Both matter.

Never approve a hire on ARR alone. ARR is accrual run rate; payroll is cash weekly. The CEO should present hires as lines in the 13-week forecast, not bullets on an org chart.

RelayOps's CAC of roughly $18,000 per customer means a new SDR hire must produce more than one net customer every few months to pay back sales labor alone, before covering marketing spend. Gate 4 burn-multiple math: if annualized net burn is $1.44M and each net customer adds $96,000 ARR, you need roughly fifteen net customers per year just to drive burn multiple toward 1.0 in a static model. Real businesses improve margin and slow burn, but the hire case must cite a path to net new ARR, not hope.

Contingent offers are underused. RelayOps can sign an engineer with a May 1 start tied to closing a $96,000 prepay or a financing milestone. Contingency protects cash and signals discipline to investors. Unconditional offers made under cash pressure create morale risk when later rescinded. Model contingent starts explicitly in downside scenarios so the board sees headcount flex without a layoff narrative.

Vendor terms: float, discounts, and trust

Vendor terms translate directly into working capital. RelayOps spends roughly $28,000 monthly on cloud and tools. Paying net-30 versus net-60 shifts $28,000-$56,000 across a quarter with no P&L change if expense is accrued when incurred. That is legitimate float if disclosed in cash forecasts. Silent delay destroys vendor relationships before due diligence calls reference checks.

Framework for vendor negotiation: classify vendors into critical path (AWS, payroll provider, core CRM) versus replaceable. Critical vendors get paid on time; negotiate annual commits for discounts, not hidden stretches. Replaceable vendors can move to net-45 if needed with explicit CFO approval. Take early payment discounts (e.g., 2/10 net-30) when APR (annual percentage rate) equivalent exceeds your cost of cash. A 2% discount for paying ten days early on a $30,000 invoice annualizes well above seed-stage borrowing costs.

Accrual accounting records expense when service is consumed. If RelayOps uses AWS in March but pays in April, March P&L includes March usage; March cash excludes it. The balance sheet shows AP (accounts payable) rising. When April payment hits, AP falls and cash falls. Founders reading only bank balance think March was cheap. Framework users read AP rollforward alongside cash.

Vendor terms interact with fundraising. Investors ask for AP aging (list of unpaid bills by age). Spikes in 90+ day AP before a round signal distress even if cash looks stable. RelayOps should keep 90+ day AP near zero unless a documented dispute exists.

Renegotiating terms before you need them works better than emergency calls. RelayOps approaching AWS or a CRM vendor in February with a transparent "we are opening a seed process and need net-45 for ninety days" preserves trust. Vendors often agree when they see a dated financing plan and historical on-time payment. Silent stretching followed by a data room AP schedule is how deals die in diligence.

Prepaying annual software contracts can make sense when discount exceeds cost of cash and the tool is mission-critical. A 15% discount on $12,000 annual spend saves $1,800 but consumes cash today. Model the trade in all three scenarios: base might skip prepay, upside might take it after Series A wire. The decision belongs in the cash forecast, not in a credit card swipe without finance visibility.

Document every term change in the board appendix so scenarios stay honest.

Fundraising triggers: process start vs cash need

Fundraising triggers are pre-agreed conditions that move the CEO from "monitoring" to "executing" a capital raise. Cash need and process start are different dates. Venture rounds often take four to six months from first meeting to wired funds. RelayOps with $640,000 cash June 30 and $86,000 net burn has roughly 7.4 months runway mathematically, but effective runway is shorter because investors discount companies under three months cash without a term sheet.

Standard trigger stack for seed-to-Series-A transition:

Trigger A (process start): base case 13-week forecast shows runway below six months within the forecast window, or below nine months if enterprise sales cycles require it. RelayOps February base case week-13 cash near $412,000 fires this trigger: open data room, refresh deck, allocate CEO time.

Trigger B (bridge or cut): downside scenario cash below $500,000 before expected close, or net burn above plan two months running. Options: convertible note per relayops.js ($400,000, 6% interest, 18-month maturity), expense freeze, or bridge from insiders.

Trigger C (term sheet urgency): cash below three months net burn without signed term sheet. Negotiating power collapses; valuations and terms worsen.

Fundraising affects statements distinctly. A SAFE (Simple Agreement for Future Equity) adds cash and a liability until conversion; no revenue. A priced Series A adds cash, APIC, and new shares; still no revenue. Convertible note adds debt, cash, and future dilution at conversion. Each appears in scenario financing rows, not in MRR.

RelayOps Series A facts from anchor data: $4,000,000 raised at $16,000,000 pre-money, $20,000,000 post-money, $1.60 price per share, 2,500,000 new shares. Founders must model dilution alongside cash extension. Cash solves runway; APIC records the investment; cap table shows ownership shift.

Board reporting should include a financing Gantt (timeline chart): data room ready, first meetings, partner meeting, diligence, legal, close. Tie hires and vendor prepays to that timeline.

RelayOps's convertible note option ($400,000, 6% interest, 18-month maturity, $10,000,000 cap, 15% discount per relayops.js) is a bridge tool, not a substitute for Series A planning. Notes add debt and future dilution at conversion. Use them when Trigger B fires and Series A timeline slips, with board approval and explicit use of funds (runway extension, not speculative new product bets). Document expected conversion mechanics in the investor appendix so Harbor Seed understands overlap with their SAFE.

Fundraising also requires a use of funds table tied to hires and milestones, not generic "growth." Example RelayOps seed/Series A use: 55% engineering, 25% sales, 10% customer success, 10% G&A for eighteen months. Each line maps to dated payroll in the forecast. Investors compare use of funds to scenario MRR outcomes; misalignment suggests the raise size is wrong.

Prepare a diligence-ready data room when Trigger A fires, not when a term sheet arrives. Minimum contents: three-statement monthly history, deferred revenue schedule, cap table with SAFE and option pool, last eight weeks of forecast vs actual, customer list with ACV and billing terms, and AP aging. RelayOps assembling this in February while cash is still near $920,000 beats scrambling in July at $580,000 with sloppy books. Clean data rooms shorten legal review and reduce retrade risk on valuation.

Integrated RelayOps decisions: putting it together

The applied decision memo format for RelayOps has six sentences: decision stated; cash impact weeks 1-13; accrual impact on MRR and net burn; scenario comparison; trigger if wrong; approval requested. Example: "Delay second engineer eight weeks; saves ~$67k cash in base case; MRR unchanged; downside week-13 cash rises from $287k to $354k; if enterprise deal closes week 6, move hire forward; approve delay pending board seed mandate."

Three decisions interact in H1 2025. Decision 1: Start seed/Series A process February based on base forecast, not June bank balance. Decision 2: Approve one SDR only with two signed LOEs worth $192,000 ACV combined, appearing as week-6+ prepays in forecast. Decision 3: Renegotiate AWS to net-45 temporarily, freeing ~$28,000 once, disclosed in AP footnote, not hidden.

Write decisions in a shared decision log with date, approver, forecast version, and review date. RelayOps revisiting the engineer hire in April without a new log entry should default to the prior board contingency rather than restarting debate from zero. Decision logs prevent amnesia when cash stress rises and everyone forgets what was already agreed.

Integrated leaders reject false choices. Cutting all hires preserves cash but may stall MRR; spending on two SDRs without pipeline burns cash without ARR. Frameworks force middle paths: contingent hires, vendor float with disclosure, financed growth separated from operating cash scenarios.

Cross-check every decision against Lesson 1 articulation. If cash forecast improves but deferred revenue does not, you borrowed time from customers, not fixed economics. If MRR rises but cash falls, you may be billing monthly instead of annual prepay: better accrual story, worse near-term bank. State which stakeholder priority wins and for how long.

Unit 1 closes with a simple test: can you explain RelayOps's next thirteen weeks to a engineer, a seed investor, and your bookkeeper using the same model with different emphasis? The engineer needs hire dates and runway. The investor needs MRR, burn multiple, and scenarios. The bookkeeper needs deferred revenue, APIC, and AP timing. One reconciled spreadsheet, three legitimate reads. That is applied startup finance.

Carry forward a personal decision checklist after this unit: before any spend above one week of net burn, update the thirteen-week forecast, name the scenario that breaks, and record who approved. RelayOps founders who institutionalize that habit rarely get surprised by payroll week; they get surprised by markets, which is unavoidable but different. The checklist takes five minutes once the model exists; skipping it costs weeks of credibility.

RelayOps contemplates hiring Engineer #6 at $160,000 base, fully loaded $200,000 per year ($16,667 monthly, $8,333 biweekly). Start date options: March 3 or May 1. February base week-13 cash $412,000; downside $316,000 without hire adjustments.

Part A: Cash forecast insert (March start)

Add $8,333 biweekly from weeks 3-13 (11 payroll halves ≈ 5.5 pays) ≈ $45,833 extra outflows in 13-week window plus one-time equipment $3,500 week 3.

Adjusted base ending ≈ $412,000 − $45,833 − $3,500 = $362,667.

Check: hire reduces ending cash by fully loaded payroll plus equipment ✓

Part B: May start comparison

Delay 8 weeks: save ≈ $66,664 payroll (8 weeks × $8,333) in the same 13-week horizon.

Adjusted base ending ≈ $412,000 − $0 March-April payroll for this hire = $412,000 (hire exits forecast window partially; exact model adds payroll from week 9).

Ending with May start roughly $395,000 after partial period payroll weeks 9-13 (~$41,665).

Check: May start preserves ~$17k-$27k more cash than March start in weeks 1-13 ✓

Part C: Accrual and MRR read

Engineer does not move MRR for two quarters realistically. Accrual net burn rises $16,667 per month immediately if product not shipped. Burn multiple worsens unless ARR adds $200,000+ within twelve months at current efficiency.

Part D: Decision memo

Approve May 1 start contingent on seed process launched by March 1; if downside cash < $350,000 any week, slide to July 1. Board approves contingent hire, not unconditional.

RelayOps June 30 cash $640,000; net burn $86,000; considering (i) $400,000 convertible note week 1 July, (ii) AWS net-45 instead of net-30 for July bill $30,000, (iii) one $96,000 prepay closing week 3 July.

Part A: July weeks 1-4 cash (simplified)

Beginning $640,000. Week 1: +$400,000 note − regular outflows $48,000 ≈ $992,000. Week 2: −$54,000 payroll −$19,000 other ≈ $919,000. Week 3: +$96,000 prepay − outflows ≈ $946,000. Week 4: − outflows; AWS $30,000 not paid until August (float) ≈ $877,000 if other outflows $69,000.

Check: note + prepay − operating outflows + AP float reconciles to ~$877k week 4 ✓

Part B: Balance sheet July 31 (sketch)

Cash up from note and prepay; convertible note liability $400,000 plus accrued interest; deferred revenue +$96,000 minus July recognition; AP +$30,000 AWS float.

Assets = Liabilities + Equity holds with documented AP timing.

Check: AP float increases cash without reducing expense ✓

Part C: Fundraising trigger read

Note extends runway ~4.7 months at $86k net burn ($400k / $86k) but signals if Series A not progressing. Board should pair note with explicit Series A milestone dates, not passive hope.

Part D: Managerial read

Vendor float and note are tools, not strategy. Prepay adds MRR and deferred revenue; note adds cash and debt. Series A remains primary path per relayops.js cap table plan.

Before signing the note, compare all-in cost to slowing hires. $400,000 at 6% for eighteen months is cheaper than emergency equity if Series A slips, but conversion dilution at the cap still matters. Present both paths in the board memo with dilution math, not only cash extension months.

RelayOps August 2025: cash $580,000; net burn $77,000; base 13-week ending cash $380,000 without changes. Proposed: hire Customer Success Manager (CSM) $130,000 fully loaded $162,500/year ($6,771 biweekly) starting week 2; renegotiate CRM vendor to save $2,000/month cash from week 1; start Series A conversations if week-13 cash < $400,000 in base.

1. Estimate adjusted week-13 cash with CSM and vendor save (13 weeks).
2. Compute runway months from adjusted week-13 cash at $77,000 net burn.
3. Does the Series A process trigger fire under adjusted base? Explain.
4. Write a six-sentence decision memo approving, modifying, or rejecting the CSM hire.

Solution

1. CSM cost weeks 2-13 ≈ 12 halves × $3,385 biweekly half of $6,771 ≈ $40,620 (approximate fully loaded biweekly $6,771 × 6 pays = $40,626). Vendor save $2,000/month × 3 months ≈ $6,000. Net cash impact ≈ −$40,626 + $6,000 = −$34,626. Adjusted week-13 ≈ $380,000 − $34,626 = $345,374.

Check: hire cost exceeds vendor save ✓

2. Runway from $345,374 at $77,000/month ≈ 4.5 months.

3. Trigger fires if rule is week-13 base < $400,000: yes, adjusted $345k starts Series A conversations under stated policy.

4. Sample memo: "Reject immediate CSM hire; vendor save approved. CSM would reduce base week-13 cash to ~$345k, firing Series A trigger while net burn still $77k. Delay CSM to week 8 contingent on one $96k prepay; saves ~$27k in window. Accrual churn risk noted if delay extends past two months. Downside without prepay falls below $300k; pair with bridge only if Series A meetings slip 30 days. Request board approval for vendor renegotiation and delayed contingent CSM, not week-2 start."

The memo works because it cites forecast lines, triggers, and a contingent alternative rather than a vague "not now." Practice converting emotional hiring debates into this format until it becomes default staff meeting language.

RelayOps closes Series A ($4M at $16M pre per anchor facts) in December 2025. List four statement and cap-table effects in plain language and state whether each helps near-term cash.

Solution

(1) Cash increases $4M: helps cash immediately. (2) APIC increases with share issuance at $1.60: no cash effect, documents equity. (3) SAFE converts to shares: reclassifies liability to equity; no cash. (4) Option pool refresh may dilute founders: no immediate cash, affects ownership. Net income unchanged solely from raise.

Key takeaways

• Hire timing must pass cash-week, scenario, and burn-multiple gates, not ARR headlines alone.
• Vendor terms are working-capital tools: use disclosed float, not surprise AP aging before diligence.
• Fundraising triggers separate process start from cash need; base forecasts should exclude unsigned rounds.
• Integrated decisions use the six-sentence memo: cash, accrual, scenarios, trigger, approval.
• RelayOps Unit 1 tools converge here: statements, metrics, forecasts, and board rhythm drive executable choices.

1. Take one real hire your company is considering: insert fully loaded payroll into a 13-week forecast and compare base vs downside ending cash.
2. Write three fundraising triggers (process start, bridge, urgent) with dollar thresholds for RelayOps using June cash $640k and net burn $86k.
3. Return to the unit page for assessments, or review Lessons 1-3 if any vocabulary or forecast mechanics still feel fuzzy.