Many Associations, One Office
A managing agent runs a portfolio of residential communities. Each one is its own association, with its own board, budget, contractors and house rules. The same staff work across several of them at once, and a resident may own in two.
The work is spread across a spreadsheet per building, a shared mailbox, an accounting package and the telephone. Dues are raised by hand, one customer at a time. A maintenance request arrives by phone, and the only record of it is somebody's memory. A resident's question waits for office hours and a free person.
Where a Simple Build Fails Later
None of this is research. It is a business application, and the difficulty sits in the places where the obvious implementation quietly fails months later.
- Isolation written as a filter. A community column added to every query means every new query has to remember it. One forgotten condition shows one association's data to another, and nothing fails loudly.
- A role as a column on the user. The same person is a manager in one community, a resident in another and a board member in a third. One column cannot hold that.
- Rules that differ per community. Configurability usually means forking the permission logic. The forks drift, and a guarantee that should hold everywhere stops holding in one of them.
- Billing as one action. The same invoice lives in the app, the payment provider and the accounting system. Keeping the three in step through a refund or a failed sync is the real work.
- Deleting records. An association answers to an audit. A deleted unit takes its invoices with it.
What the Platform Covers
The platform covers properties and units, people and access, dues and payments, maintenance, assets, vendors, communication, documents and the assistant. Every record belongs to exactly one community, and that boundary is enforced beneath the queries rather than written into each of them.
- One person, many memberships. One email address is one account. The role, the status and the unit assignments are held per community, so a person can be deactivated in one association and keep working in another.
- Permissions are data. Each role has platform defaults that stay fixed. A community switches individual permissions on and off on top of them.
- Money stays in step. A community's manager sets up and approves its fee schedules. Once approved, a schedule raises invoices on its billing day, and the accounting system remains the ledger. A unit and a billing period are claimed before an invoice is created, so the same period is never billed twice.
- The assistant answers in words. It draws only on that community's own house rules, bylaws and policies. A resident can ask by voice and hear the answer back. A technician can ask for the next work order hands-free. A manager can ask a plain-language question about the platform's own data. An answer marked as wrong opens a tracked request.
Technology Stack
Guarantees Built Into the Data Model
Three rules run through the whole platform: each community is a hard boundary, permissions are stored as data, and records leave active use by being archived.
- Configurable within the hierarchy. No community setting can cross the role hierarchy, and nobody gains authority over a person above their own level.
- Money errs toward the missed charge, never the double one. A failed run releases its claim, and the next run catches it up.
- Archive instead of delete. A unit, a person, a vendor or a document leaves active use but stays readable and can be restored unchanged, and every change records who made it and the previous value. Personal data is handled differently: when a person makes a valid erasure request under data-protection law, their personal data is erased.
- Access changes take effect at once. When a role, a permission or an assignment changes, the live session ends with the reason on screen.
Capacity and Limits
The specification the platform was designed to:
- Nine areas of a managing agent's work on one platform.
- Seven roles, several of which one person may hold at once, with the highest one protected.
- Forty-three permission subjects a community can adjust, on top of defaults that stay fixed.
- One community never sees another's units, residents, invoices, documents or settings.
- Each community has its own sending identity, so one community's bounced mail does not harm another's.
Similar Multi-Organization Operators
One operator, many separate client organizations and the same staff across all of them: this shape is common well beyond homeowners associations.
- client organizations that must never see each other's data;
- the same person holding different roles in different organizations;
- rules that differ per organization without forking the code;
- money kept in an external ledger that has to stay in step with the application.
Facilities and campus management, franchise and clinic networks, student housing and coworking operators run on the same pattern. Parts of the platform, such as the assistant or billing, can also be added to an operator's existing systems. The assistant is a retrieval-augmented generation system, explained in our glossary and on our enterprise knowledge assistants page. For an earlier build in real estate, see the real estate application powered by AI.
areas of a managing agent's work on one platform, from dues to documents
roles, from platform administrator to resident, held per community
permission subjects each community can configure for itself