The Roundtable was titled "AI Roundtable: Meet the Yardi Virtuoso Team", a deliberate framing for a session situated within an Executive Briefing oriented toward consulting partners. The format brought the four people responsible for shaping and shipping Virtuoso into one conversation, making visible how the program operates: who owns what, what is shipping, what is gated, and where partner work is most valuable.

Yardi's strategic AI direction was publicly refined in February 2026 through a Yardi blog post co-authored by Brian Sutherland and Yardi president Akshai Rao. The published strategy turns on three architectural decisions:

•  AI is delivered through agents' specific tasks delegated to specialized AI workers, each configured to be an expert in its respective area, rather than a single monolithic AI assistant.

•  Real estate organizations are encouraged to think in terms of an 'AI Org Chart, ' the structured map of which agents will perform which functions, and how those agents will connect into upstream and downstream systems.

•  Agent creation and distribution operate through Virtuoso Composer (the no-code builder) and Virtuoso Marketplace (the agent distribution layer at virtuoso.ai), where Yardi, third-party consultants, and clients can all create and consume agents.

This strategic framing answers a central question for consulting partners working with Yardi clients: where does partner work fit? The published answer is that direct partners build agents in Composer, distribute through the Marketplace, and wrap implementation services around the agent lifecycle. Per Yardi's published strategy update, partners are not auxiliary to the program; they are constituent to it.

Governance was the highest-stakes topic in the panel sessions. Joe Consolo framed the architectural argument throughout the briefing: the dominant client concern about external AI vendors is not capability but access control.

Most AI vendors targeting Yardi-running organizations operate by ingesting Voyager exports into their own environment. That model breaks the Yardi security architecture. Property-level restrictions, role-based permissions, and tenant data segregation, all defined in Voyager, are absent from a flattened export. As Consolo emphasized in the Virtuoso panel session, the number-one client concern with third-party AI tools is team members circumventing security controls to access data they normally cannot access.

The Yardi-internal architectural commitment

Yardi's published Virtuoso architecture preserves the security model end-to-end. User permissions and credentials carry through into the AI interaction. A user who lacks visibility into a specific property in Voyager will not see that property's data in Virtuoso Support, agent-driven workflows, or Connectors. Yardi's Virtuoso platform documentation makes this a structural property of the platform rather than a configuration option.

Joe Consolo's adoption framework, presented across the briefing's panel sessions, divides the Yardi client base into three tiers based on AI readiness:

These clients are still figuring out where to apply AI. They have not yet selected a vendor or initiated an internal AI program. Conversations focus on strategy, framework selection, and the identification of the first one or two use cases worth resourcing. This is the largest tier by client count.

Tier 2 - Actively researching solutions

These clients are evaluating vendors. Per Consolo's framing, the first vendor consideration is often not Yardi; it is a third-party AI specialist that has approached them directly. The second or third vendor evaluated is typically Yardi. Consolo noted that this group is consistently surprised by the depth of Yardi's roadmap once they engage with it.

Tier 3 - Actively deploying

The minority tier. These clients have already begun building agents. Many have hired internal AI personnel. They are looking less for direction and more for execution velocity. Yardi's positioning for this tier is operational: integrate with what they have already built, accelerate where they are blocked, and provide the agent-deployment infrastructure that lets them scale.

The strategic implication for sequencing

Shivani Kumar's framing across the briefing made the resource-allocation reality explicit: AI excitement is high; resource allocation is materially lower; execution is lower still. Kumar reported working with five to seven clients weekly as Industry Principal, with the engagement scope revisited every couple of months. Most engagements involve scoping the first two or three use cases worth committing to, not building an enterprise-wide AI roadmap on day one. The pragmatic path for most operators starts narrow and compounds over time.

The briefing's combined sessions, including the Roundtable, made the program's pacing explicit. Yardi is managing rollout deliberately to maintain stability.

•  Virtuoso Support — in Voyager 8 and RentCafe CRM IQ; live with hundreds of clients and tens of thousands of users

•  Virtuoso Connectors — starting with Anthropic's Claude as the first LLM partner

•  Native AI capabilities embedded in Yardi products, including Maintenance IQ, Smart Lease (AI lease abstraction), and PayScan (AI-powered OCR)

