How to Structure an AI Agent Fleet for a Property Management Company
If you're a PM owner experimenting with AI agents, the first real question isn't "which tool," it's org structure. Just like a human shop lives or dies on how you split leasing, maintenance, accounting, and resident relations, an agent-run shop lives or dies on how you group the agents. Get the structure wrong and you build a swarm of half-overlapping bots nobody can audit. Get it right and you get a tight, scalable operation that runs your book around the clock.
Here's the structure I'd build, why, and the order I'd build it in.
The short version
- Human PM companies pick from three structures: portfolio (one person owns a slice of doors end-to-end), departmental (functional teams serve the whole book), and pod (small cross-functional squads owning a slice). Past roughly 700 to 1,000 doors, the human industry trend is pods, because human coordination and headcount costs push you there.
- AI agents invert that tradeoff. The reasons humans go pod (one throat to choke, relationship continuity, low coordination overhead inside a small team) mostly evaporate when "headcount" is nearly free and an orchestrator coordinates at near-zero cost. For an agent-run PM company the right answer is a centralized, departmentalized fleet with an orchestrator on top: a "functional fleet." Pods come back only as a scaling/sharding device once one department-agent can't hold the whole book in working memory.
- Recommended structure: a thin orchestrator over six functional department-agents (Maintenance/Property Ops, Leasing, Resident Relations & Collections, Accounting/AP-AR, Business Development, Compliance), each fronting a library of sub-agents and playbooks. Plus a small set of platform agents (dev/integrations, analyst, code review) that build and maintain the fleet itself.
- Most functions are NOT their own agent. The biggest mistake is one-agent-per-function sprawl. Most of what a PM company does is a skill run by a department-agent, not a standing bot. Reserve full-agent status for functions that need continuous ownership of an outcome or an external relationship.
The rest of this is the detail behind those four points.
1. The full functional breakdown of a PM company
Before you can map functions to agents, you have to name them all. Here's every function a real residential shop runs, grouped, one line each. The items owners most often forget or underweight are flagged [OFTEN FORGOTTEN].
Property / Portfolio Management (the "PM seat")
| Function | Day-to-day reality |
|---|---|
| Portfolio oversight | Owns the P&L and health of a set of doors; the escalation point for anything cross-functional. |
| Owner-facing decisions | Approves spend over threshold, sets rent strategy, signs off on turns, evictions, capital work. |
| Exception handling | Anything that doesn't fit a playbook lands here: angry owner, weird legal edge case, vendor blowup. |
| Cross-function coordination | Makes leasing, maintenance, and accounting agree on the same resident/unit reality. |
Leasing
| Function | Day-to-day reality |
|---|---|
| Marketing / listing / vacancy | Writes listing copy, posts to portals, manages photos, tracks days-on-market per vacant unit. |
| Prospect intake & showings | Responds to inquiries fast (speed-to-lead), qualifies, schedules/runs showings. |
| Applications | Collects application + docs, checks completeness, runs the packet through the funnel. |
| Tenant screening | Credit / background / income / rental-history checks against objective criteria; approve/deny/conditional. |
| Lease prep & execution | Generates lease from template, adds addenda, routes for e-sign, counter-signs. |
| Move-in | Schedules walkthrough, collects deposit + first month, hands over keys, documents condition. |
| Renewals | Times the renewal offer, sets new rent vs market, chases non-responders, tracks signed renewals. [OFTEN UNDERWEIGHTED as just "send a letter," it's the single biggest retention + revenue lever.] |
| Move-out & turnover handoff | Processes notice-to-vacate, schedules walkthrough, hands turn scope to maintenance, kicks deposit reconciliation to accounting. |
Maintenance / Property Operations
| Function | Day-to-day reality |
|---|---|
| Work-order intake & triage | Receives requests (app/phone/text/email), classifies urgency, asks diagnostic questions, requests photos. |
| Vendor dispatch & scheduling | Picks the right vendor, confirms a window before promising the resident, tracks confirmation. |
| In-house tech coordination | Assigns techs, enforces photo + hours + notes discipline, closes out. |
| Make-ready / turns | Scopes a vacated unit, sequences trades (clean, then paint, then repair, then final), races days-vacant. |
| Preventive maintenance & inspections | Scheduled HVAC/filter/gutter/seasonal work; periodic interior + drive-by inspections. [OFTEN FORGOTTEN, the cheapest way to cut emergency spend.] |
| After-hours / emergency coverage | 24/7 triage of "no heat / flood / lockout / safety" so a true emergency never sits in a queue overnight. [OFTEN FORGOTTEN until a 2am flood.] |
| Invoice / AP review (maintenance side) | Checks vendor invoices against the scope/quote before they go to accounting to pay. |
| Recurrence / root-cause tracking | Notices a unit's repeat issues and escalates the underlying defect, not the symptom. |
Resident Relations
| Function | Day-to-day reality |
|---|---|
| General communications | Day-to-day resident questions, status updates, account help, the human-facing tone of the company. |
| Complaints / disputes | Noise, neighbor conflicts, "the AC is too loud": de-escalation and resolution tracking. |
| Lease violations | Notices for unauthorized pets/occupants/parking, cure-or-quit, documentation trail. |
| Delinquency / collections | Late-rent reminders, payment-plan negotiation, escalating ladder before legal. [OFTEN UNDERWEIGHTED, it's a pipeline, not a one-off task.] |
| Eviction process | The formal legal ladder once collections fails: notices, filing, court, writ; mostly attorney-driven, tightly compliance-bound. [OFTEN FORGOTTEN how procedural and jurisdiction-specific this is.] |
| Renewals-relationship layer | The retention conversation that precedes the leasing-side renewal paperwork. |
Accounting / Finance
| Function | Day-to-day reality |
|---|---|
| AR / rent posting | Posts rent, applies payments, tracks who's short, feeds the delinquency pipeline. |
| AP / vendor payments | Pays approved vendor invoices, manages bills, 1099 tracking. |
| Owner draws & statements | Monthly owner statements + distributions, a top driver of owner retention. [OFTEN UNDERWEIGHTED.] |
| Trust accounting | Keeps owner/resident funds segregated and reconciled per state law; the #1 source of PM legal/compliance blowups. [MOST FORGOTTEN, highest-risk.] |
| Reconciliation | Bank rec, three-way trust rec, catching the penny-off before it's a $40k-off. |
| Reporting | Owner P&Ls, portfolio dashboards, tax-package prep. |
| Security-deposit accounting | Holds, itemizes, returns deposits on statutory timelines (statutory penalties if late). [OFTEN FORGOTTEN.] |
Business Development
| Function | Day-to-day reality |
|---|---|
| Owner acquisition / sales | Finds rental owners/investors, runs consultative discovery, books + closes new-door contracts. |
| Owner onboarding | New-owner intake: docs, property data, lease assumption, expectations in the first 90 days. [OFTEN FORGOTTEN, bad onboarding is the #1 cause of first-year owner churn.] |
| Owner relations / retention | The proactive "your portfolio is healthy" touch that prevents churn and drives referrals. |
Compliance / Legal
| Function | Day-to-day reality |
|---|---|
| Fair Housing | Every prospect/resident interaction on objective criteria; no protected-class language. Cross-cuts leasing + resident relations. [HIGH RISK, OFTEN UNDERWEIGHTED.] |
| Section 8 / subsidy compliance | HAP contracts, inspections, recerts, jurisdiction rules if any subsidized units. [OFTEN FORGOTTEN.] |
| Habitability | Statutory repair timelines, warranty-of-habitability, safety. Cross-cuts maintenance. |
| Eviction-process compliance | Notice form/timing/service rules: get one wrong and the case is dismissed. |
| Licensing & registration | Broker/PM license upkeep, local rental registration, lead-paint/RRP, business licensing. [OFTEN FORGOTTEN.] |
| Vendor compliance / insurance (COI) | Every vendor's license + insurance current; expired COI = the PM eats the liability. [MOST FORGOTTEN operational-risk item.] |
| Resident insurance tracking | Required renters-insurance proof, expiry monitoring. [OFTEN FORGOTTEN.] |
| Regulatory-change monitoring | Rent-control/notice-period/screening-law changes by jurisdiction. |
Admin / Ops (the connective tissue)
| Function | Day-to-day reality |
|---|---|
| Data hygiene | Keeps your system of record (units, residents, leases, vendors) clean and authoritative: the source of truth everything else reads. |
| Document management | Leases, addenda, COIs, notices filed and retrievable. |
| Reporting / dashboards | Cross-function status: occupancy, days-vacant, delinquency %, open WOs. |
| Systems / integrations | Keeps your PM software, comms channels, and agent stack talking. |
| Knowledge management | Vendor quirks, owner preferences, jurisdiction rules: the institutional memory. |
2. The three org models, compared
Human PM companies organize along three named styles. (Sources at the end. Note the industry uses portfolio where some people say "pod-of-one," and reserves pod for the cross-functional-squad variant.)
| Dimension | Portfolio model | Departmental model | Pod model |
|---|---|---|---|
| Shape | One PM owns a slice of doors end-to-end (leasing + maintenance + resident + reporting for their properties). | Functional departments (leasing, maintenance, accounting, etc.) each serve the whole book. | Small cross-functional squad (PM + maintenance coord + leasing coord) owns a slice of the book end-to-end. |
| Pros | Deep relationship + context per property; one owner-facing contact; fast within-portfolio decisions. | Specialization + repeatability; process consistency; easy to scale a function independently; no single point of failure per door. | Pod owns outcomes end-to-end with low cross-team handoff; relationship continuity plus some specialization; scales by cloning pods. |
| Cons | Single point of failure (overload/turnover takes the whole portfolio down); no specialization; inconsistent process; doesn't scale past one person's capacity. | Handoffs between departments create seams (the resident gets bounced); no single owner of a door's overall health; coordination overhead. | Hardest to staff (need 3 right people per slice); duplicated function across pods; can drift into inconsistent process pod-to-pod. |
| When it fits | Small shops (under 200 to 300 doors), boutique/high-touch books. | Mid-to-large shops that have productized each function; high volume per function. | Large shops (1,000+ doors) that want ownership + to scale by adding identical squads. |
| Failure mode | The PM quits, then 150 doors in freefall. | Resident falls in a seam between leasing and maintenance; nobody owns "is this door okay overall." | Pod A's process diverges from Pod B's; quality variance; you've rebuilt silos at pod scale. |
Hybrid (what most growing shops actually run): pods/portfolios for the resident-facing, relationship-heavy work (leasing, maintenance, resident relations) + centralized departments for the back office (accounting, trust accounting, BD, compliance) where specialization and a single source of truth matter more than relationship continuity. This is the dominant real-world answer at scale: front-of-house owns relationships, back-of-house owns the ledger and the law.
Industry sources describe pods as "a hybrid blend of portfolio + departmental," and the consistent observation is that shops past roughly 1,000 doors gravitate to pods. See Second Nature, Blanket (Departmental vs Portfolio), Access PM Group, and BetterWho.
3. Why AI agents flip the answer
Here's the thesis. For an agent-run PM company, the right structure is a centralized, departmentalized fleet + orchestrator: a "functional fleet." Not pods. The human industry trends toward pods at scale; agents shouldn't. Four reasons the human answer doesn't carry over:
- What pushes humans to pods is coordination + headcount cost. A human department-of-one for 700 doors gets overwhelmed; you can't cheaply clone them, so you bundle three generalists into a pod and replicate it. An agent department doesn't get "overwhelmed" the same way: you scale it by spawning sub-agents/workers, not by hiring. Cloning is nearly free. The overload pressure that creates pods is largely gone.
- Specialization is cheaper than relationship continuity for agents. Pods exist partly so one human keeps the resident relationship warm across functions. Agents share a common knowledge base and a single source of truth; "continuity" is a database read, not a person's memory. The relationship argument for pods weakens.
- A single source of truth + one process beats per-pod drift. The departmental failure mode (seams between departments) is cheap to fix with agents: the orchestrator + shared knowledge base close the seam. The pod failure mode (process drift pod-to-pod) is expensive, and it's exactly the "agent sprawl" the current multi-agent research warns against.
- The field is re-centralizing. Current consensus favors orchestrator-based systems that blend centralized coordination with specialized distributed workers, not swarms of co-equal autonomous agents (MIT Tech Review; arXiv hierarchical MAS taxonomy).
Where pods do come back: as a sharding mechanism, not an org philosophy. When one Leasing agent can't hold the whole book's renewals + applications + move-ins in working context, you don't reorganize into pods, you shard the Leasing department by region/portfolio (Leasing-West, Leasing-East), each still a department-agent, all coordinated by the orchestrator. That's pods-as-implementation-detail, with departmental discipline preserved. Departmental in design; shardable into region-pods only when a single agent hits a context/throughput ceiling.
4. The decision rule: full agent vs sub-agent vs skill
This is the single most important call you'll make, and it's where most fleets go wrong. There are three "types," and most functions are not the top one.
- FULL AGENT: persistent identity, own goals, own inbox, runs continuously, owns an outcome and a relationship surface, makes judgment calls, escalates. Use when a function needs continuous ownership, an external relationship, or cross-task memory.
- SUB-AGENT / WORKER: spawned by a full agent for a bounded task, runs, returns a result, dies. No persistent identity. Use for heavy, parallelizable, or isolatable work (a screening run, a turn-scope, a report pull).
- PLAYBOOK / SKILL: a documented procedure a full agent runs in its own context. No separate process. Use when the work is a deterministic-ish procedure the parent should do inline, with judgment, keeping the thread's memory.
Heuristic: Relationship or continuous ownership, then full agent. Bounded heavy/parallel job, then sub-agent. Procedure-with-judgment, then skill. Most functions above are skills under a department full-agent, not their own agents.
Resist one-agent-per-function sprawl. Every full agent is a standing process, an inbox to monitor, a heartbeat to keep alive, and a coordination edge for the orchestrator. Each one you add is real overhead. A skill costs nothing when idle. The current multi-agent research is explicit that "agent sprawl" (too many autonomous agents, inconsistent oversight, hard to audit) is the main failure mode, and the field is re-centralizing onto orchestrator + fewer, deeper agents (MIT Tech Review, Berkeley CMR, arXiv taxonomy).
Function to agent-type map
| Function | Type | Lives under |
|---|---|---|
| Orchestration / chief-of-staff | Full agent | (top) |
| Portfolio / PM-seat exception handling | Full agent (or the orchestrator at small scale) | top |
| Work-order intake & triage | Skill | Maintenance |
| Vendor dispatch & scheduling | Skill | Maintenance |
| Make-ready / turns | Sub-agent (multi-step scope) + skill | Maintenance |
| Preventive maintenance & inspections | Skill (cron-driven) | Maintenance |
| After-hours / emergency | Skill (always-on triage path) | Maintenance |
| Maintenance invoice/AP review | Skill | Maintenance, handoff to Accounting |
| Marketing / listing / vacancy | Skill | Leasing |
| Prospect intake & showings | Skill | Leasing |
| Applications + screening | Sub-agent (screening run) + skill | Leasing |
| Lease prep & execution | Skill | Leasing |
| Move-in / move-out coordination | Skill | Leasing |
| Renewals (scoring + offer + chase) | Sub-agent/engine + skill | Leasing |
| General resident comms | Skill | Resident Relations |
| Complaints / disputes | Skill | Resident Relations |
| Lease violations | Skill | Resident Relations |
| Delinquency / collections | Skill (stateful pipeline) | Resident Relations |
| Eviction process | Skill (compliance-gated) | Resident Relations, Compliance gate |
| AR / rent posting | Skill | Accounting |
| AP / vendor payments | Skill | Accounting |
| Owner draws & statements | Skill (cron) | Accounting |
| Trust accounting & reconciliation | Sub-agent (verify run) + skill, human-approval-gated | Accounting |
| Security-deposit accounting | Skill | Accounting |
| Owner reporting | Sub-agent (report build) + skill | Accounting |
| Owner acquisition / sales | Skill (consultative-sales flow) | BD |
| Owner onboarding | Sub-agent (onboarding checklist) + skill | BD |
| Owner relations / retention | Skill | BD |
| Fair Housing | Cross-cutting gate-skill (called by Leasing + Resident) | Compliance owns the skill |
| Vendor COI / insurance tracking | Skill (cron expiry watch) | Compliance |
| Resident insurance tracking | Skill (cron) | Compliance |
| Section 8 / subsidy, habitability, licensing | Skill(s) | Compliance |
| Regulatory-change monitoring | Skill (cron + analyst) | Compliance |
| Data hygiene / source-of-truth | Skill | Platform + every agent |
| Integrations / systems | (platform) | Dev agent |
| Knowledge management | Skill (KB writes) | every agent |
Why so few full agents: a function earns full-agent status only if it needs continuous ownership of an outcome or an external relationship surface. Everything else is a skill the department-agent runs.
5. The department tree
This is the shape to build toward. An orchestrator on top, six department full-agents, each fronting skills and sub-agents, plus a small platform layer that builds and maintains the fleet.
ORCHESTRATOR / Chief of Staff [full agent]
│ decomposes directives, routes to departments, monitors fleet health,
│ sends briefings, routes approvals, cascades goals. Holds the PM-seat
│ exception role until scale justifies a separate Portfolio agent.
│
├── PROPERTY OPS / MAINTENANCE [full agent]
│ ├─ skill: work-order intake & triage
│ ├─ skill: vendor dispatch & scheduling
│ ├─ skill: in-house tech coordination + closeout discipline
│ ├─ skill: preventive maintenance + inspections (cron)
│ ├─ skill: after-hours/emergency triage path
│ ├─ skill: recurrence/root-cause tracking
│ ├─ sub-agent: make-ready/turn scope builder
│ └─ handoff: maintenance invoice review to Accounting
│
├── LEASING [full agent]
│ ├─ engine/sub-agent: renewals scoring
│ ├─ skill: renewals offer + chase cadence
│ ├─ skill: prospect intake + showings
│ ├─ sub-agent: applications + screening run
│ ├─ skill: lease prep + e-sign execution
│ ├─ skill: move-in / move-out coordination
│ ├─ skill: marketing / listing / vacancy
│ └─ calls: Fair Housing gate (Compliance)
│
├── RESIDENT RELATIONS & COLLECTIONS [full agent]
│ ├─ skill: general resident comms
│ ├─ skill: complaints / disputes
│ ├─ skill: lease violations
│ ├─ skill: delinquency / collections pipeline (stateful)
│ └─ skill: eviction handoff, calls Eviction-compliance gate
│
├── ACCOUNTING / AP-AR [full agent]
│ ├─ skill: AR / rent posting, feeds delinquency pipeline
│ ├─ skill: AP / vendor payments
│ ├─ skill: owner draws + statements (cron)
│ ├─ sub-agent: trust accounting reconcile (HUMAN-APPROVAL-GATED)
│ ├─ skill: security-deposit accounting
│ └─ sub-agent: owner report builder
│
├── BUSINESS DEVELOPMENT [full agent]
│ ├─ skill: owner acquisition (consultative-sales flow)
│ ├─ sub-agent: owner onboarding checklist runner
│ └─ skill: owner relations / retention
│
└── COMPLIANCE [full agent, cross-cutting]
├─ skill (gate): Fair Housing (called by Leasing + Resident)
├─ skill (gate): eviction-process compliance (called by Resident)
├─ skill: vendor COI / insurance expiry watch (cron)
├─ skill: resident insurance tracking (cron)
├─ skill: Section 8 / habitability / licensing
└─ skill: regulatory-change monitoring (cron + analyst)
PLATFORM / META (build & maintain the fleet, not PM functions):
Dev / Integrations [full agent]
Analyst / system health [full agent]
Code review [full agent]
A note on the platform layer: you need agents that build the fleet as well as agents that run the book. A dev/integrations agent to wire your PM software and automations, an analyst to watch system health, and a code-review agent to keep the build clean. They aren't PM functions, but without them the PM agents have nothing to stand on.
6. Where to start: a phased build order
You don't build all six departments at once. The natural first build is the highest-ROI department, then you work outward in dependency order. Here's the sequence I'd use for any shop.
Phase 1: Leasing, renewals-first.
Why first: renewals are the highest-ROI lever you have (retention + rent), the work is concrete and measurable, and it forces you to build the read path into your PM system of record that every later department will reuse.
- Stand up the Leasing agent; wire a renewals scoring engine as its first capability.
- Renewal offers route recommendations to the orchestrator/PM-seat for the rent-vs-market call. Don't auto-price.
- Add a move-out to maintenance turn-handoff so Leasing and Maintenance share one unit reality.
- Done when: Leasing can pull the renewal pipeline, score it, draft offers, and hand price decisions up.
Phase 2: Accounting / AR spine + delinquency feed.
Why second: AR posting is the data source for collections, and owner statements drive retention. Start read-only (post/report). Keep money-movement and trust reconciliation human-approval-gated from day one.
- AR posting, owner statements (cron), security-deposit accounting.
- Trust-accounting reconcile = a sub-agent that verifies and flags, never moves money unattended.
- Expose a clean "who's delinquent" feed for Phase 3.
Phase 3: Resident Relations & Collections.
Why third: it depends on the AR feed and closes the most commonly orphaned functions (delinquency, violations, eviction handoff).
- Comms, complaints, violations, and the stateful collections pipeline (surface only on state change, don't re-poll static state).
- Eviction handoff calls the Compliance eviction-gate (Phase 4).
Phase 4: Compliance as a cross-cutting gate layer.
Why now, not later: it's the function most likely to bite you and most likely to be skipped. Fair Housing tends to live implicitly inside leasing, while vendor COI, licensing, and eviction-process compliance go unowned.
- Build it as gate-skills other agents call + cron watchers (COI/insurance expiry, regulatory monitoring). Pull it forward.
Phase 5: Business Development (last).
Why last: it grows the book, but everything above must run cleanly first or new doors land on a shaky operation.
- Owner acquisition + an onboarding-checklist sub-agent + the retention touch.
Continuous, across all phases: the platform agents wire integrations, watch system health, and review the code; the orchestrator coordinates, cascades goals, and routes approvals. Every new agent should pass a governance/safety gate before it goes live.
7. The roles you'll forget (this is the gold)
These are the functions a PM owner building an agent fleet is most likely to skip or underweight, ranked by risk times forgettability. If you read one section twice, make it this one.
- Trust accounting & three-way reconciliation. The highest legal-risk function in PM, and the most boring, so it's the most skipped. Commingling or a blown rec is a license-revocation / lawsuit event. Never let an agent move trust funds unattended: verify-and-flag only, human approval to move money. (Rentvine)
- Owner reporting & retention. Owners churn from reporting confusion and late distributions even when ops are great. Clean monthly statements + on-time draws are the cheapest retention you can buy, and a pure agent strength. (Rentvine)
- Vendor compliance / COI & insurance tracking. When a vendor's insurance lapses, the liability rolls to you. Expiry-watching is tedious and constant, exactly what a cron-skill should own. Forgotten until a vendor causes damage uninsured. (NetVendor)
- Fair Housing risk. Cross-cuts every prospect/resident touch. One agent improvising tone or asking the wrong screening question is a federal-complaint surface. Must be a gate-skill on objective criteria, not vibes, and callable so it can't be bypassed.
- After-hours / emergency coverage. Easy to design for business hours and forget that floods happen at 2am. A true emergency can never sit in a queue. Needs an always-on triage path, not a 9-5 one.
- Delinquency to legal pipeline. Collections is a stateful escalation ladder (reminder, plan, notice, legal), not a one-off message. Eviction is procedural and jurisdiction-specific: get the notice form/timing wrong and the case is dismissed. Owners underbuild this because it's unpleasant.
- Lease-renewal-vs-market-rent strategy. Often treated as "send a renewal letter." It's the biggest combined retention + revenue lever, and the rent decision is a judgment call that stays with the PM-seat: the engine recommends, a human decides.
- Vacancy marketing / days-on-market. Every vacant day is lost revenue; listing, photos, and speed-to-lead get underweighted relative to maintenance fires. Make days-vacant a tracked metric Leasing owns.
- Preventive maintenance & inspections. The cheapest way to cut emergency spend, always deprioritized under reactive work orders. Cron-driven, agent-perfect.
- Owner onboarding. A bad first-90-days is the top cause of first-year owner churn. BD closes the door; onboarding keeps it. Build it as a checklist sub-agent, not an afterthought.
- Security-deposit accounting & statutory timelines. Return-deadline misses carry statutory penalties. Pure deadline discipline, agent-perfect, owner-forgettable.
- Licensing / rental registration / lead-paint (RRP). Quiet until an audit or a fine. A cron-watched compliance checklist.
8. One-page summary
| Department (full agent) | Build phase | Key sub-agents / engines | Highest-risk skill |
|---|---|---|---|
| Orchestrator | (n/a) | (n/a) | approval routing |
| Property Ops / Maintenance | (n/a) | turn-scope builder | after-hours emergency |
| Leasing | 1 | screening run; renewals scorer | Fair Housing gate (calls Compliance) |
| Accounting / AP-AR | 2 | trust reconcile (human-gated); report builder | trust accounting |
| Resident Relations & Collections | 3 | (n/a) | delinquency to eviction pipeline |
| Compliance (cross-cutting) | 4 | (n/a) | vendor COI / Fair Housing / eviction gates |
| Business Development | 5 | onboarding checklist runner | owner onboarding |
| Platform: Dev / Analyst / Code review | continuous | sub-agents as needed | (n/a) |
Closing
The temptation with agents is to spin up a bot for everything: a leasing bot, a maintenance bot, a screening bot, a collections bot, and end up with a swarm nobody can supervise. Don't. Think like an org designer: one orchestrator, a handful of department-agents that own outcomes and relationships, and a deep library of skills and sub-agents underneath them. Build the highest-ROI department first, gate the money and the legal-risk functions behind a human from day one, and pull compliance forward before it bites you.
So here's the question for your own shop: if you mapped every function you run onto full-agent / sub-agent / skill today, how many things are you about to make a standing bot that should really just be a skill? Start there.
Sources
- How to Structure a Property Management Company, Second Nature
- Departmental vs Portfolio, Blanket
- Departmental vs Portfolio, Access PM Group
- How to Organize a Property Management Company, BetterWho
- What is Trust Accounting, Rentvine
- Trust Accounting & Owner Retention, Rentvine
- Vendor Compliance Guide, NetVendor
- Rethinking Org Design in the Age of Agentic AI, MIT Technology Review
- Governing the Agentic Enterprise, Berkeley CMR
- A Taxonomy of Hierarchical Multi-Agent Systems, arXiv 2508.12683
Get the next one
Want more like this?
New essays on building agents for property management, straight to your inbox.