Real estate organizations generate enormous amounts of information across properties, tenants, leases, vendors, accounting, maintenance, banking, construction, and portfolio operations.

Historically, organizations could sometimes work around data inconsistencies through spreadsheets, manual reviews, institutional knowledge, or reporting adjustments.

AI changes the equation.

When organizations begin asking intelligent systems to interpret data, identify anomalies, recommend actions, or participate in operational workflows, data quality becomes significantly more important.

An AI system can process millions of records but processing poor-quality data faster does not necessarily create better decisions.

Before organizations invest heavily in AI, they should therefore ask:

Can we trust our data?

Many real estate companies have expanded their technology environments over years or even decades.

A typical enterprise environment may include:

Yardi or MRI + CRM + banking platforms + construction software + document management + Power BI + procurement tools + spreadsheets + custom applications.

Each system may contain a different part of the organization's information.

Over time, this can create challenges such as:

• Duplicate records
• Inconsistent naming conventions
• Missing information
• Different property identifiers across systems
• Outdated vendor records
• Multiple versions of reports
• Manual spreadsheet transformations
• Unclear systems of record
• Legacy integrations
• Data isolated within individual departments

These issues already affect reporting and operational efficiency. In an AI-driven environment, their impact can become even greater.

The traditional technology principle of “garbage in, garbage out” becomes especially relevant with artificial intelligence.

Imagine an AI system analyzing lease information across a large portfolio.

If renewal dates are missing, tenant names are inconsistent, lease amendments are stored separately, and critical information exists only in unstructured documents, the system may be working with an incomplete picture.

Or consider an AI-enabled financial workflow designed to identify unusual transactions.

If account mappings are inconsistent between properties or historical transactions contain classification errors, AI may generate unnecessary exceptions or unreliable recommendations.

The sophistication of the AI model cannot compensate for every weakness in the underlying information.

AI-ready data does not mean every database has to be perfect. Instead, organizations should focus on several fundamental characteristics.

1. Accuracy

Information should correctly represent the property, tenant, lease, vendor, financial transaction, or operational event it describes.

2. Consistency

The same information should follow consistent structures and definitions across systems.

For example, property identifiers should not change depending on whether the information comes from the property management system, reporting environment, CRM, or another application.

3. Completeness

Critical information required for reporting, automation, and decision-making should not routinely be missing.

4. Accessibility

Data must be available to authorized applications and users when required.

Information trapped inside isolated spreadsheets or legacy systems can be difficult to use effectively for enterprise AI.

5. Governance

Organizations should clearly understand:

Who owns the data?
Who can modify it?
Which system is authoritative?
How long should information be retained?
Who should have access?

These questions become increasingly important as AI systems interact with enterprise information.

For many property owners, operators, managers, and investment organizations, platforms such as Yardi Voyager and MRI Software serve as critical systems of record.

They may contain information supporting accounting, leasing, property management, maintenance, budgeting, and other essential processes.

That makes the configuration and quality of these environments particularly important.

Before connecting AI or advanced automation to a property management system, organizations should understand:

• How properties and entities are structured
• How charts of accounts are configured
• How tenant and lease information is maintained
• How vendors are managed
• How historical information has been migrated
• How custom fields are being used
• Which integrations create or update records
• Which processes still depend on spreadsheets

Configuration decisions made years ago can eventually become data problems affecting reporting, integration, automation, and AI initiatives today.

Data migration is another area where AI readiness can be won or lost.

When organizations migrate from legacy systems or consolidate portfolios, the objective should not simply be to move every available record into the new platform.

A successful migration should consider:

What data should move?
What should be cleaned?
What should be standardized?
What should be archived?
What information is duplicated?
How should historical records be mapped?

Migrating poor-quality information into a modern platform simply relocates the problem.

Instead, migration can become an opportunity to improve the organization's overall data foundation.

Integrations are essential in modern PropTech environments. However, poorly designed integrations can also introduce inconsistencies.

Consider an environment where information moves between:

Property Management System → CRM → Banking → Reporting → Construction Platform → Data Warehouse

If every integration applies different transformation rules or uses different identifiers, inconsistencies can multiply.

This is why organizations should establish clear systems of record.

For each major category of information, there should be clarity around which platform owns the authoritative record.

For example:

Property data → Property management system
Customer interactions → CRM
Financial transactions → ERP/property accounting system
Analytics → Data platform/BI environment

The exact architecture will vary by organization, but the principle remains the same:

Every critical data element needs an authoritative source.

Excel remains an important business tool, and it is unlikely to disappear from real estate operations.

The problem occurs when spreadsheets become unofficial databases.

Organizations may have critical processes where teams:

Export → Clean → Reformat → Combine → Calculate → Email → Re-upload

Every manual step introduces another opportunity for inconsistency.

It also makes automation and AI harder because the information exists outside governed enterprise workflows.

Organizations preparing for AI should identify spreadsheet-heavy processes and determine whether some activities can be replaced by:

• System integrations
• Automated workflows
• APIs
• Centralized reporting
• Data platforms
• Business intelligence tools

The objective is not to eliminate Excel. It is to reduce unnecessary dependency on manual data movement.

Organizations sometimes respond to reporting challenges by creating additional reports.

But when different teams produce different numbers for the same metric, the underlying problem may not be the reporting tool.

It may be the data architecture.

For example:

Finance reports one occupancy number.
Operations reports another.
Asset management has a third spreadsheet.

Before introducing AI-generated insights, organizations need confidence that fundamental metrics are being calculated from trusted information.

A strong reporting environment should therefore establish:

Common definitions + Governed data + Reliable integrations + Consistent calculations.

Once this foundation exists, AI can add another layer of intelligence rather than another layer of confusion.

Many real estate organizations have already invested in platforms such as Power BI and other analytics tools.

These environments provide an important bridge toward AI.

Traditional business intelligence primarily answers:

“What happened?”

Advanced analytics can help answer:

“Why did it happen?”

Predictive models may address:

“What might happen next?”

And emerging AI systems increasingly aim to help answer:

“What should we do about it?”

The further organizations move along this progression, the more important reliable data becomes.

AI should therefore be viewed as part of a broader data and analytics strategy, not as a standalone technology project.

