Every Series A analyst has a habit. They open the assumptions tab first, the cash flow statement second, and the monthly P&L third. Everything else, they get to later. A founder who knows this can structure the model to win the first ten minutes.
Tab one: assumptions.
This is the tab the analyst reads to decide whether the founder understands the business. Every input lives here: pricing, growth, churn, COGS, hiring cadence, capital raises, working capital terms. Color-coded blue (inputs), referenced everywhere else in the model.
The assumptions tab is also the diligence weapon. When an analyst flexes the model, they change inputs here. If the inputs are not centralized, they cannot flex the model, and they will assume the founder cannot defend it.
What belongs in assumptions.
- Revenue drivers. Pricing per tier, customer acquisition cadence, conversion rates, churn rates by segment.
- COGS structure. Variable cost per unit, infrastructure spend tied to scale, payment processing or platform fees.
- Hiring plan. By role, with start month, fully-loaded comp, and department. Not a single "headcount" line.
- Operating expenses. Tools, marketing, legal, accounting, rent. By category, monthly.
- Working capital terms. AR days, AP days, deferred revenue recognition cadence.
- Capital structure. Existing cash, SAFEs outstanding, planned raises with timing and amount.
Tab two: monthly cash flow.
Cash flow is where companies actually die. Investors know this. They go straight to the cash flow tab to see how the company looks across the trough months.
The structure should be indirect method. Start with net income, add back non-cash items (depreciation, stock-based comp), adjust for working capital movements (AR, AP, deferred revenue), subtract capex, layer in financing (capital raises, SAFE conversions). Ending cash on the cash flow ties to cash on the balance sheet.
If the cash flow does not balance to the balance sheet, the analyst stops reading.
Tab three: monthly P&L.
The income statement is the storytelling layer. It shows the revenue trajectory, the gross margin trend, the operating leverage point, and the path to profitability (or to the next raise).
Structure it cleanly. Revenue by stream, COGS by category, gross profit, operating expenses by department, EBITDA, depreciation, interest, taxes, net income. Twenty-four months of monthly resolution. Annual summary columns at the end for the headline numbers.
The mistake founders make is putting revenue assumptions inside the P&L tab itself. Pricing, customer count, churn. All of it belongs in assumptions and flows into the P&L through formulas. The P&L is the output, not the source.
Why monthly resolution matters more than length.
Founders sometimes ask whether they should build 24 months or 60 months. The answer is almost always 24 to 36, but at monthly resolution. A 60-month model with annual rollups hides everything that matters: hiring waves, contract renewals, seasonality, cash troughs.
Investors care about months 6 through 18 more than they care about year 5. That is the window where the next milestone hits, the next raise happens, or the company runs out of cash. Annual numbers cannot tell you which.
The three supporting tabs.
Beyond the first three, a complete model includes:
- Balance sheet. Monthly, tied to cash flow. Verifies the model balances (assets equal liabilities plus equity).
- Cap table and use of funds. Where the capital comes from, where it goes, and what ownership looks like after the raise.
- Unit economics. CAC, LTV, payback period, contribution margin. Computed from the underlying customer cohorts, not asserted.
Each is referenced from the assumptions tab. Each holds up under flex.
The scenario layer.
One file, three scenarios. Base case is the operating plan you intend to run. Downside strips out 30 percent of revenue and delays hiring. Upside assumes the raise closes on time and the pipeline converts. Toggle between them inside the model, not across separate files.
Investors do not ask whether your scenarios are realistic. They ask whether the model holds up structurally when assumptions move. If the answer is yes, you have a model. If the answer is no, you have a deck spreadsheet.
One question that distinguishes the two.
If you change the hiring start date for your first sales engineer by one quarter, do revenue, cash, and option pool dilution all update correctly? If yes, you have a model. If no, you are not ready to send it to an investor yet.