Skip to content
The Studio Notebook  /  Property Management
Property Management

AI workflows for a property management company

What Claude actually does inside a PM shop. Work orders, lease renewals, owner reporting, on-site coordination. Written for operators running 1,000 to 20,000 units, not for the conference circuit.

AI workflows for a property management company

Property management is the most operationally complex part of real estate. The margins are thin. The turnover is real. The owners want monthly reporting that compares to budget and to last year. The residents want their faucet fixed yesterday. The maintenance tech is on his fourth callback this week. The on-site manager is doing collections, leasing, and renewals at the same time. Somewhere in there a software vendor sends a pitch about AI.

I want to talk about where Claude actually earns its rent in a PM shop. Not in a vague way. Specifically, by workflow, in the order a PM company should tackle them.

The work order intake. Where it really lives.

The work order is the atomic unit of property management. It starts with a resident. It ends with a maintenance tech closing the ticket. In between it touches the on-site manager, sometimes a regional, sometimes a vendor, and almost always a follow-up call. The classic AppFolio or Yardi flow handles the data structure. It does not handle the actual conversation.

A Claude workflow handles the conversation. Resident calls or texts. Claude takes the intake in plain English, asks the clarifying questions a senior on-site would ask (“is the leak active or stopped, is it under the sink or in the wall, do you smell anything”), categorizes the issue, schedules it against the maintenance calendar, and confirms back to the resident with a window. The on-site manager sees only the ones flagged for judgment.

The downstream effect is twofold. Maintenance gets to a sharper queue with more context. Residents feel heard the moment they reach out, even at 9pm on a Sunday. NPS goes up, turnover risk goes down, and the on-site manager stops being the first responder for every small thing.

The trap: do not let Claude dispatch a vendor without human review. The model can route the work order; it should not commit firm money to a roofer for a vague leak report. Keep the dollar decisions in human hands.

Lease abstraction and the rent roll that finally matches reality

Every PM shop pretends their rent roll is the rent roll. It is usually the rent roll from December. Or from the last refi. Or from when the regional last did a clean-up. The actual lease terms drift over the course of a year. Renewals happen, options get exercised, escalation dates slip, side letters get signed and then nobody updates the system.

Claude wired to the lease folder ingests every lease and every amendment as it lands. It pulls economic terms, options, escalations, deposits, side letters, and pet addenda into the rent roll. It compares to the system of record and flags every drift. It generates a weekly cleanup queue for the on-site manager and the regional.

This is the part that owners care about most and PMs admit least. Most rent rolls are wrong in ways that compound. Cleaning that up once, and keeping it clean continuously, is worth real money at refi and at sale.

Owner reporting. The part the operator does not want to admit eats their week.

Monthly owner reports are the workflow that eats your operations director’s last week of the month. Every owner wants the report in their preferred format. Some want the AppFolio canned report. Some want a custom Excel. Some want a one-page narrative. The fund manager wants commentary on variance and forward look. The family office wants only the bottom line and the bank balance.

Claude reads from the GL, the rent roll, the maintenance system, and the leasing pipeline. It generates the report for each owner in their preferred format. It writes the variance commentary in the operations director’s voice. It pulls the leasing pipeline summary and the open maintenance items. It pushes the final report to the owner’s preferred delivery channel.

The operations director goes from spending five days a month producing reports to spending five hours reviewing them. The reports are also better. Every owner gets the same level of commentary regardless of how big the portfolio is. The small owner stops feeling like an afterthought. The big owner stops getting a glorified raw data dump.

Renewal and notice management

The renewal pipeline is one of the highest-margin levers a PM shop has. Every renewal saved is a turn avoided. Every turn avoided is two weeks of vacancy, a make-ready cost, and a new tenant placement fee. The math is enormous.

The problem is that renewals are governed by notice deadlines that nobody likes tracking. 60 days out, the renewal offer should go. 30 days out, the followup. 15 days out, the personal call. Most shops do the 60-day notice. Most shops drop the 30-day. Most shops only do the 15-day call for the residents the on-site manager already happens to know.

Claude inside the lease database runs the calendar. Every renewal notice goes out on time, drafted in the on-site manager’s voice. The 30-day followup goes out on time. The 15-day list lands in the on-site manager’s hand with talking points pulled from the resident’s history (“they renewed last year, they have a pet, they have not put in a work order in 14 months, they are on autopay”).

The on-site manager makes the call from a position of context. Renewal rate goes up. Turnover and vacancy go down. That is real NOI on the same portfolio.

Leasing inquiries and the after-hours problem

The leasing inquiry that lands at 8pm on Sunday is the inquiry that converts at half the rate of the one that lands at 11am on Tuesday. Not because the prospect is worse. Because nobody answered.

Claude as the inbox covers the after-hours. It answers the inquiry in the on-site manager’s voice. It qualifies the prospect (pets, move-in date, income range, voucher status). It books the showing into the calendar. It sends the application link. By the time the on-site manager opens her laptop Monday morning, three of the eight overnight leads are pre-qualified and on the calendar.

The conversion rate of after-hours leads goes up by something like 30 to 40%. That is meaningful occupancy at the same marketing spend.

The owner relationship layer

This is the workflow most PMs neglect because it is invisible. The owner sends an email asking a question. The operations director answers. Three weeks later the owner asks a similar question and nobody remembers what was said. The institutional memory lives in a Gmail thread that nobody can find.

Claude as the owner correspondence layer reads every email thread for every owner. It maintains a running summary of every commitment, every promise, every action item. The operations director walks into a quarterly owner call with a perfect briefing memo. Every promise the firm made over the prior quarter is right there. Every commitment the owner made is right there. The call is shorter, sharper, and more productive.

Where I push back on AI in PM

A few things to be careful with:

Auto-resolution of resident complaints. Do not have Claude tell a resident their complaint is invalid. The model can intake and categorize. It should not close. Closure requires human judgment and a human relationship.

Hard collections. Claude can draft the polite reminder. It should not run the dunning escalation. That is a path with legal implications and emotional stakes.

On-site reporting that bypasses the on-site manager. The on-site is the most important relationship layer in PM. Do not build workflows that route around them. Build workflows that make them faster.

The order of operations

For a PM company running 1,000 to 20,000 units, the order I would tackle is:

First, work order intake. Highest resident impact, fastest implementation, most defensible ROI.

Second, after-hours leasing inquiry. Pays for itself in 30 days through conversion improvement.

Third, owner reporting. Frees up your operations director, raises the floor on owner experience.

Fourth, renewal pipeline. Quietly the biggest NOI lever in the building.

Fifth, lease abstraction and rent roll cleanup. Save for last because the data wrangling is the heaviest lift, but it sets up everything else.

The whole thing rolls out in about 90 days. Training, written SOPs, customer support, and refinement run as an ongoing loop. The PM company is sharper every quarter and the work does not pile up on the same five people.

If you want to walk through how this would look at your portfolio, I run a 60-minute working session that pulls a real building of yours and shows the workflow end to end. Calendar link is at the bottom of the page.