Real estate organizations do not need to rebuild their entire technology environment before experimenting with AI.

A structured approach can help prioritize the areas that matter most.

Step 1: Identify Critical Data

Determine which information supports the organization's most important financial, operational, leasing, and reporting processes.

Step 2: Map the Data Landscape

Understand where information originates, where it moves, and where it is ultimately consumed.

Step 3: Identify Data Quality Issues

Look for duplication, missing records, inconsistent identifiers, outdated information, and manual transformations.

Step 4: Establish Systems of Record

Clearly define which application owns each major category of information.

Step 5: Modernize Integrations

Reduce unnecessary manual exports and fragile point-to-point connections where practical.

Step 6: Improve Governance

Define ownership, access, security, retention, and data-quality responsibilities.

Step 7: Connect AI to Trusted Data

Once the foundation is reliable, organizations can introduce AI into carefully selected workflows where it can create measurable value.

Once the data foundation improves, organizations can explore more advanced capabilities with greater confidence.

Intelligent Lease Analysis

AI can help extract, classify, summarize, and analyze lease information, allowing teams to work with large volumes of documents more efficiently.

Financial Exception Detection

AI and analytics can help identify unusual transactions or patterns and surface them for human review.

Automated Bank Reconciliation

Automation and intelligent matching can reduce repetitive reconciliation work while directing attention toward exceptions that require review.

Predictive Maintenance

Historical maintenance and equipment information can support more proactive identification of potential issues.

Portfolio Intelligence

AI can help users explore large datasets through natural-language queries and automated analysis.

Intelligent Reporting

Executives and property teams can potentially move from static dashboards toward more conversational and proactive insights.

The common requirement behind all of these capabilities is trustworthy information.

As AI tools become more widely available, simply having access to artificial intelligence will become less of a differentiator.

The advantage will increasingly come from an organization's ability to connect AI to its own trusted operational data and workflows.

Two real estate companies may use similar AI technologies.

But the organization with cleaner data, better integrations, stronger governance, and more standardized processes may be positioned to generate significantly more value from those tools.

That makes data modernization more than an IT initiative.

It becomes a business capability.

Preparing real estate data for AI requires an understanding of both technology and the business processes behind the information.

Assetsoft works with real estate organizations across Yardi, MRI Software, data migration, system integration, reporting, automation, and technology optimization.

Assetsoft can support organizations with:

• Yardi consulting and optimization
• MRI Software consulting
• Data migration
• Data quality assessment
• System integration
• API strategy
• Reporting and analytics
• Workflow automation
• Process optimization
• AI-readiness assessment

Rather than starting with the question,“Which AI tool should we buy?”, organizations can begin with a more fundamental question:

“Is our data ready for AI?”

AI can transform real estate operations, but its value depends on the quality of the data behind it. By improving data quality, integrations, governance, and Yardi or MRI environments today, real estate organizations can build a stronger foundation for intelligent automation and AI-driven operations tomorrow.

The first stage of enterprise AI adoption focused largely on experimentation.

Organizations tested AI for activities such as:

• Lease and document abstraction
• Tenant and resident communications
• Invoice processing
• Reporting and analytics
• Data extraction
• Knowledge search
• Maintenance support
• Workflow automation

The next stage is considerably more complex.

Instead of simply generating an answer or summarizing information, emerging AI systems can potentially participate in multi-step business processes, collecting information, identifying exceptions, recommending actions, triggering workflows, and interacting with enterprise applications.

This evolution is often described as agentic AI.

For property management and real estate organizations, that could eventually mean AI supporting workflows across accounting, leasing, maintenance, procurement, reporting, and portfolio operations.

But there is an important catch:

AI can only operate effectively when the systems underneath it are ready.

It can be tempting to treat AI as another application that can simply be added to the technology environment.

In practice, enterprise AI depends heavily on the quality of the infrastructure surrounding it.

Consider a property management organization operating:

Yardi or MRI + CRM + banking platforms + document management + Power BI + construction systems + spreadsheets + custom applications.

If those systems contain inconsistent data, disconnected processes, outdated integrations, and large amounts of manual work, adding AI does not automatically solve the problem.

It may simply add another layer of complexity.

Before organizations scale AI, they should therefore evaluate several foundational areas.

AI systems depend on data.

For real estate organizations, that data may include:

• Properties
• Units
• Tenants and residents
• Leases
• Vendors
• General ledger information
• Work orders
• Invoices
• Bank transactions
• Budgets
• Contracts
• Portfolio performance

If information is duplicated, inconsistent, incomplete, or stored across disconnected systems, AI-generated insights and automated actions can become less reliable.

Organizations preparing for AI should review their data quality, ownership, structure, governance, and accessibility.

This may involve cleaning historical data, standardizing records, improving data migration processes, and establishing clear governance around how information moves between platforms.

For Yardi and MRI environments in particular, the quality of the underlying configuration and data structure can have a major impact on downstream automation and analytics.

Modern real estate technology environments rarely consist of one platform.

Property management systems often need to communicate with banking platforms, CRMs, construction systems, business intelligence tools, procurement applications, document repositories, and specialized PropTech solutions.

AI adds another participant to this ecosystem.

That makes integration architecture increasingly important.

Organizations should understand:

- Where does the data originate?
- Which system is the system of record?
- How does information move between applications?
- Which integrations depend on manual exports?
- Which processes rely on spreadsheets?
- Where are APIs available?

A fragmented integration environment can make AI implementation significantly harder.

A well-designed integration strategy, on the other hand, creates a reliable foundation through which applications, automation platforms, and AI services can securely exchange information.

APIs have already become fundamental to modern PropTech environments.

Their importance increases further as AI becomes embedded into operational workflows.

For example, imagine an AI-enabled process that identifies an accounting exception.

Recognizing the exception is only one part of the workflow.

The system may also need to:

Retrieve data → Analyze transaction → Compare records → Recommend action → Obtain approval → Update enterprise system → Record result

That requires reliable connections between multiple systems.

Real estate organizations should therefore evaluate whether their existing applications and custom integrations can support this level of connectivity.

This is where an API-led integration strategy can help reduce dependency on manual exports and fragile point-to-point connections.

