← All Journal articles

Property Operations

More Doors per Employee Is Not an AI Strategy

A higher doors-per-employee ratio may reflect real AI-enabled capacity—or outsourced work, overtime, shifted costs or deferred service. Multifamily owners need a fuller scorecard and a comparable pilot before treating the ratio as ROI.

Sunlight casts diagonal shadows along an apartment corridor with terracotta walls and blue entry doors.

The ratio is a claim, not the return

A higher doors-per-employee ratio can be good news. It may mean the operation removed manual steps and gave managers more time for judgment, field decisions, exceptions and resident relationships.

It can also mean the work went somewhere less visible.

Units per employee can rise because work moved to a call center, vendor, offshore team, regional manager or owner. Headcount may fall while overtime, contractor invoices, unresolved work and service risk rise.

That makes the ratio a capacity indicator, not an AI return calculation. The owner question is whether the operation delivered useful capacity or stronger outcomes at an acceptable fully loaded cost, without transferring an undisclosed amount of labor, delay or risk elsewhere.

Give the ratio its fair hearing

There is a credible operating case for a higher ratio. A June 28, 2026 One Home Agent article argues that AI can handle repetitive intake, routine responses, follow-up, triage, documentation and tracking. It proposes moving from roughly 50–75 doors per residential manager to 120–150 or more while retaining human approval for higher-stakes decisions.

Useful AI can create real capacity. If a system handles defined, low-risk work and escalates exceptions reliably, an operator may absorb growth without hiring ahead of it. The return could also appear as better coverage, more consistent documentation or more time for work that requires human judgment.

But the proposed range is a vendor-authored assertion, not a controlled multifamily portfolio study. Treat it as a hypothesis. The article itself identifies risks involving edge cases, relationship depth, field responsiveness and escalation discipline. It recommends auditing current work, running a limited pilot and reviewing response and satisfaction measures before changing staffing assumptions.

That is the right instinct. Do not rewrite the staffing plan because one dashboard number improved.

Ask where the work went

Before accepting a higher ratio as AI ROI, ask what happened to the work.

Manual steps were removed. AI may eliminate duplicate entry, draft routine communications, route standard requests or assemble information staff previously gathered manually. That can create capacity, although drafting or routing one step does not mean the full service obligation disappeared.

The work moved internally. A central team may take over exception review, quality assurance, system administration or escalations. That can be a sound redesign, but its labor belongs in the analysis.

The work moved to a vendor. Outsourced maintenance coordination, after-hours coverage or leasing support may improve consistency and scale. Outsourcing is not a failure. It is also not free capacity merely because it sits outside W-2 headcount.

The work moved into additional hours. Stable headcount can conceal overtime, temporary labor, contractor hours or managers working beyond normal schedules.

The work was deferred. Work does not disappear because software sent an immediate acknowledgement. A resident still waiting for an answer, repair or escalation has not received resolution.

Count each destination consistently, including internal labor, overtime, contractors, managed-service fees, technology, quality review and exception management. The goal is not to favor internal labor over outsourcing. It is to prevent a change in accounting location from being presented as a productivity gain.

Normalize before discussing productivity

For an owner-controlled comparison, define FTE through paid hours within a fixed period and scope rather than names on an organization chart. Document onsite and regional staff, central-support allocations, salaried and hourly labor, overtime, temporary workers, contractors and managed-service work.

Portfolio mix matters too. Stabilized garden-style communities are not directly comparable with high-rises, lease-ups, affordable housing, scattered assets or older properties with heavier maintenance, compliance, inspection or reporting demands.

The 2022 NARPM Financial Performance Guide offers a useful historical warning. Its page 22 says the units-per-direct-team-member benchmark excluded companies with 20% or more occupied multifamily units. The guide described the resulting figures as relevant to single-family property management. That benchmark is not a 2026 multifamily staffing target.

If the denominator, asset mix or service scope changed, the before-and-after ratio is not a clean productivity comparison.

Current research does not make headcount reduction the AI thesis

AppFolio's February 18, 2026 release reports a survey of 1,617 U.S.-based residential property-management professionals conducted from September 26 through November 3, 2025. It found that 34% of AI adopters planned to increase headcount, compared with 25% of non-users.

That association does not show that AI caused the hiring plans, nor does it measure multifamily AI return. The release covers residential property-management organizations with different sizes, property types and operating models, not matched multifamily portfolios. It does show that fewer employees are not the only plausible expression of AI value. Created capacity might support growth, controls, coverage or service.

The National Apartment Association's 2026 Holding the Line research, conducted with Flex, surveyed nearly 400 multifamily professionals. Respondents included executives, property and regional managers, and practitioners in finance, HR, operations and asset management. NAA says the survey was fielded between mid-February and March 2026.

NAA reports broadly steady staffing alongside recruitment pressure, burnout and additional workload associated with adopting new technologies. Those conditions occurred together; the survey does not prove that technology caused burnout or that an AI tool failed to produce returns. It does make a staffing ratio an incomplete operating health check.

As of August 5, 2026, NAA's AI research review described uneven adoption and benefits commonly characterized as incremental rather than transformational. It also identified recurring questions involving data quality, cybersecurity, compliance, integration, governance and workforce readiness. Those issues belong in the return analysis because implementation can add training, oversight and exception-handling work.

Use an owner scorecard that catches cost shifting

The evidence reviewed does not establish a universal healthy staffing ratio. A practical scorecard evaluates the claimed benefit and its tradeoffs against a comparable baseline:

  • Capacity delivered: Measure defined work completed per paid FTE hour, not only units assigned per employee.
  • Fully loaded cost: Include labor, overtime, temporary staff, contractors, managed services, shared services, implementation and technology.
  • Aging unresolved work: Track priority, stage and age instead of allowing first-response speed to hide old work.
  • Repeat and reopened repairs: Watch recurring requests, repeat dispatches and work orders reopened after closure.
  • Response and resolution quality: Sample interactions for accuracy, documentation, routing and escalation. Automated acknowledgement is not resolution.
  • Owner outcomes: Define the intended result before the pilot, such as controlled growth, reliable reporting, cleaner exception management or fewer preventable escalations.

Not every measure must improve. Technology may cost more while producing better controls, or it may reduce administrative labor while requiring additional quality review. The owner needs to see those tradeoffs clearly and decide whether the resulting outcome supports the portfolio strategy.

Prove the gain before resetting staffing

A scoped pilot can provide a more credible test than a portfolio-wide ratio claim. Establish a comparable baseline, define the workflow and escalation rules, and keep service commitments steady where practical. Use matched cohorts or normalize material differences in asset type, occupancy, maintenance demand and staffing coverage.

Maintain one cost ledger from the start. Include configuration, training, output review, corrections and exception management. Those costs may be worthwhile, but they still belong in the return calculation.

Set portfolio-specific stop-loss measures before rollout. Reconsider or redesign the pilot if aging backlog, repeat repairs, missed emergency or compliance escalations, sampled quality or owner outcomes deteriorate beyond the portfolio's stated tolerance. No source reviewed establishes one universal trigger.

Useful AI should create more operating control and defensible capacity. More doors assigned to fewer names may be part of that result, but it is not the proof.

AI Management Consulting

Put perspective to work.

Discuss your priorities and budget. Build a plan around the support your team needs.

Explore consulting options