Permit Propensity — Dima Perkis

Permit Propensity

I’m investigating whether public permit and real-estate data can uncover new opportunities and better leads for high-end home service businesses.

Read the story ↓

8,701 permit records across 7 public-source pipelines 143,031 parcel records and 97,446 valuation rows 388 named outdoor-project households identified in Atlanta and Sandy Springs

The Hunch

Landscaping companies usually hear about a project after the homeowner has already decided to act. I wondered whether public data could surface the opportunity earlier.

A pool permit can imply a yard that will need to be rebuilt. An addition, recent sale, retaining wall, or nearby completed project might also signal future outdoor work. The initial question sounded simple:

Which public signals make a household more likely to buy a high-end landscaping project?

The temptation was to jump straight to a score. I started with a back-test instead.

Round One: A Small Sample and One Surviving Signal

I resolved one landscaping client’s historical jobs to parcels, removed non-customer and zero-dollar records, and compared 30 customer properties with 140 controls matched on ZIP and appraised-value band.

The result was mostly a useful rejection of my assumptions:

Six of the 30 customer properties were within 500 meters of an earlier, different-client job. But those six observations represented only about four real geographic clusters. That is enough to support a straightforward neighbor campaign—not enough to sell a magical prediction model.

The judgment call was to leave the p-value inside the research and tell the simpler truth outside it:

Every finished project seeds its street. Start by helping the neighbors see what is now possible.

The Pivot

Instead of squeezing a fitted propensity score out of 30 cases, I reframed the work at population scale. Public home-service permits became observable project events, and the client’s customer history became a validation overlay rather than the entire truth set.

The first DeKalb pull proved that the data could be joined, but it centered on homes well below the client’s target market. So I moved the same method to Buckhead and in-town Atlanta, where the permit and parcel systems are both open.

The working data store now holds 8,701 permit records from seven public-source pipelines, 143,031 parcel records, and 97,446 valuation rows. The expanded pull also identified 388 named households tied to outdoor-project permits in Atlanta and Sandy Springs. That creates a useful, refreshable opportunity feed today. It does not yet prove which household will buy landscaping tomorrow.

Every red dot is a real outdoor-project permit. The grey field is a sample of the parcels they were screened against. Positions are offset about 55 meters so no dot points at anyone’s address. The clustering tells me where to look. It still doesn’t tell me who will buy.

From Propensity Score to Property Transition Atlas

The broader product idea is now a Property Transition Atlas:

It turns permit alerts into a map of changing properties and labels the evidence. It does not claim to identify who is likely to buy.

What the Work Changed

Still Unfinished

Models, agents, tools, and infrastructure

Python + DuckDB

Parcel-keyed data store, source ingestion, matching, back-testing, and reproducible outputs.

ArcGIS + county permit systems

Public permit and parcel sources across Atlanta, Fulton, DeKalb, Dunwoody, and Sandy Springs.

Conditional logistic regression

Compared customer parcels with value- and geography-matched controls without pretending the sample was larger than it was.

Address + parcel resolution

Parcel identifiers, normalized addresses, and spatial point-in-polygon matching connect events to properties.

Research agents

Mapped source availability, competitors, market positioning, and failure modes; claims that could change the conclusion were rechecked.

Property Transition Atlas

Turns the research into an explorable view of events, territories, contractor patterns, and evidence quality.