Not every business problem requires artificial intelligence.

In many organizations, significant efficiency gains can still come from traditional workflow automation.

For example:

Invoice received → Validate → Match → Approve → Post

If that workflow is largely manual today, introducing AI without first understanding the underlying process may simply automate an inefficient workflow.

A better approach is to identify:

• Repetitive activities
• Manual handoffs
• Approval bottlenecks
• Duplicate data entry
• Spreadsheet dependencies
• Exception-heavy processes

Organizations can then determine which steps require conventional automation and which genuinely benefit from AI.

This creates a more practical path toward intelligent operations.

As AI becomes capable of supporting more complex workflows, organizations also need to determine where human approval remains necessary.

This is particularly important in financial and operational environments.

Consider bank reconciliation.

An intelligent system might be able to:

Import transactions → Identify potential matches → Detect exceptions → Recommend resolutions

But organizations may still require a finance professional to approve specific exceptions before anything is posted.

The objective should therefore not always be 100% autonomous automation.

In many situations, a more appropriate model is:

AI identifies → AI recommends → Human reviews → System executes

This approach allows organizations to gain efficiency while maintaining appropriate controls.

Real estate platforms contain sensitive financial, tenant, vendor, lease, and operational information.

Organizations therefore need clear rules governing how AI can access and use that information.

Important questions include:

• Which data can AI access?
• Which applications can AI interact with?
• What actions can AI perform?
• Which actions require human approval?
• How are AI activities logged?
• How are permissions managed?
• How are exceptions reviewed?

AI governance should be designed alongside the technology architecture rather than introduced after deployment.

For organizations running platforms such as Yardi Voyager or MRI Software, AI readiness should begin with the existing enterprise environment.

That means reviewing areas such as:

System Configuration → Data Quality → Integrations → Reporting → Automation → Security → Governance

Organizations do not necessarily need to replace their core property management systems to become AI-ready.

In many cases, the bigger opportunity is to modernize the architecture around those platforms.

This may include improving integrations, eliminating unnecessary manual processes, cleaning data, strengthening reporting environments, and creating more reliable connections between the property management system and the broader technology ecosystem.

Once the underlying technology environment is prepared, organizations can begin identifying areas where AI can create practical value.

Property Accounting

AI and automation can support transaction matching, financial exception detection, invoice processing, reconciliation, and variance analysis.

Lease Administration

Document intelligence can help extract, classify, summarize, and analyze information from leases and related documents.

Property Operations

AI-assisted workflows can help teams organize maintenance requests, identify recurring issues, classify work orders, and prioritize operational information.

Reporting and Analytics

AI can complement traditional business intelligence by helping users explore portfolio information, summarize trends, and identify areas requiring further investigation.

Data Management

Intelligent tools can help identify duplicates, classify information, detect anomalies, and improve the way organizations work with large volumes of property data.

The goal should not be to introduce AI everywhere.

Organizations should prioritize use cases where AI can solve a measurable business problem.

Instead of starting with an AI product, organizations can begin with a structured readiness assessment.

Step 1: Map the Current Technology Environment

Document the systems supporting property management, accounting, leasing, construction, CRM, reporting, banking, and other critical operations.

Step 2: Identify High-Value Workflows

Look for processes involving high manual effort, repetitive tasks, large data volumes, or frequent exceptions.

Step 3: Assess Data Readiness

Evaluate data quality, accessibility, ownership, duplication, and governance.

Step 4: Review Integrations

Identify manual exports, outdated interfaces, custom scripts, disconnected applications, and opportunities for API-led integration.

Step 5: Automate Predictable Processes

Use workflow automation for repetitive and rules-based activities before introducing unnecessary AI complexity.

Step 6: Introduce AI Where Intelligence Adds Value

Apply AI where interpretation, prediction, classification, anomaly detection, document understanding, or decision support can meaningfully improve the process.

Step 7: Establish Governance and Human Controls

Define permissions, approvals, audit requirements, security controls, and accountability before scaling AI across the organization.

Step 8: Measure Business Outcomes

AI initiatives should be measured against business results rather than the number of AI tools deployed.

Depending on the use case, organizations can monitor metrics such as:

• Processing time
• Manual effort
• Exception volumes
• Error rates
• Reporting turnaround
• Workflow completion time
• User adoption

This can help organizations determine where AI and automation are producing meaningful operational improvements.

The next phase of real estate AI will not be defined simply by who adopts the most AI tools.

It will be defined by which organizations successfully connect data, enterprise systems, integrations, automation, governance, and AI into reliable operational workflows.

For companies operating complex Yardi, MRI, and multi-platform environments, that transition requires both technical expertise and a strong understanding of real estate business processes.

That is where an experienced PropTech consulting partner can make a difference.

Assetsoft helps real estate organizations modernize and optimize technology environments across Yardi, MRI Software, integrations, automation, analytics, and enterprise workflows.

Rather than treating AI as an isolated technology initiative, Assetsoft can help organizations examine the systems and processes that AI ultimately depends on.

Areas of support can include:

• Yardi consulting and optimization
• MRI Software consulting
• System configuration and optimization
• Data migration and data-quality initiatives
• API and system integration
• Workflow automation
• Reporting and analytics
• Process assessment
• AI-readiness planning

The objective is not simply to introduce another technology.

It is to create an enterprise environment where people, processes, data, automation, and AI can work together effectively.

Moving from AI pilots to production requires more than adopting the latest AI technology. Real estate organizations need clean data, optimized Yardi or MRI environments, reliable integrations, scalable automation, strong governance, and clearly defined human controls. By strengthening these foundations now, organizations can enter 2027 better prepared to turn AI experimentation into practical, secure, and measurable business value.

Ready to move beyond AI experimentation? Assetsoft can help assess your current technology environment and develop a practical roadmap toward connected, automated, and AI-ready real estate operations.

Walk onto the executive floor of any REIT, and you’ll find people arguing about cap rates, HVAC optimisation, agentic AI, and the CAM reconciliation that’s three weeks late. You will not find anyone arguing about urinals.

