The Problem Isn't Revenue. It's Infrastructure.
A SaaS founder came to us with $3M ARR, 85% gross margins, and six months of investor conversations that were going nowhere. Every call ended the same way: the investor would ask for the cohort analysis, the CAC payback by channel, the ARR waterfall, the headcount plan tied to the model. And every time, the answer was: 'We'll send that over.' Nothing ever went over, because it didn't exist.
The problem was not the business. The business was genuinely good. The problem was that the business couldn't prove it was good in the language investors speak. Four months after we started, they had a term sheet. The $18M Series A closed two months after that.
Figure 2: Investor readiness milestones — $3M ARR to $18M Series A
What Investors Actually Look For
Investors don't fund revenue. They fund predictability. When a Series A investor looks at your financials, they are trying to answer one question: if I give you $5M, can I predict with reasonable confidence what happens to it? That requires a very specific set of artefacts.
The data room has to have: an ARR waterfall showing new, expansion, contraction, and churn in each period; cohort retention curves by quarter of acquisition; CAC by channel with payback period at gross margin; a bottom-up financial model with three scenarios; a headcount plan that ties to the revenue model; and a KPI dashboard that updates automatically, not manually.
Most early-stage companies have fragments of this. They have some revenue data in their billing system, some headcount in a spreadsheet, some CAC estimates someone calculated six months ago. None of it connects. The investor sees disconnection and reads it as risk.
The Build: What We Actually Did
Week one was data architecture. We pulled billing data from Stripe, CRM data from HubSpot, and headcount data from their HRIS. We built a single source of truth — every metric calculated from the same underlying data, no manual adjustments, no 'the number in the deck is slightly different because we adjusted for X.'
Week two through four: the financial model. Not a template — a model built around their actual business. Their revenue had three streams: self-serve, SMB sales-assisted, and enterprise. Each had a different sales cycle, different CAC, different gross retention, and different expansion motion. The model separated all three because investors in their space knew the difference between a self-serve SMB business and an enterprise one, and conflating them would have killed credibility.
Week five and six: the KPI dashboard and the narrative. The dashboard was Power BI connected to the same data layer as the model — so when an investor asked a question in the meeting, we could answer it live, not promise to send a follow-up.
The narrative was the final piece. Not a pitch deck (they had that). A document that connected the metrics to the story: here's why our net revenue retention of 118% is not a coincidence, here's the mechanism that drives it, here's what happens to it at scale. Investors had seen hundreds of decks with NRR numbers. Few of them had seen a founder who could explain the machine behind the number.
The 2025 Investor Landscape Requires More, Not Less
The 2021 vintage of Series A — revenue growth above all else, sparse diligence, quick decisions — is gone. In 2025, investors are taking longer, asking harder questions, and rejecting more. The bar on financial infrastructure has risen significantly. We've seen term sheets pulled because the data room had inconsistent ARR definitions across different documents. That's not a business problem. That's a finance infrastructure problem.
The good news is that this is entirely solvable. It takes four to six months of focused work, the right tools, and someone who has done it before. The cost of not doing it is every investor conversation that ends with 'send us more information' and never becomes a term sheet.