← All postsfundraising · diligence

The Data Room Readiness Test: 11 Files Investors Open in Order

every series a diligence opens the same eleven files in roughly the same order. if yours aren't ready in week one, the round slows by a month.

2026-05-115 min readZift

the term sheet arrives on a friday. the partner asks for diligence access by monday. the founder spends the weekend in a panic, exporting csvs from stripe, screenshotting carta, asking the contractor accountant to "get the books in shape." by tuesday, the data room has eleven folders and four of them are empty. by friday, the partner's associate has flagged six inconsistencies.

the round doesn't die. it slows. what would have closed in thirty days closes in sixty. the founder loses leverage on the negotiation because every delay is now read as a signal — "are they hiding something?" — and the partner has time to pattern-match the gaps against other deals.

every series a diligence opens the same eleven files. they open in roughly the same order. the founders who have all eleven ready before the term sheet is even signed close on the original timeline. the founders who don't, lose a month.

the eleven files, in the order they get opened

cap table comes first. always. the partner wants to see who owns the company before they read another line. current cap table with all safes, options, warrants, and a pro-forma that models the round itself. anything missing or wrong here ends the diligence before it starts.

monthly p&l next, twenty-four months of it, exported clean from the books. the partner reads down the revenue line and across the burn line for trend, not levels. if you're missing two of the last twenty-four months, the partner assumes the books aren't closed and triggers a quality-of-earnings review, which adds three weeks.

mrr and arr waterfall, with logo retention. new mrr, expansion mrr, contraction, churn, net new — every month. logo retention by cohort. this is where the round actually gets decided. the partner spends more time here than anywhere else, and inconsistencies between the cap table revenue narrative and the waterfall reality is the single most common round-killer.

cohort retention. monthly cohorts, twelve to twenty-four months back, gross dollar retention by cohort. flat or declining cohorts are how a $5M arr company becomes a $4M arr company while still calling itself growth-stage.

top twenty customers, by arr, with tenure and contract length. concentration risk. the partner wants to know what happens if customer number three churns. if your top customer is 30% of arr, the partner needs to see the contract and a renewal plan.

sales pipeline. quarter-by-quarter pipeline, weighted by stage and conversion rate. this is where reps' projections meet reality. the partner reads back-test accuracy — what did you forecast for q3, what did you close — and uses it to discount your forward forecast.

hiring plan. what you intend to spend the round on. role-by-role, with start dates and fully-loaded cost. partners flag plans that hire too fast or in the wrong sequence.

aws/infra invoice trail. twelve months of cloud bills. partners use this to verify gross margin claims and to spot the "misconfigured s3 bucket" class of problem.

top five customer msas. the actual signed contracts. partners read auto-renewal clauses, termination-for-convenience clauses, and price-protection clauses. an msa with a 30-day-out clause is not the contract your revenue deck implied.

board minutes. last twelve months. partners use this to check whether the founder is honest with their existing board and whether the existing board functions as a working board. silence on hard topics in the minutes is a flag.

last fundraise docs. the prior round's term sheet, definitive docs, and any side letters. the partner needs to see what protective provisions, board rights, and information rights already exist before structuring the new round.

days to close · series aprepared vs unprepared
prep · day one
28d
term sheet to wire
prep · panic mode
62d
2.2x longer
diligence questions
14
prepared founder
diligence questions
73
unprepared founder

the numbers above aren't theoretical. term sheet to wire runs about four weeks for prepared founders, eight to ten for unprepared ones — a gap the portfolio notes at a16z and Bessemer have documented across multiple cohorts. the cost is rarely the four weeks of time. it's the leverage that decays during them.

why most founders prepare the deck instead

the founder rehearses the pitch deck for sixty hours. they rewrite the customer slide three times. they obsess over the magic number tile and the burn-multiple framing. all of that work targets the meeting that gets you the term sheet.

the data room is what determines whether you keep the term sheet. and almost no founder spends an equivalent sixty hours on it before going to market.

three reasons. the deck is creative work that feels like product. the data room is hygiene that feels like homework. the deck gets feedback from your seed investor and your advisor. the data room only gets read once, by people you've never met, after the deal is already moving. and finance, which owns the data room, is treated as a downstream function — something to "clean up later" — rather than a fundraising input.

the deck wins the term sheet. the data room keeps it. founders who prepare the first and skip the second get term sheets that quietly degrade in diligence.

the readiness test, in one afternoon

three questions, asked of yourself, brutally.

can you pull all eleven artifacts in two hours? open a fresh folder. set a timer. if you can't produce the cap table, p&l, mrr waterfall, and cohort retention in two hours — without the contractor accountant, without three different exports, without screenshots — your data room is not ready.

does the revenue number on the deck match the revenue number in the waterfall, the p&l, and the bank? these four numbers should match exactly. they almost never do, at series a, because they're computed by four different systems and reconciled by hand. the partner's associate will find the discrepancy in week two and you'll spend week three explaining it.

can you defend each msa clause in your top five contracts from memory? auto-renewal, termination-for-convenience, price protection, exclusivity, mfn. if you can't, the partner will read the contracts and surface the worst clauses to you in a way that costs leverage.

how zift handles this

zift keeps eight of the eleven files current to the day, every day — p&l, mrr waterfall, cohort retention, top-twenty customers, infra invoices, burn, runway, gross margin. when the term sheet arrives, you grant access instead of preparing. the associate reads numbers computed this morning, not exported friday night.

if you're a finance lead at a series a team running diligence across multiple subsidiaries, zift handles consolidated reporting and audit trails.

the founders who close in four weeks aren't faster negotiators. they just had the eleven files ready before they needed them.

Related

More on this topic.

2026-08-30 · 5 min read

Marketplace Take Rate Is the Only Number That Matters. GMV Is Vanity.

founders pitching marketplaces lead with gmv. investors discount it instantly. take rate × retention is the only revenue signal that survives diligence.

Read →
2026-08-26 · 5 min read

The Investor Reference Call That Passes on You

investors do back-channel references on every term sheet. founders rarely hear the bad ones. the language is consistent and worth recognizing.

Read →
2026-08-23 · 5 min read

Eval Cost Is the AI Line Item Nobody Budgets For

every ai startup runs evals. nobody puts them in gross margin. at scale, eval cost is 12-20% of inference and it sits in the wrong line.

Read →

Finance reports to you, not the other way.

Cash, burn, MRR, runway. Three things to look at this week. Three minutes to read. Reply with a question and Zift answers from your real numbers.

Join the waitlist →Keep reading →