Skip to content
← Writing

Ledger

Issue No. 004 · Execution

What actually happens after a fund close.

The fundraising literature covers the raise in exhaustive detail and says almost nothing about the years that follow — which is most of the actual job.

By Owen E. H. Meyer · June 9, 2025 · 4 min read

The fundraising deck gets archived the same week the wires clear. Nobody reopens it. The subscription agreements get filed, the closing binder gets assembled, and the team that spent eighteen months on the road courting LPs turns its attention to sourcing deals.

Raising the fund feels like the finish line, but operationally, it's the starting line.

Everything before the close had a deadline, a target, a number to hit — everything after it doesn't, not visibly anyway.

That's the part the fundraising literature skips. Whole books, conferences, and advisory practices exist to help a GP get from first close to final close. Almost nothing is written about the months after — which is, by any honest accounting, most of the actual job.

Week one

The close itself is rarely as clean as the press release. A handful of subscription agreements are still missing a countersignature. Two LPs wired from entities that don't match the name on their subscription documents, which someone has to chase down before the funds can be allocated. A side letter promised verbally during the raise hasn't been drafted yet, and the LP who was told it was "basically done" is starting to ask when they'll see paper.

None of this is a crisis — it's just the residue of a process that moved fast enough that documentation trailed the actual commitments by a few weeks, and now someone has to reconcile the two.

Month one

Reporting eventually settles into a rhythm, though the first few updates rarely do.

The first LP update usually goes out around week four. Most teams are creating their reporting process from scratch. Someone finds a few LP update templates online, another person forwards an old investor letter from a different fund, and the first draft grows from there.

At the same time, the loose ends from the raise start catching up. Fee concessions agreed to during fundraising have to make their way into the capital call calculations. Side letters that were discussed in principle finally have to be drafted and executed. Two LPs promised early access to the same future deals turn out to have overlapping terms. None of these issues are major on their own. They just tend to arrive all at once.

Quarter one

By the first capital call, the fund needs a cadence it's never had to produce before: how notices are formatted, how far in advance they go out, what happens when an LP misses a deadline, who signs off before a notice goes to fifty investors instead of eight. None of this existed during the raise, because during the raise there was nothing to call capital for — it gets built for the first time under an actual deadline, usually by whoever on the team has the most spare bandwidth, which is rarely the person best suited to build it.

The first compliance request tends to arrive around the same time: a routine audit inquiry, an LP's own diligence questionnaire, a request for underlying fund documents from an investor's compliance team — none of it budgeted for, because compliance wasn't part of anyone's job description before the close.

Why it lands on one person

All of it tends to land on whoever was closest to the fundraising process — not a staffing failure, but what happens when the tools a team used to raise the fund do nothing to help run it: a data room is built to hold documents during diligence, not to answer which side letter governs a given LP's fee offset a year later, and a fundraising CRM is built to track a pipeline of prospective LPs, not the growing list of post-close obligations owed to the ones who already committed.

The industry has names for fundraising. It has names for fund administration. The work between those two stages — running the day-to-day operational reality of a live fund — still has surprisingly little language around it.

THE POST-CLOSE WORKFLOWOperational work accumulates — it doesn't queue up neatly behind itCloseWeek 2–6Quarter oneCountersignatures3 subscription agreements outstandingWire reconciliation2 wires from mismatched entitiesSide lettersMFN and fee-offset language finalizedLP onboardingFirst point of contact handoffFirst reporting templateNo prior version to copyFirst capital callLive notice to fifty LPsCompliance requestsAudit inquiry, LP diligence questionnaireReporting cadenceBuilt for the first time, under deadlineLEDGERby Orivade
Nothing here waits politely for the previous stage to finish. By quarter one, a fund is running three workloads it never had to build before.

What software actually covers after a close

Where the existing tools stop

ToolWhat it doesWhat it doesn't
Data roomDocuments during diligenceOngoing LP operations
CRMFundraising pipelinePost-close relationships
Fund adminAccounting & reportingDaily operational context
EmailConversationsInstitutional memory
SpreadsheetAd hoc trackingA connected operational system

LEDGERby Orivade

Five tools, five different slices of the fund's life — none of them built to cover what happens between a close and the next one.

The word "close" is doing a lot of work it shouldn't, implying an ending — paperwork wrapped, obligations settled, attention free to move elsewhere — when for an LP relationship it's closer to a start line: the point where the fund's actual, multi-year obligations to that investor begin.

Everything that gets underestimated in the months afterward gets underestimated because the name of the milestone tells everyone the job is finished.

Everything that gets underestimated in the months afterward gets underestimated because the name of the milestone tells everyone the job is finished.