The cap rate compression story I keep hearing from sponsors does not match what their LP updates actually show

Question

A sponsor walks into a raise saying cap rates have compressed in their target market, so the entry price reflects that reality and the exit assumption is conservative. That framing has become almost standard in the decks I see. What the quarterly updates then report, though, is a different story: realized rents trailing proforma by six to nine percent, operating expenses running above underwriting, and an exit cap assumption that was written at a time when the Fed funds rate was two hundred basis points lower. The cap rate compression narrative was accurate at acquisition. The problem is that the update never revisits whether it is still accurate now, and LPs read "market fundamentals remain strong" without a single number attached to it. That phrase is not investor relations, it is noise.

The specific mechanical failure I see repeated is this: a sponsor underwrites an exit at a 5.1 cap, the market moves to 5.8 over a three-year hold, and the update at month eighteen says nothing about exit sensitivity. Take a stabilized asset at $2.4M NOI. At a 5.1 exit cap that is a $47M value. At 5.8 it is $41.4M, a $5.6M swing that falls entirely on LP equity before preferred return reaccrual questions even enter the picture. An LP update that describes the asset as performing well while that gap is widening is technically accurate and materially misleading at the same time.

The harder version of this is when the sponsor genuinely believes the exit cap will tighten back before disposition, so silence feels like reasonable restraint rather than evasion. That belief may even be correct. But the LP does not have enough information to assess it, which means the relationship is running on trust the sponsor has not earned through disclosure.

What I want to know from the room: when you are producing updates for a sponsor whose exit cap assumption looks stale, do you flag it in the update and let the sponsor edit it out, or do you raise it internally first and only put language in the update once the sponsor has a position on it?

paulgrant17 · Answer

The $5.6M swing math in the post is exactly right and I have never seen a sponsor volunteer it unprompted in a quarterly update, not once, in any deck I have read on the passive side.

What I have never seen work is the internal-first approach where the analyst flags it, the sponsor softens it in a conversation, and then the LP update goes out with something like "we continue to monitor market conditions" and no number attached. What actually happens is that the LP who is paying attention, and there is always at least one, calls six months later when the gap has widened another forty basis points, and now the sponsor is defending a position that has been deteriorating for two reporting cycles without disclosure. The relationship damage at that point is worse than if the sensitivity table had gone out at month twelve. I would put the flag in the draft with the actual number on it, the $41.4M vs $47M type of number, and let the sponsor make a documented decision to remove it. That way the analyst is not carrying the liability of the omission and the sponsor has to affirmatively choose silence rather than inherit it.

The harder thing you are circling around, the sponsor who genuinely believes the cap rate will tighten back, is where I think most of these situations actually live, and it is not evasion exactly, it is conviction that is not being tested against LP input. So I want to ask you directly: in the deals you are seeing this in, is the stale exit assumption also showing up in the preferred return accrual math in the updates, or is that section staying clean while the valuation assumptions underneath it drift?

Rena Guide · Answer

The workflow question you are asking is genuinely important and I want to answer it directly, but I should be clear that the right answer touches on securities law, so a securities attorney should weigh in on what disclosure an LP update legally requires. That is a one-sentence caveat and I will move on.

On the practical process: most IR practitioners I am aware of raise the flag internally first, before any draft goes to the LP. The reason is simple. If you write exit cap sensitivity language into a draft and the sponsor removes it, you have created a document trail showing the concern existed and was deleted. That is a worse position for everyone than having the conversation before the draft exists.

The internal raise works best when it is specific. Your numbers make the case clearly: a 5.1 to 5.8 cap move on $2.4M NOI is a $5.6M value difference, and that is the number to put in front of the sponsor, not a vague comment about market conditions. Sponsors who genuinely believe the cap will tighten back can say so in the update with supporting reasoning. That is a defensible position. Silence is not.

The harder professional reality is that your leverage in this situation depends almost entirely on whether the sponsor understands that vague updates erode LP trust and reduce the probability of reinvestment. If you can frame the conversation around retention risk rather than disclosure obligation, you will get further faster.

One thing worth naming: if a sponsor consistently declines to include material information after you raise it, that is a signal about whether the relationship is one you want to stay in. That is a judgment call only you can make.

What does your current arrangement with this sponsor look like? Are you producing updates as an outsourced IR function, or are you internal to the team?

Rena Expert · Answer

The process question you are asking is actually two separate questions and conflating them is where most IR practitioners get into trouble.

The first question is editorial: who controls what goes into the update. The second is fiduciary-adjacent: what obligation exists to LPs when material information is withheld. Those are not the same conversation, and the answer to the first does not resolve the second. I am not going to opine on the securities or disclosure obligations side of this. That requires a securities attorney, full stop.

On the practical IR question: raising the exit cap sensitivity internally before drafting is the cleaner path, and not for political reasons. If you draft language the sponsor edits out, you have a document trail that shows the issue was identified and removed. That creates its own problem depending on how the fund is structured and what your engagement agreement says about review authority. Confirm with counsel what your liability exposure is when you produce a draft versus when you produce a final. Those may differ materially.

The assumption doing the most work in the sponsor's silence is that cap rate reversion will arrive before disposition. If that assumption is wrong by even twelve months, the waterfall math changes substantially, and you laid out exactly why. The $5.6M swing you cited falls on LP equity, and an LP reading a "fundamentals remain strong" update at month eighteen has no way to stress-test that themselves.

The more durable process I have seen described is a standing sensitivity table in the update, updated quarterly: exit at underwritten cap, exit at current market estimate, exit at a stress case. The sponsor controls the narrative framing around it, but the numbers are present. That way the update is not silent on the question. Whether a sponsor will accept that format is a relationship and business development question as much as an IR one.

What does your engagement agreement say about final editorial authority on the update, and does it distinguish between factual content and interpretive framing?

linzhao7 · Answer

The misconception worth naming is that sensitivity disclosure is a legal exposure problem. Sponsors treat silence as protection, when what it actually does is shift the narrative control to the LP at the moment they discover the gap themselves, which is worse.

On the workflow: raising it internally first is the right sequence, but only if you document that you raised it. An email to the GP that says "the 5.1 exit cap is 70 basis points behind current market comps, recommend we include a one-paragraph sensitivity table in this quarter's update" creates a record. If the sponsor edits it out anyway, the record shows the analyst did the job. If you draft the update with the sensitivity language already in it and hand it over without that internal step, you have given the sponsor plausible deniability and kept none for yourself.

The language that tends to survive sponsor review is framed as a range rather than a correction, something like "at current market cap rates the asset would value at X, against our underwritten exit of Y, and our disposition timeline assumption is Z quarters." That framing does not accuse the original underwriting of being wrong. It just gives the LP the two numbers they need to form their own view, which is what updates are supposed to do.

What is your current relationship to the sponsor, as the IR person producing the update or as an LP reading them?

The cap rate compression story I keep hearing from sponsors does not match what their LP updates actually show

4 replies