Public records data mining and monitoring
Government registers publish business events every day — new entities, new licences, new permits. Software that watches them turns filings into first-mover leads.
At handover you get
- A written source map for your market: what exists, what it contains, what it costs to work
- Working pipelines for each usable register
- New-filing alerts on your cadence
- The database and the code
Fixed price agreed in writing before development starts. Hosting and maintenance are optional, and nothing stops working if you decline them — you hold the code.
Public records are the most underused lead source in the country. Every state publishes business registrations. Most counties publish building permits and business licences. Professional boards publish licensees. All of it is public, most of it is machine-readable, and almost nobody works it systematically because the formats are awful.
We specialise in exactly that awfulness. This is the same engineering behind the permit database we run on this site — several hundred thousand records assembled from official registers — applied to whichever registers matter to your business.
Where it fits
- Lead Scraper Development
- Custom Web Scraping Services
- Data Enrichment & Verification
- Custom Lead Database
- Lead Generation Automation
- CRM Integration & Lead Routing
- Lead Scoring & Prioritisation
Most projects are one build type. Some are two joined together — a scraper feeding a database, or enrichment feeding a CRM integration.
What the build covers
Register discovery
We find which bodies publish what in your target geography, in what format, on what schedule, and with what contact detail attached. That map is the first deliverable and it is often the most valuable one.
Format wrangling
Portals, exports, tables, scanned rolls and inconsistent column names normalised into one clean schema.
Event monitoring
New filings detected on each run — a business registered, a licence issued, a permit granted — so you hear about it in days rather than finding it a year late.
Entity resolution
Filings tied back to the same real business across registers, so an owner with three permits is one record with three events.
A public-records pipeline we run: PermitPulse
PermitPulse is the short-term-rental permit dataset this company builds and sells. It reads government registers, from state license files to city permit lists, and holds 283,611 records; 56 of the registers hold 150 or more records and have a public page of their own. On October 22, 2026 every register was pulled daily except Florida's license file, which is pulled every four hours.
The hard part was not the download. Several layers that looked like permit registers turned out to be something else: a city zoning map with 27,786 addresses where rentals are allowed, a county layer of 6,089 owner names with no address, a residential parcel list of 1,000 ordinary homeowners. Each is named in the code and left out of every count and export. The same check belongs in any public-records build.
- What sets the number: how many sources have to be parsed, how clean those sources are, how much data moves, and where the output has to land — not how long we spend.
- Fixed, in writing, before development starts. A paid source-mapping phase comes first so the quote is based on what the records actually contain.
- Hosting and maintenance are optional. Decline them and everything still runs, because you hold the code.
- No per-lead fees. We do not meter your own data back to you.
Questions
Which records are actually available?
It varies enormously by state and county, and honesty here saves everyone money. Some jurisdictions publish applicant phone and email on every record; some publish an address and nothing else; some preempted a programme entirely and publish nothing. Scoping starts with mapping that reality for your specific market, and if the records you need do not exist we say so before you spend anything.
How fresh are new filings?
As fresh as the publishing body. Some registers update daily, others monthly. The pipeline runs on a schedule matched to each source, and every record carries its filing date so you always know what you are looking at.
Is contacting people from public records allowed?
Public availability is not consent. TCPA, state Do-Not-Call rules and CAN-SPAM still apply, and a number on a permit is often the owner's personal mobile, which pulls consumer rules into play. We build the data pipeline; the outreach compliance is yours, and we would rather flag it now than have you learn it later.
Other build types
Lead Scraper Development
A scraper built for one job: your sources, your fields, your filters — running on a schedule and dropping clean records where your team already works.
Read more →Custom Web Scraping Services
Public web data, extracted properly: parsed, deduplicated, verified and delivered in a format your team can work the same morning.
Read more →Data Enrichment & Verification
Take the list you already have, fill the gaps from public sources, kill the dead records, and keep it that way on a schedule.
Read more →Custom Lead Database
A private database of your market — built once from public sources, kept current automatically, searchable by the people who have to call it.
Read more →Lead Generation Automation
The whole chain, wired end to end: find, verify, score, route, notify. No one on your team copying rows between tools.
Read more →CRM Integration & Lead Routing
Get sourced records into the system your reps already live in — matched, deduplicated against what is already there, and assigned correctly on arrival.
Read more →Lead Scoring & Prioritisation
Rank the list before anyone dials it — on signals from your own closed deals, not a vendor's black box.
Read more →Guides for buyers
Where we build
What 80 government registers publish
Public records vary more by publisher than by subject. Of the 80 permit registers in PermitPulse with 100 or more records (counted October 23, 2026), the table shows how many fill each field on at least half of their records. 61 name the permit type. Far fewer publish a way to reach the holder: 32 fill a phone column and 24 an email column on most rows.
That gap decides the build before any code is written. A register with names and addresses but no phone is a direct-mail source, or an input to an address match against county property records. A register with a filing date supports a weekly "new since last run" feed; one without it needs the build to keep its own first-seen date. 39 registers publish a filing date on most rows, and 15 carry ten or more applications still marked pending.
| Field | Registers that fill it on most rows |
|---|---|
| Owner or business name | 57 |
| Permit type | 61 |
| Status | 57 |
| Filing date | 39 |
| Separate mailing address | 16 |
| Phone | 32 |
| 24 | |
| Pending applications (10+) | 15 |
Describe the problem, not the spec.
Tell us who you are trying to reach and how you find them today. We come back with a source map, a fixed price, and an honest note on anything we do not think will work.