That is a mistake, and the numbers say so. With around 56 million urinals in non-residential settings in the United States alone, on the order of one million litres of urine is splashed onto the floor daily, not because of user error, but because of geometry. The urinal in Marcel Duchamp’s 1917 art piece “La Fontaine” would not look out of place in a modern restroom. A century of building science has upgraded everything around it sensor faucets, low-flow valves, touchless dispensers and left the one surface that actually receives the liquid untouched.

The consequences are measurable. Urinal surfaces carry significantly higher bacteria concentrations than traditional toilets, with the surrounding floor highest of all, and ammonia levels on the floor around a urinal run roughly 100 times higher than any area near a toilet. Every stray litre becomes a mop pass, a chemical purchase, a corroded grout line, an odour complaint, and, eventually, a five-figure restroom renovation. It is one of the largest drivers of your janitorial contract and one of the most common grievances in your tenant surveys, and almost nobody has ever put it on a dashboard.

The Nautilus, nicknamed the “Nauti-loo”, is a urinal design developed at the University of Waterloo’s Department of Mechanical and Mechatronics Engineering. Long and sleek, it nearly eliminates splatter on floors, pants, and shoes by ensuring the angle at which a stream hits the wall doesn’t exceed about 30 degrees, a threshold determined through theoretical modelling and validated by physical experiments. At that shallow angle, the liquid stops rebounding and instead forms a smooth wall film that drains away.

Start with what happens to any liquid jet. Given enough distance, a stream breaks up into droplets through the Rayleigh–Plateau instability; in the team’s tests, the median droplet diameters ranged from 4.4 mm to 7.2 mm. By the time it reaches a urinal wall, you are no longer dealing with a stream but with a train of fast-moving drops carrying real kinetic energy.

What happens next depends on the angle of impact. Hit a hard surface close to perpendicular, and each droplet shatters on contact, throwing off satellite droplets that ricochet onto the floor, the partition, the user’s shoes and as aerosol into the air. Hit the same surface at a glancing angle and surface tension and viscosity win: the droplet spreads instead of shattering, and the liquid glides along the wall as a thin film. The team’s model predicts that at a 30-degree impinging angle, splash is reduced by about 95% from maximum, and that this inflection point is almost invariant across the range of conditions found in human urination.

The engineering problem, then, was spatial. A flat plate tilted at 30 degrees would work, but only for one user height and one trajectory. Real restrooms serve children, adults, and wheelchair users, standing at different distances and aiming at different points. Thurairajah’s team reframed the question as an isogonal curve problem: find a curve that intersects a family of stream trajectories at a constant angle, and solving the resulting differential equations in the top-view plane produced logarithmic spirals, the same curve found in a nautilus shell.

The team built and tested two prototypes. Both the Cornucopia and the Nautilus keep impinging angles at or below 30 degrees across their entire surface, and experiments showed they can reduce splashback to only 1.4% of the splash of a common contemporary commercial urinal. Under the high-splash conditions where conventional fixtures perform worst, the Nautilus achieved 85% and 95% reductions; by contrast, a contemporary commercial urinal throws droplets roughly half a meter to either side.

The Nautilus won on the criteria that matter to a facility manager. Its low lip, between 430 mm and 140 mm off the floor, makes it accessible to users of all heights, including wheelchair users, exceeding accessibility standards that require a lip no more than 430 mm high; its larger open area makes cleaning significantly easier; and because it tolerates poor aim, it may prove useful on aircraft and boats. Physics got the team to a splash-free surface; industrial design got them to a product a building could specify.

One more detail matters for procurement: the improvement comes solely from geometry, requires no expensive or complicated coatings, and is compatible with conventional materials.

Facility teams have fought splashback for decades with screens, mats, and behavioural tricks. Screens and mats catch splash rather than prevent it, with no published data on their effectiveness; and the famous fly sticker at Amsterdam’s Schiphol Airport produced a reported 50–80% reduction in splashback and an 8% cut in cleaning costs a reduction, not an elimination. The fly is a nudge; the Nautilus is a law of physics. Nudges depend on the user. Geometry doesn’t.

The Ig Nobel Prizes, organized by the magazine Annals of Improbable Research, honour research that first makes people laugh and then makes them think. This year’s ceremony marked a historic shift: after 35 years in the United States, the awards moved to a convention centre in Zurich, Switzerland, amid concerns about attendees getting visas, and the 2027 ceremony is already booked for Antwerp. Real Nobel laureates Esther Duflo, Abhijit Banerjee, Michel Mayor and Tim Hunt handed out the prizes on September 3, 2026.

The Waterloo team won the Physics Prize for their “theoretical and experimental attempts to design a splash-free urinal.” They wore yellow raincoats as couture at the ceremony and collected the traditional foot-mushroom statue and a ten-trillion-dollar bill from Zimbabwe, worth 15 to 30 Canadian dollars. Back in Waterloo, the professor and student had celebrated the news by sipping blueberry wine from espresso cups in Pan’s office.

The comedy is the point; so is what sits underneath it. Thurairajah described the prize as a symbol of learning things for their own sake: even if it seems silly, “it’s beautiful to know about how the world works.” Pan, for his part, has argued that without physics and math you cannot design even a humble urinal and that a pinch of art and humour makes ordinary life a little better.

For anyone who manages buildings, the beauty is in the budget.

Take the joke out and what’s left is a cost model. Splashback drives expense through four channels at once:

1. Custodial labor. High-traffic men’s restrooms are serviced on accelerated cycles, and a disproportionate share of each visit is spent on the floor and walls around the urinals rather than the fixtures themselves.

2. Consumables and chemicals. Uric acid crystallizes as puddles evaporate, and the odor drives recurring purchases of caustic cleaners, enzymatic sprays, deodorizing blocks, and disposable mats.

3. Accelerated capital expenditure. Urine is corrosive. Repeated wetting and drying cycles push salts into grout lines and past waterproofing membranes, delaminating tile and degrading subfloor. Restrooms that should last a decade end up in the renovation queue early, and a full gut renovation of a commercial restroom runs well into five figures before you count the disruption of closed facilities.

4. Work orders and complaints. Odor and wet-floor tickets are a perennial top category in office and retail CMMS logs, and every ticket carries dispatch overhead.

