You Just Closed Fund I. Here Is the Reporting Stack Your LPs Will Judge You On
The first close is the day LP reporting stops being a courtesy and becomes a fundraising asset. Everything your LPs see from now until Fund II is evidence about how you run money, and most Fund I managers discover this the first time a quarterly deadline arrives and the numbers live in four places. This post is the CFO view of what year one actually requires, where the usual subscription stack quietly stops working, and how to plan the first 90 days so you are not rebuilding in year two.
What do LPs actually ask for in year one?
Less than you fear, and more consistently than you expect. In the first year of a fund, institutional and family-office LPs want four things delivered on a predictable cadence:
- Quarterly reporting with capital account statements, fund-level performance, and portfolio commentary that reads like judgment rather than a template.
- Capital calls and distributions that are correct the first time, with notices that reconcile to the fund's books without a follow-up email.
- Portfolio company updates at a consistent depth: what changed, what you did about it, what you expect next.
- Annual financials and the audit trail behind them, which means every number in your quarterly reports has to survive contact with an auditor in the spring.
None of this is hard on its own. The difficulty is that each item draws on a different source, and in a Fund I setup those sources are usually a fund administrator, a cap table tool, a portfolio monitoring tool, a CRM, and a spreadsheet that ties them together. The spreadsheet is where the fund's operating reputation lives, which is not where you want it.
Where does the subscription stack stop working?
The standard emerging-manager stack is sensible and I would not talk anyone out of it on day one. Cap table management in Carta or a similar tool. Portfolio monitoring in Visible or one of its peers. A CRM for deal flow. A fund administrator for the books. Spreadsheets for everything the tools do not connect.
It works because the fund is small. It stops working for reasons that are structural, not because any single tool is bad:
- Portfolio count. Monitoring tools are priced and designed around a number of portfolio companies. Somewhere around 25 to 30 companies, in our experience, the tier you started on no longer fits, the per-company economics change, and the manual workarounds multiply.
- The join is manual. Cap table data, company metrics, and fund accounting do not share a record. Every quarter someone reconciles them by hand, and every reconciliation is a chance for the LP report to disagree with the audit.
- Reporting is the last step, so it absorbs every upstream error. A metric a founder entered late, a valuation the administrator booked differently, a distribution notice with a rounding difference: they all surface in the LP report, which is the one document your LPs keep.
- Repricing follows growth. As the portfolio grows and the LP base gets more institutional, the tools you rent get more expensive at exactly the moment the reporting demands get heavier.
The honest summary: the subscription stack is right for the first 10 to 15 companies and wrong for Fund II fundraising. The question is when you cross over, and whether you plan the crossing or get surprised by it.
What does a Fund I reporting stack need to do, as one system?
Strip away the tool names and the requirements are simple. A fund needs one record of each investment that the pipeline, the portfolio, and the LP report all read from.
| Capability | What year one needs | Where subscriptions usually stop |
|---|---|---|
| Deal pipeline | Every opportunity, its stage, and who owns the next step | Lives in a CRM that never talks to the portfolio |
| Portfolio monitoring | Founder-reported metrics on a schedule, with history | Tier caps by company count; metrics re-keyed into reports |
| Capital accounts and notices | Calls, distributions, statements that reconcile to the books | Administrator output copied into templates by hand |
| LP reporting | Quarterly package assembled from the above without manual joins | The spreadsheet does the joining; errors surface here |
| Audit readiness | Every reported number traceable to its source | Reconstructed after the fact, once a year, under pressure |
The row that matters most is the last one. A reporting stack that produces a beautiful quarterly deck but cannot show an auditor where a number came from is a liability with good design.
Build, buy, or wait?
This is the decision most Fund I managers get asked and few get an honest answer to, because most of the people answering sell one of the options. Here is the version I would give a manager I liked.
Wait, if you are under roughly 15 portfolio companies, your LP base is mostly individuals and family offices who are content with a quarterly email, and you have no Fund II raise planned inside 18 months. The subscription stack is fine. Spend your money on deals.
Buy, if your problem is one specific gap, such as portfolio metrics collection, and a tool solves that gap cleanly. Do not buy a fourth tool to fix the join between the first three. That is how the spreadsheet becomes permanent.
Build, if you are heading toward 25 or more companies, your LPs are institutionalizing, or Fund II fundraising will put your operation under operational due diligence. At that point an owned system that holds the single investment record, feeds the LP report, and keeps the audit trail costs roughly what a year of the mature subscription stack would, and it does not reprice as the portfolio grows. We have built exactly this pattern, including a platform serving a network of thousands of investors, and the shape is consistent: pipeline, portfolio, capital accounts, and reporting on one record, with the fund administrator's books as the accounting source of truth rather than a competitor to it.
One rule for anyone building: do not replace the administrator. Build the layer that reads from them. Funds that try to become their own back office lose a year.
What does the first 90 days look like?
If you closed recently, here is the plan I would run, in order.
Days 1 to 30: decide the record. Write down, in one page, the fields that describe an investment in your fund: entity, instrument, ownership, valuation basis, reporting metrics, and who updates each. This document outlives every tool you will ever use.
Days 31 to 60: fix the join, not the tools. Map where each field lives today and how it gets into the LP report. Every manual copy is a defect. Decide which defects you can remove with configuration, which need a small integration, and which mean the stack has already been outgrown.
Days 61 to 90: produce one quarter the right way. Run the next quarterly package from the mapped sources with an audit trail attached to every number. If it takes a week of spreadsheet work, you have your answer about year two. If it takes a day, you bought yourself time.
What number are your LPs really judging?
It is not IRR in year one. Nobody expects year-one IRR to mean anything. The number they are judging is how many times they have to ask you for something twice. Reporting that arrives on time, reconciles to the books, and reads like you understand your own portfolio tells an LP you will be a competent steward of Fund II before you have a track record to prove it.
That is what a reporting stack is for. Not the deck. The trust.
If you are between the first close and the first audit and want a second set of eyes on where your stack sits, we are happy to look. We build these systems for funds, and we will tell you plainly if yours does not need one yet.
Related reading: LP reporting automation · Portfolio management: build vs buy · Fixed price vs time and materials · Venture capital