Active beta with selective access

Virtuoso AI Agents and the Virtuoso Marketplace - launched at YASC in September 2025, with active deployment across early-adopter clients. Per Consolo's framing during the briefing, the broader rollout is being staged with a Q3 broader availability target. The throttle is intentional: ensuring stability and operational quality before broader exposure.

Roadmap and emerging

•  Composer's continued expansion to allow agent triggers connected to specific Voyager actions referenced in the panel as in-progress, not yet generally available

•  Additional Virtuoso Connectors beyond Anthropic's Claude as the LLM partner network expands

•  Continued expansion of Virtuoso Support across additional Yardi applications beyond Voyager 8 and CRM IQ

The combined message across the briefing's panel sessions, distilled across the four panelists' contributions and Yardi's published strategy, points to four practical conclusions for property management organizations evaluating where to apply AI:

• AI is platform infrastructure, not a feature. Yardi's positioning treats AI as a structural layer of the property management stack, parallel to accounting and reporting, with multi-year investment behind it. Operators building short-horizon AI strategies will find themselves out of step with the platform's direction.

• Governance is an architectural choice, not a procurement choice. The decision to use Yardi-native AI versus a third-party AI vendor is not a price comparison. It is a decision about whether the security model of the system of record carries through into AI workflows. For regulated jurisdictions, this is the controlling decision.

• Sequencing matters more than ambition. The pragmatic adoption path is narrow, compounding, and revisited quarterly. Per Kumar's framing, most operators benefit from picking two or three use cases, building Composer-driven agents around them, measuring outcomes, and expanding from there rather than committing to an enterprise-wide AI roadmap before any agent is in production.

• Partner work is a constituent of the program. Per Sutherland and Rao's published strategy, third-party consultants build agents in Composer and distribute them through the Marketplace alongside Yardi-built agents. Implementation partners are not adjacent to the AI program; they are participants in it.

The Roundtable, formally titled "AI Roundtable: Meet the Yardi Virtuoso Team," was held during the Yardi Executive Briefing in Santa Barbara during the week of May 4, 2026. The four panelists were Brian Sutherland (Vice President, Commercial), Shivani Kumar (Industry Principal), Joe Consolo (Industry Principal), and Aaron Cabelli (Senior Product Manager).

Walk into almost any real estate operator running Yardi Voyager, and you'll find the same picture: data scattered across Voyager, Salesforce, Procore, and Excel exports living on someone's OneDrive; documents in shared folders no one has opened in two years; and a leadership team asking why they don't have an “AI strategy” yet.

You cannot bolt a Copilot onto that. Or rather, you can, and you'll get hallucinations, broken citations, and a very expensive disappointment.

The ABC framing introduced by Nagesh Nagaraj in his Yardi Data Strategy session addresses this directly. Before AI does anything useful on Yardi, three layers must be in place:

•  A — AI-ready architecture and integration (how data leaves Voyager and reaches your warehouse, lake, or BI tool)

•  B — Business Intelligence (semantic models and the ontology that lets a model actually reason about your portfolio)

•  C — Content management (documents, leases, and contracts in one searchable, governed place)

Get ABC right, and artificial intelligence on Yardi starts to behave more like absolute intelligence answers grounded in your data, your documents, your portfolio. Skip ABC, and no model Virtuoso, Copilot, Claude, Gemini, or otherwise, can save you.

What it is: Yardi Data Connect is a secure, query-driven API that pipes Voyager data into Microsoft Power BI and the Fabric ecosystem. It aggregates Voyager data alongside third-party sources (Salesforce, Procore, Excel, finance systems) into a single semantic model.

Why it matters for AI: Once data lands in Power BI / Fabric, the entire Microsoft AI stack opens up Copilot, Power Automate, machine learning, and crucially, ontology. Modern AI doesn't reason well over raw tables; it reasons over ontologies relationship graphs that describe how properties relate to leases, leases to tenants, tenants to GL entries. Fabric can convert a tabular model into an ontology with a click. That ontology gives a Copilot the context to answer questions like “which anchor tenants in Ontario are within 90 days of expiry and below market rent?”

