How real estate teams spot new homeowners from county records

Real estate teams spot new homeowners by reading the property records that US counties publish: when a home is sold, the county records the new owner, often the sale price and date, and sometimes a new mailing address. In xMap Flows the Property changes block reads those changes for a county on a schedule and passes on each new owner as an item, with the address and a position on the map. A weekly flow then filters, maps and sends the list to whoever needs it.

This article is for listing agents who farm a neighbourhood, buyer's agents, mortgage and insurance teams, renovation contractors, movers and anyone else whose business starts when a home changes hands. It covers what the records hold, the decisions they drive, a step-by-step AI employee, and the care that public records about private people deserve.

What a county record change tells you

Counties update their property records every few days on their own timetable. Each change the block finds carries its kinds, and you choose which to keep:

• New owner: the owner now and the one before, as the county writes them.
• Sale: the sale date and, where the county records it, the price.
• Value or tax: the assessed value before and after, and the change as a percentage.
• Zoning or use: a parcel whose recorded use changed.
• Mailing address: where the owner now gets mail.
• New or removed parcels: lots split, merged or created.

A sale often brings several kinds at once: a new owner, a price and a new mailing address. With Since the last run, each change is read once; the first look reads the last 7 days so the list starts with something.

Who uses new-owner records, and for what

The same change means different things to different teams. A listing agent farming a district wants to know what sold on their streets this week, at what price, to send neighbours a short market note. A lender or insurer wants to know when a home they cover changes hands, so the new owner hears from them before a policy lapses. A renovation contractor knows that kitchens, roofs and floors are redone in the first months after a purchase. A property investor watches sales above a price in a few ZIP codes, or owners whose mailing address is in another state, which often means a rental.

Each of these is a filter on the same stream, which is why one flow per use works better than one large flow trying to please everyone.

Signals to read in each change

• Owner is a company. An owner name with LLC or Inc. usually points to an investor, not a family moving in. A Branch block can send them one way and families the other.
• Mailing address elsewhere. A new owner who gets mail at another address is likely letting the property, not living in it.
• Value change. A big reassessment can mean an improvement was recorded, or a tax bill about to rise.
• Where it is. Each change is placed on the map by its parcel or, when the county no longer knows the parcel, approximately by its address. Keep only your farm area with Only in: the whole county, the Area of interest, or a list of ZIP codes.

The AI employee, step by step

Here is a made-up case: a listing team that farms three ZIP codes in Miami-Dade and sends neighbours a note when a home on their street sells.

1. Schedule: every Monday at 07:00.
2. Property changes: Changes in a county, county Miami-Dade, changes New owner and Sale, since the last run, only in these ZIP codes.
3. Only new: each sale reaches the team once, even if the county records it again.
4. Branch: owners whose names contain LLC leave from the Yes dot and are left there; the team works with families, so only the No dot carries on.
5. Sort and limit: the most recent sale date first.
6. Show on a map: the week's sales as points.
7. Email to the team once per run, with the list and the map.

On Monday morning the team sees every home that changed hands in its ZIP codes since last week, on a map, with the address, the sale date and the price where the county has one. Writing a neighbourhood note takes minutes instead of an afternoon of searching. An insurer would swap the first part for its own list of insured homes in My data and the Owner of each incoming place mode, then add What changed to catch the ones whose owner is different from last time.

Handle owners' details with care

Owner names and mailing addresses are public records, but they are about private people. xMap gives them to an AI block only when its instructions name the owner or the mailing address. Before you write to a new owner, follow the law where the property is, keep to people who would reasonably expect to hear from a local agent or contractor, and honour opt-outs. The Outreach block includes an unsubscribe link in every email and never writes again to someone who unsubscribed.

Mistakes to avoid

• Expecting every county. Coverage follows the counties xMap's property service reads. Check the County list before promising a client a market.
• Trusting dates after a gap. When a county pauses its updates for weeks, the whole gap arrives at once and its dates are approximate. The step says so and marks those changes.
• Reading every change as a sale. A new mailing address or a reassessment is not a purchase. Pick the kinds you need.
• Treating approximate positions as exact. A change placed by its address is approximate; fine for a map, not for a door-to-door route without checking.
• Sending a pitch the day after closing. New owners are flooded in their first week. A useful note, such as recent sales on their street, lands better than an offer.

Templates built on county records: new homeowners in Miami-Dade every morning, properties that sold this week in Los Angeles, new homeowners in Maricopa County, for home insurance and homes sold this week, for renovation work. The real estate page covers the work outside the US too.