A firm at 80 units and a firm at 400 units are usually described as the same business at different sizes. They are not, and the difference is not the number of units.
Ask anyone who has grown through that range where it got hard and you will not get a unit count. You will get a story about a specific inquiry that nobody answered, or a showing two people both thought the other had covered, or an applicant who waited four days for a decision because the person who had the information was on holiday.
Those are not scale problems. They are handoff problems, and they arrive on a schedule that has nothing to do with how many doors you own.
It breaks at a handoff count, not a unit count
A leasing process has four handoffs in it, and each one is a place where something can be dropped:
- Inquiry to whoever answers it. Between a person asking and a person replying.
- Reply to showing. Between someone wanting to see it and it being on a calendar.
- Showing to application. Between attending and applying, which is where the most silent loss happens.
- Application to decision, and the decision to the applicant. Between having what you need and someone hearing back.
At one person, there are no handoffs. That person is the process, and they hold the whole state of it in their head. Every handoff you add is a place where information has to survive a transfer between two humans who are not in the same conversation.
The first one to fail is almost always the first one. Inquiry to reply is highest-volume, lowest-ceremony, and it has no artefact — a showing has a calendar entry and an application has a record, but an unanswered inquiry leaves nothing behind. Nobody discovers it. It is not on any list of things that went wrong, which is precisely why it is the most expensive.
Roughly 50 to 120 units: one person is the system
Everything works, and it works well. One person knows every property, remembers who called on Tuesday, and can answer any question without looking anything up. Response times at this size are frequently better than at firms ten times larger.
The failure mode is not the process. It is that person. Their holiday is a service outage. Their resignation is an institutional memory loss. And nothing in the operation is written down, because writing it down has never once been necessary.
What to do about it here is not "add process". It is to notice that the firm's leasing rules exist only in one head, and that the cheapest moment to write them down is now, while there is still one head to ask.
Roughly 120 to 250: the first handoff, and the first silent loss
A second person arrives, and the four handoffs stop being theoretical.
This is where the first dropped inquiry happens, and — this is the part that matters — it is also where nobody finds out about it. At 80 units the same drop would have been noticed, because one person was tracking everything. At 200 units, with two people, an inquiry that neither picked up simply does not exist. There is no gap in the record, because there is no record.
The instinct at this stage is to add a rule: always cc the shared inbox, check the folder twice a day. Rules of that kind work exactly as long as everybody is having a normal week.
The other thing that shows up here is inconsistency, and it is subtler than a dropped lead. Two people now answer the same question, and they answer it slightly differently — not because either is wrong but because the firm's actual policy has never been written anywhere. An applicant who gets one answer on Monday and a different one on Thursday concludes something about your firm, and they are not wrong to.
Roughly 250 to 500: coordination outruns unit count
Here the arithmetic turns over. Adding units adds work linearly. Adding people adds coordination faster than that, because every pair of people is a new handoff and every property type is a new set of exceptions.
The calendar becomes the bottleneck rather than the inbox. Who is covering which territory, which showings are whose, what happens when two of them are out on the same Thursday. And the firm is no longer holding one kind of thing: at 300 units you are typically holding a couple of buildings, a few dozen houses and a handful of condos, run by three people with different patches and different habits.
The failure at this size is rarely that anyone is idle. It is that a rising share of everyone's week is spent on the coordination itself — and coordination work is invisible on any report you are likely to be running.
A word on how to read those three bands. They are structural observation, not survey findings. There is no study that says the first handoff fails at 137 units. The bands describe the order in which things break and roughly when to expect them, and your own numbers will differ.
Why "one person per hundred units" is measuring a different job
Everyone in this industry has heard the ratio. It is worth knowing exactly what it is and what it assumes.
It is a rule of thumb, and it is old. Writing on the NAA News Hub in April 2022, Brittney Nelson noted that "for at least 20 years, many in the apartment industry considered a ratio of one team member for every 100 units the standard for onsite staffing" — and argued it has become unsustainable, proposing something closer to one per 45 to 61 units. Writing on Multifamily Insiders in August 2025, Laura Bruyere described the same figure as a "long-standing rule of thumb" and offered no data source for it, because it is industry convention rather than a finding.
That is the first thing to know: it is folklore, not research. Nobody publishes it as a result, and both of those industry pieces are arguing against it rather than for it.
The second thing matters more for a scattered portfolio. Look at the word onsite. The ratio comes from single-site multifamily, where the leasing office is inside the asset. In that job travel time between properties is zero — the next unit is upstairs. Everything article four in this series measured, the slot-plus-the-drive, is assumed away entirely.
Applied to a scattered portfolio, the ratio is not aggressive or conservative. It is measuring a different job. And the assumption holds on both sides of the border: US garden-style multifamily and Canadian purpose-built rental both put the office inside the asset, so the correction applies in both markets for the same reason. A firm with thirty houses across two suburbs is not understaffed relative to the ratio — it is outside the ratio's domain.
We are not offering a replacement number, because we do not have one and neither does anyone else. What we would say is that any ratio you use has to have travel in it, and the only source for your travel is your own calendar.
The mixed-portfolio problem
This is where the growth story actually resolves, and it is the point of the whole article.
A firm at 300 units is rarely holding 300 of the same thing. It is holding a walk-up, a set of scattered houses and a few condos — three genuinely different leasing jobs with different showing logistics, different applicant pools and different turn profiles.
One standard workflow across all of it is what breaks first, and it breaks in a way that looks like a people problem. The process is tuned for whichever property type the firm started with, usually the buildings, and every house is handled as an exception. Exceptions are unwritten, unwritten steps depend on the person, and depending on the person is what you were trying to grow out of.
Releaser offers custom configuration for different property types, so the buildings and the houses do not have to run one process. It is worth being precise about why that matters at this size specifically: at 80 units, exceptions are fine — one person remembers all of them. At 300, exceptions are how work goes missing.
Which of these are hiring problems, and which are not
An honest split, because the answer is usually assumed rather than examined.
Hiring problems. Showing capacity — a person can only be in one place at a time, and beyond a certain number of showings a week you need another person or another model. After-hours coverage, if you insist on humans doing it. Anything that scales strictly with volume.
Sequencing and configuration problems. Dropped inquiries — a second person doubles capacity and also doubles the chance nobody owns a message. Inconsistent answers, which get worse with headcount until the rules are written down. Coordination overhead, which is the cost of the extra person. And the mixed-portfolio problem above, which no amount of hiring solves.
The reason this split is worth making is that hiring against a sequencing problem makes it worse, and it is the most common expensive mistake in this range: a firm adds a third person to fix dropped inquiries and now has three people who might each think somebody else replied.
Two numbers worth tracking before you hire
How many inquiries went unanswered for more than a day, and where they arrived. Sample a month by hand if you have to. If they cluster on evenings and weekends, that is a coverage problem and the answer is a front door that stays open. If they cluster on your busiest person's days, it is a routing problem inside your own team.
How many hours a week go to coordination rather than leasing. Scheduling, chasing internally, working out who has which property, rebuilding context somebody else already had. Nobody measures this and it is the number that decides whether the next hire pays for themselves.
Where this is going — not available today
Everything in this section describes work in design. It is not available today and there is no announced date.
Releaser is designing a layer that would let a firm write its own leasing policies down once — hours, criteria, tone, what always goes to a person — and have routine applicant correspondence follow them, so a growing firm's rules live in a document rather than in the most experienced person's memory. Enterprise white-label and custom builds are the intended expansion direction for larger firms. One thing is settled in the design rather than on the roadmap: nothing in that layer decides on an applicant. That stays with the operator.
Releaser is available to property management firms in the United States and Canada managing 50 to 500 units, with custom configuration for different property types.
Sources. Staffing-ratio discussion: Brittney Nelson, "Changing the Paradigm of Staffing Ratios", NAA News Hub, April 2022; Laura Bruyere, "1 person = 100 units. Is that working in today's multifamily world?", Multifamily Insiders, August 2025 — both cited as industry convention, not data. Canada: CMHC 2025 Rental Market Report. United States: National Apartment Association on its 2024 Income/Expense IQ. The growth bands are structural observation, not survey findings.