Choosing building software is a budget decision your board will live with for years. This guide gives you a practical evaluation process: the problems to inventory first, the questions to ask every vendor, the red flags that predict regret, and a checklist table you can bring to your next meeting.
What problems should we inventory before we talk to any vendor?
Most boards start by booking demos. That is backwards. A demo is a tour of what the vendor wants to show you. An inventory is a list of what your building actually needs. Do the inventory first and every demo becomes a test instead of a pitch.
Spend one board meeting listing your real pain, in plain words. Some prompts that work:
- Money. How do owners pay condo fees today? How many still pay by cheque? Who chases late payers, and how many hours does that take each month?
- Communication. When the water gets shut off, how do residents find out? Can you prove who received the notice? Boards get pulled into disputes that a delivery record would have ended in one minute.
- Maintenance. Where do repair requests live right now? Email, a phone call to the manager, sticky notes at the desk? Can a director see what is open, what is stuck, and what a vendor was actually asked to do?
- Governance. How do board decisions get made between meetings? Email threads with no vote record are a liability. Can you reconstruct who approved a spend six months later?
- Records. When a director leaves, where does their knowledge go? Bylaws, AGM minutes, vendor history, and unit records should belong to the building, not to one person's inbox.
Rank the list. Pick the top three problems. Those three become your scoring criteria for every vendor. If a platform dazzles on features you did not list and misses your top three, it fails, no matter how good the demo felt.
What questions should we ask every vendor?
Ask the same questions of every vendor, in the same order, and write the answers down. Here are the six that matter most for a condo board.
Who holds resident money?
This is the single most important question, and many boards never ask it. When an owner pays a condo fee or an amenity deposit through the software, does the money sit in the vendor's account before it reaches yours? If the vendor holds funds, you have taken on their solvency risk and their processing delays. The better model is a payment structure where funds settle directly to an account owned by the corporation. URBI answers this one cleanly: each building runs on its own Stripe Connect account and the platform never holds resident money. The reasoning is laid out in who actually holds resident payments and deposits, which is worth reading even if you choose different software, because the question applies to every vendor.
Is there an audit trail?
Boards are fiduciaries. Ask the vendor to show you, live in the demo, the record of who did what and when. Who changed a resident's role. Who approved a payment. Who edited a document. If the answer is a shrug or a report that has to be requested from support, that platform will not protect you when a decision is challenged. URBI keeps a permanent audit trail on actions, role changes, votes, waivers, check ins, and payments, and even logs every action its AI takes, which is the standard you should hold everyone to.
How does voting and quorum work?
Between meetings, boards approve spends, pick vendors, and defer decisions. Ask whether the software treats this as a real workflow or a comment thread. Can a decision be opened, voted on with approve, reject, or abstain, and closed with a recorded outcome? Does the system track quorum automatically and remind directors who have not voted? Can votes attach to a specific vendor bid so an RFP outcome is unambiguous? URBI does all of this natively, including per vendor voting on RFPs and automatic quorum tracking. Whatever you buy, refuse anything where the official record of a board vote is a screenshot of an email.
What does onboarding involve?
Ask exactly how your unit list, owner contacts, and documents get into the system, who does the work, and how long it takes. Ask what happens to data quality problems in your existing records. Honest vendors will tell you that onboarding is mostly about your data, not their software. Be equally honest with yourself about integrations: URBI, for example, imports from your existing systems by CSV rather than a live two way sync, so ask every vendor to state plainly what is a real integration and what is a file import.
What is the contract term, and how do we leave?
Ask for the initial term, the renewal mechanics, and the exit process. Does the contract renew automatically, and with how much notice to cancel? If you leave, do you get your data back, in what format, and at what cost? A vendor confident in their product does not need a multi year lock to keep you. A board should never sign a term longer than it would give a landscaping contractor without a strong, written reason.
How do residents actually adopt it?
Software the residents ignore is a line item with no return. Ask what a resident's first day looks like. Is there a real mobile app they will actually open? Can someone who never installs the app still pay a fee or sign a waiver from an email link? Ask the vendor for their honest view of what share of residents in a typical building are active after six months, and how they measure it. A platform that gives residents daily reasons to open it, like package notices, amenity bookings, and visitor passes, earns adoption. The URBI residential overview shows what a full resident experience looks like, from payments to amenity booking, and is a useful benchmark for judging anyone's resident app.
What red flags should make us walk away?
- Long initial terms. Three year commitments before you have seen the product work in your building shift all the risk to the corporation. Ask why a shorter term is not on the table.
- Per module pricing creep. If voting is one module, communications another, and payments a third, your quoted price is a floor, not a ceiling. Get the full list of modules and the all in cost for your real needs in writing before you compare vendors.
- No delivery tracking on communications. If the platform cannot show which residents received and saw a notice, it is a bulletin board, not a communication system. Delivery tracking is what turns "we sent it" into proof.
- Paper workarounds for voting. If the vendor's answer to board governance is "most of our boards handle that offline," the governance feature does not really exist. The same goes for proxy processes that end in a spreadsheet.
- Vague answers on money flow. Any hesitation on the "who holds the funds" question is disqualifying. This is your residents' money.
- No plain answer on data export. If leaving is hard, staying was never a choice.
What should our comparison checklist look like?
Score each vendor from one to five on every row. Ask for proof, not promises: a live demo of the feature, not a slide about it.
| Criterion | What good looks like | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| Money flow | Funds settle to an account the corporation owns; platform never holds money | |||
| Audit trail | Permanent log of actions, votes, payments, and changes, shown live in demo | |||
| Board voting | Recorded votes, quorum tracking, per vendor RFP outcomes | |||
| Communications | Urgency levels, push and email, per resident delivery tracking | |||
| Maintenance | Visible ticket workflow, vendor access without extra licenses | |||
| Resident adoption | Real mobile app plus a no account path for one off payments | |||
| Onboarding | Clear import process, named owner of the work, realistic timeline | |||
| Contract and exit | Short initial term, plain renewal terms, free data export |
Weight the rows by your top three problems from the inventory. A board whose biggest pain is communication should weight delivery tracking heavily; a board burned by a past vendor dispute should weight the audit trail. If you want a deeper look at how specific platforms stack up on these rows, see the roundup of the best condo management software and the head to head URBI vs Condo Control comparison.
Frequently asked questions
How long should a proper evaluation take?
Plan for one budget cycle: one meeting for the problem inventory, two to four weeks of demos with your fixed question list, then a scored comparison at the following meeting. Rushing to sign before a fee season is how boards end up in long contracts with unused modules. A month of diligence is cheap next to three years of the wrong platform.
Should the board or the property manager choose the software?
Both, with clear lanes. The manager evaluates daily workflows like tickets, packages, and vendor coordination, because they live in the tool. The board owns the governance questions: money flow, audit trail, voting, contract term. A platform only the manager loves fails the board's fiduciary test, and one only the board loves dies from manager workarounds.
What does URBI cover, in one paragraph?
URBI is one platform for operations, communication, payments, governance, and the resident experience, with two built in AI agents: HERO for the manager and Arthur for residents by phone, SMS, email, and in app chat. Start with what URBI is for the full platform picture, including lobby and elevator displays for building communication.
Do residents without smartphones get locked out?
They should not, and this is worth testing in every demo. Ask each vendor how a resident without the app pays a fee or signs a document. URBI handles it with a public portal: a one time code sent by email opens a single payment or document, with no app download and no account creation required.
A good evaluation is mostly discipline: inventory your problems, ask every vendor the same hard questions, and score the answers. If you want URBI in your comparison, or just want a second opinion on your checklist, write to hello@myurbi.co and a real person will answer.
