Property managers, your software problem is one of three, and each one needs a different fix

Three problems that all arrive sounding the same

Start with what sits underneath all of them. You serve three groups at once, and almost every piece of software you own treats them as variations of one user. The owner or the board pays your fee and can end the contract. The resident generates most of your daily work, didn't choose you, and can't easily leave. Your own coordinators absorb whatever the other two can't do themselves, and nobody surveys them, which is why they quietly set your capacity.

In most businesses the person who creates the work is the person paying for it. Here they aren't, which is why one underlying complaint reaches you in three different shapes.

The first is the shape of the cost. You feel it at renewal, it grows with a number somebody else counts, and the honest answer to what you'd change about your software is the invoice. That one is a counting exercise before it's ever a build.

The second is the surface. What a resident opens on a phone, what an owner logs into, what your coordinator stares at for six hours a day. It's the layer where your firm is genuinely different from the one across town, and the one you control least, because it arrived attached to the accounting underneath it. Those two layers get sold as a single product, which is why this question keeps getting asked as all or nothing when it isn't.

The third is that the work happens in buildings, and the record of it lives with people rather than in a system. A repair gets reported in a hallway, done by a vendor who doesn't work for you, and closed by a superintendent who mentions it to somebody. The office keeps whatever survived that trip, which in a lot of firms means personal phones and one person's inbox. Fine, right up until somebody asks you to produce it.

Only the second one is obviously a software project. The first is arithmetic, and the third is as much about who owns a step as about which tool they use.

How to tell which one you have

Look at who keeps raising it, and how often. If it's your finance lead, once a year, at renewal, that's the first problem, and it gets settled with a spreadsheet rather than a project. Put your door count and your annual software bill on the same chart for the last three years, then put revenue per door beside them. If the first two lines are parallel and the third isn't, you've found something worth going to look at properly.

If it's owners or a board raising the same thing repeatedly, or residents phoning about something they could have looked up, that's the surface. The question worth asking is whether what they want has a field for it in what you already run. Something the platform has no concept of is a far stronger case than something it does awkwardly.

And if the complaint is that nobody can say what happened, when, or where the photo went, it's the third. Take one routine repair from the resident's first message through to the vendor's invoice being coded, and count every point where somebody retyped something. That number tells you whether this is a software problem or a process problem. If work orders aren't being logged today, a better tool won't get them logged.

Where each one gets answered

Three pages sit under this one, and they aren't interchangeable.

If the problem is the cost shape, or you honestly don't know whether to build at all, start with product strategy for property management. That page is about deciding rather than building, and it ends in a recommendation. One of the available recommendations is not to build.

If it's the surface, and what you're picturing is a portal residents or owners log into, web app development for property management covers what that build involves, surface by surface, and what the boundary with your accounting system does to the price of it.

If it's the work in the building, start with mobile app development for property management. Most of that page is about when a native build isn't the answer, and what has to be true of your residents and your site staff before it is.

These overlap, and firms tend to arrive at them in that order. They're bought separately though, and buying the third when the problem was the first is an expensive way to learn the difference.

What we'd talk you out of

A resident app because a competitor has one. If your residents' complaint is that repairs take too long, an app gives them a faster way to watch a repair take too long.

A dashboard for a question you've asked twice. Some things are a query somebody runs, not a screen somebody maintains.

And starting a build while a large management contract is up for renewal or the portfolio is mid-acquisition, because the requirements move underneath you and the work gets judged against a business that no longer exists.