"Our Building Is Too Small for HOA Software" (No, It Isn't)
Key Takeaways:
- Compliance disclosures (like the Illinois 22.1) and lender questionnaires have no carve-out for small buildings — the requirements are identical whether you have 6 units or 160.
- Small buildings have the same maintenance obligations as large ones; the scope is smaller, but the process — and the institutional memory that walks out the door when a board member leaves — is the same.
- “Minimal activity” usually means minimal tracking, not minimal need. An emergency repair split across 6 owners hits far harder than the same repair split across 100.
- “Too small for software” usually means “can’t justify the cost,” “not enough complexity,” or “we can handle it” — and each falls apart the moment a unit sale or building failure forces you to produce information you don’t have.
- A system only needs to do three things: keep financial records current, store documents where any board member can find them, and make it possible to produce information someone will eventually ask for.
I hear this all the time: “We’re only six units. We don’t need software for that.”
It makes intuitive sense. A six-unit building doesn’t feel like an organization. There’s no office, no staff, no budget committee. The board is one or two people who volunteered because nobody else would. Monthly assessments get collected through Zelle or checks slid under a door. Meeting minutes are a group text. The financials live in someone’s head.
It works — until it doesn’t. And the moment it stops working is almost always triggered by one of three things: a unit sale, a building failure, or the person who’s been holding everything together deciding to move on — taking years of institutional knowledge with them.
The Lender Doesn’t Care How Small You Are
When an owner sells a unit, two things happen that have nothing to do with building size.
First, in states like Illinois, the board is legally required to produce a disclosure packet — a 22.1 disclosure that includes financial statements, reserve fund status, insurance details, governing documents, pending litigation, and anticipated capital expenditures. The statute doesn’t have a carve-out for small buildings. Whether you have 6 units or 160, the requirements are identical.
Second, the buyer’s mortgage lender will send a condominium questionnaire. This isn’t optional — if the board doesn’t complete it, the buyer’s financing gets denied and the sale falls through. The questionnaire asks detailed questions about the association’s financial health: What percentage of the budget goes to reserves? How many units are more than 60 days delinquent? Does the association carry adequate insurance? Are there any pending special assessments?
These questions assume you have organized financial records, current insurance documentation, and a reserve plan. They don’t assume you have a management company or a finance committee or a full-time treasurer. They just assume you have the answers. And for a small building that’s been operating informally, producing those answers under the time pressure of a real estate closing can be a scramble.
I went through this four times as board president of a 16-unit building. The first disclosure request took me an entire weekend. Not because the information didn’t exist, but because it wasn’t organized in a way that let me produce it on demand.
Small Buildings Have the Same Maintenance Obligations
A six-unit building still has a roof. It still has plumbing, electrical systems, exterior walls, and common areas that the association is responsible for maintaining. The scope is smaller, but the process is the same: identify the issue, hire a vendor to evaluate it, get a quote, approve the repair, and pay for it.
Without a system, that process lives in one person’s email inbox. The vendor quote is an attachment in a thread from three months ago. The approval was a verbal agreement at a meeting nobody took notes on. The payment was made from the board president’s personal account and reimbursed later — or maybe not yet.
This works when everything goes smoothly. But when a board member moves away, or a dispute arises about what was approved and what wasn’t, or someone asks “how much did we spend on maintenance last year,” there’s nothing to point to. The institutional memory walks out the door with whoever was holding it.
For small buildings, this problem is actually worse than it is for large ones. A 200-unit building with a management company has staff, systems, and redundancy. A six-unit building has one person. When that person leaves, everything they were tracking — vendor contacts, payment history, insurance renewals, pending repairs — goes with them unless it’s stored somewhere accessible.
“Minimal Activity” Is a Dangerous Assumption
The argument that a small building doesn’t need software usually rests on the assumption that not much is happening. Assessments come in, a few bills get paid, and that’s about it.
But “minimal activity” is often a reflection of minimal tracking, not minimal need. Buildings don’t stop aging because they’re small. Insurance still needs to be renewed annually. Vendors still need to be paid. Budgets still need to account for inflation. Reserves still need to be funded — and the consequences of not funding them hit small buildings harder because there are fewer owners to split an emergency levy.
A $15,000 roof repair split across 100 units is $150 per owner. Split across 6 units, it’s $2,500. The math is simple, but it catches small buildings off guard precisely because they assumed nothing big would come up.
The buildings that feel like they have minimal activity are often the ones most at risk — not because they’re neglected, but because nobody is tracking the slow accumulation of deferred maintenance, expiring contracts, and underfunded reserves.
What “Too Small for Software” Actually Means
When someone says their building is too small for software, what they usually mean is one of three things:
“We can’t justify the cost.” This is the most reasonable version of the objection, and it’s worth addressing directly. Most HOA software charges per unit — which means a small building often pays the same per-owner cost as a large one for features they’ll never use. That pricing model genuinely doesn’t work for small associations. But not every platform works that way. Nestingbird’s Community plan is free, with no per-unit fees and no resident limits. The question isn’t whether you can afford software — it’s whether you can afford to keep operating without a system when the next unit sale or building failure hits.
“We don’t have enough complexity.” This conflates volume with obligation. A small building has lower volume — fewer transactions, fewer meetings, fewer maintenance events. But the obligations are the same: financial reporting, document retention, compliance disclosures, reserve planning. Low volume makes these things easier to manage, but it doesn’t make them optional. And low volume is also what makes them easy to neglect, which is where the risk lives.
“It’s just us, we can handle it.” This is true right up until it isn’t. “We” usually means one person, and that person’s capacity isn’t infinite. Life changes — new jobs, new kids, a move — and suddenly the person who was holding everything together isn’t available anymore. The question isn’t whether you can handle it today. It’s whether the next person can pick up where you left off.
The Real Cost of Not Having a System
The cost of operating without a system isn’t visible until something forces you to produce information you don’t have. A unit sale requires financial statements you haven’t been generating. A lender questionnaire asks about your reserve funding status and you’re not sure of the answer. A new board member takes over and inherits a box of unsorted documents with no context.
I’ve been that board member. The time I spent reconstructing our building’s financial history — pulling bank statements, categorizing transactions, building reports from scratch — was time I could have spent actually improving the building. The information existed. It just wasn’t organized in a way that made it usable.
A system doesn’t have to be expensive or complicated. It just has to do three things: keep your financial records current, store your documents where anyone on the board can find them, and make it possible to produce the information someone will eventually ask for — whether that’s a buyer’s attorney, a lender, or the next board president.
If your building has owners, collects assessments, maintains common property, and exists within a legal framework that requires financial transparency — you need a system. The size of your building doesn’t change that. It just determines how painful the lesson is when you find out the hard way.
About the Author: Nathan Jones is the founder of Nestingbird, a platform that helps HOA boards and property managers handle finances, maintenance, and communication — free for buildings of any size, with no per-unit fees.
Keywords: small HOA software, do small HOAs need software, HOA management small building, small condo association management, HOA compliance small building, HOA lender questionnaire, self-managed HOA tools, small HOA financial reporting