How to Actually Collect KPIs From Portfolio Companies (Without Chasing Founders Every Quarter)

Most funds have a KPI list. Few have a system that reliably gets those numbers out of founders every quarter. The gap between "we track ARR, burn, and runway" and "we actually have Q2 numbers for eleven of our thirteen companies by the fifteenth" is where most portfolio visibility quietly falls apart. Here is a practical framework for closing it.

Last week we covered which KPIs micro-VCs should actually track, and which ones do not earn their place on the request. That question matters, but it is the easier of the two problems. The harder one is getting founders to send the numbers back, on time, in a format you can actually use, quarter after quarter.

Most funds discover this the hard way. The metric list gets agreed at investment. The first quarterly request goes out on schedule. Then the replies trickle in over three weeks instead of three days, half of them as narrative paragraphs instead of numbers, and by the time the partner meeting happens the “portfolio update” slide is really just whoever replied fastest.

This is not a founder problem. It is a systems problem, and it is fixable.

Why KPI collection breaks even when the KPI list is right

Three failure modes show up again and again in how funds run portfolio reporting, independent of what is actually on the metric list.

The first is information lag. A quarterly update that reveals a cash problem is reporting on a problem that has been developing for weeks already. By the time the number arrives, the window for a useful conversation about it has often closed.

The second is inconsistent format. Every founder reports differently unless told exactly what to send and how. One sends a spreadsheet, one sends a paragraph, one sends a screenshot of a dashboard. Comparing traction across a portfolio then requires manual normalisation that most funds do not have the bandwidth for, so it simply does not happen.

The third is founder burden, and it compounds. Writing an investor update takes time founders would rather spend on the business, and the more investors on the cap table, the more requests pile up. The quiet result is founders sending shorter, vaguer updates over time, which is the opposite of what the fund needs.

None of these are solved by picking better KPIs. They are solved by fixing the mechanics of the ask.

1. Fix the cadence before you fix the format

Quarterly is the reasonable default for most portfolio companies. Monthly is worth the extra overhead only for two situations: companies within roughly nine months of an anticipated raise, where investors and founders both benefit from tighter visibility, and companies showing early stress signals where you want to catch a problem before it becomes a crisis. Bi-annual is acceptable only for very early, pre-revenue companies with genuinely slow-moving milestones.

Whatever cadence you pick, the mistake to avoid is applying one cadence uniformly across a portfolio that does not have uniform needs. A pre-seed company six weeks from running out of cash and a profitable Series A company on a two-year runway do not need the same reporting rhythm, and treating them the same either over-burdens the healthy company or under-serves the one that needs closer watching.

2. Ask for the same numbers every time

Reporting consistency starts before the first request goes out, not after the first reply comes back. At the point of investment or shortly after, walk the founder through exactly what you will ask for, on what cadence, and why. Founders who understand that the reporting exists to help you spot problems early and offer support, not just to flag failures after the fact, are more likely to report honestly rather than optimistically.

Keep the core metric set small and fixed. A sensible ceiling is 10 to 15 KPIs per company, covering the same baseline across the portfolio (revenue or ARR, cash position, burn and runway, headcount) with two to four company-specific additions for stage or sector. When every company reports on the same baseline, comparison becomes possible without manual translation. When the list balloons or drifts company to company, it does not.

Resist the temptation to add a metric because it would be nice to know. Every additional field is friction on the founder’s side and noise on yours.

3. Make reporting easier than not reporting

This is the single biggest lever most funds under-use. Compliance is not primarily a discipline problem on the founder’s side, it is a friction problem on the fund’s side. A quarterly email asking for six numbers “whenever you get a chance” will get replies whenever founders get a chance, which in practice means late, incomplete, or not at all.

A structured submission mechanism, whether a short form, a locked template, or a founder portal, removes the ambiguity about what is being asked for and how long it should take to answer. Nire’s portfolio tracker is built specifically around this problem: fund managers set the KPI request once, founders submit through a structured form rather than an email thread, and the fund gets a comparable dataset without chasing anyone. Reducing that friction is consistently associated with materially higher compliance rates, because filling in six fields in a form takes minutes, while composing a narrative email from scratch takes much longer and is easier to deprioritise.

If you are still requesting updates over email with no fixed structure, this is the highest-leverage change available before anything else on this list.

4. Build the follow-up into your calendar, not your inbox

The default failure pattern is chasing replies reactively: the request goes out, some founders reply, some do not, and a week later someone remembers to follow up with the ones who have gone quiet. This works until portfolio size passes roughly ten to twelve companies, at which point tracking who has and has not replied becomes its own manual job.

Put the follow-up cadence on a calendar, not a mental note. A fixed schedule (request sent, reminder at day seven, personal follow-up at day fourteen for anyone still outstanding) means chasing happens on schedule regardless of how busy the week is, rather than depending on someone remembering.

5. Keep collection separate from analysis

Once the numbers are in reliably, the more valuable work becomes possible: spotting a flattening growth curve, a shrinking runway, or rising burn two quarters before it becomes a crisis, rather than reading about it after the fact. That forward-looking read is the actual point of collecting KPIs in the first place. It only works once the collection mechanics stop being the bottleneck.

Worth noting for funds with more than one person touching portfolio data: who is allowed to enter numbers and who is only allowed to read them matters more as a team grows. Nire’s platform enforces this distinction directly: analysts can submit KPI updates, but strategic decisions like follow-on recommendations stay with the people who own that call. Operational data entry is a different kind of action from a strategic call, and the tools and permissions around each should reflect that.

What good KPI collection looks like month to month

At a fund running this well, the pattern is unremarkable, which is exactly the point. The request goes out on a fixed date each quarter, in a fixed format, to a fixed list of recipients. Most replies arrive within the first week because the form takes five minutes, not an evening. Anyone outstanding gets an automatic reminder before anyone has to think about chasing them. By the time the partner meeting happens, the numbers are already in a comparable format across the portfolio, and the conversation is about what the numbers mean rather than which ones are still missing.

Frequently asked questions

How many KPIs should we actually be asking founders to report?

Ten to fifteen per company is a sensible ceiling. That typically breaks down as four or five baseline metrics tracked consistently across the whole portfolio (revenue or ARR, burn, runway, headcount) plus two to four metrics specific to that company’s stage or sector.

Should reporting cadence be the same for every company in the portfolio?

No. Quarterly is a reasonable default, but monthly makes sense for companies within around nine months of a likely raise or showing early stress signals, and bi-annual can be appropriate for very early pre-revenue companies. Uniform cadence across a non-uniform portfolio tends to either over-burden healthy companies or under-serve the ones that need closer attention.

What is the single change that improves reporting compliance the most?

Reducing friction on the founder’s side. A structured form or template that takes minutes to complete consistently gets better compliance than an open-ended email request, because the effort required is the main thing standing between a founder and an on-time reply.

How do we handle founders who consistently report late?

Build the follow-up into a fixed schedule rather than chasing reactively. A reminder at a set number of days after the request, followed by a personal follow-up if there is still no reply, keeps the process consistent regardless of how busy a given week is for the fund.

Is a spreadsheet good enough for KPI collection at a small fund?

For two or three companies, yes. Past roughly ten to fifteen, spreadsheets tend to break down on version control (multiple people editing the same file), historical trend analysis across quarters, and the manual work of normalising inconsistent founder submissions into a comparable format.

This article is general guidance, not financial or legal advice. Reporting practices vary by fund size, stage focus, and portfolio composition. Specific situations may require tailored advice.