One vehicle per asset, ring-fenced, fees and carry on other people's capital. Plus the own-goals (master-lease mismatch, starved fees) that sink platforms.
The vehicle you wrap around a real asset decides whether one bad quarter stays contained or takes down the platform. This is the version that holds.
Disclosure: a venture in our portfolio uses structures of this kind. We name our stake. The structural points here are general and illustrative, not legal, tax, or investment advice.
Real-asset platforms rarely die of bad operations. They die of bad structure. The building was fine. The vehicle around it wasn't. So before anyone gets excited about the asset, the more useful question is how it's wrapped, because the wrapper is what fails first.
Below is the structure that holds, then the specific ways a careless one breaks.
Start with the unit of the structure. A real-asset platform done right runs one special purpose vehicle per asset. A separate entity per property. Ring-fenced.
The reason is containment. If every property sits in its own vehicle, a problem in one (a soft market, a bad tenant, a development delay) stays in that one. It can't reach across and pull down the others. The blast radius is a single asset, by design.
One vehicle per asset. Ring-fenced. A problem in one can't reach the others. That's the whole point of the structure.
Put several assets in a shared entity to save on setup, and you've quietly wired them together. Now one default is a portfolio event. The "efficient" structure is the fragile one. The slightly more expensive structure, an entity per asset, is what lets the platform survive a bad outcome on any single property.
The second design choice is whose balance sheet carries the asset. The durable answer, for a platform, is mostly: not yours.
The stronger model earns fees and carry on other people's capital and other people's assets rather than warehousing property on the platform's own books. The platform structures the vehicle, brings the deal, operates the asset, and takes economics for doing so. The capital and the asset risk sit largely with the investors in the vehicle. That keeps the platform capital-light and lets it scale across many assets instead of being capped by its own balance sheet.
Warehousing does the opposite. Buy and hold property on your own books at platform scale and you need balance-sheet depth most ventures don't have, and every asset you add consumes capital you could have used to grow. Fine for a REIT with a permanent capital base. Wrong shape for a young platform.
Now the failure modes, stated plainly, because they're specific and they recur.
The master-lease mismatch. Sign fixed-rent master leases on property and then re-let that space at variable, market-driven rates, and you've built an arbitrage that works right up until demand softens. When it softens, the fixed rent is still due and the variable income isn't there. This one mismatch has sunk some of the most cautionary names in the space, the ones that filed at high occupancy. They mostly carried exactly this structure. Avoid it.
Cross-collateralization. Pledge the vehicles against each other to raise cheaper debt and you've undone the ring-fence you paid to build. One default becomes a cascade. The whole reason for one-vehicle-per-asset is gone the moment the vehicles guarantee each other.
Starved intercompany economics. A platform that builds and operates the asset layer needs to be paid fairly by it: management, technology, and service fees set at real, defensible rates. Set those intercompany fees too low to flatter the asset returns and you starve the operating company that's doing the work. The asset looks great on paper while the platform that runs it slowly runs out of room.
Liquidity promises the structure can't keep. Promise investors easy exit that the underlying property can't actually deliver, and you've written a check the asset can't cash. Liquidity has to match the asset, not the pitch.
None of this is glamorous. It's plumbing. But plumbing is precisely where real-asset platforms succeed or fail, and a studio that finances and builds the layer above the asset has every reason to insist the layer below it is conservative by construction. The fast-moving platform on top is only safe because the asset layer underneath is boring on purpose: one vehicle per asset, fees and carry over warehousing, and a hard refusal of the four own-goals above.
Get the vehicle right and the asset can have a bad quarter without it becoming a bad company. Get it wrong and no amount of occupancy saves you.
Read next: The Layer-1 model: financing the tech under a real asset
Nothing here is an offer to sell a security or investment advice. Structural descriptions are general and illustrative; they are not legal, tax, or investment advice, and they are not representations about any specific company's structure or performance. Failure modes are described generically and are not characterizations of any named company.
Field notes on venture building, AI, and capital. No spam, unsubscribe anytime.
By subscribing you agree to receive AOS Insights e-mails. We use your address only for this newsletter - see our Privacy Policy.