The researchers put a Canadian number on it. Using Toronto subway data, they note the TTC was projected to spend an annual average of $122,418 CAD per bathroom on cleaning alone from 2020 through 2024, and estimate that up to around $10,000 CAD per bathroom could be saved annually. That’s transit-grade traffic. Here is what the same logic looks like for a typical commercial asset:

A worked example. Take a Class-A office building or suburban mall with 40 urinals. Assume custodial staff spends four minutes per fixture per day on splash-related cleanup. That is 160 minutes, about 2.7 hours every day. At a fully loaded contractor rate of $28 an hour, the routine costs roughly $27,000 a year, and it exists only because liquid escaped a basin it was never supposed to leave.

Eliminate 75% of that work, and you free up about $20,400 a year in operating expense. Because commercial assets are valued as Net Operating Income divided by the cap rate, $20,400 of recurring NOI at a 6.0% cap rate translates into roughly $340,000 of asset value before counting chemical savings, deferred CapEx, or reduced ticket volume. Multiply that across a 50- or 100-property portfolio, and the ceramic fixture becomes a seven-figure decision.

In a post-pandemic market, physical space has to justify its existence. Office landlords compete against the kitchen table; shopping centres compete against a phone. Both win or lose on the quality of the in-person experience, and few things undercut a premium environment faster than a restroom that smells, feels sticky underfoot, or shows visible splatter around the fixtures.

In retail, restroom cleanliness is one of the most reliable predictors of dwell time and brand perception; a bad washroom in a luxury centre reads, subconsciously, as bad management everywhere else. In the office sector, tenant satisfaction surveys consistently rank restroom condition alongside temperature as a top workplace grievance, and unlike temperature, it is a grievance the landlord fully controls.

Thurairajah framed it in human terms: if the team can make bathrooms and public spaces more inviting, “that’s, like, a good thing for society.” For a landlord, the same sentence reads: more inviting facilities, higher retention, stronger asking rents.

Sustainability frameworks LEED, BREEAM, and WELL now shape tenant leasing decisions and institutional financing terms, and restrooms carry an awkward contradiction. Low-flow and waterless urinals cut potable water use, but with less flow to carry residue away, they often worsen odour and crystallization. Facility teams compensate with hot-water mopping, disposable mats and harsher chemicals, quietly undoing the gain the fixture was installed to deliver.

Containing splash at the source resolves the paradox. The researchers estimate that if the Nautilus replaced the 56 million non-residential urinals in the U.S., and cleaning consumes ten times the volume of splashed urine, it could save up to 10 million litres of fresh water a day. Add the disposable mats that never need to be bought, the quaternary ammonium compounds and bleach that never reach the sewer, and the aerosolized droplets that never degrade indoor air quality, an audited parameter under the WELL Building Standard.

A low-flow valve is an ESG line on a spec sheet. A fixture that stops the mess before it starts is an ESG outcome.

Here is the uncomfortable truth about physical innovation in real estate: a better fixture alone does not move NOI. Savings that are never measured never make it to the valuation model. The second half of the Nautilus story is digital.

At Assetsoft, we spend our days inside real estate's operational systems implementing and integrating Yardi Voyager and MRI Software; building automations with UiPath and Power Automate; and wiring Power BI to the data that actually runs a portfolio. When a client installs splash-free fixtures, the questions we help answer are the ones that turn a nice idea into a documented return:

• Is the labour saving real? Tag janitorial time and consumables in the CMMS by restroom and fixture class in Yardi Facility Manager or MRI X, so the before-and-after is a report, not an anecdote.

• Are cleaning schedules responding to reality? Occupancy sensors feeding the work-order system let cleaning cadence follow foot traffic instead of a fixed clock.

• Does finance see it? Vendor invoices, work orders, and property-level cost codes need to move between systems without manual keying. Working with integration partners such as KriyaGo, we connect the CMMS, the ERP, and the bank so the savings reconcile automatically and show up in the numbers finance actually reports.

In our world, the equivalent of fluid splashback is data splashback: the manual keying error, the unreconciled work order, the misallocated CAM charge, the broken handshake between two systems that should have talked to each other. It splatters drag across finance, leasing, and operations, and people spend hours every week mopping it up.

What the Waterloo team did with porcelain is what a good systems team does with an ERP, and the principles are identical:

1.Reject the default. A fixture, workflow, or report having worked “that way” for a century is not evidence that it is optimized.

2.Consult the mathematics. Solutions built on measured data and modeled behavior beat cosmetic tweaks and nudges every time.

3.Design for reality. Real users vary in height and trajectory, or in how they key an invoice. The system has to absorb that variance, not assume it away.

4.Capture compounding margins. Four minutes per fixture or thirty seconds per invoice is trivial once and transformative at scale.

The coverage has been global, which tells you the pain point is too. CBC Radio’s As It Happens interviewed Thurairajah on the research and the Zurich ceremony, and CBC’s The National featured him in a video segment.The Guardian covered the laureates in the UK; PBS NewsHour, Scientific American and the Daily US Times covered it in the United States; and the fluid-dynamics community’s own outlet, FYFD, walked through the physics. The University of Waterloo profiled the team in Waterloo News and on the MME department site, and the underlying study is open-access in PNAS Nexus.

The Ig Nobels promise to make you laugh first and think second. The Nautilus delivers on both: it is funny that a seashell fixes the men’s room, and it is serious that a hundred-year-old ceramic default has been quietly draining operating budgets the entire time.

Optimization happens at the margins. The owners who outperform on NOI over the next decade will be the ones willing to question every layer of their operating model: the fixtures, the data pipelines, the maintenance logs, the manual processes everyone else takes for granted. That is exactly where the untapped value is sitting.

Ready to find the splashback in your operations? From tuning your Yardi or MRI environment to automating reporting, integration, and reconciliation, Assetsoft engineers the digital layer that turns physical improvements into measurable returns. Talk to our real estate technology consultants.

As of July 2026, Yardi Virtuoso Connectors has entered general release. For property owners, managers, and asset teams, this is the moment a capability that spent the past year in early access becomes something you can actually put in front of your operators. The short version: you can now ask questions of your live Yardi data in plain English and get answers grounded in your own portfolio no export, no custom report, no waiting on a dashboard refresh.

