Every Irish property manager starts the same way: a spreadsheet, a shared inbox, and enough attention to keep everything moving. For portfolios under 10 units, this works. The mental map is intact, nothing slips through, and the landlords are happy.
Then the portfolio grows. And the tools that got you here start working against you.
Here is what actually happens at each stage of portfolio growth — and what your systems need to do to keep up.
Stage 1: 1–10 units — The spreadsheet era
At this stage, one spreadsheet covers everything: tenancy start and end dates, rent amounts, deposit records, maintenance notes. The property manager knows every tenant personally. Issues are handled by phone and email.
What works: Low overhead. Fast decisions. No system cost.
What starts to strain: Anything that depends on memory. Rent review dates, RTB registration renewals, and maintenance follow-ups begin to slip when attention is divided.
What you need at this stage: At minimum, a shared calendar for key dates and a basic document folder structure per property. This is not the time for a full ERP — but it is the time to build habits that scale.
Stage 2: 11–30 units — The coordination problem
A second person joins. Now there are two spreadsheets, two inboxes, and no single source of truth. A rent review gets processed twice. A maintenance request sits in one inbox while the other person follows up on it separately. A landlord calls about an invoice that was already sent, but no one can find it quickly.
What breaks: Handoffs. When responsibility is shared across people without a shared system, information gets duplicated, dropped, or both.
What you need at this stage: A single shared system for tenancy records, maintenance tracking, and invoice history. This does not need to be a full property management platform yet — but it cannot be individual spreadsheets.
Stage 3: 31–75 units — The invoicing bottleneck
This is the stage where rent invoicing moves from inconvenient to unmanageable. At 50 tenancies, generating invoices manually takes 6–10 hours per month. Arrears tracking requires a dedicated weekly session. RTB compliance review dates are being managed in a spreadsheet that is always two weeks out of date.
8 hrs
Average time spent on manual invoicing per month at 50 units
23%
Of RTB reviews are procedurally late in non-automated portfolios
2 weeks
Typical arrears lag when tracking manually at this portfolio size
What you need at this stage: Automated rent invoicing, arrears dashboards, and RTB compliance date tracking — all in one connected system. This is the inflection point where operational software pays for itself within the first quarter.
Stage 4: 76–200 units — The reporting gap
Landlord expectations change at this scale. Owners with larger portfolios want monthly statements, not ad hoc calls. They want to see void rates, arrears totals, and maintenance spending per property. They are comparing your service to the professional agency down the road.
Meanwhile, the management team has grown. There is now a lettings manager, a property manager, and finance support — each working in a system that was not designed for three people with different roles.
What breaks: Reporting. The data is in the system but pulling a coherent owner statement or management report requires manual assembly from three different places.
What you need at this stage: Role-based access, automated owner statement generation, and management dashboards that show portfolio-level KPIs without requiring manual data extraction.
Stage 5: 200+ units — The compliance and scale challenge
At this scale, the compliance burden is significant. Hundreds of RTB registrations to maintain. Potentially dozens of rent review notices per year, each requiring correct procedure. A maintenance queue that runs hundreds of jobs per month. Payroll and contractor management for an in-house maintenance team.
The operational model is now a business, not a side function. And the systems need to reflect that.
| Stage | Units | Key Pain Point | Critical Capability |
|---|---|---|---|
| 1 — Starter | 1–10 | Memory-dependent management | Shared calendar & document structure |
| 2 — Coordination | 11–30 | Handoff failures between people | Single shared tenancy & maintenance system |
| 3 — Invoicing bottleneck | 31–75 | Manual rent invoicing & arrears lag | Automated invoicing + arrears dashboard |
| 4 — Reporting gap | 76–200 | Owner statements assembled manually | Auto owner statements + role-based access |
| 5 — Scale & compliance | 200+ | RTB compliance across hundreds of tenancies | Full compliance tracking + bulk operations |
The common thread
Across every stage, the pattern is the same: a tool that worked at the previous scale becomes the problem at the current one. Spreadsheets that worked at 10 units break at 30. Manual invoicing that was manageable at 30 is a liability at 75. Informal reporting that was fine at 75 is professionally unacceptable at 200.
The property managers who grow successfully are the ones who replace their tools one stage ahead of where they are — not one stage behind. By the time the pain is acute, you are already losing landlord relationships and team capacity to the inadequate system.
The question is not whether to upgrade your operational systems. It is whether to do it before or after the growth pains make the cost of not upgrading obvious.