Ask a fund manager to name their biggest operational pain, and reporting is usually the first word out. Push past that answer, and a different one tends to surface: not the report itself, but realizing two weeks too late that a portfolio company needed a warm intro, a bridge conversation, or a hard question, right when it would have mattered.
Reporting gets the attention because it has a deadline. Follow-up doesn't, and that's exactly the problem.
A quarterly cadence was never built to catch a weekly signal
An LP report is a snapshot: here's where things stood at the end of the period. It's genuinely useful for that purpose. It is structurally the wrong tool for catching something that needed a response the week it happened, a competitor's raise, a co-founder's exit, a founder quietly asking for help before they ask directly. By the time that shows up in the next report, the window to act on it has usually already closed.
What's actually happening: fund managers build their whole operational rhythm around the one task with a visible deadline, and the task without a deadline, staying close enough to catch a live signal, loses the time competition by default. Nobody decides to deprioritize follow-up. It just never gets a slot.
The cost shows up as a missed outcome, not a missed task
This is why follow-up latency is hard to see coming: it doesn't fail loudly. Nobody gets an error message. The fund manager finds out a founder needed help, or a competitor made a move worth responding to, through an offhand comment or a LinkedIn post, weeks after the moment that mattered. It reads as bad luck in the moment and as a pattern in hindsight.