This post breaks down what Virtuoso Connectors is, what “general release” changes mean, how the technology works, what you can do with it today, who can access it, and the part most announcements skip: what it takes to get real value out of it.

Yardi Virtuoso Connectors are a secure bridge between your Yardi data and modern AI assistants. Rather than exporting spreadsheets or building one-off reports, an authorized user can open an AI chat interface and ask operational or financial questions directly against real-time Yardi data.

Connectors are part of Yardi Virtuoso, Yardi’s AI platform for real estate. Where a bolt-on AI tool sits beside your system of record, Virtuoso is designed to work from inside the Yardi ecosystem, which is what allows the answers to be grounded in trusted, current data instead of a stale snapshot.

First unveiled at the Yardi Advanced Solutions Conference (YASC) in September 2025 and added to Virtuoso Enterprise in June 2026, the connector reached general availability in July 2026, when Yardi extended access more broadly, including directly to its Independent Consultant Network.

Early access is a proving ground: limited clients, tight guardrails, and a lot of hand-holding. General release means the capability is considered production-ready and is being offered to a much wider audience under standard terms.

Three practical shifts come with that:

1.  Broader eligibility. Any client on a Virtuoso Enterprise licensing agreement can turn it on, and ICN members can now access it directly regardless of their own Virtuoso status.

2.  A clearer roadmap. Claude is the first supported assistant; Yardi has signalled Microsoft Copilot as the next LLM, with additional providers to follow. Betting on a single vendor is no longer the risk it once looked like.

3.  A shift in where the work lives. When access was scarce, the story was about getting in. Now that access is broad, the differentiator moves to data readiness and governance the unglamorous groundwork that decides whether an AI answer is trustworthy.

Under the hood, Virtuoso Connectors are built on the Model Context Protocol (MCP), an open standard for connecting AI models to external data and tools. That architecture is what makes the connector portable across any MCP-compatible model rather than hard-wired to one vendor.

Two design choices matter most for operators:

●  Authentication runs through Yardi. Data access automatically follows each user’s existing Yardi permissions. Someone who can only see one region’s portfolio in Voyager sees only that region through the AI interface too. Permissions aren’t reinvented; they’re inherited.

●  Answers are grounded in live data. Because the assistant queries current Yardi data on demand, responses reflect what’s true now, not what a report captured last week.

The practical experience is “Bring Your Own AI Assistant”: you interact through the LLM interface you already use, Claude today, and the connector handles secure, permission-aware access to your Yardi environment behind the scenes.

The tools available at general release span four core areas of the business:

More tools are planned over the coming months, but even this initial set covers a large share of day-to-day operator questions. A few examples of what natural-language access looks like in practice:

●  “Show me commercial leases expiring in the next 180 days across the East region, with current base rent.”

●  “Which properties are trending over budget on repairs and maintenance this quarter?”

●  “Summarize open high-priority work orders older than 14 days by building.”

●  “What’s my portfolio-wide occupancy this month versus last?”

The point isn’t to replace canned reports; it’s to make the questions *between* the reports answerable in seconds, and to support scenario modelling, budget-variance testing, and risk analysis that would otherwise take an analyst a day to assemble.

There are two distinct paths, and they matter depending on who you are:

●  Yardi clients. If your organization has signed a Virtuoso Enterprise licensing agreement, the connector is available to you as part of that platform.

●  ICN members. Members of Yardi’s Independent Consultant Network, the ecosystem of independent implementation and advisory partners can now access Virtuoso Connectors directly, regardless of their own Virtuoso status, by entering a case through Yardi Client Central.

That second path is significant: it means the consultants and implementation partners who advise real estate operators can build hands-on fluency with the connector and design real use cases before rolling it out to clients.

Virtuoso Connectors don’t exist in isolation. They sit alongside the rest of the Virtuoso AI platform, including Virtuoso AI Agents for automating multi-step workflows, the Virtuoso Marketplace of pre-built agents, and Virtuoso Composer, a no-code builder for creating and testing your own agents.

Connectors are the conversational, ask-anything layer; agents are the do-something-repeatedly layer. Most organizations will get value from starting with connectors because they surface where the real questions and data gaps are and graduating to agents once those workflows are well understood.

Here’s the part the launch email won’t tell you. An AI assistant grounded in your Yardi data is only as good as that data, those permissions, and your reporting definitions. Point a natural-language interface at a messy chart of accounts, inconsistent property attributes, or ambiguous status codes, and you’ll get fluent, confident, *wrong* answers, which is worse than no answer at all.

Before a tool-first pilot, the enablement work looks like this:

●  Data hygiene. Reconcile the fields the AI will lean on: account structures, property and unit attributes, lease and work-order status codes, so questions map cleanly to reality.

●  Permission review. Because access inherits Yardi permissions, confirm those roles are correct *before* you expose them through a chat interface, not after.

●  Reporting definitions. Align on what “occupancy,” “in budget,” or “open work order” actually mean across teams, so the AI’s answer matches your operators’ mental model.

●  Governance and review points. Decide which questions are self-serve, which outputs need a human check, and how you’ll audit AI-assisted analysis that feeds decisions.

●  Use-case selection. Start with a handful of high-value, low-risk questions where a fast answer clearly beats the status quo, then expand.

Do this first, and Virtuoso Connectors becomes a genuine force multiplier. Skip it, and you’ve simply made bad data easier to reach.

Maryland SB 335, formally Landlord and Tenant Discrimination in Housing for Income-Based Housing Subsidies and Positive Rental History Reporting, was introduced by Senators Love, Charles, Henson, Hettleman, Lam, Muse, and Sydnor during the 2026 Regular Session. It passed both chambers, was approved by the Governor on May 26, 2026, and becomes Chapter 773 of the Laws of Maryland.

The Act adds § 20-705.1 to the State Government Article and § 8-208.4 to the Real Property Article. Both take effect October 1, 2026.

For owners and operators, it is best understood as two separate compliance workstreams that happen to share an effective date.

