Summary

• Integration depth is about what a tool can write back, not how many logos it lists. A tool that only reads your PMS still leaves your team doing the updates by hand.

• Most property AI tools sit somewhere between a one-way data feed and full read-and-write access to specific records such as leads, viewings, residents and work orders.

• Before you buy, ask for the object-by-object list of what the tool reads and writes in your system, how fast it syncs, and what happens when a sync fails.

What does integration depth mean for property AI tools?

Integration depth is how much of your operating data a tool can read, and how much it can change, inside the systems you already run. A deep integration reads live records and writes its work back. A shallow one pulls a copy and leaves the rest to your team.

That difference matters more with AI than with most software. An AI leasing assistant can answer a hundred enquiries overnight. If it can book the viewing, create the lead record and log the conversation in your PMS or CRM, your team starts the morning with an accurate pipeline. If it can only read unit availability, someone spends the morning copying those hundred conversations into the system of record.

So the useful question is never "does it integrate with Yardi?" It is "what exactly does it read, what exactly does it write, and how quickly?"

How do property AI tools compare on integration depth?

Property AI tools fall into roughly four levels, and the same vendor can sit at different levels for different systems. Knowing the levels helps you see past a logo wall.

• Scheduled data feed. The tool receives an export of units, prices or residents on a timetable, often nightly. It can answer questions from that copy, but nothing it does flows back, and its answers are only as fresh as the last file.

• Live read access. The tool queries your PMS or CRM directly, so availability and pricing are current. It still cannot create or update records, so the team does the admin after every conversation.

• Read and write on specific records. The tool reads live data and writes back defined objects, for example new leads, booked viewings, conversation notes or maintenance requests. This is where the time saving shows up, because the system of record stays accurate without anyone re-keying.

• Native to the PMS. The AI is built by the PMS vendor and works inside its own database. Access is usually deepest here, but it only covers that vendor's system, which matters if you run more than one.

Even the PMS vendors draw this line themselves. AppFolio's pricing page lists "AppFolio API (read only)" on its Plus plan and "AppFolio API (read/write)" on its Max plan. Buildium's pricing page includes its Open API only on the Premium plan. So a tool that "integrates with" either system may be limited by which plan you are on, before the AI vendor's own work even comes into it.

Which property management software integrates with Yardi?

A lot of it. Yardi says it works with 450+ trusted partners through standard interfaces, so the better question is which Yardi interface a tool uses and what that interface allows.

Yardi publishes separate interfaces for different jobs, including maintenance, collections, receivables, screening, revenue, master data, and internet listing and guest cards. Each one covers different data. Its maintenance interface, for example, covers resident, unit and lease information along with work orders and work order updates. A tool connected through one interface will not automatically have access to the data behind another.

When a vendor says it integrates with Yardi, ask three things:

• Which interface or interfaces do you use? A guest card connection for leasing is not the same as a maintenance connection.

• Which records do you write, not just read? Get the list in writing.

• Is this live in production with an operator like us? A connection that exists on paper is different from one running across a portfolio every day.

The same questions apply to MRI, res:harmonics, Mews, Arthur, Reapit or any other system you run.

Why isn't our PMS talking to our CRM?

Usually because the connection between them is shallower than it looked when it was sold, or because something in the data path has quietly broken. Neither system has to be down for records to stop moving.

The common causes are worth checking in this order:

• It was only ever one-way. Data flows from the PMS to the CRM but not back, even though both vendors call it an integration.

• It syncs on a timer, not live. The connection works, but it polls every few hours, so the CRM always looks slightly out of date.

• Fields don't map. Unit, property or resident IDs don't match between systems, so records fail to link or create duplicates.

• Credentials changed. A password reset, expired token or permissions change cuts the connection without anyone being told.

• Single records are failing silently. One malformed record fails while the dashboard still shows the connection as healthy.

