How to run a large apartment portfolio without more staff

The first ten apartments run on memory. You know which tenant texts about the boiler, which one always pays late, and which contractor answers on a Sunday. Somewhere past a dozen units that memory stops being a system. A repair gets missed because it was reported in a chat reply you scrolled past. A payment gets chased that already arrived. An evening a week disappears into matching bank rows to apartment numbers.

Growth is what breaks the informal setup. Every apartment you add is another stream of “the faucet is leaking” and another line of “did they pay this month?”, and both streams still land on one phone. The portfolio can keep growing. The way you run it cannot, unless the operations move off the phone and into something built for the shape of the work.

Kvaro handles the operational half of a rental portfolio: the repairs and the money that arrive after move-in. Listings and leases stay in whatever you use today. What follows is how an owner runs both jobs at fifty apartments with the effort the phone demanded at ten.

Give every apartment one place to report a problem

Right now maintenance requests reach you by every channel at once: a text, a call, a message to the super, a note under a door. Each channel loses something. A call has no photo. A text has no address once it scrolls away. You become the router, re-typing “leaking pipe, apartment 14, urgent” into whatever list you keep.

Kvaro gives every resident the same front door. A tenant opens the app and files an issue with a title, a description, a priority (Low, Medium, Urgent), an optional category, and photos. The photo alone saves a visit: you see the corroded valve before you send anyone. The issue arrives attached to the apartment and the building, so nothing needs re-typing and nothing is anonymous.

You can file on a resident’s behalf too, for the older tenant who calls instead of taps. Pick who it is filed for, and it lands in their feed with a notification, so the record is identical whether they typed it or you did.

Every repair carries a state, so nothing sits

A flat list of open problems hides the ones that matter today. What an owner across many buildings needs is the state of each repair: what is new, what is moving, and what is stuck. Each issue in Kvaro moves through New, In Progress, Review, and Resolved, with a separate Nothing-to-Fix outcome for the ones that need a reason instead of a visit. The tenant confirms the fix, or you mark it resolved directly. If the fault returns, it reopens with a mandatory reason, so a recurring problem leaves a trail instead of vanishing.

For an owner watching many units, the queue is the point. It is filterable and paginated, so “every urgent issue still open across all six buildings” is one view, not six scrolls through six chats. When a contractor clears ten small tickets in a morning, you resolve them in one bulk action. Push alerts reach you when the burst pipe is filed, not when the downstairs tenant calls about the ceiling. If those reports currently live in a group chat, that is its own quiet tax, covered in the group-chat piece.

The full mechanics of the ticket flow, from intake to close, are in the ticket-system guide.

Route repairs so they don’t all land on you

A portfolio stops scaling when one person sits in the middle of every task. Kvaro is built to take you out of that middle.

When an issue is filed it can route on its own: to the default contractor for that category, to a pool of fixers matched by skill who claim it themselves, to the building’s manager, or to you. A fixer only sees the categories they handle, so the plumber gets plumbing and never wades through the rest. As the portfolio grows you add a fixer or a co-manager and hand them a lane, instead of adding another hour to your own day.

Your plan sets how far that delegation goes. Free runs unlimited buildings and apartments with up to three managers and five fixers, which carries most owners well past their first few addresses. Premium and Ultimate widen the manager and fixer counts and add automatic ticket routing as you take on more, and Ultimate lets you pin a default fixer per building so each address routes to its own trusted contractor. The tool grows one tier at a time with the unit count.

Let payments identify themselves

The other half of the portfolio is money in. At ten apartments you recognize the names on the statement. At fifty, “S. Miller” could be three tenants, and matching a transfer to an apartment becomes guesswork you repeat every week.

Kvaro removes the guessing. When you raise a collection, whether it is monthly dues, a one-off for a roof repair, or a reserve contribution, every apartment gets its own payment reference. The resident gets a push notification and sees the amount and that reference in the app, ready to copy into the memo field of their bank’s online bill pay. When the money lands, the reference on the statement says exactly which apartment paid, down to the cent.

You then get a who-paid view per collection: every apartment shown as paid, partial, or outstanding. Chasing shrinks from a weekly scan of the whole statement to contacting only the few who actually owe, with the numbers in front of you. Chasing someone who paid three weeks ago costs more goodwill than any late payment, and reference-matched records make that mistake impossible.

The bank statement is the record. Import it, don’t retype it.

Your bank already keeps the authoritative log of the building’s money: every payment in and every cost out, dated and complete. Copying it into a spreadsheet makes a worse version, then a second job keeping the copy in sync.

Kvaro imports the statement instead. You pick the file and it is parsed on your own device, in the browser or on the phone, and never uploaded or stored anywhere; only the transaction rows you choose to save leave the device. That matters, because a building statement carries every resident’s name and payment history. Incoming rows match to the paying apartment by reference on their own, and outgoing rows link to the cost they settle, so a recorded expense flips to paid, partially paid, or unpaid from the statement rather than your memory. The who-paid list and every status are drawn from what the bank said.

One check quietly saves the whole record. Each statement declares an opening and closing balance, and Kvaro verifies the opening balance against the building’s recorded balance before it imports. Skip a month in the chaos of a burst pipe and the next import refuses to let the gap slide through: it stops and tells you a statement is missing. A continuous chain of statements is what lets you prove, at any moment, where every payment went and where every cost came from, which is exactly what a co-owner or an HOA board asks for. The full payment-tracking system is laid out in the building-finances guide.

Get the app into residents’ hands

None of this works if the residents are not in the app, and across a large portfolio that sounds like the hard part. It is the easy part. Each building has a six-character join code and a share link; a resident taps it, and the link opens the app straight on the join screen with the code already filled in, or sends them to the store to install first. One tenant can belong to several of your buildings and switch between them, so a resident who moves within the portfolio keeps one account.

The resident app is also your quietest sales tool. When you pitch the next building, “your residents get an app that shows a repair being logged and closed, and shows exactly what they owe” is a concrete difference from the manager who still runs a phone. That is the argument that wins the contract.

Prove it per building, on demand

Owning a portfolio means answering the same question for every address: how is this building actually doing? Kvaro generates a per-building PDF report over any date range that pulls together the resolved issues with their photos, the finances, and the announcements and any votes. It renders server-side and pings you when it is ready, so a six-building month is six taps, not a weekend of assembling.

The report earns its keep twice. It is the record you hand an HOA board or a co-owner, and it is the proof you show the next building you want to win. On Ultimate the reports schedule themselves monthly or quarterly, publish to the building’s document library, and carry your own logo. The full picture is in the reports guide.

What actually scales

The honest test of any tool is whether the twentieth building costs less to run than the fifth did. It does here, because the work each apartment creates now flows into a system instead of onto you. A repair routes to a fixer and closes itself. A payment identifies itself and reconciles from the statement. A report assembles itself on demand. What you add per apartment is a row, not an evening.

That is the difference between owning a lot of apartments and running a lot of apartments. The apartments were always the easy part. How many one person can actually run before the operations cap the growth is the real ceiling, worked through in how many buildings one person can handle. Move the repairs and the money off your phone, and the number of apartments one person can run climbs with them.