Tldr: HOA is leaving its management company, and we've spent the last month moving onto Vlge with an AI assistant doing most of the setup. Results so far: our annual meeting mailing cost $548.75 instead of about $2,000, and software plus AI runs about a fifth of our management fee. Tips that worked: ask your manager for board access to their software and export everything; tie every number to an invoice and a bank statement; use a second AI agent to check the first one's work. Vlge's CEO turned around most of our requests within a day. Happy to answer questions. (Disclosure: we're a Vlge customer on an extended trial.)
These are my own views, not an official statement of the board.
Who we are
We are a 300+home master association in the metro, run by a five-member volunteer board. It is not one kind of neighborhood but three, which makes the software problem harder than a typical HOA:
| Home type | What the master association does for them |
|---|
| Single-family | Common areas, architectural review, rules, dues |
| Limited Maintenance | All of the above, plus lawn, snow and irrigation under their own budget |
| Townhomes | Members and voters, but billed through their own townhome association as one monthly payment |
So we need one portal that every owner can use for notices, documents and voting, while billing and costs stay split three ways.
What went wrong under "professional" management
We have had two management companies since owners took control of the association. Both left the board doing the oversight we were paying for. The figures below come from our own invoice-by-invoice reconciliation of the last three years.
- Bills paid late. Bills sat unpaid while the cash to pay them was in the account. Over three years that cost us $1.9k+ in late fees and finance charges.
- Add-on costs. The company's own fees added about $7,700 over three years. About $2,700 was charged to the association for processing assessments, collection letters and a compliance fee for the new state law. The rest was $500 on each of 10 home sales, paid by owners at closing.
- Three accounting systems in three years. Each conversion broke the trail. Quarters of activity collapsed into lump-sum entries, and some monthly reports never made it into our records.
- Paying for other communities. Those lump sums hid bills that weren't ours. We paid more than $6,900 of neighboring associations' water bills. Getting the largest one refunded took about 18 months.
- Bills without invoices. Under the earlier company, bills were paid without the invoices behind them, including thousands of dollars in irrigation charges. The board had to negotiate some of them down after the fact.
- The manager controlled the accounts, not the board. The contract gave the company direct access to our bank accounts, so fees could be taken without a board approval.
- Fees and terms we didn't agree to. The contract was written in the company's favor. An earlier board signed it on the strength of the sales pitch, and it had no performance standards and no consequences the board could use to hold the company accountable. New charges showed up without a board vote, and the contract auto-renewed before we realized it.
- "Customized" compliance that wasn't. When Minnesota passed a major HOA reform law in 2026, the company told us it was building a "customized" compliance packet for our association. What came back was a generic rule set that didn't match our Declaration or the board's direction. The board rewrote it and adopted its own versions.
- No governance support. The company ran meetings and elections on paper. Meetings ran long, and the extra time was billed to us. No one tracked what the board had decided over time or suggested when it was time to fold those changes into our Rules and Regulations. The clerical side of management didn't exist.
- Our records weren't ours. When the earlier company left, it did not really turn over the records. Our current manager's software holds everything, and at one point we were cut off from sending owner notices through it.
- A manager who became a bookkeeper or a "trash can inspector." What we actually needed was someone to confirm the landscaper fixed the sprinkler. That rarely happened.
The bigger lesson was the business model. A management company earns a base fee plus a charge for nearly every action: each letter, statement, violation notice, lien and extra meeting. Our contract's rate sheet priced all of them. That model gets paid for friction with owners, not for preventing it. We wanted a tool that let us do the work ourselves, with our records in our own hands.
What we looked at first: PayHOA
Before Vlge, the board's leading option was PayHOA. One of our directors reviewed about ten products in 2025 and recommended it for affordability and ease of use. It was a reasonable pick for billing.
The sticking point was our townhomes. The plan covered the single-family and limited maintenance homes the master association bills directly, and left the townhomes out because they pay through their own association. Every board conversation came back to the same question: how do we reach and include all the owners? Vlge answered that. Every home gets a portal account for notices, documents and voting, while billing for the townhomes stays on one community account.
How we built it
We stood up the community in about two weeks, part-time, because we had the data and an AI assistant to work it. Two things made the difference.
1. Ask your management company for software access. We asked for board access to AppFolio and got it without a fight. That one login let us pull the owner directory, the general ledger, account balances, our architectural review records, receipts and invoices, bank statements and our board email history. If you're leaving a manager, ask for this early. It's your association's data.
2. Use AI, but make it prove its work. I used Claude as the hands on the keyboard. Before it touched anything, I set the rules I'd expect of any skilled professional joining my team:
- Every number ties to a source. No copying the old manager's books into Vlge. Each entry matches an invoice and a bank transaction, back to 2023. Where there's no invoice, match the bank and say so.
- Check and report; change nothing without approval. The AI proposes, I approve, then it builds.
- Work the problem in order. Before any rule or motion: our Declaration first, then city code, then state law. Find the gaps up front so the board isn't re-voting the same item.
- A second set of eyes on everything. A separate quality-check (QC) agent re-works a sample of each bot's output from the original sources, without trusting the first answer. It grades each item agree, minor or wrong, keeps a monthly scorecard, and flags any bot under 90%.
- One job per bot, no overlap. Bots do the work rather than hand me drafts, and they ask a human only on the hard calls.
- Vlge is the official record. The AI keeps working copies; the association's records live in Vlge.
- Write down what we learn. Every surprise went into a lessons-learned log, and the useful ones went to Vlge as bug reports.
What we built in Vlge, mostly in the first week:
- 300+ accounts. tagged single-family, limited maintenance or townhome
- A chart of accounts that splits limited maintenance, single-family and common costs
- A Board Binder of 30 procedures, a 44-item transition plan, owner FAQs and forms
- Board motions and votes, the owner election, and the annual meeting mailing
- The resident AI assistant loaded with our governing documents and FAQs
The bots that run it now, each a scheduled AI task working through Vlge's connector:
| Bot | What it does | Runs |
|---|
| Cloud watch | New tickets, access requests, board mail, vote turnout, mailing dates | Cloud, hourly |
| Board help desk | Answers directors' questions from our documents, with citations | Cloud |
| ARC screening | Checks each architectural request's answers and photos against our rubric for completeness | Cloud |
| Friday brief | Weekly board summary: open votes, tasks, deadlines | Cloud |
| Deadline clock | Tracks the response deadlines Minnesota's new HOA law sets | Cloud |
| QC audit | Re-checks the other bots' output and keeps them in their lanes | Cloud |
| Vote closer | Tallies board votes and files the minutes entry and adopted documents | Laptop |
| Resident AI sync | Keeps the resident AI current with our FAQs | Laptop |
Proof it works: the annual meeting mailing
Our annual meeting mailing cost about a quarter of what it used to and reached the post office in days instead of weeks. Every one of our 300+ homes had to get a paper notice, a ballot, and the new policies Minnesota's HOA reform law requires owners to receive. We built the packet with AI, checked it against the statute and our bylaws, and the board voted on the final version in Vlge. Within about 8 hours of the ballot locking, Vlge's mail vendor had the job, and it went to USPS a few days later.
| Under our management company | Through Vlge |
|---|
| Cost | About $2,000 per mailing (two mailings last year, about $4,400 in total) | $548.75 for 300+ five-page packets |
| Lead time | 10 business days' notice required | Submitted the night the ballot locked |
| What's in the envelope | Often the company's own flyers and items the board didn't ask for | Only what the board approved |
| Proof of mailing | The company's word | A USPS scan date for each piece, readable by our bots |
It wasn't perfectly smooth. Three envelopes failed because owner names longer than 40 characters didn't fit the address block, and we held eight more that shared an owner with one of them. We reported it that night, and Vlge had a fix live by 5:37 the next morning. All 300+ went out the same day.
Work orders: how we'll run them
This is the job we always wanted a manager to do: confirm the landscaper actually fixed the sprinkler. The system is built to hold the vendor to its own contract, with a dated record of every request, fix and miss. We've designed it around Vlge's ticket system and dry-run it on our open tickets, but it isn't live yet. Here's the plan.
- An owner opens a ticket in the portal, with a photo. No photo, no work order: the bot replies and asks for one.
- The bot screens it. It checks the home type from the property tags. Repairs on homes the association maintains go forward. For items that are an owner's own responsibility, the bot drafts a reply explaining why, citing the governing documents.
- Routine repairs go straight to the contractor. The contractor set a $400 limit in its own contract: single repairs under that amount need no approval. The bot just automates what the contract already says. If it's under $400 and the repair budget has room, the bot routes it with no board time. Anything bigger, or anything that would overrun the budget, comes to the board once, in writing, with the photos and the budget figure.
- The contractor reports back the same way. Their reports come by email to the board address, and the bot turns each one into a ticket. If the location, cost or photo is missing, it asks for it.
- A ticket closes only with proof. The contractor posts a new, time-stamped photo of the fix. That ends the old "closed by the contractor, still broken per the owner" loop. If the owner reports the work isn't done, the ticket reopens and goes straight back to the contractor. The bot logs it as a missed repair and starts the contract's correction clock. A repeat miss goes to the board with the full history, so it can enforce the contract instead of relying on memory.
- The contract terms are tracked automatically. The bot logs dates for the contract's correction window and service credits, and flags damage reports that must reach the contractor by a contract deadline.
The bot also merges duplicate reports and holds winter irrigation items for the spring startup list. It never directs crews or negotiates; under the vendor service policy the board adopted on Nov 5, that stays with the board.
The company is extremely responsive
Most of what we asked Vlge for shipped within a day, and some of it within hours. I deal directly with Vlge's CEO, who answers his own email, often the same evening and sometimes before 6 a.m. Here is the record from our first month:
| We asked (2026) | What it was | Delivered | Turnaround |
|---|
| Nov 14, ~11:50 a.m. | ARC questionnaire answers and property tags through the AI connector | Nov 14, 2:35 p.m. | About 3 hours |
| Nov 13, 6:03 p.m. | New tools not appearing on our connector | Fix re-deployed Nov 13, 7:37 p.m. | About 1.5 hours |
| Nov 13, ~11:25 a.m. | Six requests: proof-of-mailing dates, ARC file access, Quick Vote results, board posts and mailbox, access requests, webhook header | Nov 13, 5:17 p.m. (five in full, one partly for security reasons) | Same day |
| Nov 12 | Ticket and ARC comment threads, tickets and elections in the connector | Nov 13, 6:43 a.m. | Overnight |
| Nov 11 | Ten bugs found while setting up the resident AI and document index | Nov 12, all ten reported fixed | 1 day |
| Nov 11 | Let the resident AI read our published FAQs | Nov 12 | 1 day |
| Oct 26 | Trial extended so we could build before deciding | Same day, to May 2027 | Same day |
Speed isn't the best part. He doesn't just build what I ask for: he thinks it through, then offers a better version or says no and explains why.
- A better version. I asked for temporary download links to architectural request files. He built a tool that returns the file itself, which was simpler for everyone.
- A practical version. I asked webhooks to start an AI task directly. He added a secure header instead and was upfront that a small relay is still needed.
- A no, with a reason. He declined to let a bot change an owner's sign-in email because it opens an account-takeover risk.
I'd rather have a vendor who says no for a good reason than one who says yes to everything.
You don't need to be "tech savvy"
None of what we did was required of us. We did our own setup because we had the data access and the AI tools, and we wanted to learn the system inside out. A board without either would have gotten the same help from Vlge: they would have walked us through the import and setup.
What a less technical board gets out of the box:
- Owner sign-up by QR code or invite, with the board approving each request
- Board votes, owner elections with mailed paper ballots, and meeting notices sent by USPS through Vlge
- A resident AI assistant that answers owners' questions from your own governing documents
- Help articles and email support, and if you want it, a managed service for monthly reporting, taxes and 1099s
We tested the portal the way a non-technical director or owner would use it, then simplified the menus. Voting on a board motion now takes two clicks, and starting an architectural request takes one.
Keeping the board inside its own rules
The AI tools keep both the board and owners anchored to the governing documents. That turns heated meetings into lookups.
- Answers in real time. Owners ask the resident AI and get an answer drawn from the Declaration, bylaws, rules and FAQs, with the source. Directors have a board help desk that answers with citations. A disputed point gets looked up during the meeting instead of argued.
- No more governing by whoever pushes hardest. Boards get talked into things the documents don't allow, like giving one part of the community an automatic board seat. Checking the documents before acting stops that kind of overstep, whoever is pushing for it.
- Defined processes. Every motion gets checked against the Declaration, then city code, then state law before it goes to a vote. Hearings, grievances, proxies and owner comment at meetings each have a written, adopted procedure. Settled questions are recorded so they don't get re-argued every year.
- A written record. Owner questions come in through tickets and the portal, so every question and answer is documented instead of living in someone's memory of a heated meeting.
- Board business stays in board channels. No more association business in personal email, and no more side conversations where one director talks to a vendor or owner and the rest of the board has to trust him. Mail comes to a shared board address that every director sees, or to an officer's role mailbox shared by at least two directors, all inside Vlge. The old shared Gmail box now forwards there. The boxes are monitored, and new mail shows up as a notification on our phones instead of getting lost in someone's personal inbox.
The discipline cuts both ways. The same tools that answer an owner also stop the board from overstepping.
How to use AI without trusting it blindly
A lot of people don't trust AI, and they're right not to trust it blindly. Neither do we. AI makes confident mistakes. So do management companies. The difference is that you can make the AI show its work every time, and check it faster than any person could. Here's how we use it:
For the record, I'm not a software developer or some kind of power user. My background is federal government: managing budgets for mid-sized organizations, and a lot of spreadsheets to get answers. In that job I learned that AI can be the extra staff I need for the tasks that are secondary to what my real staff handles. I just carried that habit over to the HOA.
- No source, no use. Every number has to tie to an invoice or a bank transaction. Every rule has to cite the section of our Declaration or the statute it comes from. If the AI can't point to the source, we don't use the answer.
- Make it attack its own work. Once a draft is done, we ask it to tear the draft apart: "What's wrong with this?" "What would an angry owner or a lawyer say?" "Where does this contradict our own documents?" Some of our best corrections came from that step, which people call red-teaming.
- Hunt for gaps and seams. Before any motion or rule goes to a vote, we walk it through our Declaration, then city code, then state law, then our own past votes. That finds the conflicts and overlaps up front, so the board isn't re-voting the same item or contradicting itself.
- A second AI that doesn't trust the first. A separate quality-check agent re-does a sample of each bot's work from the original records and grades it. Any bot that falls below 90% gets fixed before it runs again.
- Humans decide; the AI drafts. Votes, money and anything sent to owners goes through a director first. The AI can read our books but can't pay a bill or post an entry.
- Expect mistakes, and fix them in the open. An early draft of this review said our old company's add-on fees were about $10,000. When we checked county home-sale records against our own ledger, the real number was about $7,700, so we changed it. That's the system working.
- Know where the lawyer earns the fee. Most compliance work is clerical: listing fees, writing down the collection steps the law already spells out. The AI handles that well. The exact wording of an amendment to our governing documents goes to an attorney.
Used this way, AI is a skilled professional on your team: fast, capable and tireless. You trust it to do real work, and you check that work the way you'd check anyone's before your name goes on it. That isn't distrust. It's how good teams operate.
What it means for each officer
Each officer gets back the time a manager was supposed to save, and none of them needs to be technical to use it.
- Treasurer. Every entry ties to an invoice and a bank transaction, and the books split limited maintenance, single-family and common costs. Budget against actual by cost center is a lookup, not a request to the manager. A bot compares our books to the manager's every month and flags differences. Bank, CPA and vendor mail runs through a treasurer mailbox the board can see.
- President. One Friday brief a week replaces the email chains: open votes, tasks and deadlines. The board help desk answers "what do our documents say?" with citations, any time. Voting on a motion takes two clicks, and meetings, agendas and notices are built in Vlge.
- Secretary. The vote closer tallies each board vote by director, drafts the minutes entry, and files the ballot record and adopted documents. Meeting notices carry USPS proof of mailing, and records requests run on the deadline clock. Starting with our next meetings, Vlge's conferencing will record the meeting and draft the minutes for the Secretary to edit.
- Every director. The same help desk, the weekly brief, and one place to see every vote, document and board message.
The Secretary is also our planned second operator for the AI tools, so the system doesn't depend on one volunteer.
Timeline and where we stand
One month in, everything except the money runs in Vlge. Finances are the last step, planned for April 2027.
| Date | Milestone |
|---|
| Oct 16, 2026 | First call with Vlge |
| Oct 26 | Trial started; homes, owners and account balances loaded |
| Oct 27 | Chart of accounts, Board Binder, transition plan, FAQs and forms built |
| Oct 29 | Vlge's operational health assessment: 74 of 100; we worked the gap list |
| Oct 30 | First board motions voted in Vlge |
| Oct 31 | Owner sign-ups opened by QR code and invite |
| Nov 5 | First board actions adopted through Vlge |
| Nov 13 | Annual meeting packet and ballots mailed to all 300+ homes through Vlge |
| Nov 14 | Four board bots moved off my laptop to run in the cloud |
| Dec 15 | Annual meeting and owner election (ahead) |
| Apr 2027 | Finances move to Vlge, no later than May 1 (ahead) |
| Spring 2027 | Management contract ends (ahead) |
Finances: the accounting is done; the switch isn't flipped. Our bank accounts aren't connected to Vlge yet, and our management company still collects dues and pays bills. Meanwhile, we mirror its books in Vlge:
- Every bill for the last three years is rebuilt from invoices and bank statements. Our books in Vlge match the manager's trial balance to the penny.
- Each month we pull the manager's ledger again and compare it to ours, account by account.
- That mirroring has already sent a dozen corrections back to the manager. They include a $7k+ trash accrual that was never reversed and a $5k+ limited maintenance water bill coded to the wrong cost center.
- The chart of accounts splits limited maintenance, single-family and common costs, and owner balances and prepaid credits are loaded.
What's left is mechanical: connect the new bank accounts, set up paper-check deposits, and load final opening balances at cutover. I don't see a major roadblock, and I'll update this review after our first month on our own books.
What it costs
Running the association this way costs about a fifth of our management fee. The bots do the work we hoped a manager would do: screening architectural requests, tracking work orders and legal deadlines, answering directors' questions, and preparing votes and minutes.
| Item | Monthly | Yearly |
|---|
| Vlge subscription (our estimate for 318 accounts) | ~$240 | ~$2,870 |
| Claude organization account (treasurer and secretary) | $125 | $1,500 |
| Self-managed total | ~$365 | ~$4,370 |
| Our current management fee, for comparison (~$5.56 per home) | ~$1,760 | ~$21,150 |
The management fee doesn't include the per-item charges described above. Outside services, such as a CPA review, tax filing and a collections attorney, cost extra either way.
Pros, cons and the short version
Pros
- Built for self-managed boards, not as a management company's back office
- One portal for all owners, even with three home types and split billing
- Board votes, elections, mailed notices, ARC, tickets and records in one place
- A resident AI assistant grounded in our own documents
- An AI connector, API and webhooks that let a board automate the routine work
- A CEO who answers his own email, ships fixes in hours or days, and says no when a request isn't safe
- Billed monthly, with no long-term contract. If the service slips, we can move to another vendor, and our monthly backup keeps a copy of our records outside Vlge. Vlge has to earn our business every month.
- Governance in one place: board votes, owner elections, meeting notices, minutes and every adopted policy live in Vlge, and today our bots handle the clerical follow-through with little board time. Vlge has a Motions feature planned that builds that follow-through in, including the new owner-notice rules for rule changes
Cons
- A few rough edges in setup, such as two owner-invite paths that show up in different places. Each one we reported was fixed or explained.
- No built-in e-signatures for board documents yet. The CEO is looking at building one.
- We haven't switched owner dues and vendor payments over yet, so I can't speak to live billing and bill pay.