Happy Thursday and welcome. As always, let's dive in.

Today we’ll be talking about everyone’s favorite topic: Portfolio monitoring.

The problem for LPs is that most GP portfolio updates are written as if the prior quarter never happened.

You get a company description. You get this quarter's developments. Maybe a KPI or two. And then you move to the next company.

What you almost never get is a dashboard showing the overall status of each portfolio company linked back to the original investment thesis. Where did we say this business would be at this point in the hold? Where is it actually? What's changed in our thinking - and why?

Instead, the report resets. Fresh narrative. Clean slate. This quarter, the dental roll-up completed three add-on acquisitions and is tracking ahead of its consolidation targets…

Great. But what did you write about the dental roll-up last quarter? And the quarter before? Is this trajectory consistent with what you underwrote when you bought it? What was the original thesis - and is the business actually living up to it, or just staying busy?

Yes, the current mark is a guide but how and why has it changed?

Most reports make that question surprisingly hard to answer.

Sidebar: I should say that some GP reports are genuinely good - but they are far from the majority.

I recently saw a quarterly report from a large-cap buyout fund with roughly twenty-five companies in the portfolio.

Each company had a two-page narrative update. Well written, detailed, clearly prepared with care. 50 pages of updates.

What it didn’t have were tables. Or deltas. Or any indication of how the key numbers had moved since the last quarter.

If you wanted to understand what actually changed, you had to go back to the previous report, find the same company, and reconstruct the movement yourself.

Multiply that exercise across twenty-five companies and you start to see the problem. The information exists, but the structure of the report makes the signal hard to see.

This is not a conspiracy. It's just incentives.

GPs raise the next fund. That means the quarterly report - however carefully designed to look like a disclosure document - is also, functionally, a marketing document. The goal is to tell a coherent story. Emphasise what's working. Give context for what isn't. Land the narrative.

The best GPs do this thoughtfully, and it's not dishonest. But the report is not built to give you the analytical picture you need. It's built to give you their picture. Which is a different thing.

You'll get headline figures. You'll get a portfolio update section that's somewhere between a press release and a progress report. You'll get a market commentary written during the week before distribution, where the actual purpose is to frame whatever the marks are doing - and whatever was top of mind for the associate on the other side writing this.

What you'll rarely get is clear attribution. How did NAV move from last quarter to this one, and why? What drove it - realisations, markups, new investments, valuation methodology changes?

The headline number doesn't tell you. And most GPs don't make it easy to find out.

Here's what I actually want to know every quarter:

What moved? And what drove the movement?

A realised exit says something very different from a markup across comparable companies. A write-down because a business genuinely underperformed is different from a write-down because the GP finally caught up with where public market multiples had been for six months. A stable NAV during a period of falling market sentiment might reflect genuine portfolio resilience - or it might reflect a valuation team that hasn't updated their assumptions yet.

The headline number does not distinguish between these.

Understanding why a number moved - quarter to quarter, fund to fund, over time - is what turns monitoring from a reporting exercise into something that actually informs decisions. And that requires tracking changes consistently, building the picture yourself, and maintaining enough context about each fund's history that movements become interpretable rather than merely visible.

The quarterly review can easily become a catching-up exercise. Numbers get entered, documents get filed, the review gets written up. But the analytical thread - what changed, what drove it, what does it tell me - gets lost in the volume.

That's not a bandwidth problem. It's a design problem. And once a portfolio reaches a certain size, design quickly becomes infrastructure - because the only way to maintain the analytical thread across dozens of funds is to build systems that track it continuously.

When you have ten funds, you can hold the picture in your head. You know what each fund is doing. You've been on the calls. You remember the last quarter's numbers.

At thirty funds, that's not possible. The cognitive load exceeds what any small team can actually hold, especially during a compressed reporting window when thirty documents arrive in the same three weeks.

Reporting is document management. Monitoring is portfolio awareness.

Most GP reports tell you what happened this quarter. It’s your monitoring that tells you what actually changed.

And change - the deltas, the drift, the movement in assumptions - is where the information lives.

That picture doesn’t assemble itself. It has to be built.

How are you building it?

One question we hear more often than we would like is:

“What does FundFrame actually do?”

Part of the honest answer is that we have not always been great at explaining it.

LPs are used to thinking about their work as separate tasks, each with its own tool:

Different workflows. Different systems. Often different people responsible along the way. Each centred around a job to be done.

What we are building with FundFrame is simply the system that connects those workflows.

The same manager you meet in sourcing should already exist when diligence starts. The thesis you wrote when committing should still be visible when monitoring the investment years later. The assumptions used during underwriting should already exist when building portfolio forecasts.

Instead of separate tools for each step, it becomes one system that carries the investment workflow forward.

We’ve started calling that the operating infrastructure for LPs.

Which of course leads to the next question:

“What does that mean?”

That is what we are currently practicing how to explain.

If you've found a good way to describe a platform that crosses workflows - or if you just have a better phrase than "operating infrastructure" - hit reply. I’d love to hear your take.