NewWhen S*** Hits Fans: Hidden Risks in CRERead more

When S*** Hits FansHidden Risks in CRE

by Starboard Team8 min read
There is a pervasive fiction in commercial real estate: that a well-staffed deal team working through a comprehensive checklist will find every material risk before closing. This fiction persists due to survivorship bias. The plans that died tell a different story, and it is not a story about carelessness. It is a story about how the industry has structured risk discovery. Until now...

"Only when the tide goes out do you discover who's been swimming naked." — Warren Buffett

The traditional process has four properties, and each one is a way of losing money.

1. Sequential, not parallel. A deal-killer is not 10x less likely to surface in hour 50 as opposed to in hour 5, and by hour 50 the time and money are already wasted.

2. Reactive, not anticipatory. Diligence workflows are built around known categories of risk. Novel or hyperlocal risks sit outside the standard template, which is exactly why they are the ones that hurt.

3. Human-bandwidth-constrained. Even the best deal teams face a hard ceiling on how many data sources they can meaningfully interrogate inside a 30 day exclusivity window.

4. Optimism-biased. Once a team is inside exclusivity, the psychological and financial incentives point towards confirming the thesis, not challenging it.

Put together, they produce a systematic underproduction of risk assessment at the exact moment it matters most. Two cases below, both reconstructed from the public record, show what the checklist missed and what a search built around the business plan would have asked first.

Case one

Fire flow sinks a Miami warehouse

In 2022 a publicly traded REIT with more than $5bn in assets identified a well-located Class B warehouse in Miami-Dade County as a value-add acquisition. The thesis was simple: buy at a discount to replacement cost, raise clear heights from 32 to 36 feet, and reposition to capture logistics tenants paying premiums for modern high-bay space.

The underwriting penciled. Strong last-mile positioning, proximity to the Port of Miami, good highway access. The structural report confirmed the building could take the ceiling raise. The team moved quickly into exclusivity.

What they missed

Not the sprinklers. The ceiling raise meant a new ESFR system designed to the taller roof, which nobody disputed: ESFR is standard for high-bay, its design criteria come out of NFPA 13 as adopted by the Florida Fire Prevention Code, and every industrial team in the country budgets a fire pump alongside it, because municipal pressure on its own is almost never enough for ESFR anywhere. The pump was in the budget.

The pump was also beside the point. A fire pump raises pressure. It cannot create flow that the main does not have.

The ESFR design at the new roof height needed roughly 2,000 gpm at the riser plus a 250 gpm hose allowance. The hydrant test came back at 1,100. The main was an 8-inch line laid in 1971, undersized for what the block had become and already on the water department's replacement list.

That left two ways to keep the plan alive. A storage tank and pump house would have solved the flow problem for about $750,000, but needed 4,000 square feet of truck court the site could not give up without losing six trailer stalls. Upsizing the main meant $1.8m of unbudgeted cost and an 18-month coordination window with the utility, which the financing structure could not absorb.

The timeline is the uncomfortable part. The price was agreed in month two, on the assumption that the raise would work. The flow test was ordered in month three, once the sprinkler design was far enough along to need it, and came back in month four, by which point the REIT had closed on the building. The next five months went on tank layouts, WASD's timetable for the main, and a lender that would not extend the redevelopment facility to wait for it. In month nine the redevelopment was shelved.

The REIT still owns the warehouse. It paid a 36-foot price for a 32-foot building, and on top of that overpayment it wrote off roughly $400,000 of redevelopment spend: fire protection engineering, structural design, and permitting for a project that will not happen.

Here is the part worth sitting with. The public record never held the number that killed the redevelopment. Available fire flow comes from a hydrant test you have to request, and the utility's letter of availability is a per-project document that confers no vested rights on anybody. What the public record did hold was every reason to order that test in week one: the main's age and diameter, the county's own capital programme flagging the block for replacement, and adjacent-property permits where prior tenants had hit the same wall. Three sources, none of them secret, none of them on the checklist. Ordered in week one, the test would have come back before the price was agreed, and the $400,000 would never have been spent.

Case two

A Georgia site with nowhere to send the sewage

A regional multifamily developer with a strong Southeast track record identified a parcel in a fast-growing suburban Atlanta corridor as the site for a 100+ unit garden-style community. The land basis was attractive and the market fundamentals were strong: comparable properties in the submarket were posting rent growth well above both the national average and peer markets. The developer secured an option and began working through entitlements. The local planning commission was supportive. Groundbreaking looked twelve months out.

What they missed

Georgia's suburban growth corridors have been among the fastest-developing regions in the country for the better part of a decade, and in several of them, wastewater treatment capacity has not kept pace with residential approvals. The relevant county utility authority runs its own capacity allocation programme, and that programme is not integrated with the planning department's entitlement process. Planning can therefore approve a project the utility authority has no capacity to serve.

