Prepared for Neil King  ·  Dewitt Carolinas

Off-market site flow, built from public data.

You named three challenges. This is about the second one, because it is the one that is actually a data problem. Rather than write you a proposal, I built a first pass across the Triangle and put it here.

The question I started with

If a site that pencils for 200+ units surface parked is sitting out there unlisted, what would have to be true about it, and can any of that be seen from a desk?

Before writing a line of code I spent the first stretch on the industry rather than the data, because the fastest way to build the wrong thing is to automate a process nobody actually uses. Two things came out of that.

First, the tooling gap is real and it is specific. The platforms that sell themselves as land-sourcing tools — the parcel aggregators, the ownership-data products, the site-selection suites — overwhelmingly filter on parcel size, zoning designation, and owner record. Those are the easy layers. They are easy because they come prepackaged statewide. Every developer running those tools is looking at the same filtered list, which is exactly why the good sites are competitive by the time they surface.

Second, that is not what actually kills a deal. Talking through how these sites die, the pattern is that a parcel clears acreage and zoning, gets a letter of intent, and then fails on something physical: a floodplain nobody looked at, a wetland that shrinks the buildable footprint below the unit count, or a sewer connection that turns out to be 2,000 feet and a lift station away. Those are the constraints that determine whether a site exists, and they are the ones the commercial tools do not filter on.

So I built the screen around the constraints that kill deals rather than the ones that are convenient to query.

How it was assembled

Five counties — Wake, Durham, Johnston, Orange and Chatham — and four public data sources, none of them purchased: the NC OneMap statewide parcel layer, the published gravity sewer networks from Raleigh Water and the Town of Cary, the FEMA National Flood Hazard Layer, and the USFWS National Wetlands Inventory. Everything was pulled fresh on August 6.

The density model is not a rule of thumb. It is calibrated against Litchford 315: 240 units on 14.3 acres, which is your own executed proof that the math works at that density. Each parcel is reduced by its floodplain and wetland area, then by a site-loss factor for roads, stormwater and setbacks, and the remainder is run at the Litchford ratio for three and four stories.

18,098parcels evaluated
564cleared every filter
40ranked for outreach
$0spent on data

How 18,098 became 564

Parcels 12–35 acres across five counties
18,098
Owner can actually sell: no government, HOA, conservation, utility or rail
16,427
Owner has a mailable address of record
16,306
Under-improved: improvements ≤30% of assessed value
10,742
Within 1,500 ft of a public gravity sewer main
997
≤15% of the site in floodplain or wetland
640
Carries 200+ units at surface-parked density
564

Sewer proximity eliminated 90% of the parcels that survived every other test.

10,742 sites cleared acreage, ownership and the under-improvement test. Fewer than a thousand of them sit within 1,500 feet of a public gravity main. That single layer is the difference between a list anyone can generate and a list worth acting on, and it is the clearest evidence that the constraint worth modeling is the physical one.

The under-improvement filter is doing quieter work worth calling out. Screening for parcels whose improvements are worth 30% or less of total assessed value is a proxy for an owner whose land is worth more than what is standing on it. That is a seller who has a reason to take a call, which is a different question from whether the site is buildable, and the reason the outreach list is 40 rather than 564.

Three of the forty

Owners, parcel IDs and addresses are withheld on this page. Everything else is exactly what the screen produces per site.

Site A

Raleigh, Wake County

Gross acres29.0
Developable acres22.6
Units, 3 story452
Units, 4 story588
To gravity sewer63 ft
Flood + wetland0.0%
Improvements$0
Land value per unit$4,264
Held by owner49 years
OwnerEntity, absentee
Name, PIN, addresswithheld
Site B

Unincorporated Wake County

Gross acres23.2
Developable acres18.1
Units, 3 story363
Units, 4 story471
To gravity sewer184 ft
Flood + wetland0.0%
Improvements$0
Land value per unit$1,950
Held by owner45 years
OwnerEntity
Name, PIN, addresswithheld
Site C

Unincorporated Wake County

Gross acres34.6
Developable acres25.9
Units, 3 story517
Units, 4 story672
To gravity sewer0 ft
Flood + wetland4.3%
Improvements$0
Land value per unit$4,449
Held by owner28 years
OwnerIndividual
Name, PIN, addresswithheld

Each of the 40 also carries the owner of record, their mailing address, ownership tenure, and the source layer and retrieval date behind every number, so verifying a site takes half a minute rather than half a day.

What it does not know yet

Worth being straight about, because this is the distance between a list and a pipeline.

Why the timing matters

Two North Carolina statutes move the buy-box inside the next five months. Parking minimums end statewide on January 1, 2027. And the 2026 Regulatory Reform Act, passed August 4 and awaiting signature, would permit residential redevelopment of previously developed commercial land by right in Raleigh, Cary and Charlotte, with no local height cap below 60 feet.

Meanwhile multifamily starts nationally are down 73% from peak, the lowest since 2011, with deliveries falling through 2027. A site controlled now and entitled through next year opens into the thinnest supply in a decade. Anyone screening against today's rules is screening against rules that expire.

What this is actually an example of

Site sourcing is one bottleneck. It is the one I could see from the outside, which is the only reason it is the one I built.

The useful thing here is not the list. It is that a constraint your team carries in its head — where the sewer is, what the flood map does to a footprint, which owner has a reason to sell — turned out to be expressible as a filter, and that filter now runs across 18,000 parcels in the time it takes to read this page. That same move applies to most of the repetitive judgment inside a development shop. Some candidates:

Entitlement and approval trackingWhere every active project sits across a dozen jurisdictions, each with its own calendar, portal and notification habits.
Capital partner reportingThe recurring package each equity and debt partner expects, assembled from the same underlying numbers in a different shape every time.
Bid leveling and cost historyComparing GC bids against what line items actually cost you on the last four projects rather than against each other.
Draw and lien-waiver administrationChasing the same documents monthly, per project, with the same three things always missing.
Lease-up and absorption trackingLive comps against pro forma, so a project trending behind is visible in week three rather than month four.

I do not know which of those is the expensive one for Dewitt. That is exactly what the next conversation is for.

The next step

A Discovery Session. Half a day with you and whoever else owns the operational reality, structured in two halves.

The first half is this build. We pressure-test the filter against how your team actually thinks, correct what it gets wrong, and walk the sites that survived, with owners and addresses attached.

The second half is wider. We map where the repetitive, judgment-heavy work actually sits across your operation, and rank it honestly by what it costs you now against what it would take to fix. Some of it will be worth building. Some of it will not be, and you will get told which is which.

You leave with your screening criteria written down in your own language, the ranked Triangle list, and a prioritized map of the operational opportunities worth pursuing, whether or not you pursue them with me.

Discovery Session

Half a day. Your team, your criteria, your operation.

$2,500

Credited in full toward whatever we build together.

Email Jason