This guide walks commercial property managers, asset managers, and operations directors through evaluating building software: how to define requirements across operations, tenant experience, and money, the exact questions to ask vendors, the red flags to watch for, and a checklist you can take into demos.
Why does every commercial building end up with five systems?
Nobody plans a fragmented stack. It accumulates. A tenant experience app gets bought to help leasing. A CMMS gets bought after a maintenance audit. A visitor system arrives with a security upgrade. Communications live in a mix of email blasts and a portal nobody opens. And the connective tissue between all of it is spreadsheets.
Industry research on why commercial operators buy technology puts fragmentation at the top of the pain list: operators commonly run five to fifteen or more point solutions that do not talk to each other. The knock on effects are the rest of the list. Vendor management gets chaotic because bids and communications are scattered. Reporting stays manual because leadership cannot get portfolio wide visibility without someone compiling it by hand. Reconciliation lives in email threads.
So the first real decision in any evaluation is structural: are you buying another point solution, or are you consolidating? Platforms like URBI are built around the second answer, putting work orders, tenant communications, visitor management, amenity booking, events, and payments in one product. You can read the full picture in what URBI is and the commercial specifics in URBI for commercial buildings. Whichever direction you choose, choose it deliberately, because it shapes every other question below.
How do you define requirements before you talk to vendors?
Write requirements in three columns before any demo. Vendors are very good at demoing what they have. Requirements keep you anchored to what you need.
Operations
- Work orders: intake with photos, triage, priorities, assignment, recurring preventive maintenance, and a full activity log per ticket.
- Vendors: how outside contractors receive work, schedule visits, and report completion. Ask whether every technician needs a paid license.
- Visitors and access: guest passes, contractor check ins, denial reasons, and a searchable log.
- Physical inventories: fobs, keys, parking, storage. Who tracks what is tied to a suite when a tenant moves out?
Tenant experience
- One app for tenant employees covering requests, bookings, guest passes, packages, news, and messaging. Adoption dies when tenants need three logins.
- Amenity booking for conference rooms, fitness, and shared spaces, with rules, pricing, and closures handled properly.
- Events with real capacity management, not a signup form. See how events drive commercial tenant experience for what good looks like.
- Communications with urgency levels, targeting by floor or suite, and read tracking.
Money
- Where payments flow: rent, CAM, amenity fees, event tickets. Whose account holds the funds between charge and payout?
- Deposits and liability for amenity and booking charges. The details matter more than most buyers expect; amenity booking and deposits covers why.
- Reporting the asset manager will actually accept: portfolio roll ups, per property drill downs, and an audit trail behind every number.
The same research on buying criteria says commercial operators weigh demonstrated return, ease of implementation, scalability from one building to a portfolio, tenant adoption, total cost of ownership, and vendor stability. Put those on your scorecard alongside features. A comprehensive product that takes a year to implement can lose to a simpler one your team uses next month.
What questions should you ask every vendor?
One platform or a stack of point solutions?
Ask the vendor to list every adjacent tool their typical customer still runs after buying them. A tenant experience app that assumes a separate CMMS, visitor system, and payment tool is not consolidation. It is a sixth login.
What is your real tenant adoption?
Ask how tenants without accounts are handled. A visiting executive or one time vendor should be able to pay a fee or sign a waiver from a link, without downloading an app. URBI handles this with an OTP gated public portal, which is one honest reason its adoption story holds up: the app serves regular tenant employees, and everyone else still gets served.
How do work orders and vendor flows actually run?
Walk through a full ticket: intake with photos, triage, assignment, subtasks, and closure. Then ask the recurring maintenance question that separates real CMMS capability from a form builder: if the quarterly chiller service runs late, does the next one fire on schedule or after completion? URBI supports both trigger types. Also ask how a contractor participates. URBI sends vendors a tokenized work order link by email; they schedule, toggle subtasks, and upload completion photos with no account and no license fee for the HVAC tech.
What can you do with events and amenities?
Ask for ticket tiers, automatic waitlists, refunds, check in scanning, and post event surveys, not just an RSVP list. Ask whether closing an amenity for repair automatically detects conflicting bookings. URBI does both well; building events software explains what a full event stack includes.
Who holds tenant payments?
This is the question buyers most often skip. If the software vendor pools tenant money in its own account before paying you out, you carry their counterparty risk. On URBI, each property is its own Stripe Connect connected account, so rent, CAM, amenity fees, and event ticket revenue land in the property's own balance. The platform never holds the money. The reasoning applies to any vendor you evaluate; payments, deposits, and liability goes deeper.
What does the audit trail look like?
Ask to see the log, not hear about it. Every check in attempt should resolve to a recorded status with who, when, and why, including denials. Every ticket should carry a full activity history. Governance decisions and votes should be permanent records. When an asset owner asks why a contractor was denied entry on a Tuesday evening, the answer should be one query, not an email hunt.
What reporting does leadership get?
Ask for a portfolio view across buildings and a per property deep dive, without exporting to spreadsheets. Then ask what the AI layer really does. URBI's HERO is the manager facing AI: it answers live questions against building data, files tickets, drafts announcements, and drafts owner reports. Arthur is the separate tenant facing AI, answering calls, texts, email, and in app chat in ten languages, booking rooms and filing tickets. If a vendor says "AI," make them show which side of the desk it serves.
How do you handle integrations, honestly?
Ask every vendor for the unvarnished answer, and expect one in return. URBI's honest answer: data comes in from legacy property management systems via CSV import, not a live two way sync, and there is no published public API today. If a live sync with your existing accounting suite is a hard requirement, weigh that. If your current stack is the problem you are replacing, it matters less.
What are the red flags?
- Adoption numbers without definitions. "Ninety percent adoption" of registered users is not the same as adoption across all tenant employees in the building.
- Per seat pricing for vendors and contractors. Your contractor list changes weekly. Licensing every technician punishes you for using the system.
- Pooled tenant funds. If the vendor cannot clearly explain whose account holds tenant money and when it reaches yours, stop.
- Roadmap sold as product. Ask "is this shipped today?" for every feature in the demo, and get it in writing.
- No visible audit trail. If denials, refunds, and overrides are not logged, you will discover that during a dispute.
- Implementation measured in quarters. Ease of implementation is a top buying criterion for a reason. Long deployments burn internal sponsorship.
- No answer for the lobby. Communication should reach people who never open an app. Lobby and elevator screens with emergency takeover, like URBI Display, close that gap.
The evaluation checklist
| Area | Ask the vendor | What good looks like |
|---|---|---|
| Scope | What tools will we still need after buying you? | One platform for work orders, tenants, visitors, amenities, events, and payments |
| Tenant adoption | How do non account holders get served? | App for tenant employees plus a no download portal for everyone else |
| Work orders | Show recurring maintenance and the full ticket history | Schedule and completion based triggers, priorities, subtasks, activity log |
| Vendor flow | How does a contractor receive and complete a job? | Tokenized link, scheduling, photo proof, no per technician license |
| Events and amenities | Show tiers, waitlists, refunds, and booking conflict handling | Automatic waitlists, closure conflict detection, surveys |
| Payments | Whose account holds tenant money? | Funds land in the property's own account; platform never holds money |
| Audit trail | Show the log for a denied check in and a refund | Every action recorded with who, when, status, and reason |
| Reporting | Show a portfolio roll up and a per property drill down | Live views, no spreadsheet compilation, AI that queries real data |
| Integrations | What syncs live, what imports, what is roadmap? | A straight answer, in writing |
| Implementation | Time from contract to first building live? | Weeks, with a pilot path before portfolio rollout |
Frequently asked questions
Should we pilot before a portfolio rollout?
Yes. Most commercial operators pilot at one to three buildings before going portfolio wide, and the full cycle from identified need to full deployment commonly runs a year or more. A pilot tests the two things demos cannot: real tenant adoption and how your site teams actually work in the tool day to day.
Is a best of breed stack ever the right call?
Sometimes. If you have a deeply embedded CMMS your engineers love and a mandate only for tenant experience, a point solution can be rational. The cost is permanent: separate logins, separate reports, and spreadsheets as the glue. Price that integration burden into total cost of ownership before deciding, not after.
How should we evaluate AI claims from vendors?
Ask what the AI does against live building data, and for whom. URBI draws a clean line: HERO serves the manager inside the operator workspace, and Arthur serves tenants over voice, SMS, email, and in app chat. Ask any vendor to show the AI completing a real task end to end, with the action logged.
What about accounting?
Treat accounting claims carefully across all vendors and confirm what is shipped. URBI's accounting product, with general ledger, receivables, payables, and reconciliation, is in beta today, and URBI says so plainly. Prefer vendors who label beta and roadmap honestly over ones who demo futures as product.
A good evaluation is mostly good questions asked early. If you want to see how URBI answers every question in this guide against your actual building, write to hello@myurbi.co and ask for a walkthrough with your own requirements list in hand.