The quickest diagnosis is to take one recent record, such as yesterday's new lead, and follow it. Does it exist in the first system? Did it arrive in the second? If not, where did it stop? If the answer is "nobody can tell", that is the real problem: an integration with no visibility of its own failures.

What should you check before you buy a property AI tool?

Ask every vendor the same questions and ask for the answers in writing. A good vendor will have them ready for your specific systems.

• The read list. Which records does the tool read from each of your systems, and is that live or from a scheduled export?

• The write list. Which records does it create or update? Leads, viewings, notes, applications, work orders, resident contact details? Anything not on the list is still your team's job.

• Sync speed. How long between the AI doing something and it appearing in your PMS or CRM? Seconds and hours lead to very different mornings.

• Duplicates and conflicts. What happens if a prospect already exists, or a team member edits the same record at the same time?

• Failure handling. When a write fails, who finds out, and how? You want an alert and a retry, not a gap you discover at month end.

• Audit trail. Can you see what the AI changed, when, and why? This matters for complaints, for compliance, and for trusting the tool with more.

• Your plan with the PMS vendor. As the AppFolio and Buildium examples show, your own PMS subscription can cap what any third party can do.

• The data processing contract. Under UK GDPR, the ICO is clear that every time a controller uses a processor there must be a written contract, and Article 28(3) sets out what it must include, from the type of personal data processed to deleting or returning it at the end. A tool that reads and writes resident records is handling personal data, so check this before go-live, not after.

One more test is worth running on a demo. Ask the vendor to complete a real task, such as booking a viewing, and then show you the record it created in your system. Two minutes of that tells you more than any integrations page.

What does this look like with Vinny?

Vinny is the AI teammate for property teams, and it works alongside your existing systems rather than replacing them. It connects to your PMS and CRM to read and act on live operational data, then writes updates back where appropriate so your systems of record stay accurate and auditable. The aim is simple: no double entry, and no handoffs where information gets lost between a conversation and the system your team relies on.

In practice, Vinny syncs leads, residents and availability in real time. When a prospect asks about a flat at 11pm, Vinny answers from live availability and pricing, qualifies them and books the viewing, and the lead syncs to your system instead of sitting in an inbox waiting to be copied across. The same conversation can run across voice, SMS, email, web chat and the portals.

Vinny connects with property management systems including Yardi, MRI, res:harmonics, Mews, Arthur and Reapit, CRMs including Pipedrive and Salesforce, the major portals such as Rightmove and Zoopla, and tools such as WhatsApp, Gmail, Outlook, Docusign and Stripe. On security, Vinny is SOC 2 and ISO 27001 certified, and GDPR compliant, and abides by the UE AI Act.

The honest caveat applies to us as much as anyone. The depth of any connection depends partly on what your PMS exposes and which plan you are on, so ask us the same questions in this post about the systems you run. You can see the full list on the integrations page, or book a demo and ask us to show you a record Vinny has written back.

Integration depth is one of the clearest ways to tell whether a property AI tool will take work off your team or quietly add to it. If you are earlier in the search and weighing up what an AI leasing assistant should do in the first place, start with our guide to what an AI leasing assistant is and how it works.

Frequently asked questions

What is bi-directional sync in property management software?

Bi-directional, or two-way, sync means data moves in both directions between two systems. A property AI tool with two-way sync reads records such as availability from your PMS and writes records such as new leads back into it.

Is an open API enough to guarantee a deep integration?

No. An open API means integration is possible, not that it has been built. Ask which records the vendor already reads and writes in your specific system, and whether that connection is live with other operators.

Does integrating an AI tool with Yardi need Yardi's involvement?

Yardi runs standard interfaces for its partners, grouped by job, such as maintenance, collections and guest cards. Check with both the AI vendor and your Yardi account team which interface the tool uses and whether your setup includes it.

Does Vinny replace our PMS?

No. Vinny works alongside your PMS and CRM, reading live data and writing updates back where appropriate, so they stay your systems of record.