Growth does not always break bad processes. Quite often, it exposes the limits of good ones.

A property management company may have an experienced team, reliable routines, long-standing relationships with residents and contractors, and a way of working that has served it well for years. Nothing is obviously wrong. Requests get handled, bills go out, residents know whom to call, and managers know how to solve problems when they appear.

Then the portfolio grows. There are more buildings, more residents, more requests, more contractors and more people involved in every decision. What used to be handled through experience and personal coordination starts taking more time. Information becomes harder to follow. A process that worked perfectly well for three buildings becomes surprisingly fragile at ten.

This is where the idea of operational maturity becomes useful. It is not about dividing property management companies into “modern” and “outdated,” or “good” and “bad.” It is about understanding how much of the operation has become a repeatable system, and how much still depends on individual effort.

We explore this idea in the book From Night Alarms to 24/7 Digital Resilience, which looks at the shift from reactive property management to structured digital operations.

One of the questions behind the book is simple: which of the routines that made a company successful at its current size will still work at the next one?

Communication usually works — until volume changes

Most experienced property managers already know how important communication is. Residents need to know where to go with a problem, they expect a response, and they want to understand what is happening when something takes time.

The issue is rarely whether communication exists. The more interesting question is how it is organized.

If the number of residents doubled tomorrow, could the team maintain the same level of responsiveness without doubling the stress? Does everyone work from the same communication history, or does part of the context live in one manager's phone or inbox? If that person goes on holiday or leaves the company, can somebody else pick up the conversation without asking the resident to explain everything again?

A communication process can feel very strong precisely because the people running it are good at their jobs. But when continuity depends heavily on particular employees, growth makes that dependency increasingly expensive.

The book describes the same distinction as the difference between a stable process and a scalable one: individual effort can create excellent service, but structure is what allows that quality to survive growth.

The same is true of service requests

Property management teams accumulate an enormous amount of practical knowledge. An experienced manager often knows almost instinctively who should handle a particular problem, which contractor is reliable and which issue needs to be escalated immediately.

That experience is an asset. The difficulty begins when the organization cannot see or reuse it.

Can you follow a request consistently from the moment it arrives until it is resolved? Can you see where delays usually happen? Can you compare what is happening across several buildings rather than investigating them one by one?

If the answer depends on someone remembering to follow up, checking a messenger thread or asking a colleague what happened, the service may still work — but the cost of keeping it working grows with the portfolio.

Operational maturity does not mean replacing experience with software. It means turning experience into a process that other people can follow and the company can actually analyze. The original framework in the book makes exactly this distinction between a team that knows how to solve problems and a system that makes those solutions visible and repeatable.

Billing has its own version of the same problem

A billing process can be perfectly accurate and still be difficult to scale. The useful questions here are not only whether invoices are calculated correctly. They are also whether residents can understand the logic behind them, whether a new service can be added without creating a large amount of manual work, and what happens when an adjustment has to be made.

As portfolios and service models become more complex, the difference between an accurate billing system and an adaptable one becomes increasingly important. A process designed around a fixed set of charges may work for years. But if every change requires another spreadsheet, manual recalculation or workaround, growth starts turning accuracy into administrative overhead.

Adding something new should not make everything else harder

This becomes particularly visible when a management company wants to introduce a new resident service, payment method, access system, booking tool or other digital feature. Almost anything is technically possible. The better question is how difficult it is to add.

Does each new service require another standalone system? Does the team have to maintain another database or repeat the same information in several places? Does an integration affect workflows that were already working?

If every improvement makes the operation more complicated, the limitation may not be the team's ability to innovate. It may simply be the architecture underneath it.

This is why modularity matters increasingly in property management. A mature operation should be able to evolve without having to rebuild itself every time a new requirement appears.

And then there is the part that is hardest to measure: the team

Strong managers are very good at hiding weak systems.

They remember things. They follow up. They know who needs to be called. They notice when something has been forgotten and fix it before it becomes visible to the resident.

From the outside, the operation may look perfectly efficient.

The cost shows up elsewhere: in constant coordination, too many decisions being made in chats, interruptions throughout the day, and the feeling that everything works as long as the right people continue holding it together.

That can be sustainable for a long time. It simply becomes harder to sustain as the business grows.

The goal of digital infrastructure is not to remove those people from the process. It is to stop using their attention and memory for work that a system can carry instead. As the framework in the book puts it, when processes live primarily in people rather than systems, growth increases fatigue instead of creating leverage.

So how mature is your operation?

There is no single point at which a property management company becomes “digitally mature.” A company can be highly structured in billing and still rely heavily on manual coordination for service requests. Communication may scale beautifully while introducing a new service remains unnecessarily difficult.

That is why we turned the operational maturity framework from the book into a separate Operational Maturity Check.

It contains 18 questions across five areas: communication, service handling, billing, service expansion and team load. Each statement is scored from 0 to 2, giving a total score from 0 to 36.

The number is useful, but it is not really the most important part.

What matters more is noticing where the lowest scores appear. Those are often the places where the company is already compensating for structural limitations with extra time, attention and manual work — and where growth is most likely to create pressure next.

You can use the check on your own, but it may be even more useful to complete it with someone else on the team. If two people give very different answers to the same question, that difference is useful information in itself.

Download the Operational Maturity Check

And if the assessment raises questions about how to move a particular process from manual coordination to a more scalable structure, talk to us. That is exactly the kind of operational problem Unitify was built to solve.