Published 2026-05-01 | Conversion + Trust crossover | 4-vendor 60-day HITL convergence read
Three Architectures, One Missing Layer — What 60 Days of CRE-AI Platform Launches Tell You About Where to Put Your Pilot
BLUF: Inside 60 days (Mar 2026 → late Apr 2026), four named CRE intelligence platforms — Cherre, VTS Asset Intelligence, Altus ARGUS Assist, and Yardi Virtuoso Spring 2026 — converged on the same architectural shape: a horizontal CRE-data platform with a human-in-the-loop (HITL) AI overlay that ranks deals, abstracts leases, and flags portfolio anomalies. That is a real category and we expect it to consolidate. But every one of those four products skips the same operational layer — BMS-integrated AI HVAC, jurisdictional code, embodied carbon during construction, IPMVP-anchored M&V, hybrid-occupancy with privacy broker. If you are scoping a 2026 pilot, the convergence read is: stop choosing between the four — buy one for deal-tier and a vertical operational layer for the rest. Trying to make one platform cover both is how 92% of pilots stay pilots.
The 60-Day Convergence
Four launches, four different go-to-market motions, one identical architectural pattern.
| Vendor | Launch month | Headline product | HITL pattern | What it answers |
|---|---|---|---|---|
| Cherre | Mar 2026 | Composite Intelligence (CRE data fabric + AI ranking layer) | Analyst confirms top-N anomalies; agent re-ranks portfolio | "Where in my portfolio do I have data drift / risk?" |
| VTS | Mar 2026 | VTS Asset Intelligence | Leasing agent reviews AI-flagged tenant retention risks; agent updates renewal probability | "Which tenants are at risk of non-renewal?" |
| Altus Group | Mar 2026 | ARGUS Assist (in-app AI tier on the ARGUS valuation platform) | Valuation analyst reviews AI-suggested DCF inputs; agent re-runs the model | "What is my deal-tier IRR / NAV / CapEx forecast?" |
| Yardi | Spring 2026 | Virtuoso (NLP layer over Yardi Voyager) | Property manager confirms AI-summarized lease abstracts; agent files in DMS | "What is in my lease portfolio, abstracted?" |
Strip away the marketing surfaces and the architecture is the same: pull data into a horizontal CRE platform; apply an LLM-anchored ranking / abstraction / flagging step; route the top-N to a human; learn from the human's accept/reject; re-rank. This is a real, valuable, and durable architecture. We expect it to consolidate to 2-3 winners by 2027. It also does not solve the operational layer.
The Missing Layer — In Plain Language
The four platforms above answer questions about deals, leases, valuations, and portfolio risk. They do not answer questions about how the buildings actually run. Specifically, none of the four ships any of the following:
- BMS-integrated AI HVAC with IPMVP-anchored verification. Reading sequences off Tridium Niagara / Honeywell WEBs / Distech / Schneider. Tuning chiller-plant set-points against ASHRAE 90.1-2022 and the local jurisdictional code. Closing the IPMVP Option C / D loop on a 12- or 24-month savings claim. None of the four does this.
- Jurisdictional code engine. SG CORENET-X / NYC DOB / HK BD / JP BSL / AU NCC / UK Building Regs / EU EPBD / IBC / IECC / NEC / NFPA / ASHRAE — each with version-aware corpus ingest and code-triggered upgrade detection. None of the four covers this; one (ARGUS) covers the appraisal side of US tax code only.
- Embodied carbon during construction. Real-time A1-A3 ingest with procurement-substitution alerts. (Covered separately in the embodied-carbon wedge post.) None of the four.
- Hybrid-occupancy with privacy broker. Sensor + badge + reservation fusion under differential privacy noise, k-anonymity, GDPR Art. 9 / BIPA / Colorado biometric / SG PDPA / EU AI Act consent-on-file. None of the four.
- Claims early warning + RFI/CO automation on the construction execution side. Pattern detection across RFIs + COs + daily reports + meeting minutes that predicts construction claims 30-60 days before formal filing. None of the four — this is purely AISB-CRE-CON territory.
This is not a small gap. It is roughly 60-70% of the operational risk and value-creation surface of a CRE portfolio.
Why Did Four Independent Vendors All Skip the Same Layer?
Three reasons, in declining importance:
- Data acquisition cost. Building-operational data lives in BMS systems, badge systems, reservation systems, IoT sensors, FDD platforms — each with its own protocol, its own commissioning state, its own owner. Building a credible operational layer requires a 12-24 month data-engineering investment per category. The four platforms above optimized for fast time-to-revenue on data they could buy commercially (transaction comps, public records, NOI data, lease structures).
- Jurisdictional code is hard. Maintaining a versioned, queryable code corpus across 9+ jurisdictions and 7+ standards bodies (ASHRAE, ICC, NFPA, BCA, USGBC, BREEAM, NABERS) is a continuous engineering effort, not a one-time ingest. Most horizontal platforms cannot justify it on their unit economics.
- The buyer is different. Deal-tier and asset-management buyers (Investment Ops, Asset Management, Acquisitions) procure differently from operational buyers (Head of Workplace, Director of Engineering, Head of Sustainability, GC Project Executive). Building a sales motion across both is structurally hard. The four vendors above all chose the deal-tier buyer.
None of these are bad reasons. They are good reasons that explain why the operational layer is open. We have spent the last 18 months filling exactly that gap.
Where the Operational Layer Actually Is
The vertical operational layer is what AISB ships. We have 9 squads, each anchored to a domain:
| Squad | Domain | Headline product | Deal-tier overlap with the four? |
|---|---|---|---|
| CRE-AD (Architecture & Design) | Concept → Construction Documents | Retrofit Compliance Scan + jurisdictional code intelligence | None — no overlap with the four |
| CRE-PM (Project Management) | Owner-side project execution | EVM Theater detection (CPI/SPI vs PPC divergence) | None |
| CRE-CON (Construction Execution) | Builder-side execution | Claims Early Warning + Embodied Carbon Tracker | None |
| CRE-SS (Soft Service) | FM / Workplace Services | KPI Theater detection (vendor SLA vs occupant NPS divergence) | None |
| CRE-SP (Space Planning) | Hybrid Calibrator | Policy → Headcount → Demand Curve | Adjacent — VTS does deal-tier leasing analytics, not hybrid utilization |
| CRE-TS (Technical Service) | MEP / BMS / IoT / Energy M&V | AI-HVAC + IPMVP Option C/D verification | None |
| CRE-EN (Energy + Dynamic Occupancy) | Real-time fused occupancy under privacy broker | Privacy-first occupancy product | None |
| CRE-KE (Knowledge Engine) | Daily pre-training of all 7 production squads | 5-signal claim classifier; per-squad isolated brains | None — a fleet-internal layer |
| DIS (Deal Intelligence Squad) | Counterparty + sourcing | Bayesian deal-precedent library | Direct overlap — DIS competes adjacent to Dealpath / Northspyre |
Eight of nine squads have zero overlap with Cherre / VTS / Altus / Yardi. One — DIS — does compete in deal-tier territory, and we are explicit about that scoping.
How to Read the Convergence in Your RFP
Three concrete revisions to a 2026 CRE-AI RFP that will save the procurement team a quarter of churn:
- Drop the requirement that one vendor cover both deal-tier and operational. No vendor in the market does this credibly today, and the four vendors above are all explicit that they do not. Forcing this requirement will yield a winner that ships 60% of what the RFP asked for. Two contracts is fine; that is how the data center stack already works.
- Specify IPMVP options on operational claims. If a vendor proposes to track or improve any operational metric (energy, occupancy, carbon, equipment health), the RFP should require an IPMVP Option (A / B / C / D) and a measurement boundary. Vendors that cannot answer this question are pre-pilot.
- Specify the human-in-the-loop pattern explicitly. Borrow the architecture from the four — every AI-flagged action gets a human reviewer, every reviewer accept/reject feeds back. The horizontal vendors have already done the framing work for you. AISB's squad commanders use the same pattern.
What AISB Will Actually Do With You
If you are evaluating 2026 platforms and want to test the "operational layer" claim, the fastest path is a 60-90 minute scoping conversation with the AISB agent fleet:
- Describe your portfolio shape (size, geography, asset class, age, BMS make/model).
- Describe the in-flight RFP or pilot question.
- The agents will produce a vertical-operational-layer scope memo, with citations, that explicitly maps which questions Cherre / VTS / ARGUS / Yardi answer well and which questions belong to AISB.
- If the answer is "buy one of those four — AISB does not add value here," that is the answer. We do not pitch where there is no wedge.
Start the scoping conversation here. The agents will respond inside the same browser session and produce the scope memo as a PDF you can take into your committee.
Cross-Reads
- Why 92% of CRE Teams Pilot AI and Only 5% Ship It — the deployment-gap math that explains the convergence.
- The Embodied Carbon Wedge No One Else Ships — one specific operational layer the four miss.
- The IPMVP Verification Framework — the language operational claims must speak.
- AISB for Enterprise — Three pilot tiers.