Start with your problems, not their features
Before any demo, write down the three things that cost your building the most time or trust today. For most it is some mix of: identifying who paid, answering the same questions from owners, and notices that do not reach people. Judge every product against that list. A long feature list you will not use is not an advantage.
Money
- Does the software move money, or does it record payments made to the building’s own bank account? Both are legitimate; you need to know which, and who holds the funds in the meantime.
- How does a deposit get matched to a unit? By reference, by amount, by hand? What happens to a deposit with no reference?
- Which bank file formats does it read, and does your bank export one of them?
- Can it handle special assessments, partial payments and payments for several months at once?
- How is late interest handled, and who decides whether it is applied?
- Does it issue Mexican tax receipts (CFDI)? If your building needs them, ask how; if the answer is no, ask what it gives your accountant instead.
What owners can see
- What exactly does an owner see: their own balance only, or the building’s expenses and budget too?
- Can an owner open the receipt behind an expense?
- Who decides what each role sees, the vendor or your association?
- Is there a record of who changed what, and for how long is it kept?
Languages
- Is the whole interface available in each language your owners read, or only parts of it?
- Are notices and statements produced in both languages, with the same numbers?
- Who writes the second language: a person, or automatic translation? If automatic, who is responsible when it is wrong?
Your data, and the way out
This is the section boards skip and later regret.
- Who owns the records: the association, the management company or the vendor? Ask to see it in the contract.
- If the building changes administrators, do the records stay with the building?
- Can you export balances, payments, expenses and documents in a format another system or an accountant can read? Ask to see an export, not a promise.
- What happens to the data if you cancel, and how long do you have to take it out?
- Where is the data hosted, and is it used for anything besides running the service, such as advertising?
Security and privacy
- Is there two-step sign-in, and can each person turn it on?
- Is one building’s data kept apart from another’s when the same company manages both?
- Is there a privacy notice you can read before signing, and a way for a resident to ask for their data to be corrected or deleted?
- If the product stores ID copies or photos of visitors, who decides that, and when are they deleted?
Assemblies and votes
Be careful with the word “voting”. Whether a decision is valid depends on your state’s condominium law and your bylaws: the notice, the quorum, how shares are counted and who may hold a proxy. The state law guides show how much those rules differ. Ask the vendor directly: is this an opinion poll or a vote that replaces the assembly, and on what legal basis in my state? An honest answer may be less exciting than the demo.
Cost and commitment
- What is the price based on: per building, per unit, per user? What happens to the bill if you add staff or owners?
- Is there a setup or migration fee, and what does it include?
- Is there a minimum term, and what does leaving cost?
- What is included in support, in which languages and at what hours?
Ask what it does not do
The most useful question in any demo is “what does your product not do yet?” A vendor who answers plainly is telling you how they will behave when something goes wrong. A vendor who says “it does everything” has told you something as well.
Test it with your own building
- Ask for a walkthrough with realistic data: your number of units, your kind of dues, a month of your bank activity.
- Have the person who does the month-end close try the reconciliation themselves.
- Have an owner who is not technical, and one who reads the other language, try to find their balance and an expense receipt.
- Ask for an export of everything you entered.
Then plan the move itself with the migration checklist.
How Atriovia answers its own checklist
- Money. Atriovia does not move money. Owners pay by transfer or deposit to the building’s account; Atriovia records those payments and matches them to units from the bank’s CSV file, by each unit’s reference. A deposit with no reference stays pending until a person assigns it. It calculates late interest and shows it, but does not add it to the statement on its own. It does not issue CFDI; it gives CSV exports for your accountant.
- Transparency. Owners see their balance and statement, and each posted expense with its receipt and the budget totals. Your association assigns the privileges by role, and there is an activity log kept for five years.
- Languages. The whole product is in Spanish and English and each person chooses. Statements come as a PDF in either language. Notices are written by the administration in both; Atriovia does not translate automatically.
- Data. Each condominium’s information belongs to its association and is kept apart from every other building’s. There are CSV exports of payments, balances and ledger entries. Data is hosted with providers in the United States, is not used for advertising and is not sold.
- Security. An encrypted connection and two-step sign-in for anyone who turns it on. Residents can ask to access, correct or delete their data.
- Assemblies. Polls are opinion polls, counted by unit and by indiviso. They are not legally binding votes; decisions are made at your assembly.
- Cost. A flat rate per building, not per user. We are still shaping the plans with the first buildings.
- What it does not do yet. Online payment, tax invoices, store apps and automatic translation. Atriovia is in early access, and the features page keeps that list current.