I wrote recently about how LP pressure is reshaping portfolio operations. Distributions at 14% of NAV. Fundraising down 16%. Over half of LPs reporting more leverage than a year ago. The conclusion was that the pressure flows downstream, from the LP to the GP to the portfolio company, and that it lands on data infrastructure.
This post goes one level down. It is about the room. The diligence call where an LP is deciding whether to commit to your next fund, and the operating review where they are checking whether the current one is on track.
LPs ask different questions now. The questions sound like reporting questions. They are actually data infrastructure questions in disguise. And the way you answer tells a sophisticated LP more about the state of your portfolio than the answer itself.
Here are the four I hear most, what the LP wants to hear, and what the common weak answer reveals.
How fast can you produce portfolio-wide metrics?
The question sounds operational. An LP asks how long it takes you to pull revenue, EBITDA, and a few operational KPIs across the whole portfolio. They are not curious about your process. They are testing your reaction time.
The answer they want to hear is days, not weeks. A GP who can produce portfolio-wide metrics in days has standardized reporting at the portfolio company level, a defined set of metrics, and a way to roll them up without a manual reconciliation marathon. That GP can also respond to a market shock, a covenant question, or a co-investment opportunity at the speed those things actually move.
The weak answer is some version of “we’d need to go back to the portfolio companies and pull that together.” That answer reveals that there is no portfolio-wide data layer. Every number lives in a separate company’s separate system, in a separate format, and producing a fund-level view is a project each time rather than a query. The LP now knows that your quarterly reporting is assembled by hand, which means it is slow, expensive, and prone to error. They also know you cannot see your own portfolio in real time, which means you are managing it on a lag.
Speed is the tell. A fund that needs three weeks to answer a basic portfolio question is a fund that finds out about problems three weeks late.
How consistent are definitions across your portfolio companies?
This is the question that separates the GPs who have done the work from the ones who think they have.
An LP asks whether net revenue retention means the same thing at every company in the fund. Whether gross margin is calculated the same way. Whether a “new customer” at one portco is a “new customer” at another. The question is quiet and it is devastating, because most GPs have never checked.
The answer they want to hear is that you defined a standard metric dictionary and enforced it across the portfolio, usually in the first 100 days after each acquisition. When definitions are consistent, fund-level analytics actually mean something. You can compare companies, spot the operational plays that work, and replicate them. You can tell an LP that the portfolio grew net revenue retention by four points and have it be a real number rather than an average of four different definitions.
The weak answer is “each company reports its own way and we normalize at the fund level.” That reveals that there is no shared definition, only a translation layer that someone maintains in a spreadsheet. The moment that person leaves, or the format changes, the comparability breaks. Worse, it tells the LP that your fund-level numbers are an interpretation, not a measurement. Every roll-up carries a judgment call that nobody outside your finance team can audit. This is the same problem I described in data governance that raises valuation. Consistent definitions are governance, and governance is what makes a number defensible.
A sophisticated LP will sometimes ask the same metric two ways to see if the definitions hold. If your team gives two answers, the LP has learned everything they need to know.
Can you show operating data in something close to real time?
The board deck with a three-week lag used to be the standard. It is now the floor, and a low one.
An LP asks whether you can see operating data, not just financials, on a cadence faster than quarterly. Pipeline. Bookings. Churn signals. Utilization. The leading indicators that move before the lagging financials do. They are testing whether you find out about a portfolio company’s trouble while you can still act on it, or only after the quarter closes.
The answer they want to hear is that key operating metrics flow on a monthly or better cadence, with leading indicators visible between board meetings. A GP who can see early warning signs can put an operating partner on the right company at the right time. That matters more than ever, because DPI pressure and the data gap means operating partners are spread thinner across more companies and have to triage where their time goes. Real-time visibility is what makes that triage possible.
The weak answer is “we get the numbers in the quarterly board pack.” That reveals a portfolio that is being managed on a lag, where problems surface a full quarter after they start. It also reveals that the underlying data does not flow. If it took a manual close to produce the board pack, there was no way to see anything sooner. The LP now knows that your operating model is reactive by construction. You cannot intervene early because you cannot see early.
The gap between monthly operating visibility and quarterly financials is the gap between catching a stall in time and explaining it after the fact.
How do you know the numbers are right?
This is the one that exposes the most, and it is the one GPs are least prepared for.
An LP asks how you know the EBITDA figure you just reported is correct. Not whether it is audited at year end. How you know, this quarter, that the number reconciles to source and that the same number would come out if someone else pulled it. They are testing whether your reporting rests on a controlled process or on trust.
The answer they want to hear involves a single source for each metric, a defined owner, and reconciliation that happens as part of the reporting process rather than after a problem is found. When the data has lineage back to the source system, you can show the LP not just the number but where it came from. That is what investor-grade reporting means. The number survives someone pulling the thread.
The weak answer is confident and vague. “Our finance teams are very experienced.” “We’ve never had an issue.” That reveals that the control is a person, not a process. The number is right because someone careful produced it, which means it is right until that person is on holiday, or the volume gets too high, or a definition shifts and nobody catches it. An LP who has sat through a diligence where the headline EBITDA did not survive scrutiny knows exactly what that answer means. It means the number is plausible, not proven.
This is also the answer that follows you into a sale. The same reconciliation gap that makes an LP uneasy in an operating review is what a buyer’s diligence team finds when they map your numbers back to source and the lineage runs out. The fund that cannot prove its numbers to an LP cannot prove them to an acquirer either.
What the pattern reveals
Look at the four questions together. Speed. Consistency. Timeliness. Accuracy. None of them is really about reporting. Each one is a probe into the data infrastructure underneath the reporting, and an LP who knows what to listen for can read the state of your portfolio from the texture of your answers.
A GP with strong data foundations answers all four the same way. Quickly, specifically, with numbers and process rather than reassurance. A GP with weak foundations answers all four the same way too. Slowly, with caveats, with “we’d need to pull that together,” with confidence that rests on people rather than systems. The LP does not need to audit your data to assess it. They just need to ask, and listen to how the answers land.
The uncomfortable part is that the weak answers are not a reporting problem you can fix before the next call. They are a data problem, and data problems take a quarter or two of real work to fix, not a polished slide. The GPs who will answer these questions well in next year’s fundraise are the ones building the foundations now, in the early hold, while there is still time for the work to compound.
If you are not sure how your team would answer these four questions today, that uncertainty is the answer. The good news is that the fix is more about discipline than technology. Pick the metrics that matter, define them once, give each one an owner and a source, and make the reporting reconcile as it runs. Do that across the portfolio and the next LP who asks how fast you can produce portfolio-wide metrics gets the answer that wins the commitment.
If you want to pressure-test how your portfolio would hold up to these questions, that is the conversation I have most often. Happy to be a resource.