Where Property Data Tools Get Their Data

Every few weeks someone in a wholesaling forum asks the same question: where does PropStream actually get its data? Usually it's because two tools handed them the same owner and the same "high equity" tag, or because a lead they paid for turned out to be six months stale. The answer is a lot less proprietary than the pricing implies.

Short version: the same public records you could pull yourself, licensed in bulk from a handful of county-data wholesalers, and refreshed on a lag.

Property data tools like PropStream, BatchLeads, and PropertyRadar don't own their data. They license bulk public records, county assessor rolls, deed and mortgage recordings, and tax-delinquency files, from a small set of data wholesalers, then normalize and repackage them. The records are public. What you pay for is the aggregation and the skip tracing bolted on top, not a private feed nobody else can see.

Understanding that changes how you think about finding distressed properties: the raw material is free, and the fresher version of it is the one you assemble yourself.

The three files every tool is built on

Strip any of these platforms down and you find the same three public sources underneath.

• The assessor roll. Every county assessor publishes ownership, parcel characteristics, square footage, year built, and an assessed value. This is where "owner name" and the "equity estimate" come from. It's public, and most counties will sell you the entire file.
• The recorder's index. Deeds, mortgages, liens, and the notices that kick off a foreclosure all get recorded at the county. This is the source for "pre-foreclosure," "free and clear," and transaction history.
• Tax records. Delinquent property taxes are public, and they're the backbone of the "tax delinquent" list every tool sells.

That's the engine. Owner data, mortgage data, tax data, all county-level, all public, all resold by the same few vendors. It's why PropStream, BatchLeads, and PropertyRadar keep surfacing the same records in different interfaces. They're drinking from the same well.

The lag nobody prints on the pricing page

Here's the part that quietly costs you deals. Bulk county data doesn't refresh in real time. A vendor pulls a county extract on a schedule, monthly or quarterly for plenty of jurisdictions, and the platforms load it whenever they get it. So a deed recorded last week, a default filed this month, an owner who just inherited a house, none of it lands in the tool the day it happens. It shows up on the next refresh, assuming the county is one of the fresher ones.

For contrast: the code enforcement data I work runs on a daily pull. 84,430 cases across seven Puget Sound markets, and the newest cases in the file are from this week. That gap, this-week versus last-quarter, is the whole difference between a signal you can act on and one two hundred other investors already worked to death.

The data they mostly don't have

The bigger problem isn't lag. It's coverage. The bulk-data model works for records that are standardized and sold statewide: assessor, recorder, tax. It falls apart for records that live inside individual city departments and never get packaged for resale. That's most of the distress signals that actually predict a sale.

Code enforcement is the clearest case. Violations are filed city by city, across a dozen incompatible systems, with no standard format and no national vendor bundling them up. So they mostly aren't in the big tools at all. Same for 311 complaints, expired permits, and fire incidents. I keep a running directory of which cities publish code enforcement data and which make you file for it, and the pattern holds: this is the layer aggregators skip because it's too much work to collect and too fragmented to resell.

Which is the opening. A vacant-building citation, or a stack of repeat complaints, tells you more about seller motivation than an equity estimate does, and it's not sitting in the list your competition just bought. The fresher version is the one you pull and assemble yourself, straight from the city.

Aggregators vs pulling from the source

Neither column is the right answer for everyone. The point is knowing which one you're paying for.

So how accurate is the data, really?

Accuracy is really two questions: is the record right, and is it current.

The record itself is usually right, because the assessor and recorder are authoritative sources. Owner name, parcel data, recorded mortgage, those are generally accurate. Where it goes sideways is the derived stuff and the timing. "Vacant" and "absentee" are inferred, and inference off a lagged file is exactly where the errors live. Skip-traced phone numbers, the part that isn't public record at all, are the least reliable field in any of these tools.

So "how accurate is property data software" has an honest answer. The ownership backbone is solid. The freshness is only as good as the last county refresh. And the further a field sits from the raw public record, the more you should distrust it.

Where the big tools genuinely win

None of this makes the aggregators useless. It makes them a different tool. If you work nationwide, PropStream and its peers give you every county in one login, and no city-data approach comes close on breadth. They bundle comps, they bundle skip tracing, they run the driving-for-dollars workflow. For a lot of investors that convenience is worth the subscription, and I'd never tell someone farming ten states to go pull county files by hand.

The trade is breadth for depth. Buy the aggregator for national coverage and one-stop convenience. Don't expect it to hand you live, city-level distress signals it was never built to carry, and whatever list you do pull, filtering it down to the open, severe cases is still on you. If your edge is knowing a few markets deeply, the fresher and less-worked data is the one you build from the source.

If you want to see the layer the aggregators skip, the free map shows live code enforcement across our Puget Sound markets, pulled daily, no county-extract lag. Same public records those tools resell, minus the wait, plus the signals they don't carry.

Frequently asked questions

Where does PropStream get its data?

From bulk public records. PropStream licenses county assessor data (ownership, parcel details, assessed value), recorder data (deeds, mortgages, liens, foreclosure notices), and tax-delinquency records from data wholesalers, then normalizes and repackages them. The underlying records are public. The subscription pays for aggregation and the skip tracing layered on top, not a private source nobody else can reach.

Why do PropStream and BatchLeads show the same data?

Because they buy from the same well. Most property data platforms license the same county-level public records from the same handful of wholesalers, so their core ownership, mortgage, and tax data is nearly identical. The differences are in the interface, the skip-tracing vendor, and which extra lists they layer on, not in some proprietary feed one has and the others don't.

Is property data software accurate?

The authoritative fields usually are. Owner name, parcel characteristics, and recorded mortgages come straight from the assessor and recorder, so they're generally right. The weak spots are freshness, because bulk county data refreshes monthly or quarterly and recent changes lag, and derived fields like vacancy or equity, which are inferred and only as current as the last refresh. Skip-traced phone numbers are the least reliable field of all.

Do these tools have code violation data?

Mostly no. Code enforcement records are filed city by city in non-standard systems and aren't sold as a national bulk file, so the big aggregators generally don't carry them, the same goes for 311 complaints, permits, and fire incidents. That's precisely why those signals stay less competitive: they take real work to collect and can't be bought off the shelf.

Is the data real-time?

Rarely. Because it's licensed as periodic bulk county extracts, most platform data runs days to months behind the county, depending on that jurisdiction's refresh schedule. If timing is your edge, pulling a specific record straight from the source, or using a tool that refreshes daily, beats waiting on the next bulk load.