Three-Statement Financial Model Template
A three-statement financial model — P&L, Balance Sheet, Cash Flow — typed, linked, and live. Drag a lever; every downstream value recomputes. Fork it in the Workshop and it's yours.
This is not a spreadsheet download. It is a compiled model with typed assumptions, an explicit dependency graph, and assertion guardrails. The kind of model your investor's CFO will recognize as institutional.
Inputs · typed assumptions
Outputs · compiled in topological order
Assertions · guardrails
How to read it
- The Inputs panel: named, typed assumptions with units. Not cells — drivers. Each one knows what it is.
- The Outputs: P&L, working capital, cash flow, and key metrics — computed in topological order from the assumptions.
- The Assertions panel: guardrails that flag when the model violates a financial rule — gross-margin floor, non-negative cash, a runway minimum, positive net growth.
The key architectural point: change monthly_growth_rate from 8% to 12% and every downstream value — ARR, revenue, gross profit, EBITDA, cash, runway — recomputes instantly. The dependency graph is explicit. Nothing is a broken formula chain waiting for the next editor to snap it.
The three-statement mechanic
"Three-statement" means integrated: the Profit & Loss, the Balance Sheet, and the Cash Flow statement are all driven by the same assumptions, and they reconcile to each other. When you change COGS, it flows through gross profit (P&L), through receivables and payables (Balance Sheet), and into cash from operations (Cash Flow) — automatically.
That integration is the whole point, and it's exactly what a spreadsheet makes fragile. In Excel, the three statements are linked by cross-sheet cell references that you wire by hand and hope nobody breaks. There is no structural guarantee that the cash flow actually ties to the P&L and the balance sheet — only a chain of formulas and the discipline of whoever last edited the file.
In a typed compiled model the integration is enforced structurally. Each driver declares its dependencies; the engine compiles them in dependency order; the same inputs produce the same outputs every time. The assertions make the financial rules explicit and checkable rather than tribal knowledge. That is the difference between a grid that looks like a three-statement model and a model that is one.
Fork and own it
When you fork: the model is yours. Your assumptions. Your compile. A file on your machine (~/.flatland/models/) that Flatland never holds. You own the Excel export too.
Installation takes about eight minutes. Install Flatland — or read what a Finance Engineer is and what FP&A is. For a deal model, see the LBO model preset.