A property manager running thirty-five communities can't carry every vendor rating, every seasonal maintenance pattern, and every improvement in their head at once. LotWize's Cross-Portfolio Intelligence dashboard benchmarks vendors, forecasts seasonal maintenance risk, and surfaces best practices across every community a PMC manages — automatically.
A property manager renegotiates a landscaping contract at one community after catching a vendor padding invoices for six months. Three miles away, in another community the same PMC manages, the identical vendor is still billing the same way — because the manager who caught it at Community A has no reason to know that vendor also services Community F, G, and J. The fix exists. It's documented. It just never left the folder it was solved in.
This happens constantly at portfolio scale, and it isn't a training problem or a communication failure — it's a structural one. A property management company running twenty or forty HOA communities has, in aggregate, more institutional knowledge about what works than any single manager could hold in their head. A vendor performing well in one community and poorly in another. A maintenance pattern that hits every property in the portfolio the same month every year. A billing practice one board caught that five others haven't. None of that knowledge moves between communities unless someone deliberately notices the pattern and tells someone else — and at portfolio scale, nobody has time to notice everything.
LotWize's Cross-Portfolio Intelligence dashboard exists to close that gap. It's a PMC-only feature — built for portfolio owners and staff who manage multiple communities under one account — that pulls data already sitting in LotWize (vendor ratings, sentiment trends, community rosters) and turns it into three concrete outputs: which vendors are underperforming relative to the rest of the portfolio, which maintenance categories are coming up in the next 90 days, and which improvements observed in one community might be worth trying in another.
Most HOA software, LotWize included at the single-community level, is built around one community's data: one board, one budget, one set of vendors, one set of violations. That's the right model for a self-managed HOA board — a board president only needs to see their own community. It's the wrong model for a property manager whose job is to run the same set of operational problems across dozens of communities that never talk to each other.
The result is that a portfolio's collective experience gets siloed by default. A property manager who negotiates a better rate with a pool-service vendor at one community has no built-in mechanism to flag that same vendor's pricing at a sister community. A community that handles storm-prep well every spring doesn't automatically share that timeline with a community two zip codes over that gets caught flat-footed every year. Nothing is hidden on purpose — it's just that nobody's job is to sit across all the communities at once and compare notes. Cross-Portfolio Intelligence is built to be the thing that does that comparison, continuously, without anyone having to remember to ask.
The dashboard, at /pmc/intelligence, is organized into three tabs that a portfolio owner or PMC staff member can switch between. Each one answers a different question, and each one is honest about what's a hard number and what's an AI-generated inference.
This is the most literal, least speculative piece of the feature. LotWize already tracks a rating per vendor per community (vendorRating) and which vendors serve which communities in a portfolio (vendorCommunityLink). The vendor benchmark tab takes every vendor in the portfolio, groups them by category — landscaping, pool service, HVAC, and so on — and computes a straightforward category average rating across every community using a vendor in that category.
Any vendor rated below 75% of its category average gets flagged. That's plain arithmetic, not AI — a landscaping vendor rated 2.9 against a portfolio category average of 4.1 gets flagged whether or not an AI model is involved. The table shows the vendor's own rating, the category benchmark, and how many communities currently use that vendor, so a portfolio owner can see at a glance whether an underperforming vendor is a minor, single-community annoyance or a vendor quietly serving six communities at below-average quality.
Only for the vendors that get flagged, Claude generates a short renegotiation-or-replacement suggestion — a sentence or two per vendor, not a full contract analysis. That's a deliberate scope limit: the arithmetic does the actual detection work, and the AI only adds a starting point for the conversation the manager was already going to have.
The second tab forecasts maintenance risk across the whole portfolio for the next 90 days, covering categories like pool inspections, HVAC, landscaping, roofing, and storm prep. It's calibrated to LotWize's actual launch market — Oklahoma's seasonal weather pattern — rather than a generic template, since that's where the communities in a typical LotWize portfolio actually are.
Each prediction includes a risk level (low, medium, or high), a timeframe, which communities in the portfolio are affected, a specific recommendation, and an urgency label (routine, proactive, or urgent). The dashboard also surfaces a single "top priority" call-out — the one action the AI considers most worth doing first, out of everything it generated — so a manager opening the tab on a Monday morning has an obvious place to start instead of a wall of equally-weighted line items.
It's worth being precise about what this is and isn't. These predictions are generated from regional seasonal patterns and the portfolio's community list — not from sensor data, inspection reports, or a specific vendor's maintenance schedule for a specific pool. It's a planning aid that tells a manager "storm prep season is starting, here's who it affects across your portfolio," not a substitute for an actual site inspection. Treat it as the thing that reminds a manager to schedule the inspection, not the inspection itself.
The third tab is the most inferential of the three, and it's worth explaining exactly how it works rather than letting it sound more magical than it is. LotWize already computes a rolling sentiment score for every community — the same score used by the portfolio sentiment tracking feature to catch communities trending unhappy. The best-practices tab reuses that same data from the other direction: it compares each community's most recent 30-day sentiment average against the preceding 30 days, looking for communities whose trend improved.
For communities showing a real uptick, Claude is given the trend data and asked to generate 3–5 hypotheses about what might be driving the improvement, each with a title, a plain description, the community where it was observed, the metric that improved, a confidence rating (low, medium, or high), and a list of other communities in the portfolio that might benefit from trying the same thing.
The honest caveat here matters: this tab is inferring a plausible practice from an observed outcome, not reading a change log of what a board actually did differently. It's a hypothesis generator ranked by confidence, meant to give a manager a lead worth checking on — "Community A's sentiment climbed 30% over the last month, here's a plausible reason why, and three communities with a similar profile that might benefit" — not a verified case study. A manager still has to call the community, confirm what actually changed, and decide if it transfers. The value is in surfacing the lead at all; without this tab, nobody is comparing thirty-five communities' sentiment trends against each other every week to notice which one just turned a corner.
None of these three views make changes on their own. Nothing gets sent to a vendor, cancelled, or scheduled automatically — every output is a suggestion surfaced to a human, consistent with how LotWize handles AI across the rest of the platform. The vendor benchmark doesn't know why a vendor's rating dropped, only that it did. The seasonal forecast doesn't know a specific roof's condition, only that roofing tends to need attention in a given month across an Oklahoma portfolio. The best-practices tab doesn't know what a board actually changed, only that something changed and sentiment moved. Each tab does one narrow, well-defined comparison across the portfolio and hands the result to a person who has the context to act on it — or decide it doesn't apply.
A self-managed HOA board with one landscaping vendor has no portfolio to benchmark against — there's nothing to compare that vendor to except its own history. A property manager running three communities can probably keep the differences between them in their head without much help. The value curve on Cross-Portfolio Intelligence bends sharply upward as the number of communities grows, because the thing it's solving — the fact that useful information about vendor X is sitting in Community A's data while Community F is stuck using the same vendor with no visibility into A's experience — only exists once there's more than a handful of communities to compare.
A PMC managing 30 communities with an average of 5-8 vendors each is tracking somewhere around 150-200 vendor relationships, many of them the same handful of vendors repeated across multiple communities. No manager reviews that many vendor relationships side by side every month on their own initiative. The dashboard doesn't replace the manager's judgment about any individual vendor, community, or season — it replaces the assumption that someone would otherwise notice the pattern across all of them, which at portfolio scale, nobody reliably does.
This pairs directly with AI due diligence for HOA portfolio acquisitions, which applies similar cross-community comparison to communities a PMC is considering adding, and with balancing property manager workload across a portfolio, which addresses the attention-scarcity problem that makes manual cross-community comparison unrealistic in the first place.
2026 Update: Cross-Portfolio Intelligence is available on LotWize's PMC portfolio tier. Explore LotWize for property managers or start a free trial to see vendor benchmarking, seasonal predictions, and best-practice suggestions generated from your own portfolio's data.
A property management company's collective experience — which vendors underperform, which maintenance categories are coming up, which improvements are working — is usually siloed by community, because nobody's job is to compare across all of them at once.
Vendor benchmarking is plain arithmetic (category averages, a 75% threshold) with AI-generated renegotiation suggestions layered only on top of vendors that are already flagged — the detection isn't AI, the suggestion is.
Seasonal predictions forecast 90 days of maintenance risk across a portfolio's communities, calibrated to LotWize's Oklahoma launch market — a planning aid, not a replacement for an actual site inspection.
Best-practice suggestions come from comparing each community's sentiment trend against its own recent history — they're ranked hypotheses worth a phone call, not verified case studies of what a board did differently.
None of the three views take action automatically — every output is a suggestion surfaced to a property manager who still makes the call.
Cross-portfolio intelligence refers to software that compares data across every community a property management company manages — rather than looking at one community in isolation — to surface patterns a manager wouldn't otherwise catch. LotWize's version benchmarks vendor performance, forecasts seasonal maintenance risk, and identifies best practices, all computed across an entire PMC portfolio at once.
LotWize calculates an average rating per vendor category (landscaping, HVAC, pool service, etc.) across every community in the portfolio using that category, then flags any individual vendor rated below 75% of its category's average. For flagged vendors, an AI model drafts a short renegotiation or replacement suggestion. The flagging itself is arithmetic; only the suggested next step is AI-generated.
It can generate a reasonable 90-day forecast based on regional seasonal patterns — LotWize's predictions are calibrated to its Oklahoma launch market and cover categories like pool inspections, HVAC, landscaping, roofing, and storm prep. These are planning prompts based on typical seasonal timing, not readings from sensors or per-property inspection data, so they work best as a scheduling nudge rather than a diagnosis.
They come from comparing each community's rolling homeowner sentiment score against its own recent history. When a community's sentiment trend improves, the system generates hypotheses about what might explain it and suggests other communities in the portfolio that share a similar profile. These are inferred leads ranked by confidence, not confirmed reports of what a board actually changed — a manager still verifies the underlying cause.
No — it's specifically a property management company (PMC) portfolio feature, because it only produces useful output when there's more than one community to compare. A self-managed board with a single community and its own vendors doesn't have a portfolio to benchmark against; LotWize's single-community tools (vendor tracking, violation management, financial reporting) cover that use case directly.
The fix your best manager already found is probably sitting unused in another community right now. Start a free LotWize trial to see what Cross-Portfolio Intelligence surfaces in your own portfolio, or read how balancing staff workload across a portfolio tackles the attention problem that makes manual cross-community comparison unrealistic in the first place.
LotWize handles violations, resident questions, dues reminders, and meeting packets automatically — so your board gets its time back.
More guides for HOA boards
Changing who manages an HOA — self-managed to professional, or one management company to another — is usually a manual, records-losing scramble. LotWize's Community Transfer feature turns it into a governed, board-approved, automatically-billed workflow.
Property management companies acquiring a competitor's HOA portfolio usually get a CSV manifest, a data room, and two weeks. AI due diligence reads that data the way an analyst would — scoring financial health, maintenance backlog, document quality, and compliance risk before the deal closes.
One property manager has 12 communities and a clean inbox. Another has 9 and is buried in escalations. Portfolio owners rarely see the gap until someone quits. LotWize's staff workload dashboard scores every property manager's caseload and lets owners rebalance it in a few clicks.