Convergence Radar

← Feed

D

LeadMap: national lead-service-line & PFAS risk dataset from freshly-mandated utility disclosures

33/100

Normalize thousands of newly-published LCRI lead-line inventories and PFAS results into one address-level risk API/map — but the contractor lead-gen buyer is the weak link; the stronger play is selling the normalized dataset to PropTech/inspection or building the utility-side reporting tool.

Archive. · created 2026-07-14 12:45 UTC

public recordsregulationapisaaslong-termrevisit later

Scorecard

newness 6/10
convergence 5/10
demand evidence 2/10
existing spend 4/10
solo feasibility 5/10
speed to mvp 6/10
speed to revenue 4/10
distribution 4/10
competitive gap 5/10
expansion 7/10
founder fit 5/10

Penalty flags
no clear buyer no urgent pain adequate free path (−15 from raw 48)

Opportunity brief

What changed
Two 2024 federal drinking-water rules created brand-new public data artifacts. FACT: the LCRI (final rule, 2024-10-30) requires water systems to inventory and replace lead and galvanized-requiring-replacement service lines and lowers the lead action level to 0.010 mg/L. FACT: the PFAS NPDWR (final rule, 2024-04-26) set enforceable MCLs for six PFAS (PFOA/PFOS at 4.0 ppt), forcing monitoring and treatment. HYPOTHESIS: initial LSL inventories were broadly published by/around the Oct 2024 compliance date, so a corpus of address- and system-level disclosures now exists that did not exist to scrape before.
Why now
The disclosures are new and multiplying monthly as more systems post inventories and PFAS monitoring results, and Context.dev (YC S26) claims one-API schema-defined extraction from arbitrary sites, lowering the cost of normalizing heterogeneous utility pages without per-site scrapers.
Converging signals
Regulation (LCRI) + regulation (PFAS MCL) + dev capability (Context.dev extraction API) meet at 'newly-public compliance data that is expensive to normalize.' The convergence is real; the disputed link is whether the normalized data is accurate enough to route a truck and whether the named buyer will pay.
Customer pain
INFERENCE, not evidenced here: remediation contractors want geo-targeted replacement leads; realtors/inspectors want address-level lead/PFAS risk for disclosures. demand_evidence is EMPTY — no complaints, job ads, or spend proof for any of these buyers is in the input, so all pain is hypothesized.
Who pays
Claimed: LSL/PFAS remediation contractors buying leads; secondarily relocation/real-estate and home-inspection firms buying address-level risk data. The forced party (utilities) is NOT the proposed buyer — a key weakness.
Solved today
Contractors buy leads from generic marketplaces (Angi/Thumbtack) and door-knock post-notification lists; researchers/PropTech pull scattered utility PDFs and state dashboards by hand; EPA and several states already publish aggregated LSL data.
Why current solutions are bad
Fragmented, inconsistent formats; huge 'unknown material' fractions in inventories make address-level risk noisy; no single national, normalized, queryable layer.
Proposed product
A normalized national lead/PFAS risk dataset with an address-lookup API + map, ingested via Context.dev-style extraction, geocoded, QA'd against known inventories. Monetize as a data/API subscription first (PropTech, inspection, insurance, environmental firms), with contractor alerting as a secondary, later channel — NOT as the launch wedge.
MVP version
Pick 25-50 utilities with published inventories, extract + normalize to a schema (address, material class lead/GRR/non-lead/unknown, source URL, date), geocode, and expose an address lookup. Run the input's KILL TEST: hand the extracted data to one remediation contractor and one inspector and measure accuracy/actionability before scaling.
30-day build
Build the extraction+normalization+QA pipeline for a single state with good disclosure coverage; measure extraction error against 5-10 hand-verified inventories; publish a free public lookup for that state to seed inbound and prove accuracy.
60-day build
Expand to 3-5 states; add PFAS monitoring results; talk to 15-20 candidate buyers (inspection franchises, PropTech data teams, environmental consultancies) to find who actually pays for the dataset/API; validate a price.
90-day revenue plan
Sell dataset/API access to the first paying data buyer(s); only then test contractor lead alerting where lead density is high. Also validate the pivot below.
Distribution path
SEO on 'is my address lead pipe / PFAS' address pages (inbound), direct outreach to inspection franchises and PropTech data buyers, and a public map for credibility. Contractor lead-gen would require ad spend/cold sales — the channel the founder avoids.
Pricing hypothesis
Data/API subscription $200-$1,500/mo by seat/volume for professional buyers; per-report micro-fees for consumer lookups. Contractor per-lead pricing only if lead quality is proven.
Technical difficulty
Moderate-to-hard: single-API extraction is easy; the real cost is QA/entity-resolution/geocoding across thousands of inconsistent formats and bounding extraction error so the data is trustworthy. 'Unknown' material fractions cap achievable precision.
Legal / regulatory risk
Data itself is public. Real risk is liability/accuracy claims if address-level 'lead risk' drives real-estate or health decisions — needs disclaimers and sourcing/citation to the utility record. PFAS/lead health framing invites scrutiny.
Platform dependency
Dependent on Context.dev (single young vendor, terms/pricing/uptime risk) and on utilities' publication formats; not deplatformable by a marketplace.
Founder fit
Partial. Public-records + regulation aggregation matches his strengths, but the proposed monetization is discretionary contractor LEAD-GEN (ad-spend/relationship-sales flavored), which he explicitly avoids — NOT the forced-filer/per-filing shape he excels at. The higher-fit pivot: build the UTILITY-SIDE tool that helps small water systems compile and submit their LCRI inventory to the state primacy agency's portal (per-system SaaS/per-filing) — that is his proven FMCSA-shaped play. Recommend surfacing that pivot.
Breakout potential
Moderate: a trusted national lead/PFAS address dataset could expand across 50 states and into insurance/mortgage/environmental data buyers. But it risks becoming a commodity if EPA/states publish clean aggregated data themselves.
Final recommendation
WEAK as pitched (contractor lead-gen), PROMISING as a pivot. Do NOT launch as contractor lead-gen. Do a 2-week accuracy spike (the KILL TEST) on one state; if extraction is trustworthy, monetize as a normalized dataset/API to professional buyers, and separately scope the far-higher-fit forced-filer play: a per-system tool that helps small water utilities assemble and submit their LCRI inventory to the state primacy portal.
Next action
Extract and normalize inventories from 25 randomly chosen utility sites, hand the output to one remediation contractor and one home inspector, and measure whether the data is accurate/actionable enough to pay for — decide go/no-go from that.