Four weeks in, with construction financing already being lined up, the developer learned this from a different broker who happened to know someone at the utility authority: no additional sewer capacity would be available in the service district for at least 48 months, pending a treatment plant expansion that was itself subject to permitting delays.

None of the alternatives worked. A private package treatment plant meant $2.2m of additional capital cost and permanent operational complexity. The other two options were a multi-year hold on an optioned land position, or a negotiated exit at a loss. The developer exited, absorbing a $600,000 write-off across option payments, predevelopment costs and consultant fees.

Every treatment plant's permitted capacity is written into its NPDES permit, and its monthly flows go into discharge monitoring reports that the EPA publishes through its ECHO database. Divide one by the other and you have utilisation, plant by plant. The water authority's own master plan and board minutes explained the rest. Any of those, or a single conversation with a local civil engineer, would have surfaced the constraint before the option was signed.

What agentic orchestration does differently

Neither team was careless. Both ran the process the industry runs: a data room, a structural or civil consultant, a checklist built from the last hundred deals. Most AI sold into that process is a reading accelerant, and reading faster would not have helped, because in both cases the failure was not slow reading. It was that the decisive question arrived after the capital had been committed.

What Starboard adds is the order of operations. A coordinated set of specialised agents, each owning a risk domain, runs in parallel from day one across the public record a team would otherwise reach in sequence, if at all. They start from the business plan rather than the checklist: tell the system you intend to raise clear heights to 36 feet, and available fire flow becomes a question it asks in week one, before the price is agreed, not in month three once the sprinkler design needs the number. A good team would have asked it eventually. The point is when.

Sourcing the evidence
Today: Reads the data room and the consultant reports, plus what the team thinks to pull
Starboard: Pulls the public record against the business plan before the data room arrives
Sequencing
Today: Specialist reports land one after another across the diligence period
Starboard: Every domain runs in parallel from day one
Where the questions come from
Today: A checklist built from the last hundred deals
Starboard: This deal's business plan, which is where the novel risk lives
The ceiling
Today: The hours and specialists on the team
Starboard: The breadth of sources the agents can reach
Synthesis
Today: Cross-domain interactions depend on someone noticing
Starboard: Agents flag where two domains' findings collide
After closing
Today: Periodic review, driven by the asset manager's calendar
Starboard: Continuous, with alerts on material changes
Fig. 1Six points in the diligence process and what an orchestration layer changes at each. The left column is how a competent team already works; the right is what moves earlier, wider, or past closing when the search is delegated to a coordinated set of agents.

The compounding value of breadth

The cases above are point-in-time discovery, which is the easiest version of the argument to make but also the least interesting. The orchestration layer compounds in three ways that matter more.

Cross-domain risk synthesis. Individual risk factors interact. A property with marginal flood risk, aging utility infrastructure and a municipality under fiscal stress is a materially different asset from one carrying any of those alone. Human deal teams rarely have the bandwidth to model the interactions explicitly. Starboard's agents share findings across domains and produce a synthesised risk narrative that reflects the interaction effects, rather than just an itemised list of separate concerns.

Portfolio-level pattern recognition. Across a portfolio, the orchestration layer surfaces systemic exposures that asset-by-asset review cannot see: a concentration in municipalities with deteriorating infrastructure credit, say, or an overweight in markets facing a contracting insurance market. In Starboard's Sandbox a firm can sensitise its whole portfolio against underwritings it has actually done, and catch the risks before the risks catch it.

Monitoring that does not stop at closing. Zoning ordinances change. Infrastructure constraints worsen. Regulatory environments shift. Agents running continuously alert asset managers to material changes in the risk environment of existing holdings, which turns diligence from a one-time exercise into a permanent capability.

Where this leaves the industry

The data needed to make better investment decisions has never been more available, and the gap between the teams who can systematically reach and synthesise it and the teams who cannot will continue to widen. The barrier is no longer cost, because most of what would have flagged those two deals was free. The barriers are structural: human bandwidth, domain fragmentation, and workflow design. Starboard's agentic orchestration addresses all three.

For institutional investors the implication is concrete. The checks that killed these two deals were not expensive. They were late. An orchestration layer brings them forward to the week the deal arrives, before the price is agreed, before the option is signed, before the next tranche of capital is committed, and it does so across more domains than a deal team can hold in its head at once. That is the benefit: the same questions, asked while the answer can still change the decision.

The deals that define the next fund's performance will not be won by the teams that work harder in diligence. They will be won by the teams that see more, sooner, and act on what they find.

If you have a deal with an esoteric risk in it, we would love to plug it into Starboard with you and see how quickly Starboard finds it.

Header photographs: a distribution warehouse loading dock in Miami, Florida, by Ryan Parker on Unsplash, and a garden-style apartment community seen from the air, by Chris Grant on Unsplash. Both are toned to match; neither depicts a property named in this article.

Bring us a live deal and a business plan

We will run the orchestration layer against it while you watch, and show you what it retrieves that was never on the checklist.

Request a demo