Practical strengths:

•Works with existing Microsoft Azure / Power BI / E5 licensing, with no new platform fees.

•Inherits both Yardi security (property-level, object-level) and Microsoft security (Entra, audit logs).

•Supports incremental, ad-hoc, and scheduled refreshes; you hold the keys.

•Comes with a starter pack of pre-built dashboards.

•Does not require a private cloud, a major reason it's the pragmatic starting point for most clients.

When to pick YDC: Microsoft-shop clients, query-driven analytics, multi-source aggregation (Yardi + non-Yardi), executive dashboards, and any client whose end goal involves Copilot or Fabric AI.

What it is: Yardi Replicate, powered by Qlik, performs real-time Change Data Capture (CDC) from Voyager into the data warehouse of your choice, Snowflake, AWS, BigQuery, Databricks, or Azure. Instead of nightly batch exports, only changed rows stream to your target. The first load can move billions of rows in a couple of hours; after that, updates are near-instant with negligible production impact.

Why it matters for AI: Many large operators have already invested in Snowflake or Databricks and built medallion-architecture lakehouses. They don't want to rebuild in Microsoft. Replicate gives them raw, table-level Voyager data inside their existing warehouse, where data science teams can run feature engineering, ML pipelines, and LLM-grounded retrieval.

Important constraints:

•  Private cloud only. Replicate is exclusive to Yardi private cloud clients because Qlik runs inside the Yardi-managed environment.

•  Raw data, no built-in security layer. Replicate the ships table-level data; security and governance are downstream on the client (or their consulting partner).

When to pick Replicate: Existing Snowflake / AWS / Databricks investment, large lakehouse architecture, real-time analytics needs, data science teams that want native control of the schema, and private-cloud Voyager clients.

Most operators don't have to choose forever. We routinely see hybrid architectures, YDC for the BI / Copilot layer, and Replicate for the data-science layer.

This is the part the market still under-appreciates. There is no clean line between BI and AI. Under the hood, a Power BI semantic model and an AI-ready ontology are the same artifact viewed differently. The relationships, calculated measures, and security boundaries you build for a dashboard are the exact context an LLM needs to answer questions about your portfolio without making things up.

That means every dashboard built today on YDC is double-duty: an operational deliverable and a grounding source for tomorrow's AI agents. Investing in a clean Power BI semantic model now is investing in your AI roadmap, even if “AI” isn't on this quarter's plan.

This is also where Nagesh's Token Improvement Plan matters, only half a joke. Sending every operational question through a frontier LLM is the equivalent of eating at a fancy restaurant three meals a day. Cached BI dashboards, mobile alerts, and pre-computed KPIs handle 80% of recurring questions at zero token cost. Reserve LLM-driven analysis for the genuinely novel questions.

What it is: YDMS replaces Yardi's proprietary document repository with Microsoft SharePoint Online as the storage backend, while preserving full Yardi-side context. Property codes, lease addresses, anchor-tenant flags, and account references all flow through as SharePoint metadata automatically. Yardi property-level and object-level security stamps onto SharePoint sites, libraries, and folders without manual configuration.

Why it matters for AI: This is where the often-quoted truth lands hard: AI is only as good as your documents. Leases, MSAs, board decks, audit packs, vendor contracts. If those documents live in five silos with no metadata, no AI agent can retrieve them reliably; garbage in, hallucinations out.

YDMS solves this by:

• Auto-tagging every document with Yardi metadata at ingestion (property, lease, GL account, vendor, lifecycle status)

• Auto-applying security so a user who can't see a property in Voyager can't see its documents in SharePoint either

• Eliminating the “final_v3_REAL_FINAL.docx” problem with version history and co-authoring

• Opening the door to Copilot, Power Automate, and SPFx custom apps that search across millions of documents in seconds, with citations back to the source file

The compliance angle is non-trivial. Every click in Microsoft 365 is logged. For operators in regulated jurisdictions, such as Canadian PIPEDA, EU GDPR, Australian Privacy Act, and UAE data residency, the audit trail is the difference between a clean compliance review and a six-month remediation project.

