Our apartment association in Āgenskalns has 38 units. For six years, we ran it on a combination of WhatsApp groups, a shared Google Drive, and one board member who kept the financial records in an Excel file that nobody else could open because it was password-protected and he wouldn't share the password.
When he moved out in 2023, we discovered the Excel file hadn't been updated in four months. €12,000 in unrecorded maintenance expenses. Reserve fund contributions that were logged but never reconciled with the bank. A roof repair invoice we'd apparently paid twice.
That's when we started looking at HOA software. Not because we wanted to digitize for its own sake, but because our manual system had created a single point of failure that nearly cost us five figures.
If you're on a resident association board — whether it's an HOA in the US sense, a dzīvokļu īpašnieku kooperatīva in Latvia, a korteriühiö in Estonia, or a Wohnungseigentümergemeinschaft in Germany — this is what I think you actually need from software in 2026. Not the vendor feature list. The real list.
The core problem: collective decision-making with no infrastructure
Resident associations are weird organizations. They're democratic — every owner gets a vote proportional to their share. They're mandatory — you don't choose to join, you buy into one when you buy your apartment. And they're run by volunteers who have day jobs and no training in property management.
This combination creates a specific set of problems that general property management software doesn't solve. A landlord-tenant platform handles one owner managing many tenants. An association platform needs to handle many owners making collective decisions about a shared building.
That distinction matters more than people realize.
What you actually need
Voting and decision records
This is the single most important feature for an association, and it's the one most generic platforms lack.
In our association, we hold an annual general meeting (AGM) and 2-3 extraordinary general meetings (EGMs) per year. Decisions range from the mundane (approving the annual budget) to the expensive (authorizing a €40,000 roof replacement). Each decision needs to be proposed, discussed, voted on, and recorded with the exact vote count.
Under Latvia's Law on Residential Property Management (Dzīvokļa īpašuma likums), a decision to undertake major repairs requires a qualified majority — two-thirds of voting shares represented at the meeting. Get the math wrong, and the decision can be challenged in court. I know two associations that had renovation projects delayed by a year because their vote records were sloppy.
Good HOA software should:
- Track each owner's voting share (based on square meters, not "one unit one vote")
- Record who was present, who voted by proxy, and how each person voted
- Automatically calculate whether a decision met the required threshold
- Store the decision with a timestamp so it's legally defensible
If a platform can't do this, it's not association software. It's landlord software with an "association" label slapped on.
Transparent financial tracking
The single biggest trust issue in any association is money. Owners want to know where their maintenance fees go. Boards want to prove they're being responsible. Auditors want records that make sense.
Our pre-software financial reporting was a monthly email from the treasurer that said something like: "Income €2,840, expenses €2,100, reserve fund contribution €740." No breakdown. No receipts. Owners were expected to trust this.
After the Excel disaster, trust was gone. We needed a system where any owner could log in and see:
- How much they personally owe and have paid
- The building's total income and expenses for the period
- Individual expense items with receipts attached
- The current reserve fund balance
This level of transparency sounds obvious, but I'm amazed how many associations operate without it. When we implemented it, the number of "why am I paying this much?" questions dropped by maybe 80%. People don't argue with a receipt. They argue with a summary.
Maintenance request management that isn't a group chat
Our building's maintenance "system" was a WhatsApp group with 38 members. Someone would post "the elevator is making a weird noise" and then 15 people would reply with their own elevator theories. The board member responsible for maintenance would eventually see it, call the service company, and try to report back in the same chaotic thread.
It was, to put it mildly, not a system.
What you need is a structured request flow: a resident submits a request with a description and optional photo, it gets assigned to a board member or property manager, the status updates as it progresses, and the resident gets notified when it's resolved. The whole history is preserved.
This matters for two reasons. First, it prevents requests from getting lost in chat noise. Second, it creates a maintenance history for the building — when the elevator was last serviced, how much it cost, what the recurring issues are. That history is gold when you're planning a capital expenditure or arguing with a warranty provider.
Communication that reaches everyone (without spamming)
Association communication has a Goldilocks problem. Too little, and people don't know what's happening. Too much, and they mute the channel and miss the important stuff.
We tried email newsletters. Half the owners never read them. We tried a Facebook group. A third of the owners didn't have Facebook. We tried the WhatsApp group. It worked for urgent stuff but everything else got buried.
What actually works is a system that sends targeted notifications: a rent reminder goes only to people who haven't paid, an AGM notice goes to everyone with a voting interest, a maintenance update about the elevator goes only to people on floors 4-9. Different messages, different audiences, one platform.
Most HOA software supports this through a resident portal with configurable notification preferences. The resident chooses how they want to be reached — email, SMS, push notification, or in-app — and the system respects that choice.
Document storage that's organized, not a digital junk drawer
Every association accumulates documents. Building plans, insurance policies, contractor contracts, AGM minutes, energy performance certificates, audit reports. In our Google Drive, these were scattered across folders with names like "IMPORTANT," "old stuff," and "MAYBE KEEP."
HOA software should provide a structured document repository — categorized by type (financial, legal, maintenance, governance), searchable, and accessible to owners at the appropriate permission level. You don't want every owner seeing the building's insurance policy details, but you do want them to be able to find the AGM minutes from last year.
What you probably don't need
AI-powered predictive maintenance. Sounds impressive. For a 38-unit building, it's meaningless. You don't have enough data for predictive models to be useful. You need a system that records what happened, not one that predicts what might.
Integration with 47 third-party services. You're not running a property management company. You're running a building. You need maybe two integrations: your bank and your accounting system. Everything else is noise.
A mobile app with 40 screens. A responsive web app that works on a phone is enough. Native apps are nice but they're a maintenance burden for the vendor and rarely worth the premium you pay for them.
The pricing reality for associations
Association budgets are tight. Most of our income goes to maintenance, utilities, and the reserve fund. Software is an overhead item, and boards are rightly cautious about overhead.
Here's what I've seen in the market:
- Basic platforms: €15-30/month for a single building, covers the essentials (financial tracking, document storage, basic communication)
- Mid-range with voting and maintenance management: €30-60/month
- Full-featured platforms with bank integration and utility billing: €60-120/month
For a 38-unit building paying €75/month for maintenance fees, a €50/month software cost works out to about €1.30 per unit. That's reasonable. It's less than what we were losing to errors and inefficiency.
But don't buy the most expensive option just because it has the most features. Buy the cheapest option that covers your actual needs. You can always upgrade. You can't get back money spent on features you never use.
Implementation: getting a volunteer board to actually use it
This is the part nobody writes about, and it's where most software implementations fail.
Our board had five members ranging in age from 34 to 71. The 71-year-old had never used cloud software. The 34-year-old was a developer who wanted to configure everything. The other three fell somewhere in between.
Here's what worked:
Assign one person as the system owner. Not a committee, not "everyone." One person who is responsible for the setup, data entry, and training. In our case, that was me. I spent about 20 hours over two weeks getting everything configured.
Migrate incrementally. We started with financial tracking only. Got the board comfortable with it over a month. Then added maintenance requests. Then voting. Trying to launch everything at once overwhelmed people.
Train the board before the residents. If the board can't use the system, they can't help residents. I did a two-hour Saturday session with the board, walking through every feature with our actual data.
Accept that not everyone will use the portal. Some owners will never log in. That's fine. The system still works for them — they get paper invoices and email notifications, and the board tracks their data internally. You're improving the system, not forcing participation.
The legal angle: why decision records matter more than you think
In Latvia, an association decision can be challenged in court within two months of it being made. If your vote records are incomplete — missing proxy forms, unclear vote counts, no proof of notification — the court can annul the decision.
I'm aware of a case in Riga where an association authorized a €60,000 facade renovation, and three owners sued because the AGM notice was sent 6 days before the meeting instead of the legally required 14. The court annulled the decision. The renovation was delayed by 8 months. The contractor charged a price escalation of €4,200.
Software that tracks notification delivery, records meeting attendance, and stores proxy documents isn't just convenient. It's legal protection. If you're an association board member, think of it as insurance against your own procedural mistakes.
Making the case to your board
If you're the one pushing for software and the board is skeptical (they probably will be), here's what worked for me:
Don't lead with features. Lead with the disaster story. Every association has one — a lost invoice, a disputed decision, a maintenance issue that spiraled. Start there. "Remember when we couldn't find the insurance renewal date and almost lost coverage? This prevents that."
Then show the cost. Not the software cost — the cost of not having it. The hours the treasurer spends on manual reporting. The disputes over unclear fees. The maintenance requests that disappeared. Put a number on it. For us, it was roughly 15 hours/month of board time plus the €12,000 accounting error. The software paid for itself in month one.
Urbaneta handles association management with voting, financial transparency, maintenance tracking, and document storage built for the Baltic and European market. You can set up a trial and run your next AGM through it before committing.
