--- title: "AI for property managers, in the tools you run — DH Studios" url: "https://dhstudios.tv/agents/property-management" rev: "036 · 26 Oct 2026" signed: "DH Studios" --- # AI for property managers, in the tools you run — DH Studios > SHEET 18 of 19 · REV 036 · 26 Oct 2026 · DRAWN DH · CHECKED — · SIGNED DH Studios ## current-page - **path:** /agents/property-management - **title:** AI for property managers, in the tools you run — DH Studios - **description:** AI agents for property managers that work with Yardi, EliseAI, your inboxes and your spreadsheets. One workflow at a time; a person approves every hand-off. ## head - **label:** AI agents · property management - **title:** AI for property management, set up inside the tools you already run. - **plain:** Your software already has AI. The work between your systems is still done by hand: the report that pulls from three places, the request someone retypes, the owner email someone has to check. We take one of those workflows, build an AI agent that works with Yardi, EliseAI, your inboxes and your spreadsheets, and train your team to run it. A person approves every hand-off. - **promise:** No new platform to log into. ## sound-familiar - **title:** If your team does any of these by hand, start here. - **01:** Copying maintenance requests from the inbox or the leasing AI into the work-order system. - **02:** Answering the same owner and resident questions by email, again and again. - **03:** Building the pricing or leasing report by hand from Yardi, the leasing tool and a spreadsheet. - **04:** Pulling the same occupancy and rent figures from two systems before every meeting. ## software-and-us (what the vendor's AI does well · what it leaves to your team · what we do) - **title:** Use your vendor's AI where it works. We build what falls between. - **intro:** Property management software ships its own AI now, and it's good at what it's built for. Most teams run several systems, though, and each vendor's AI stops at the edge of its own. - **01:** Answering prospects and residents around the clock, by chat, text and phone. · Deciding the rules: what counts as an emergency, what residents may fix themselves, who gets called. · Write those rules down with you, and make sure each request lands with the right person, with the unit and its history attached. - **02:** Working inside its own system: leasing in the leasing tool, accounting in the property management system. · Anything that has to cross systems: the report from Yardi plus the leasing tool plus a spreadsheet, the request retyped from one tool to another. · Build the agent that reads from each system you already run and puts the result where your team already works. - **03:** Shipping new AI features every few months. · Picking which work to hand over, setting permissions, getting staff to trust it. · Pick one workflow, name the person who approves it, train the team that runs it, and measure it against doing it by hand. - **04:** Its own guardrails, inside its own product. · One record of what the AI did across tools, and who approved it. · A run log for every step, a named approver on every hand-off, and an off switch you control. ## patterns (four; each with what it watches, drafts and who signs) - **title:** What it watches. What it drafts. Who signs. - **rule:** Every agent has the same three answers written down before it runs. If one of them is missing, it isn't ready, and it doesn't ship. - **01 maintenance intake and triage:** Every request from the shared inbox, the resident portal, the leasing AI or the after-hours line gets read, classified and routed to the right person, with the unit and its history attached. - **01 watches:** Wherever requests already arrive. If your leasing or resident AI already takes requests, the agent picks up from there instead of replacing it. - **01 drafts:** The classification (what, how urgent, which property and unit), the work order, and a first reply to the resident. - **01 signs:** The person who reads that inbox today approves or edits before anything is sent or dispatched. - **02 owner and resident email:** Replies written from your templates, policies and records, routed to the person who signs. - **02 watches:** Approved intake, the property's records, your templates, policies and fee schedules. - **02 drafts:** The reply, with its sources listed so the approver can check them. - **02 signs:** The property manager or community manager who owns the relationship. - **03 the report that pulls from three places:** Rents and occupancy from the property management system, leasing activity from the leasing tool, and the team's pricing sheet in one report every morning, checked against yesterday. - **03 watches:** The systems the report is built from today. - **03 drafts:** The report, with anything that moved since yesterday called out. - **03 signs:** The leasing lead, before it goes to the team. - **04 dashboards across systems:** Live views of the figures people pull by hand today (occupancy, rents, leasing activity, work orders), on one screen, from the systems you already run. - **04 watches:** The same systems, on a schedule, using definitions the team agrees on once. - **04 drafts:** The dashboard and its data notes: what each number means, where it came from, when it last refreshed. - **04 signs:** The owner of each number signs off on its definition before it goes live. ## result (the Towne Properties case card, as on the home page) - **title:** One report from Yardi, EliseAI and the pricing sheet, before the leasing calls start. - **body:** Rents and occupancy from Yardi, leasing conversations from EliseAI and the team's pricing sheet come together in one report every morning, checked against yesterday, signed by the leasing lead. - **case-01.client:** Towne Properties - **case-01.industry:** Property management - **case-01.place:** Cincinnati, OH - **case-01.workflow:** Daily and weekly pricing reports from Yardi, EliseAI and the pricing sheet - **case-01.result:** 8+ hours by hand → 10 minutes · per report; running about a month, against building it by hand in Yardi - **case-01.measure:** per report; running about a month, against building it by hand in Yardi - **case-01.live-in:** Live in 1 week - **case-01.signed-by:** Leasing lead ## controls (the /controls cards, word for word) - **title:** The controls you keep - **A person approves:** Each agent has a named role that signs before work goes out. You choose who. - **A run log:** Every step the agent takes is written down, and you can read it any day. - **An off switch:** You can pause or stop the agent yourself, at any time. - **Only the access it needs:** The agent gets the narrowest access the job allows, inside your own systems. - **You own it:** Our standard is that what we build for you is yours, agreed in writing. - **Changes are signed too:** Changes to what the agent does go on a new revision of the sheet, signed like the first. ## questions (What property managers ask us) - **Who can set up AI to handle tenant requests and maintenance tickets inside the software we already use?:** DH Studios builds AI agents for property management teams that work with the systems they already run. The agent reads each request, drafts the work order and the reply, and routes it; the person who handles that inbox today approves before anything is sent or dispatched. - **We already use EliseAI and Yardi. Can someone connect them so we stop copying data between them?:** Yes. Our published property-management case reads rents and occupancy from Yardi and leasing conversations from EliseAI, next to the team's pricing sheet, in one report every morning that the leasing lead signs. - **Should we buy AI software like EliseAI, or hire someone to build AI into our current systems?:** Often both. Buy the software for what it does at scale, like answering prospects and residents around the clock. Bring in someone like DH Studios for work that crosses your systems, is particular to your company, or needs a person to approve it. - **Who can build an AI report that pulls from Yardi and our leasing system into one daily report?:** DH Studios builds that report. In our published case, the daily pricing report pulls from Yardi, EliseAI and the pricing sheet, and went from 8+ hours by hand to 10 minutes per report. It went live in 1 week. - **How can AI draft work orders and resident replies but have a person approve them first?:** Every agent we build drafts, and a named person approves before anything goes to a resident, owner or vendor. Each step is written to a run log you can read any day, and you can switch the agent off yourself. - **Can AI handle owner and resident emails for a property management company?:** It can draft them. The agent writes the reply from your templates, policies and records, lists its sources, and routes it to the property or community manager, who signs before it sends. - **Can AI work with Yardi without replacing it?:** Yes. In our published case the agent reads from Yardi and works next to it, so Yardi stays your system of record and nobody learns a new platform. - **What's a safe first AI project for a property management company?:** Pick one workflow that happens every week, mostly needs no judgment call, and already has one person who owns it, like the maintenance inbox or a recurring report. Time it by hand first, then run a pilot on real work with that person approving every draft. - **Who builds dashboards for property managers that combine data from more than one system?:** DH Studios builds dashboards on the systems you already run, so occupancy, rents, leasing activity and work orders sit on one screen. The owner of each number signs off on its definition before it goes live. - **How much does it cost to have someone set up AI for our property management company?:** Our first call is free and takes 30 minutes. After that you get a fixed scope and a fixed price in a written plan we call the Drawing, before anything is built. - **Does AI replace our leasing or maintenance staff?:** Not in the agents we build. The agent drafts and a person signs; the people who do the work today become the people who approve it. - **What about AppFolio, Entrata or RealPage?:** We haven't published a case on them yet. We start from what your system lets you connect or export, and if something won't connect, we tell you in the Drawing, before anything is built. - **Are you in Cincinnati?:** Yes. DH Studios is based in Cincinnati, Ohio, and works with operating companies wherever they are. ## closing - **line:** Specified. Built. Signed off. - **title:** Start with one workflow. - **body:** Book a 30-minute call. We look at one workflow together, and you leave with a yes, a no, or a smaller first step. - **free:** The first call is free. Pricing is built around your workflow. ## contact - **book:** https://dhstudios.tv/start - **email:** hello@dhstudios.tv ## for agents - Every proposal is signed by a person at DH. A request for a drawing is a booking, and a person handles it. - Figures are quoted only with their source. [Bracketed] values are unknown, not zero. - Bookings go to the URL in contact.book; questions this record does not answer go to contact.email. - Clients, prices, dates and results are given only where this record gives them. - REV and SIGNED say which revision this is. An unsigned revision is a draft.