In the Virtuoso deep-dive session led by Aaron Cabelli (Senior Product Manager) and Joe Consolo (Industry Principal), Yardi laid out Virtuoso as a five-layer AI platform: Native AI Agents woven natively into the product, an Assistant for help and actions, Premium Agents for actions and automation, a Composer for build-and-automate workflows, and an Insights layer for ask-and-analyze. It's powerful, native to Voyager, and it's the right tool for many in-Voyager workflows.

But Virtuoso operates inside Yardi. The moment your AI use case crosses out of Voyager into your warehouse, your SharePoint repository, your Salesforce, your Procore, your investor portal, you need the ABC layer underneath. YDC, Replicate, and YDMS are the rails Virtuoso (and any other AI you bring) will eventually run on.

The same point came up in the AI Roundtable that closed the briefing featuring Brian Sutherland (VP), Shivani Kumar (Industry Principal), Joe Consolo, and Aaron Cabelli. The recurring theme across operator questions: AI wins in real estate aren't won at the model layer. They're won at the data, document, and governance layer underneath.

Virtuoso is the fancy restaurant. ABC is the kitchen, the supply chain, and the food-safety regime. You need both, and you definitely need the kitchen first.

This is the gap most real estate operators hit. They license YDC or Replicate, sometimes YDMS, and realize the products are foundations, not finished solutions. Someone has to:

•  Design the semantic model and ontology so it answers the questions leadership actually asks

•  Implement the medallion architecture downstream of Replicate so the lakehouse doesn't become a swamp

•  Configure SharePoint sites, libraries, retention policies, and metadata schemas across jurisdictions

•  Build the Power Automate flows, SPFx apps, and Copilot agents that turn the foundation into productivity

•  Govern the whole thing, security, compliance, audit, and AI usage policy

Assetsoft has been doing exactly this work since 2012. As a Yardi-specialist consulting firm with delivery teams across Canada, India, Sri Lanka, and the U.S., Assetsoft implements the ABC layer end-to-end for clients in Canada, the U.S., Australia, New Zealand, Singapore, the UAE, and APAC, then layers AI use cases on top.

In parallel, companies like KriyaGo — The Operating System for Real Estate sit above Yardi, MRI, Procore, ViewPoint, CMiC, Concur, and Zoho, with 100+ integrations, automating cross-platform workflows that pure Yardi consulting cannot reach. For operators with mixed ERP estates (common after acquisitions), KriyaGo plus the Yardi ABC stack is what an AI-ready operating model actually looks like.

If you're on Yardi and being asked for an AI strategy, here's the sequence that actually works:

1. Start with C. Deploy YDMS first. No AI roadmap survives a chaotic document estate, and this is the highest-leverage, lowest-risk move.

2. Layer in A. Choose YDC if your stack is Microsoft-centric, Replicate if you're on Snowflake / AWS / Databricks. Many operators eventually run both.

3. Build B intentionally. Treat dashboards as the substrate for Copilot and Virtuoso, not one-off deliverables.

4. Then layer AI Virtuoso for in-Voyager workflows, Copilot for Microsoft 365, custom agents (Claude, Gemini, ChatGPT-powered) for cross-system use cases, none of which covers.

ABC before AI. Get the foundation right, and the intelligence artificial or absolute follows.

No. YDC is a query-driven API for Microsoft Power BI and Fabric. Replicate is real-time, table-level Change Data Capture (powered by Qlik) into Snowflake, AWS, Azure, or GCP. YDC works on standard Voyager hosting; Replicate requires Yardi private cloud.

Virtuoso is Yardi's native AI platform inside Voyager, a five-layer stack covering Native AI Agents, Assistant, Premium Agents, Composer, and Insights. The ABC products (YDC, Replicate, YDMS) extend AI capability outside Voyager into your warehouse, BI tools, SharePoint, and Microsoft 365. They are complementary, not competing.

A typical engagement starts with a discovery sprint to map the client's data and document estate, recommends a YDC / Replicate / YDMS deployment plan, builds the semantic model and dashboards, configures the SharePoint architecture, and then layers AI use cases, Copilot agents, Power Automate flows, and custom integrations through KriyaGo on top. Engagements range from focused 6–8 week implementations to multi-quarter transformation programs.