Every new HOA a property management company takes on used to start as a blank slate — no vendor list, no templates, no reference point. LotWize's Community-Similarity Matching compares a new community against the rest of a PMC's portfolio the moment it's added and surfaces the closest matches as an onboarding starting point.
A property management company signs its fortieth community. The onboarding checklist is the same one the PMC has run thirty-nine times before: set up the roster, pick a violation fine schedule, line up landscaping and pool vendors, decide on a budget structure. None of that work carries over automatically, even though the PMC almost certainly already manages a community down the street with a nearly identical unit count, a similar HOA structure, and vendors who'd happily take on one more account. The knowledge of "who to call" and "what usually works" lives in a manager's head, not in the new community's record — so every new community starts from the same blank page as the first one did.
LotWize's Community-Similarity Matching is built to close that specific gap. It runs automatically the moment a PMC adds a new community to a portfolio: it compares the new community against every other community the PMC already manages, ranks the closest matches, and hands the onboarding manager a short AI-written note pointing at the communities worth borrowing from first.
Most property management software, LotWize included, treats each community as its own record — its own roster, its own budget, its own vendor list, its own violation rules. That's the correct model once a community is up and running; a board shouldn't be looking at a sister community's data by accident. But it means the setup phase for a new community has no built-in way to reference anything a PMC learned onboarding the last one.
In practice, that institutional knowledge doesn't disappear — it just stays inside whichever manager handled the last few similar onboardings. A manager who just finished setting up a 180-unit community with a rental cap and a shared clubhouse knows exactly which vendors to call and which fine schedule tends to hold up for a community that size. A different manager, or the same manager six months later, has no structured way to find that reference point. They either remember it, ask around, or rebuild the same decisions from scratch. At a PMC managing dozens of communities, that's a lot of onboarding hours spent re-deriving answers the portfolio already has.
The feature sits behind the "Add a community" form in the PMC dashboard (/pmc/communities/new). A manager fills in the new community's name and an estimated unit count, submits the form, and — without any extra step on their part — LotWize kicks off a similarity check in the background against every other community already in that PMC's portfolio.
Here's what happens under the hood, described plainly rather than dressed up:
claude-haiku-4-5), a fast, low-cost model well suited to short text generation, along with each match's name and similarity percentage. Claude writes two to three plain-language sentences explaining what the match means for onboarding — which communities are worth looking at first for a starting point on templates and vendor choices.The entire round trip — building profiles, ranking, and generating the briefing — happens in the few seconds after a manager clicks "Create community," which is what makes it usable as a default rather than a report someone has to remember to go run.
It's worth being precise about the boundary here, the same way LotWize's other AI features draw an honest line between what's computed and what's suggested. This feature does not automatically copy a vendor list, a violation fine schedule, or a budget template from the matched community into the new one. It doesn't touch the new community's records at all. What it does is point a manager at the two or three communities in their own portfolio most worth opening side-by-side before they start making onboarding decisions from scratch — a ranked shortlist and a one-paragraph reason, not an automated setup wizard.
It's also worth being honest that the similarity score is only as rich as the inputs behind it. Right now, that's primarily unit count, because that's the one structured signal available at the moment a community is created — before any roster, budget, or vendor data exists for it yet. That means today's match is a reasonable first-pass filter based on scale, not a comprehensive comparison across every operational dimension a community has. A 150-unit gated community and a 150-unit non-gated townhome development will match closely on unit count alone even though their vendor needs might differ. The value isn't that the match is perfect — it's that "these two or three communities are worth a look" beats "start from nothing," and a manager still applies their own judgment about whether the resemblance holds up once they actually compare the two.
A PMC onboarding its second community doesn't need this — there's exactly one other community to compare against, and a manager will remember it without help. The value shows up as the portfolio grows past the point where a manager can hold every prior onboarding in their head. By the time a PMC is running twenty, thirty, or fifty communities, "which of our existing communities looks like this one" stops being a question a manager can answer from memory and becomes a question that requires actually comparing structured data across the whole portfolio — which is exactly the kind of always-on comparison a person won't reliably do for every new account, but software can run automatically every single time.
It also compounds with LotWize's broader bulk-onboarding tooling. A PMC bringing on a single new community gets the similarity briefing at creation time; a PMC importing an entire book of business through the portfolio onboarding wizard benefits from the same underlying comparison across every community being added at once, rather than each one landing as an isolated blank record. Neither replaces a manager's judgment about vendor quality or fine-schedule fit for a specific community — both exist to make sure a manager starts that judgment call with a reference point instead of a blank page.
This pairs naturally with AI due diligence for HOA portfolio acquisitions, which applies structured comparison to communities a PMC is considering adding, and with Cross-Portfolio Intelligence, which runs the same kind of portfolio-wide comparison on an ongoing basis — vendor performance, seasonal risk, and best practices — once a community is already live rather than at the moment it's created.
2026 Update: Community-Similarity Matching runs automatically for every community added through LotWize's PMC portfolio tier — no setup required. Explore LotWize for property managers or start a free trial to see how your own portfolio's communities compare when you add the next one.
Onboarding a new community traditionally starts from a blank slate, even when a PMC already manages a near-identical community — because nothing connects the new record to the portfolio's existing experience.
Community-Similarity Matching runs automatically when a community is added: it builds a numeric profile (currently led by unit count), ranks every other portfolio community by cosine similarity — plain arithmetic, not AI — and surfaces the top three matches.
Only the ranked matches get handed to AI, which writes a short plain-language briefing pointing at which communities are worth using as an onboarding reference — the matching itself isn't AI-generated, the explanation is.
The feature doesn't copy vendor lists, fine schedules, or budgets automatically — it's a ranked shortlist and a reason, not an automated setup wizard, and a manager still verifies the resemblance holds up.
The value scales with portfolio size: it's unnecessary at two communities and increasingly valuable past the point where a manager can no longer hold every prior onboarding in memory.
It's a PMC portfolio feature that automatically compares a newly added HOA community against every other community already in a property management company's portfolio, ranks the most similar ones, and generates a short AI-written note explaining which communities are worth using as an onboarding reference — for vendor selection, templates, and general setup decisions.
LotWize builds a numeric profile for each community and ranks similarity using cosine similarity, a standard method for comparing numeric profiles. Unit count is currently the primary signal, since it's the one structured data point available the moment a community is created, before any roster, budget, or vendor history exists for it. The comparison itself is arithmetic, not an AI judgment call.
No. Community-Similarity Matching surfaces a ranked shortlist of similar communities and a short explanation of why they're relevant — it doesn't modify the new community's records, copy vendor contracts, or apply a fine schedule automatically. A manager still reviews the suggested matches and decides what, if anything, to carry over.
Not particularly — with only one or two other communities to compare against, a manager doesn't need software to remember what those look like. The feature's value increases as a portfolio grows past the size where a manager can reliably recall every prior community's setup from memory, which is typically well before a PMC reaches double digits.
Community-Similarity Matching runs once, at the moment a new community is created, to give onboarding a reference point. Cross-Portfolio Intelligence runs continuously on communities that are already live, benchmarking vendor performance, forecasting seasonal maintenance risk, and surfacing best practices across the whole portfolio. One solves the cold-start problem at onboarding; the other solves the ongoing comparison problem once a community is operating.
The fortieth community a PMC onboards shouldn't take as long as the first one did. Start a free LotWize trial to see which of your own communities the next one matches, or read how Cross-Portfolio Intelligence keeps comparing your portfolio's communities against each other long after onboarding is done.
LotWize handles violations, resident questions, dues reminders, and meeting packets automatically — so your board gets its time back.
More guides for HOA boards
Property managers overseeing dozens of HOAs can't read every legislative update and manually cross-reference it against every community. LotWize's Legal Tracking logs state law and regulation changes once, then uses AI to flag which communities in the portfolio are affected and what to do next.
Email doesn't reach every homeowner, and it definitely doesn't prove a notice was ever sent. Here's how LotWize sends real USPS letters for violation notices — with address verification, delivery tracking, and an automatic email fallback — directly from the board's workflow.
LotWize's Community Board gives verified residents a moderated discussion space inside the same portal they already use for payments and violations — with automatic profanity filtering and board pin/delete controls Facebook groups don't offer.