Under the new § 20-705.1, an income-based housing subsidy means recurring monetary assistance to a landlord from a governmental entity or nonprofit intended to defray a tenant's rent obligation, expressly including Housing Choice vouchers issued under the United States Housing Act of 1937.

If your rental application uses financial information, including credit history, you may not refuse to rent to a prospective tenant who pays with a subsidy based on:

1. The prospective tenant's income;

2. The prospective tenant's credit score, or lack of a credit score; or

3. Adverse credit history that arose during a period when the applicant did not have a subsidy, where the applicant confirms that period, voucher paperwork, public housing authority documents, or a PHA response to your request.

You also may not require a public housing authority to verify subsidy dates to assess credit history.

The bill preserves meaningful underwriting latitude:

• Income sufficiency for the tenant's portion. You may verify the applicant can pay the rent and utilities not covered by the subsidy, provided you use an income-to-tenant-portion ratio substantially equivalent to the ratio you apply to non-subsidized applicants.

• Behavioral history. You may decline based on any commercially reasonable and nondiscriminatory use of a landlord reference, or a history of lease violations, unpaid utilities, nuisance, or property damage.

• Funding-mandated collection. Landlords receiving funding that requires income qualification for income-restricted units may still collect financial information where that collection is a condition of the funding.

The compliance risk is concentrated in that phrase substantially equivalent. If your screening matrix applies a 3x income test to market applicants and a 3x-of-gross-rent test to voucher holders, you have a defect, and under amended §§ 20-701(c) and 20-1020(e), it is a discriminatory housing practice subject to Maryland Commission on Civil Rights enforcement.

New Real Property § 8-208.4 applies only to landlords who own six or more residential rental units in the State. If that's you, every written lease must now include the option to have the tenant's positive rental payment history reported to at least one consumer reporting agency.

"Positive rental payment history" means complete and timely rent payments and expressly excludes any instance in which the tenant did not pay in full or on time. This is an upside-only feed.

For existing leases, delivery must be by first-class mail with a certificate of mailing, a tracked delivery service with confirmation, or electronic delivery if the tenant has elected to receive notices that way. If you mail it, you must include a self-addressed, stamped envelope for the return election.

What the Offer Must Contain

The Secretary of Housing and Community Development will prescribe the form by regulation. The statute requires it to include: a statement that reporting is optional; the name of each consumer reporting agency; the amount of any fee; instructions for submitting the written election; notice that the tenant may opt in at any time; notice that the tenant may stop at any time but cannot resume for at least six months; opt-out instructions; and a signature block the tenant dates and signs to accept.

Tenants may request additional copies of the election at any time, and you must comply.

The Fee Mechanics Read These Twice

• The fee is capped at the lesser of your actual cost or $10 per month.

• Payment or nonpayment of the fee may never be reported to a consumer reporting agency.

• The fee is not rent. It cannot be credited toward rent or any other lease obligation.

• If a tenant is 30+ days delinquent on the fee, you may stop reporting, and the tenant cannot re-elect for at least six months from the date the fee first became due.

• On any written request to stop, you stop, and a six-month lockout applies before re-election.

Every one of these requirements maps to something inside Yardi Voyager, MRI Living, RealPage, or Entrata:

• Lease templates and clause libraries need the § 8-208.4 option embedded, not stapled on as an addendum someone forgets.

• Screening criteria need a separate, defensible ruleset for subsidy applicants with an income-to-tenant-portion test that provably mirrors your market test.

• Charge codes need a non-rent, non-ledger-crediting fee that never touches your delinquency or reporting feed.

• Notice generation and delivery tracking need to produce certificates of mailing or tracked delivery evidence, on an annual recurrence, per lease.

• The CRA data feed needs to suppress every non-complete, non-timely payment with a filter, not a dump.

• Audit trails need to survive a Commission on Civil Rights inquiry two years from now.

The six-month lockout rules alone are a state machine most PMS platforms do not model that's integration work natively.

The five-layer framing presented at the briefing is a teaching model. Yardi's publicly published Virtuoso architecture, captured on the Virtuoso product page and in the September 2025 launch announcements, organizes the same capabilities under three operational categories: Native AI, Virtuoso Connectors, and Virtuoso AI Agents (with Marketplace and Composer as sub-components). The table below reconciles the two frames.

The mapping matters for one practical reason: when Yardi clients procure, license, and deploy Virtuoso, they engage with the published taxonomy. The five-layer briefing model is useful for explaining the platform; the published taxonomy is what appears in contracts and product documentation.

Per Yardi's "Introducing Yardi Virtuoso" announcement, Native AI is built directly into the Yardi products that clients already operate. The framing is deliberate. Adoption is the dominant constraint on enterprise AI, not technical capability. AI surfaced inside an existing workflow has fundamentally different adoption economics than AI surfaced in a separate application.

Native AI underpins capabilities that ship as features of existing Yardi products: AI-driven work order classification in Maintenance IQ, AI lease abstraction in Smart Lease, AI-powered OCR in PayScan, and AI course creation in Aspire. Property management staff use these capabilities without ever consciously interacting with a separate AI tool.

For consulting and implementation engagements, Native AI changes the discovery question. The relevant question is no longer 'should AI be deployed' but 'which Native AI capabilities are turned on, configured correctly, and being measured against operational baselines.' A Yardi estate with Maintenance IQ that has not enabled AI work-order classification is leaving its deployed AI capability unused.

Layer 2 corresponds to Virtuoso Support, launched in September 2025 and available in Voyager 8 and RentCafe CRM IQ at the time of the briefing. Per Yardi's published metrics, Virtuoso Support resolves 78% of queries without escalation and is live with hundreds of clients and tens of thousands of users.

Virtuoso Support is built into the Yardi application as a conversational interface. A property manager working in Voyager 8 can ask, in natural language, how to configure a recurring journal entry, where to find a specific report, or what fields are required for a particular workflow. The Assistant returns an answer drawn from Yardi documentation, the user's actual application context, and the user's existing permissions.

Per the September 2025 launch press release, when the Assistant cannot resolve a question, it routes the user to Yardi's existing client support organization, preserving the existing escalation path. Yardi also publishes a monthly report to clients summarizing Virtuoso interactions and user questions, and a built-in feedback mechanism that surfaces training gaps and recurring issues.

