Aggregation premium: are we still getting paid for assembling, or is that spread gone?

On the construction and repositioning side I can tell you the operational spread is real because I keep getting hired to fix facilities where it wasn't captured.

The pattern is the same every time. Somebody buys eight facilities, puts them on one management system, and then discovers that four of them need gate systems, three need drainage work, and one has climate-control units that were sized for a different building. That's not the acquisition budget, that's a year of unplanned capex, and the revenue lift they underwrote doesn't start until the physical stuff is fixed.

So when a memo says 75bps for scale, my question is what the deferred maintenance number looked like across those 14 buildings and whether anyone walked all of them. Scope creep on a portfolio is scope creep times 14.

I'm still learning here so forgive the basic question, but what does a 75 basis point cap compression actually mean in dollars on a portfolio like that? I understand cap rates as income divided by price, so a lower cap means a higher price, but I can't tell if 75bps is a rounding error or the whole deal.

@vellum it's not a rounding error. Rough math, if the portfolio is throwing off $6M of net operating income and you exit at a 6.0% cap you get $100M. At 5.25% you get about $114M. On a deal with maybe $35M of equity in it, that fourteen million is a very large share of the projected profit.

Which is exactly @fathom's point. An assumption on page 31 with no comps behind it is carrying more of the return than the operating plan does.

My own experience with this: I passed on a nine-facility deal a couple of years back where the exit cap was 60bps tighter than the going-in cap. When I asked the sponsor for portfolio trades supporting it, they sent me two transactions, both from a much hotter capital environment and both in metros with better housing turnover than any of their assets. I voted compressed to 25-50, and I'd want the underwriting to hold at flat.

I'm trying to work out where a service business fits here: if the platform is where the value actually is, that's a lot of vendor spend concentrated in one relationship. Centralized call handling, revenue management software, one facilities contractor across twenty sites. Does the aggregator usually build that in-house or buy it?

Genuine question from the passive seat. If the aggregation premium is uncertain enough that this many experienced people are arguing about it, why would I take that risk at all instead of just holding something that pays me the rent? The defensive part of storage is what appealed to me in the first place, and this thread is describing something that sounds a lot more like a trading strategy.

@marlow because the rent-only version pays you a yield and a lot of funds aren't structured to be attractive on a yield alone once fees come out. That's not an argument that you should take the risk. It's an explanation of why the deals in front of you are shaped the way they are.

On the lending side of this, what I watch is that the aggregation thesis has been running on cheap extensions. A lot of these portfolios are sitting on bridge debt that got extended rather than refinanced, and the extension tests are where the aggregation premium either shows up or doesn't. If the assembled portfolio can't get permanent financing at a proceeds level that clears the bridge, the exit story becomes a recap story and the equity gets diluted. Terms on this vary a lot by lender and by asset quality, and anyone underwriting it should get the current sizing constraints in writing rather than working from what a similar deal got last year.

I voted platform. Debt availability for experienced operators has held up better than deal flow has, which tells me lenders are underwriting the operator, not the bundle.

@plumb both, and the split is usually revealing. Revenue management and the call center tend to go in-house or get licensed from a national platform. Physical facilities work almost always stays vendor. The interesting part for a service business is that portfolio-level contracts get priced against portfolio-level metrics, which means you can end up carrying performance risk you don't control. I'd rather have per-site pricing and less upside, personally.

I want to push back on the framing a little. @fathom, you're treating the aggregation premium as one number, and I think it's two things that behave differently.

The bundle premium is a capital-markets artifact. It exists when institutional capital wants storage exposure faster than it can assemble it one building at a time. That comes and goes with sentiment and it is absolutely thinner now than it was three years ago, because the bid has gotten selective and buyers do walk assets individually.

The platform premium shows up in the operating statements before any exit. If centralization takes 180bps off the expense ratio across twenty facilities and revenue management adds real dollars of revenue per occupied square foot, that's realized NOI. It gets capitalized at whatever cap rate the market gives you, and you don't need any compression assumption at all.

So the test I'd apply to that memo is simple. Strip the 75bps out, hold the exit cap flat to going-in, and see what the return looks like on the operating plan alone. If it still clears your hurdle, the compression is upside and you can ignore page 31. If the deal needs it, you're being asked to underwrite a market call dressed up as an operating thesis. Every portfolio memo I've said yes to in the last two years passed that test. Most of them didn't.