Here is a pattern that repeats in almost every growing property management company. The portfolio expands, the team feels stretched, so you hire. It helps, for a while. Then you hire again. And somewhere around the third or fourth round, someone in finance looks up from the numbers and notices something uncomfortable: the team is a third bigger than it was last year, and the operation is not a third faster, or a third more profitable, or a third easier to run.

The question most operators ask at that point is how many units one employee should be able to handle. It is the right question, but the honest answer is that there is no single number, and chasing someone else's number is how portfolios end up either burnt out or overstaffed. What the ratio actually tells you is something more useful: whether your business is growing or scaling.

The Benchmarks, and What They Are Worth

The oldest rule of thumb in multifamily is one employee per 100 units. It has been quoted for two decades, and the National Apartment Association has published a fairly blunt argument that it no longer holds, proposing something nearer one per 45 to 61 units once resident expectations and scheduling reality are accounted for.

The measured picture sits somewhere else again. Setting Census rental counts against Bureau of Labor Statistics employment data, AppFolio's economists put the US average at 54 rental units per employee, and the regional spread is wide: roughly 35 in Salt Lake City, roughly 77 in New Orleans.

Two things about that figure matter. It counts every office employee, accounting and admin included, so a front-line manager's real load runs higher than 54. And the variation is not random. Markets with more large buildings employ proportionately more people per unit, because concierges, security, and common-area maintenance do not scale down.

Our own thresholds for when to add staff put a well-supported residential manager at 100 to 150 units, falling to 50 to 70 without proper systems. Notice what moves that number. Not effort, not experience. Systems.

That gap is the whole subject of this article, because it is not really a staffing question. It is a leverage question.

The Ratio That Predicts Your Margin

Units per employee is one of two numbers worth watching. The other is cost per unit under management, and together they tell you which kind of company you are running.

Growing means your costs rise in step with your units. Scaling means your capacity rises faster than your costs. From the inside the two feel identical: more units, more activity, more revenue every month. The difference hides in the unit economics.

• If cost per door holds flat or creeps up as you add units, you are growing. Each new property is carrying its full weight in cost, sometimes more.

• If cost per door falls as you add units, you are scaling. You are absorbing new properties into capacity you already built and paid for.

That is the entire test. A business that is truly scaling gets cheaper to run per unit as it gets larger, and its units-per-employee figure climbs while it does. A business that is only growing gets more expensive per unit, and usually cannot say exactly when that started.

The headcount model almost guarantees the expensive version, because it welds capacity to payroll. If the only way to do more is to hire more, cost climbs at exactly the rate capacity does, and the economies of scale you were counting on never arrive.

Why More People Eventually Returns Less

This is not a motivational point about working smarter. It is structural, and the clearest description of it does not come from real estate at all. It comes from software, where teams hit the same wall decades ago and someone finally sat down and wrote out why.

Brooks's Law, Borrowed From Engineering

Fred Brooks spent years running large software projects, and in The Mythical Man-Month he landed on an observation that has held up remarkably well: adding people to a late project often makes it later. Not because the new people are bad, but because coordinating them costs more than the output they bring. He was describing programmers. He could just as easily have been describing a leasing team in its third round of hiring.

The mechanism is coordination math. Two people have a single line of communication between them. Five people have ten. Ten people have forty-five. The connections you have to maintain grow much faster than the headcount does, and every one of them is somewhere a handoff can drop or an afternoon can vanish into alignment. Past a certain size, a real slice of each new hire's week goes not to the work but to the overhead of being one more node in a busier network.

The Costs Nobody Puts on the Org Chart

Coordination is only the first tax. There are two more.

The hire itself, before any output.
The BLS puts average annual pay in residential property management at $69,700, and salary is only the visible part. Recruiting spend, the seat sitting empty while you fill it, and the months of partial productivity that follow all land before the first day of full output. A company that grows by hiring pays that tax again on every hire, over and over, at precisely the moment it is trying to move fastest.

Key-person risk.
The more your operation runs on what people remember rather than what your systems record, the more brittle it gets. When the one person who knew how a process worked moves on, the process leaves with them, and you pay all over again to rebuild it.

Stack these up and the conclusion is hard to avoid. Beyond a certain point, each new hire returns a little less than the last, because more of their effort is being eaten by the cost of the organisation simply being larger.

The Scaling Ceiling
There is a point where this stops being a nuisance and becomes the thing holding you back. We call it the scaling ceiling: the level at which the value of your next hire is mostly consumed by the cost of adding them.

Under the ceiling, hiring works and feels like it works. Above it, you keep hiring and the operation refuses to get easier. You add three people over two quarters and somehow the close is still late and the maintenance backlog is still there.

The cruel part is that nothing marks the line. You only recognise the ceiling in hindsight, usually after a year of hiring that did not pay off like the year before. Operators who miss it respond the only way they know, by hiring harder, which quietly makes the problem worse.

What Actually Raises Units Per Employee

Leverage is anything that lets output grow without labour growing at the same pace. It comes from four places, and the operators whose ratios climb tend to have built all four on purpose.

Standardisation

A written process does the remembering, so the skill lives in the system instead of in someone's head. Ten people each running move-outs their own way gives you ten different results and no way to train the eleventh. One documented workflow makes that eleventh hire useful in days rather than months. That is most of the gap between a manager capped at 50 units and one comfortably carrying 150.

