There is a list in our code of every question we are allowed to ask about a community.
It runs to more than a hundred questions.
One of them is about pets.
We still don't ask anybody to change their accounting system. We plug in behind whatever they already run.
A company registers its system once. Credentials encrypted, a status light, a last-synced time. That's the setup.
Behind that connection sits the least glamorous thing we've built and probably the most important: one contract, with over a hundred methods.
In plain English — a single fixed list of questions the platform is allowed to ask about a community. Every accounting system we support has to answer all of them, in exactly the same shape.
Associations. Units. Owners. Board members. Employees.
Violations, with their actions, fines and hearings.
Work orders. Architectural requests. Delinquencies. Insurance.
Chart of accounts. Balances. Transactions.
Vendors. Invoices. Statements. Resale status.
Vehicles. Pass keys. Pets.
Vehicles reads like filler on that list until somebody buys a condo. Then it is the make, the model, the color and the year, the plate and the state that issued it, the assigned parking space, the number on the sticker, and whether the registration is still active. It hangs off the ownership, not off a name in a contact list. Nobody puts it in a brochure. Somebody asks for it at nearly every condo closing.
Here's why the sameness matters.
A letter that prints a community's open violations doesn't know which system answered. A form pre-filling an owner's details doesn't know. The document pull inside a flow doesn't know.
They all ask the same way. Every time.One accounting system is live in production today. The framework is built to take the next one: an interface and a credential type, not a rewrite.
And that's the strategic bit, honestly.
Connecting to the books takes days.
Replacing books that are wired into an association's bank accounts, its audit history and its statutory reporting takes years — and nobody finishes that project in a good mood.
Not the books. The storefront on top of them.Next: the two kinds of community data — and why keeping one of them would be a liability, not a feature.