Skip to content
Working Theory

Property management automation: what to automate first

For 50 to 500 door property managers: which of maintenance intake, rent follow-up, owner statements, renewals, and vendor scheduling to automate first.

By Levi Johnson, founder

Property management between 50 and 500 doors is a strange size. Big enough that the owner cannot touch every request, small enough that there is no operations department. The software is usually fine. The work around the software is where the hours go. Here are the five workflows we look at first, in the order we would automate them, and why.

The five workflows, ranked

1. Maintenance intake and triage. Requests arrive by portal, email, text, phone, and the occasional note under the door. Somebody reads every one, decides how urgent it is, and assigns a vendor. This goes first because it is the highest-volume, most-interrupting work in the business, and because it is where AI is actually good. Reading an unstructured message and sorting it into “emergency, urgent, routine, not maintenance” is exactly the task language models handle well. The human stays in the loop for anything flagged emergency.

2. Rent follow-up. Reminders before the due date, a friendly nudge after, and a clear list of who has not paid by day five. This is second because it is pure rules, the data already lives in your software, and it directly affects cash. It is also where we draw a hard line: a reminder is automatable, a legal notice is not. More on that below.

3. Vendor scheduling. Once a request is triaged, someone has to find a vendor, confirm a window, tell the tenant, and chase the vendor for a completion note. Third because it depends on intake being clean first. Automating scheduling on top of messy intake just sends the wrong vendor faster.

4. Lease renewals. Ninety days out, pull the expiring list, check the market, draft the offer, send it, and track the response. Fourth because the volume is lower and the timing is forgiving, but the cost of missing one is a vacant unit. This is a good fit for a simple monthly automation and a draft written by AI for a human to edit.

5. Owner statements. Monthly, tedious, and usually late because they wait on reconciliation. Fifth not because it matters least, but because automation rarely fixes the real bottleneck, which is the books not being closed. If statements are late, look at the accounting calendar before buying anything.

If you only do one thing, do intake. It is the one that gets someone’s phone buzzing at dinner.

Where AI fits, and where it does not

AI is useful in three places here: reading messy inbound requests and classifying them, drafting routine replies and renewal offers for a human to approve, and summarizing a long thread so the next person does not have to read all of it. In each case the model reads or drafts and a person decides.

AI does not belong in three places. It should not decide that a request is not an emergency without a human seeing the flagged ones. It should not set rent or renewal terms on its own, because fair housing law means the reasoning has to be defensible and consistent. And it should never send a legal notice. A pay-or-quit, a lease violation notice, or a non-renewal has statutory requirements that vary by state and sometimes by city. Automate the reminder, the draft, and the tracking. A named person reviews and sends the notice.

We are deliberately not quoting hours saved per hundred units. Vendors publish such figures and they vary enormously with portfolio type and how the work was being done before. If you want a number for your portfolio, count how many maintenance messages arrived last week and how long each one sat before someone acted on it. That is the figure that matters.

What a two-week sprint would cover for a 400-door company

This is a plan, not a case study. Say you manage 400 doors across a mix of single-family and small multifamily, with a team of six, running mainstream property management software. Here is what a two-week Implementation Sprint would cover.

Days one and two. We will sit with whoever reads the maintenance inbox and watch a full day of requests come in. We will write down the categories your team actually uses, not the ones the software offers, and agree in writing what “emergency” means for your portfolio.

Days three through five. We will connect the inbound channels, starting with email and the portal, to a triage step that reads each request, assigns a category and urgency, and drafts a first reply. Emergencies will page a named person by text. Everything else will land in a sorted queue. We will run it alongside the existing process, not instead of it, so nothing is missed while we learn what it gets wrong.

Days six through eight. We will fix what the real requests broke. Expect the model to confuse “no hot water” with “water heater leaking” until it is told the difference. We will add the handful of rules that matter for your buildings and tighten the draft replies until the coordinator would send most of them unedited.

Days nine and ten. We will add vendor assignment for the routine categories: the right plumber, electrician, or handyman proposed by area and trade, with a confirmation text to the vendor and a status note to the tenant. The coordinator will approve each assignment with one click. We will leave the approval in place; removing it is your call in month two, not ours in week two.

Days eleven and twelve. We will turn on rent reminders: one before the due date, one after, with a day-five list for the property manager. We will confirm in writing which messages are reminders and which are notices, and the notices will stay manual.

Days thirteen and fourteen. We will train the team, hand over plain-English documentation, and watch the system run for two days while we are still reachable. You will leave with a short list of what to do next, ranked, which usually starts with renewals.

The custom pieces in that plan, the connector between your channels and the triage step, and the vendor assignment logic, are the kind of small build we describe on the custom software and automations page. None of it replaces your property management software. It feeds it.

What it costs, roughly

As a market range as of September 2026, connecting intake to a triage step with a no-code tool and a language model runs from about $50 to $300 a month in subscriptions once it is set up. A small custom connector that handles the same job with better exception handling and an audit trail typically costs from about $3,000 to $12,000 to build from an independent developer or small practice, plus hosting. A two-week sprint that covers intake, vendor assignment, and reminders, with training, would sit in the same general range. If you want to see how we think about those numbers, we wrote up what automating a business process actually costs.

Before you automate any of it

Two checks. First, ask the two people who handle requests to describe how a routine one moves from inbox to closed. If the answers differ, settle that first. Automation on top of two processes produces two automated messes. Second, pick the named human for each approval point: emergencies, vendor assignments, notices. If you cannot name them, the automation has nowhere to hand off.

Then start with the inbox. It is the workflow everyone is tired of, the data is already there, and it is the one where a half day of watching usually turns into a change that is working before we leave.

Common questions

Should we replace our property management software first?

Almost never. Most 50 to 500 door companies already run AppFolio, Buildium, Rent Manager, or similar, and the gaps are usually in the work that happens around the software, not inside it. Automate the intake, follow-up, and scheduling that feed the system before considering a switch.

Can AI handle maintenance requests on its own?

It can read, categorize, and draft. It should not decide. A tenant saying 'there is water coming through the ceiling' needs a human within minutes, and the safest setup has AI flag that and a person act on it. Everything routine can be sorted and drafted without anyone typing.

What about late rent notices?

Automate the friendly reminders before and just after the due date. Do not automate anything that functions as a legal notice, such as a pay-or-quit. Those have state-specific requirements and a person should review and send each one.

How long does it take to see a difference?

Intake triage is usually working within two weeks. Rent follow-up and vendor scheduling take a month to settle because they depend on your data being clean. Owner statements depend mostly on whether the accounting is reconciled on time.

Found this useful? Share it on LinkedIn.

Show us the maintenance inbox

Half a day on site, from $750. We watch how requests come in, rank the five workflows for your portfolio, and get one of them working before we leave.

Book a free intro call

Or see what the Assessment includes