Layer 3 corresponds to Yardi's Virtuoso AI Agents platform, launched at YASC in September 2025 and available through the Virtuoso Marketplace. Per Yardi's published documentation, the Marketplace is a curated library of expert-built agents addressing core property management workflows.

Per the September 2025 press release, Virtuoso AI Agents have demonstrated:

•  Maintenance operations: agents review work orders and prepare purchase orders overnight, saving 15 to 30 minutes of administrative time per property daily

•  Month-end close: financial reporting and reconciliation workflows reduced from over 20 hours to under five hours per property

•  Vendor management: intelligent invoice routing has cut accounts payable processing times by up to 60%

Why was the month-end close selected as the anchor use case?

Aaron Cabelli explained the rationale in the panel: every property management organization, in every asset class, has to close its books. Month-end is a workflow that touches the most clients across verticals, making it the highest-leverage anchor for an agent-based platform. Cindy Fisher, President of KETTLER, quoted in Yardi's launch announcement as an early adopter, described Virtuoso AI Agents as 'critical to improving capacity, efficiency, and accuracy across our entire platform.'

Per Yardi's product documentation, Virtuoso Composer is a drag-and-drop, no-code interface that allows clients to design their own agent flows, customize prompts, and interact with agents in real time before deploying them to live environments. Composer enables non-technical staff to orchestrate agent workflows without writing code or stored procedures.

The architectural primitive that Composer enables is a manager-and-sub-agent pattern: a manager agent receives a user request, decomposes it into sub-tasks, and dispatches those sub-tasks to specialized sub-agents that handle individual components of the workflow. The manager agent then assembles results and returns a unified response. This is the same orchestration pattern used in production agent frameworks across the broader AI industry, exposed through a no-code interface.

Why agents instead of stored procedures

An audience question during the panel asked when an agent should replace a stored procedure or scripted function. Aaron Cabelli's answer drew the practical line: agents are the right tool when input variability exceeds what deterministic code can handle. Stored procedures excel at handling structured database inputs and rule-based logic. They struggle with PDFs, scanned documents, image attachments, and free-form payment files. The example given in the session was an automated ACH check application: when a payment posts as a scanned image referencing multiple leases with embedded notations, deterministic code cannot reliably parse the input. An agent can. The decision is engineering, not preference.

Layer 5, framed as 'Insights Ask & Analyze' in the briefing, corresponds in Yardi's published architecture to Virtuoso Connectors. Connectors provide a secure bridge between real-time Yardi data and external large language models, starting with Anthropic's Claude. Per Yardi's published examples, the use cases include questions like 'Which properties are likely to exceed budget next quarter?', questions that require analytical reasoning over current operational data, returned in conversational form.

The architectural decision worth understanding: Connectors do not extract data and ship it to a third-party AI environment. The query is grounded in real-time Yardi data via a secure connector, and the response is returned to the user in the LLM interface they already use. The data does not leave Yardi's environment; the model interacts with the data through the connector boundary.

Joe Consolo emphasized during the panel that the number-one client concern about third-party AI tools is team members circumventing security controls to access data they normally cannot access. A generic AI vendor that ingests Voyager exports breaks the Yardi security model: tenant-specific permissions, property-level restrictions, and role-based access controls are absent in a flattened export. Virtuoso Connectors preserve these controls. User permissions and credentials carry through into the AI interaction, which is the architectural commitment that makes the Yardi approach defensible to a CISO or compliance officer.

The five-layer model is a description of the platform, not a deployment sequence. For most real estate firms evaluating Virtuoso, the deployment sequence that minimizes risk and maximizes early value runs in approximately reverse order:

•  Begin with Layer 2 (Assistant / Virtuoso Support), the lowest deployment cost, highest user-visible benefit, available today in Voyager 8 and RentCafe CRM IQ. The 78% query resolution figure is achievable from the first month of deployment.

•  Add Layer 3 (Premium Agents) anchored on month-end, close the highest-leverage initial agent deployment per Yardi's own published metrics, and the use case that touches every operator regardless of asset class.

•  Layer Layer 1 (Native AI) via configuration audits of existing Yardi modules, Maintenance IQ, Smart Lease, PayScan, and Aspire to confirm AI capabilities already paid for are turned on and measured.

•  Bring in Layer 4 (Composer) once the team has experience operating Yardi-built agents and understands the operational characteristics of agent-based workflows. Composer is the customization layer; it is most valuable when the operator already understands what they are customizing.

•  Deploy Layer 5 (Insights / Connectors) for analytical and strategic use cases once the underlying data layer is well-governed. Connectors against poorly modeled data produce confidently wrong answers.

The five-layer framing — Native AI Agents, Assistant, Premium Agents, Composer, and Insights is the framework Yardi presented at the May 2026 Executive Briefing in Santa Barbara to organize Virtuoso for consulting partners. Yardi's publicly published architecture on yardi.com/virtuoso organizes these capabilities into three operational categories: Native AI, Virtuoso AI Agents (with Marketplace and Composer as sub-components), and Virtuoso Connectors. The two are consistent; the briefing framing is a teaching model that decomposes the published categories into more granular layers.

Per Yardi's September 2025 launch announcement, the in-app conversational assistant is officially named Virtuoso Support. Earlier Yardi materials and partner content sometimes refer to it as the Virtuoso Assistant, the same capability, an earlier naming convention. In the Yardi ecosystem in 2026, "Virtuoso Support" is the current term.

The Virtuoso Marketplace, hosted at virtuoso.ai, is Yardi's curated library of expert-built AI agents addressing common property management workflows. Per Yardi's launch documentation, agents in the Marketplace are developed by Yardi's product teams and a network of industry experts and independent consultants trained on Virtuoso Composer. Clients can browse, customize, and deploy any agent within their own environment.

Per Yardi's September 9, 2025, press release, Virtuoso Support is currently available in Voyager 8 and RentCafe CRM IQ, with support for additional Yardi applications planned for future updates. Virtuoso AI Agents are deployable through the Virtuoso Marketplace into compatible Yardi environments. Virtuoso Connectors are available starting with Anthropic's Claude as the first LLM partner.

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).