A practical model for drafting capital-account statements and commentary, with a controller signing off on every figure.
Key takeaways
Once NAV is finalised, a stretch of the quarter typically goes to drafting narrative commentary, chasing portfolio-company updates, and formatting capital-account statements to match the terms in the LPA. For a lean fund-ops team, that's time not spent on the next deal or the next raise.
None of it is difficult work. Most of it is repetitive, template-driven, and exactly where a drafting tool earns its keep.
A first-pass narrative built from portfolio-company updates and fund financials already validated by the admin system, and a populated capital-account statement pulled from the same source, are both reasonable starting points for a controller to review.
What it doesn't do is calculate NAV, decide what gets disclosed, or touch the underlying fund accounting. Those stay exactly where they are today.
Every figure an LP will rely on for their own reporting has to be checked against the fund's books before it goes out. In practice that means a controller compares each number in the draft against the source ledger and corrects anything that doesn't match, before a single LP sees it.
That review step is the whole point — a faster draft is only useful if what leaves the fund is still fully verified.
The gain isn't that reports get written faster because a model writes faster than a person. It's that commentary drafting stops being the thing the whole team is waiting on.
Funds that put a controller-reviewed draft in front of the team days earlier are the ones that clear LP deadlines without a last-minute scramble — the constraint simply moves back to controller review time, which is where a fund actually wants it.
A 30-minute call is enough to tell you whether AI pays for itself here.
