On this page
A data room checklist for a venture raise starts with the finance folder: monthly financial statements, the operating model and forecast, the ARR waterfall and cohort data, written metric definitions, budget versus actual history, debt documents, tax filings and a reference copy of the cap table. Investors use that folder to test whether every number in the pitch deck ties to the books, so each document should reconcile to the others before the first meeting.
This playbook covers only the finance folder for a seed to Series B equity raise. Where the raise fits in the wider finance work at each stage is covered in the guide to a fractional CFO for startups.
The finance folder, subfolder by subfolder
Each row is a subfolder; the third column is what a diligence team will test.
| Folder | Documents | What investors check |
|---|---|---|
| 1. Historical financials | Monthly income statements for the operating history, annual statements, any review or audit reports | Months are closed and reconciled; revenue recognition is consistent; one-time items are visible |
| 2. Balance sheet and cash flow | Monthly balance sheets, cash flow statements, bank statements for recent months, deferred revenue and receivables aging | Cash ties to bank statements; deferred revenue moves with billings; receivables are collectible |
| 3. Operating model and forecast | Driver-based model with the hiring plan, a monthly forecast through the next raise, base and downside cases, use of funds | Drivers are realistic against history; the raise amount covers the plan with a buffer; runway is shown under more than one case |
| 4. ARR waterfall and cohorts | Monthly ARR waterfall (new, expansion, contraction, churn), customer level ARR schedule, retention by cohort | Ending ARR ties to contracts and to recognized revenue; net and gross retention are both shown |
| 5. SaaS metrics definitions | One page defining ARR, customers, churn, NRR, GRR, burn multiple and CAC payback, with any changes noted | Definitions match the deck and stay stable across periods |
| 6. Budget vs actual history | Each annual budget against actual results, with variance commentary | How far forecasts have missed, and whether the misses were explained |
| 7. Cap table (reference) | Current fully diluted cap table and option pool summary | Matches the master held by legal counsel; dilution in the model matches |
| 8. Customer contracts summary | Top customers by ARR with term, renewal date, pricing and any unusual terms | Concentration; renewals due soon; terms that affect revenue recognition |
| 9. Debt and venture debt | Loan agreements, amendments, covenant calculations, warrant terms | Covenant headroom; maturity against runway; how new equity affects the facility |
| 10. Taxes | Federal and state income tax returns, sales tax registrations and filings, payroll tax filings | Filings are current; no unrecorded exposure where the company sells or employs |
Legal counsel keeps the master cap table; the finance folder holds a dated reference copy so the model's dilution math can be checked. The contracts themselves sit in the commercial folder; finance owns only the summary.
The definitions page should use the same wording as the SaaS metrics already reported to the board, and the net revenue retention figure should be reproducible from the customer level schedule in folder 4.
Keeping the deck, the model and the data room consistent
Most finance diligence time goes to one question: why does this number differ from that one? Every headline figure in the pitch deck should appear in the data room exactly once, in a schedule that reconciles to the books and to the model. Where cutoffs or definitions differ, show the bridge.
An ending ARR reconciliation for a fictional Series A company:
| Ending ARR reconciliation, last month ($K) | Amount |
|---|---|
| ARR in the pitch deck and the model | 4,950 |
| Less: contract signed, service starts next month | (120) |
| Less: implementation fees billed as recurring | (45) |
| Add: renewal at higher price, not yet invoiced | 30 |
| ARR supported by recognized revenue run rate | 4,815 |
| Monthly recurring revenue recognized (4,815 / 12) | 401.25 |
Illustrative figures, not client data. 4,950 - 120 - 45 + 30 = 4,815.
Each reconciling item is a definition choice. The signed contract can count if the written definition says contracted ARR, but the deck should then say so. The implementation fees should not count at all, in any document. Finding items like these before an investor does is the point of the exercise.
The cash side needs the same discipline: ending cash and burn in the deck should match the bank statements in folder 2 and the opening balance of the forecast in folder 3.
When to start building it
Start about three months before the first investor meeting. Financial statements are quick if the books close monthly. The ARR waterfall and cohorts are not: they often have to be rebuilt from contracts and billing records, then reconciled to recognized revenue.
A practical order: close the historical months, build the ARR history on top of them, write the definitions page, then roll the model forward from the latest actuals. The deck comes last, drawing on the finished schedules. A company already producing a consistent startup board deck has much of this done, since both should draw on the same schedules.
Common gaps that slow diligence
- Months that are not closed. Open reconciliations mean every downstream schedule may move.
- ARR with no customer level detail. A single ARR line per month cannot be tested.
- NRR without GRR. A strong net figure alone invites the question of how much churn expansion is covering.
- No budget versus actual history. A forecast with no record of past forecasts is harder to trust.
- Covenants not calculated. Show the current calculation and the headroom under the new plan.
- Sales tax not reviewed. Registration or filing gaps where the company sells can surface late in diligence.
- Several versions of one file. Keep one current version, dated.
FAQ
Who should build the finance section of a startup data room?
The finance lead, whether a founder, controller or fractional CFO, assembles it, with the bookkeeper supplying closed monthly financials and legal counsel supplying the cap table and corporate documents. One person should own the index and the version history, so investors are never working from two different copies of the same schedule.
Should the data room be open before the first investor meeting?
Usually not in full. Many founders share the deck first and open the data room to investors who move toward a term sheet. The folder should still be finished before the first meeting, because questions arrive quickly once an investor is interested and gaps found later cost time and credibility.
How many years of financials go in a data room for a Series A?
Enough to cover the company's full operating history when it is short, and otherwise the last two to three years with monthly detail for the most recent periods. What matters more than the span is that every month shown is closed, reconciled and consistent with the ARR and metric history in the same folder.
Is a data room for a venture raise the same as one for selling a company?
No. A venture data room focuses on growth, retention, the operating model and how the new capital will be used. A sale data room goes much deeper into quality of earnings, working capital, contracts and liabilities, because a buyer is acquiring the whole business and its obligations rather than a minority stake.
Want someone looking ahead at your numbers?
Start with a 30-minute call: where things stand, what decisions are coming, and what to fix first.
Book a 30-minute callNot ready for a call? Take the 2-minute scorecard
Related reading
Educational content, not tax, legal or investment advice. Figures in examples are illustrative, not client data.
