Your owner asks a reasonable question in the monthly review: are the stores with the weakest reviews also the ones priced furthest above their markets? It sounds like one question. It touches three different sets of data, and none of your reports were built to answer it.
That is not a reporting problem. Hummingbird and just about every modern Property Management Software (PMS) ship with more than a hundred prebuilt reports, plus custom reporting and scheduled delivery, and most serious platforms in the industry offer something comparable. That reporting is accurate, it is maintained, and most operators run their week on it.
The problem is that the question reaches past what the system can see.
This post is about where those edges are, why they get filled by hand in most operations, and what it looks like to extend them.
Every report a property management system produces draws from the same place: the data the system itself holds. Tenants, spaces, rates, payments, leases, tasks, auctions. Inside that boundary, reporting is fast, reliable, and flexible, and for the day-to-day questions of running facilities, it is usually exactly what an operator needs.
The limitation is not quality. It is scope. A system can only report on what it contains, and some of the most useful questions in the business depend on information that lives somewhere else, or on combinations nobody set up in advance.
That distinction matters, because it changes the fix. If the problem were weak reporting, the answer would be better reports. Since the problem is the boundary, the answer is extending what the reporting can reach.
Three edges show up in most operations, whatever the portfolio size.
Data the system does not hold. Your property management system knows exactly what you charge. Unless something brings it in, it does not know what the competitor down the road is charging, how your website traffic converted last month, or how your review scores are trending. Those live in other systems, and a report can only use what is in front of it.
Questions the report list does not cover. Prebuilt and custom reports are both answers to anticipated questions. The one from the monthly review is a new combination, and nobody built that report because nobody knew it would be asked.
Data in a place you cannot work with it. Whoever analyzes the business, you or someone you hired, eventually wants the numbers in their own tool, joined with everything else, in a shape they control.
That usually starts with exporting and stitching rather than analyzing.
None of these are failures of the reporting. They are the natural limits of any system that reports on its own data in its own views.
In most operations, each edge already has a workaround, and the workarounds are worth taking seriously.
Market data comes from a subscription, a revenue management tool, or a manager who knows the market well. The new question gets answered in a spreadsheet somebody assembles from two or three exports. The analyst builds their view by exporting on a schedule and rebuilding it each month.
What a workaround cannot do is scale, survive turnover, or run at the moment a decision gets made. It runs when somebody has time. And because each answer costs effort, a question only gets asked when it is urgent enough to justify the work. Plenty of useful ones never clear that bar.
That is the real cost at the edges. Not a lack of information, but information that arrives on a schedule set by how busy somebody is.
Tenant Intelligence is how Tenant Inc. extends reporting past each of those three edges.
Competitor Intelligence, through a partnership with TractIQ, puts the local market inside Hummingbird, in Rate Management, in Rent Roll, and in every management report, so competitor pricing sits next to your own numbers wherever you are looking at them. That covers the first edge for the market specifically.
The MCP Connector lets a team ask Claude, ChatGPT, or other AI tools about their own business in plain English and get the answer built from their data, including the combinations no report anticipated. That covers the second edge.
Tenant Data Warehouse is a dedicated instance of the operator's own data, structured and current, bringing Hummingbird operations together with web analytics and reputation data, pointed at whatever BI tool the team already uses and exportable as CSV, JSON, or PDF. That covers the third edge, and the rest of the first.
None of it replaces the reports your team already runs on. It answers the questions those reports were never going to reach.
All three depend on consistent definitions underneath them, which is its own project and worth doing first.
Before deciding which capability to add, look at which of your questions currently get answered by hand.
If your team assembles a market picture before rate decisions, that is one edge. If somebody rebuilds the same spreadsheet every month, that is another. If whoever analyzes the business spends the first week of every month exporting rather than analyzing, that is the third.
Most operators run into at least one. The ones who hit all three are usually the ones who grew fast enough that the workarounds accumulated faster than anybody noticed.