How many buildings can one property manager realistically handle?

Every property management agency owner tries to estimate this number. How many buildings can one manager actually handle, full-time? Industry conferences throw out numbers between 8 and 20. Your competitor claims 30. Your senior manager swears the real ceiling is 4.

They are all right, depending on what the manager spends the day doing. Let’s walk through it honestly.

The naive math

Most “buildings per manager” calculators assume something like this:

• 8 working hours per day
• ~30 issues per building per month, on average
• ~15 minutes of manager time per issue (read, reply, dispatch, follow up)
• A handful of administrative tasks (announcements, document handling, AGM prep)

Plug it in and you get 12–15 buildings per manager, easily. This is the number agencies use when they pitch investors.

The number a manager achieves in practice is 3–5. So where do the other 7–10 buildings of theoretical capacity go?

Where the time actually goes

The 15-minutes-per-issue figure is correct in isolation. Issues do not arrive in isolation. They arrive embedded in a stream of context-switching that destroys most of the day before any work gets done.

Communication overhead

A single plumbing issue in a group-chat-driven workflow generates, on average:

1. The tenant’s initial message (“water everywhere”)
2. The manager’s clarifying question (“which apartment?”)
3. The tenant’s photo + answer
4. Two or three other tenants chiming in (“yes, mine too”)
5. The manager’s holding reply (“I’ll call the plumber”)
6. The plumber’s separate WhatsApp DM
7. The plumber’s update an hour later
8. The manager re-posting the update into the building chat
9. A tenant asking when it’ll be fixed
10. The manager re-explaining
11. Confirmation when fixed
12. A second tenant confirming the leak stopped

That is twelve touchpoints for one issue. Even at 90 seconds each, you have burned almost twenty minutes, and you have context-switched twelve times. Each context switch costs another two to three minutes of “where was I again?” recovery time.

Multiply by 30 issues per building per month and you reach 15+ hours per building per month on communication overhead alone. Across four buildings, that is a full work-week before any real work gets done.

The phantom workload

The other thing the spreadsheet ignores: managers handle far more than reported issues. They also deal with:

• Tenants who call instead of message (“I didn’t want to bother the chat”)
• Tenants who message the wrong manager because they don’t know which manager handles which building
• Owners (where you’re a managing agent) who want monthly summaries
• Group-chat moderation duties, keeping the discussion productive
• AGM / Eigentümerversammlung / Skupština preparation, three or four times a year, that consumes entire weeks
• Payment chasing
• Insurance and compliance paperwork

This is the iceberg under the water. None of it shows up in “issues per building per month”.

The real ceiling

Talk to managers who have scaled past five buildings without burning out, and you find one common pattern: they have eliminated themselves from the routing layer. They do not decide who handles each issue. They do not relay information between tenants and fixers. They do not moderate group chats.

What they spend their time on instead:

• Reviewing the inbox once or twice a day, not 80 times
• Talking to owners about strategic things: budgets, renovations, vendor changes
• Onboarding new buildings
• Handling the 5% of issues that genuinely need a human’s judgment

A manager whose role is reduced to inbox triage + owner communication + escalations can comfortably handle 8–12 buildings. A manager whose role still includes being the routing layer will burn out at 4.

The difference comes from structure, not talent.

What changes the structure

Three things, in order of impact:

1. Direct tenant → fixer routing

When a plumbing issue is reported, the plumber gets a notification directly. The manager does not need to be in the loop until something escalates. This single change cuts about 60% of communication overhead.

2. A status field tenants can see

When a tenant can see “In Progress, assigned to Marko, plumber” without messaging anyone, you eliminate the “any update?” loop entirely. The manager stops being a status broadcaster.

3. Self-closing tickets

When a fixer marks the issue ready and the tenant taps Confirm, the issue closes. No follow-up message. No reminder. No “did the plumber actually come?” investigation.

These three together move the ceiling from 4 to 12.

The honest answer

If you are trying to estimate manager capacity for a planning model, here are realistic numbers based on the workflow:

Workflow	Buildings per manager
Group chat + phone calls	3–5
Group chat + spreadsheet for issues	4–6
Email-based ticket system	5–7
Structured ticket app with direct fixer routing	8–12
Same, plus a manager sharing load	12–16

These figures assume full-time managers with no other roles. Part-time figures scale roughly linearly down to about 30%. Below that, the per-building overhead (knowing each building, each tenant, each fixer) starts to dominate again.

Why this matters for the business

Manager capacity is the single most important number in a property management agency, because it determines your unit economics. If a manager handles 4 buildings and a building generates €X/month in fees, your revenue per manager is 4X. If the same manager handles 10 buildings, it is 10X, while your manager salary stays roughly the same.

That is why agencies that move to structured workflows can quote 30–50% lower fees than agencies still on group chats, and still make more money per manager. The cause is mechanical: they stop paying their managers to be human routers.

If you are running an agency and wondering why your margin keeps shrinking, look at what your managers do all day. The spreadsheet model is fine. The workflow under it is the problem.