Automation

Some of the work does not need a person at all. Rent reminders, late fees, work-order routing, renewal notices: rule-based, repetitive, and quietly enormous in the hours they eat. Hand them to software and you get back capacity you never had to interview for. Our guide to property management automation tasks covers where the payoff runs highest.

Self-Service

This is the one operators leave on the table. Every time a tenant pays through a portal, files a maintenance request with a photo, or books an amenity themselves, they are doing a piece of work your team used to do. Across a full portfolio that adds up to a role or two you never had to fill. Residents tend to prefer it anyway, since nobody enjoys waiting on hold.

Unified Data

The least glamorous and often the largest. When leasing, maintenance, and accounting pull from the same record, a whole category of work just disappears. Nobody starts the morning getting three systems to agree before anyone can act. Nobody rekeys the same tenant detail into a second tool. The reconciling, the cross-checking, the "let me confirm that figure and come back to you," all of it thins out, because there is only one figure to confirm. It is dull, invisible leverage, and it is usually where the biggest hours are hiding.

None of these four asks you to hire in proportion to your unit count. That is the point of them.

How to Tell If Your Leverage Is Working

• Units per team member is trending up, not sitting flat.

• Cost per door falls, or at least holds, as the portfolio grows.

• New hires hit full stride in weeks, because the process carries them rather than a mentor's spare time.

• Taking on a block of units does not automatically mean a matching block of hires.

• Your team spends its hours on judgment and relationships, not on retyping data and chasing numbers.

When those move the right way, the leverage is real rather than hoped for.

Where the Technology Comes In

Leverage has to live somewhere. Standardisation, automation, self-service, and unified data run on a platform, and this is where software stops being a line item and becomes the engine that separates output from headcount. A pile of disconnected point tools cannot do it, because the seams between them recreate the exact manual, coordinating work you were trying to delete.

That is the problem RIOO is built for, and the capability split is worth being precise about, especially if you are the person signing off on it:

• Property operations, leasing, maintenance, move-in and move-out, tenant and owner self-service, and facility management run inside RIOO as a purpose-built property management layer.

• Finance, consolidation, multi-entity accounting, and reporting are handled by the NetSuite core RIOO is built on, which is where that depth is native.

• The two share one record, so operational and financial data stop drifting apart, and the reconciliation tax largely goes away.

The scale that architecture supports is not hypothetical: RIOO runs more than 180,000 units under management across residential and commercial portfolios. The day-to-day effect is the unglamorous kind finance teams care about. The couple of hours someone used to spend reconciling occupancy against the ledger before a Tuesday review turns into the two minutes it takes to open one report.

When You Should Actually Hire

None of this is an argument against hiring. It is an argument about what to hire for. For anything that genuinely needs a human, discretion, relationships, a difficult owner conversation, people are the right call and always will be.

Most conventional advice says to hire ahead of demand. For routine, rule-based work, that advice is quietly wrong, because you are staffing up for volume leverage could have absorbed for free. The error is reaching for headcount to solve problems that are really about standardisation, automation, self-service, and data.

So the answer to how many units one employee should manage is: more than they manage today, and the number should keep moving. If it has been flat for two years while the portfolio grew, the ratio is not telling you to hire. It is telling you the leverage was never built.

Book a RIOO Demo

RIOO gives enterprise property teams the standardisation, automation, self-service, and shared data that let a portfolio grow without the payroll growing beside it. Book a demo and see what your units-per-employee number could look like.

Frequently Asked Questions

How many units can one property manager handle?
There is no universal number. Measured across all staff, the US average is about 54 rental units per employee, ranging from roughly 35 in Salt Lake City to 77 in New Orleans. A well-supported residential manager typically handles 100 to 150 units, dropping to 50 to 70 without proper systems. Asset type, building size, turnover rate, and how much routine work is automated move the figure more than manager experience does.

What is a good property management staffing ratio?
The long-standing multifamily rule of thumb is one employee per 100 units, though the National Apartment Association has argued for something closer to one per 45 to 61. Measured company-wide across all staff, the US average is about 54 units per employee. Treat all of these as starting points. The more useful test is direction: a healthy operation sees units per employee rise over time while cost per unit under management falls.

How do you scale a property management business without adding staff?
Build leverage rather than headcount. Standardise processes so capability lives in the system, automate rule-based tasks such as rent reminders and work-order routing, move routine requests to tenant and owner self-service, and unify data so the team stops reconciling between tools. Each raises output without raising payroll at the same rate.

Why does adding people stop improving operations at some point?
Coordination cost grows faster than the output new people add, the pattern known as Brooks's Law. Ten people maintain forty-five communication paths against a two-person team's one. Add recruiting cost, ramp-up time, and key-person risk, and each new hire eventually returns less than the last. That turning point is the scaling ceiling.

What is the difference between growing and scaling a property portfolio?
Growing adds cost in step with output, so cost per unit stays flat or rises. Scaling adds output faster than cost, so cost per unit falls as the portfolio grows and units per employee climbs.

When should a property management company actually hire?
When the work genuinely needs human judgment, relationships, or discretion, and once leverage has already absorbed the routine volume. Hiring is the right tool for what only people can do, not for tasks that standardisation or automation could have handled.