Choosing tools5 min readUpdated 2026-08-01

Landlord maintenance app for 1–20 units: what actually matters

What a maintenance app must do for 1–20 units, and what it can skip: signs you’ve outgrown memory, the portal-adoption tax, a two-week trial checklist.

Most maintenance software is designed for property managers with hundreds of doors, dispatch boards, and a maintenance coordinator on payroll. You have six units and a phone. What matters at your scale is different — and so is the honest answer to whether you need an app at all.

First: do you actually need one?

Text-plus-memory is a legitimate system, and for many landlords with one to three units it genuinely works. You need something more when the cracks start showing. The recognizable signals:

As a rough rule of thumb from how this tends to play out: one to three units, memory usually holds; four to ten, the cracks appear; past ten, some system is no longer optional. Building age and tenant turnover move those lines — five old units can out-message fifteen new ones.

If none of the signals ring true, stop here and keep your current setup. Buying software for a problem you don’t have just adds overhead.

  • You found a forgotten request while scrolling for something else.
  • A vendor asked “which unit was that again?” and you had to check.
  • You can’t answer “what’s open right now, and what’s next on each?” inside a minute.
  • A move-out inspection surfaced damage from an issue that was reported — months ago.
  • Requests arrive through three channels (your texts, your email, your partner’s phone) and no single place holds them all.

The functions that matter — and the ones that don’t (yet)

At 1–20 units, maintenance handling comes down to six functions.

Everything else in “landlord app” marketing — listings, tenant screening, e-signed leases, rent collection, accounting — belongs to different jobs. Those features are valuable if you need those jobs done. If maintenance is the job that hurts, they’re weight: more setup, more interface, more places for a simple workflow to snag. Decide which jobs you’re hiring software for before comparing anything.

  • Intake where tenants already are. Requests must land in the system without depending on tenants changing behavior.
  • Threading. One issue, one conversation — every photo, reply, and update attached to it.
  • Instant acknowledgment. The tenant hears “received” fast, even when you’re driving, working, or asleep.
  • Status and next action. For every open issue: who moves it next, and what’s the step.
  • A review ritual. A short daily or weekly view of everything open, so nothing relies on your memory.
  • Vendor handoff. Getting the issue, photos, and access details to a contractor without retyping — and knowing the message actually arrived.

The portal-adoption tax

Here’s the trap built into most maintenance products at small scale: they solve your organization problem by creating a tenant behavior problem. The tenant must download an app, create an account, or accept a portal invitation before their requests enter your tidy system — Stessa, for example, tracks maintenance only once a tenant accepts a portal invitation, and portal-first tools generally assume tenants will change how they communicate.

Some tenants will. The rest keep texting you, because texting is how they talk to everyone and it has always worked. Now you’re running two systems: the portal with three requests in it, and your phone with the other nine. The portal didn’t fail — adoption did, and at 1–20 units you don’t have the leverage (or the appetite) to force it.

So ask any vendor two questions before looking at a single feature: what does my tenant have to install, join, or sign up for? And what happens to a plain text message sent to a phone number? If the answer to the first is “an account” and to the second is “nothing,” you’re buying the two-system problem. Tools built text-first — Tenvo is one, turning each tenant text or email into a threaded, auto-acknowledged ticket with nothing for the tenant to install — remove that tax by putting the structure entirely on your side.

Comparing cost honestly

Sticker prices at this scale run from free to roughly $50 a month. Some full platforms are free or nearly free to landlords because they monetize elsewhere — tenant-paid fees, paid add-ons — and if minimizing cash outlay is your criterion, a free full suite wins and this is a short conversation. A maintenance-only tool charges real money for a narrower thing (Tenvo is a flat $29/month).

The comparison that actually matters is workflow cost: what happens, in minutes and missed steps, when a request arrives? Who types what? What does the tenant have to do? What slips when you’re busy? A single leak that sat unread for four days costs more than a year of any subscription on this list — evaluate against that number, not against the difference between $0 and $29.

The two-week trial checklist

Whatever you pick, run it against real traffic for two weeks and grade it on the functions that matter:

A tool that fails on threading, acknowledgment, or the digest is failing at the core job, whatever else it bundles. Drop it, keep the spreadsheet, and revisit when the unit count grows.

If the checklist above describes the tool you were hoping exists — text-first intake, automatic receipt, one thread per issue, a daily digest, you approving every outbound message — that’s precisely the shape of Tenvo: $29/month, built for landlords with 1–20 units. Run the two-week test on it and see whether the digest earns its place in your morning.

  • Route everything through it. Every request, no exceptions, or you’ve tested nothing.
  • Threading: did every follow-up — photos, “any update?”, scheduling replies — land attached to the right issue, automatically?
  • Acknowledgment: did every tenant get a fast receipt that read like you and promised nothing you can’t keep?
  • Digest: each morning, could you answer “what’s open, and what’s the next action on each?” in under two minutes from one view?
  • Control: did anything go out to a tenant that you didn’t write or approve? (Decide whether you’re comfortable with whatever the answer is.)
  • Vendor handoff: did dispatching a job take one step, and could you tell it arrived?
  • Tenant friction: did any tenant have to change how they report — and did anyone complain or go quiet?