06-reference/research

county permits data marketplace moat

2026-10-21·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
data-marketplacemoatspublic-recordsbuilding-permitscommoditization

The commoditization thesis is right about parsing and wrong about coverage. The moat survives, and it is already occupied.

The question

"Does the 'public data access is now commoditized' thesis kill the county-permits data-marketplace entry point, or does a curation/freshness moat survive for hyperlocal, poorly-structured public records?"

Two vault docs assert things that cannot both be fully true, and neither references the other. This is a reconciliation, not a market survey. Filed from the 2026-08-11 curiosity sweep.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Verdict: the thesis does not kill the entry point. It kills the entry point's description. Decomposing the difficulty four ways and marking what agent tooling actually cheapened: (a) ACCESS - split. Reading a published portal page is now near-free, which is real deflation. But an Accela tenant requires each agency's administrator to approve an app, offers no bulk export and no webhooks, and a meaningful share of jurisdictions publish nothing online or keep paper. An LLM does not shorten an approval queue, file a FOIA for free, or digitize a rural county. Shovels' own "linearly-scaling maintenance costs" is the whole economics: agents lowered the per-jurisdiction unit cost and did nothing to the exponent. Twenty thousand jurisdictions times a smaller linear cost is still a payroll. (b) NORMALIZATION - largely not cheapened, and this is where the moat concentrates. Schema reconciliation is a solvable mapping problem, but "variance in required fields" is not a mapping problem: a field the jurisdiction never collected cannot be recovered by a better reader. Missing-at-source is information-theoretically irreducible, and the residual work is per-jurisdiction semantic calibration - knowing that Tampa's declared job value understates true cost, which we learned by hand, not by model. (c) FRESHNESS - technically cheapened, bounded upstream, and not monetizable. Polling is free; the agency's nightly export is the ceiling; our own conversion evidence says buyers discount it. (d) ENTITY RESOLUTION - partially cheapened, still the hardest. Embedding and LLM fuzzy-matching genuinely help link permits to parcels, owners and contractors, but the ground-truth keys (parcel numbers, state license registries) are themselves per-jurisdiction assets you have to go get. A secondary source attributes Shovels an ~88% contractor match rate; unverified, and if true the uncovered 12% is the tell that nobody has published how to close it.

So a moat survives, but it should be renamed. It is a coverage-and-semantics moat, not a curation/freshness moat, and its defining property is that its cost is linear in jurisdiction count with no shortcut. That is the worst possible moat shape for a solo operator and a fine one for a funded team, which is precisely who holds it. Shovels claims 2,820+ jurisdictions and ~85% of population with a five-year collection head start; ATTOM, Construction Monitor, BuildZoom, Dodge and Cotality sit in the same lane; the easy slice is already a $29/mo commodity. The honest verdict is not "the thesis killed it" and not "the moat is open." It is "the moat survives, it is already occupied, and it is made of a cost RDCO cannot pay." Retire county permits as a business entry point. This costs the data-marketplace project nothing it had: [[2026-04-23-project-next-moves-audit]] already recommended defaulting to the clinical-research use case over county permits in April, and that recommendation has sat unexecuted for six months. Given RDCO is dormant (founder 2026-09-23), the right action is to strike the county-permits bullet and record why, so the next sweep does not re-raise it.

One correction propagates back. The selloff doc's claim that the data-marketplace bet is "exactly the bet that this analysis validates" should be scoped: validated for exclusive or hard-to-assemble datasets, contradicted for any entry point whose pitch is making public data searchable. That line in [[2026-02-16-vertical-software-selloff]] is the one that let this tension sit unexamined for eight months.

What is worth keeping is the demonstration, not the dataset. The four-layer decomposition above is a genuinely useful public artifact for the founder's stated near-term goal of credibility in agents-in-production for phData sales. The reason is that hyperlocal public records are the cleanest available counterexample to the lazy version of the commoditization story: model capability is not the binding constraint, harness design against thousands of non-conforming sources with missing-at-source fields and no ground truth is. We hold a non-hypothetical rep - the Tampa Accela pulls - and a concrete trap a naive agent pipeline gets wrong (declared job value read as build cost). "An agent that reads the permit perfectly and still produces a wrong dataset" is an original re-frame rather than a restatement of Bustamante, which is the bar for a Sanity Check piece. That is a writing candidate, not a venture, and it should be queued as one only if the founder wants a piece in that lane. No build, no data acquisition, no venture.

Why this is in the vault

It resolves the specific unsynthesized contradiction between moat #3 of [[2026-02-16-vertical-software-selloff]] and the county-permits bullet in [[01-projects/data-marketplace/index]], and supplies the strike-and-why for that bullet plus a scoping correction to the selloff doc's "validates the data marketplace" line. It also converts a dead entry point into a named credibility-artifact candidate for the agents-in-production positioning.

Open follow-ups

Related

Sources

Vault

Web