How to compare multifamily maintenance software

We sell one of these, so read the framing accordingly. The questions are the part worth keeping.

Feature lists do not separate products in this category. Everyone has work orders, a mobile app, photo upload, and a dashboard. What differs is whether techs use it, what happens to the work that does not fit a clean category, and whether the numbers are trustworthy.

The one that predicts everything else

1. What is your tech adoption rate, and what is the denominator?

Ask for the number and the population it is measured over. Then ask for the lowest-adoption property in that portfolio, because the average hides the interesting case.

Ours is 94% across 24,000 units and 100+ properties. Our lowest-adoption property sits at 46%. A vendor who cannot produce the low end either does not measure it or does not want to say.

Adoption is the precondition for everything else. Analytics on partial logging measures documentation habits rather than performance.

The three about work that does not fit

2. Show me a unit turn on the board, with the stage timestamps. Turn time is the maintenance metric that lands directly in NOI. Ask whether every stage is timestamped or only the endpoints. Without stage timestamps you know a turn took 11 days and nothing about where it went.

3. What happens to a high-risk work order? Water intrusion, pool, light inspections. Ask whether the photos are required or optional, whether the steps can be skipped, and whether a single person can close it. Optional documentation is documentation that does not exist when an insurer asks.

4. How does preventative maintenance get scheduled across a portfolio? Per-property manual scheduling does not survive 100+ properties. Ask whether templates can target by year built, vintage, and market, and whether the fan-out is automatic.

The two about your stack

5. Which PMS do you integrate with, what is the sync interval in minutes, and is it two-way? Ours is ResMan only, real time, two-way. We do not integrate with Yardi, RealPage, AppFolio, or Entrata, and if you run one of those this is a short evaluation.

6. Where does the integration use the API and where does it use interface automation? Where a PMS API does not reach, some vendors automate against the interface. That works, and it is a different reliability profile. Ask which parts of your workflow depend on which.

The three nobody asks

7. What does the product do about language? A meaningful share of maintenance techs in this industry prefer to work in Spanish. A tool that only works in someone's second language, for a job where precision matters, is a daily friction that shows up as low adoption rather than as a complaint.

8. Does a tech's personal phone number get exposed to residents? Techs care about this a great deal. Masked calling should route through a bridge. Most products do not address it.

9. What is your callback rate reporting? If the product cannot tell you which completed work orders came back, it cannot tell you anything about quality, and its completion metrics can be gamed by closing badly.

Where we are the wrong choice

If you are on Yardi, RealPage, AppFolio, MRI, or Entrata, we do not integrate. That ends the analysis, and there are products that do.

If you are enterprise scale and need the procurement posture that comes with it, formal SLAs, vendor questionnaires, a named implementation team, an incumbent with more staff meets all of that without a conversation.

If you primarily need a vendor network rather than internal workflow, some products in this space are built around a pre-vetted contractor marketplace and we are not.

If you run a single property, the PMS module plus a whiteboard is genuinely adequate and you should keep your money.

Run a document test rather than a demo tour

Demos show the happy path. Bring the unhappy one.

Pick your worst property, not your best. Ask for a live view of its open backlog over 90 days. Then bring three real scenarios: a water intrusion event from last quarter, a unit turn that ran long, and a resident ticket that generated a callback.

Ask each vendor to walk those three through their product with your data. That takes an afternoon and it tells you more than a quarter of feature comparisons.

Which of the nine does your current tool answer badly?