Kill arguments (adversarial)

  • demand_evidence is EMPTY — zero evidence any contractor, realtor, or inspector will pay; the entire buyer thesis is unvalidated intuition.
  • Contractor lead-gen is discretionary, ad-spend/sales-heavy, and competes with entrenched marketplaces — precisely the model the founder avoids; contractors are skeptical lead buyers who churn on lead quality.
  • Data accuracy is the whole product and the hardest part: heterogeneous formats plus large 'unknown material' fractions may make address-level routing unreliable, failing the KILL TEST.
  • EPA and multiple states already publish aggregated LSL inventories/maps, so an adequate-free-path may already exist for the very lookups you'd charge for.
  • The forced party (utilities) isn't the buyer, so the strongest demand signal (a mandate) doesn't attach to your revenue.

Competitors

• EPA / state LSL inventory dashboards (link) — Government-published, free aggregated lead inventory data that may already serve the core lookup — an adequate-free-path risk.
• Angi / Thumbtack (link) — Entrenched contractor lead marketplaces the lead-gen version would compete with on price and lead quality.
• BlueConduit (link) — Established lead-service-line predictive/inventory analytics vendor already selling to utilities — competitor and proof the utility-side is a real market.

Source citations (facts)

• Lead and Copper Rule Improvements (LCRI) final rule — Water systems must inventory and replace lead/galvanized-requiring-replacement service lines and the lead action level is lowered to 0.010 mg/L — creating the newly-public inventory data.
• PFAS National Primary Drinking Water Regulation — EPA set enforceable MCLs for six PFAS (PFOA/PFOS at 4.0 ppt), forcing utility monitoring/treatment and generating public PFAS test results.
• Context.dev (YC S26) — structured data from any website via one API — Provides schema-defined extraction from arbitrary public sites, the ingestion capability that makes normalizing heterogeneous utility disclosures cheap.

Actions