Choosing property management software: a manager's field guide

Buying property management software is annoying because the market is bimodal. On one end you have legacy desktop systems built in 2003, designed for a German Hausverwaltung who needs to print Eigentümerversammlung minutes. They are wildly over-spec’d for everything else you need. On the other end you have a hundred startup apps that do issue tracking but ignore announcements, documents, multi-building scoping, and the actual structure of how your business is organized.

This guide is a practical filter. It lists the features that matter for a working building manager, and the features that demos brag about but nobody ever uses.

What you actually need (the eight)

1. Structured tickets, not just chat

The tool needs to model an issue as a record with a status field, an assignee, and a history. Anything that is “WhatsApp but for managers” is useless for the same reasons WhatsApp is.

If you cannot filter open issues across all buildings in two clicks, the tool is below the bar.

2. Multi-building scoping

You manage more than one building. Every screen needs to show one building or all of them, never some accidental mixture. Tenants of building A should never see issues, documents, or announcements from building B, even by accident.

If the demo cannot show you a clean way to switch building context, the underlying data model is wrong and you will fight it forever.

3. Three roles, real permissions

Owner / Manager / Fixer / Tenant. Each role sees a different surface. The owner sees money and managers. The manager sees buildings and tickets. The fixer sees only their queue. The tenant sees only their building.

If the tool has only “admin” and “user”, you will hand-roll permissions in your head and one day a fixer will see an invoice they shouldn’t.

4. Tenant onboarding via code, not email link

Email-link onboarding fails about 30% of the time. Links expire, links go to spam, tenants do not have email at all (very common in older buildings). A 6-character code that the tenant types into the app works for everyone.

If the tool has only email-link onboarding, expect to manually onboard your older tenants for the rest of time.

5. Per-building documents

The handful of documents tenants ever need: house rules, fire safety plan, AGM minutes, common-cost statement. Upload once per building, every tenant in that building gets access. PDF / DOC / image. Up to 25 MB per file is plenty.

If the tool has no document storage at all, you will keep emailing PDFs and that defeats half the point.

6. Announcements with reminders

Two categories: Event (with optional reminder 1h / 24h / 48h before) and Info. That’s all. Tenants get push notifications. Managers do not get reminders for events they themselves created.

If the tool has elaborate announcement workflows with approval chains and audit logs, you are paying for a feature that exists to satisfy a procurement checklist. It does not help a manager.

7. Audit trail on every issue

When an owner asks at AGM why an issue from November took three weeks, you need to produce a timeline. Every status change, every assignment, every comment. With timestamps.

This is also legally useful. In most jurisdictions, an audit log of how you handled a complaint is your defense if a tenant escalates.

8. Mobile-first, web-supported

90% of tenant interaction is mobile. 90% of manager interaction is also mobile (you are not at a desk, you are in a building). The web app is for the office tasks: heavy admin, billing, configuration.

If the tool is web-only and the mobile experience is “responsive web”, tenants will not use it and the whole thing falls apart.

What you don’t actually need (the impressive distractions)

“AI-powered” anything

Nine times out of ten this is a feature looking for a problem. Auto-categorizing tickets sounds great until you realize the manager can do it in 1 second per ticket and the AI gets it wrong 20% of the time.

Skip until the tool you already use adds it for free.

Built-in payment processing

Sounds amazing in a demo. In practice, tenants pay rent or common costs through whatever channel their country uses (bank transfer in DACH, direct debit in the UK, NLB / mBanking apps in the Balkans), and integrating payment into your management tool means rebuilding rails that already exist. Most agencies who tried this have rolled it back.

Vendor marketplaces

“Find a plumber through our app.” The plumbers in your city are people you already know, and the marketplace’s selection is worse than your own roster. This feature exists in pitch decks; nobody uses it.

Custom workflow editors

A drag-and-drop interface for designing your own ticket statuses. Sounds powerful. In reality you will use the default and never touch it. If you do touch it, you will create a workflow that confuses every manager who joins later. The standard 5-status model works. Do not over-engineer.

“Tenant satisfaction” surveys after every issue

Tenants will fill out one survey, then ignore the rest. Issue confirmation (Confirm Fixed / Reopen) is a much higher-fidelity signal, and it is free, because it is already part of the workflow.

The pricing reality check

Pricing in this space is wild. Some tools charge per building, some per unit, some per user, some per manager. A few are flat-rate. Here is how to think about it:

• Per unit pricing is the worst. It punishes you for managing buildings with many small apartments.
• Per building pricing is fine if the cap on units per building is high enough.
• Per manager pricing aligns with how value is created in your business. Your manager capacity is what scales.
• Flat-rate with feature tiers is the cleanest, especially if it includes a Free tier for evaluation.

A reasonable price for a small agency (3–5 buildings) is €30–80/month total. Anything above €200/month for a small agency is the legacy desktop market and you should run.

The 30-minute evaluation

When you trial a tool, do exactly this and you will learn whether it is any good in 30 minutes:

1. Sign up. Did it take more than 5 minutes? Bad sign.
2. Create a building. Did it ask for 17 fields? Bad sign. Two (name and address) should be enough to start.
3. Invite a tenant. Was the flow understandable to a non-technical person? Test on your own family.
4. Submit a complaint as a tenant. Was the form fast and forgiving? Did you have to choose a category before you could even type the issue?
5. Triage as a manager. Could you assign it to a fixer in two taps?
6. Resolve as a fixer. Could you mark it ready without typing a paragraph?
7. Confirm as the tenant. Did you get a notification? Was the confirm action one tap?

If all seven steps are fast and obvious, the tool is good. If any one of them takes more than 90 seconds, the tool does not understand the workflow.

A note on internationalization

If you are in a non-English-speaking market, language matters more than you think. A tool that is fully translated into your tenants’ language will get 30% higher adoption than one that is English-only, even when your tenants nominally speak English. People deal with their living situation in their native language.

Good tools internationalize the tenant-facing surface first, the manager-facing surface second, and leave the owner / billing surface in English. That is the right order, because the tenant is the user with the highest churn risk if the experience feels foreign.

The bottom line

You are buying back two to three hours a day of your own time. Treat the evaluation seriously, give yourself a real two-week trial on at least one building before you commit, and do not get distracted by the demo theater.

The right tool is the one that, two weeks in, you would refuse to give up. Everything else is noise.