What changed
EPA finalized the Lead and Copper Rule Improvements (LCRI) on 2024-10-30, which — building on the 2021 LCRR baseline inventory requirement — compels affected drinking-water systems to maintain and update a lead/galvanized service-line inventory, lowers the lead action level to 0.010 mg/L, and mandates recurring reporting and customer notification. This is FACT, cited to the Federal Register rule text.
Why now
The baseline service-line inventory obligation under LCRR is already live (compliance date Oct 16, 2024 per the delay rule), LCRI layers durable ongoing inventory/replacement/reporting duties on top, and EPA's 8th Drinking Water Infrastructure Needs Survey (2024-12-13 ICR notice) signals continued federal data collection. Small operators are searching for a tool now because the deadline has passed the proposal stage and is dated/enforceable (FACT from cited rules).
Converging signals
Three signals meet at one point: (1) a finalized federal mandate creating a defined forced-filer class (every affected community/non-transient water system), (2) a cheap new capability — microsoft/markitdown — that converts utilities' legacy scanned tap cards/permits/office docs into structured rows, and (3) the buyer class being the least-resourced systems (few hundred to few thousand connections) with no compliance software or staff.
Customer pain
HYPOTHESIS (not directly evidenced in input, plausible from rule structure): small rural/community water systems have paper tap cards, no GIS, and a clerk/part-time operator who must produce a structured inventory in a state-prescribed format, classify every line (lead/galvanized-requiring-replacement/unknown/non-lead), file it, and send customer notifications — with penalty exposure. The mandate is FACT; the specific operational pain of these systems is inference and MUST be validated with the pre-pay test.
Who pays
Operators/clerks/managers of small community and non-transient non-community water systems facing the inventory-and-reporting deadline. Secondary buyer: rural water associations, circuit-rider/technical-assistance providers, and engineering/consulting firms that serve many small systems (white-label / multi-system channel).
Solved today
Free state-provided Excel/CSV inventory templates (most primacy states published one for LCRR), manual data entry, spreadsheets, a consulting engineer doing it as a billable project, or state technical-assistance staff helping fill the template.
Why current solutions are bad
Free templates solve the OUTPUT format but not the INPUT problem: getting decades of paper tap cards and scanned permits into structured rows is the actual labor. Templates don't do OCR/document conversion, don't track ongoing updates and re-notifications, don't generate the notification letters, and don't roll forward each reporting cycle. That gap is the wedge — but it is also the kill risk if the input volume per system is small enough to hand-type.
Proposed product
Web micro-SaaS: (1) import existing pipe records via CSV and via markitdown-powered conversion of scanned tap cards/permits/PDFs into structured rows; (2) a review UI to tag/confirm each line's material on both system-owned and customer-owned side; (3) validation against the state's required inventory schema; (4) one-click export of the EPA/state-format inventory file; (5) auto-generated customer notification letter templates and a notification log; (6) versioning so each reporting cycle rolls forward.
MVP version
Web form + CSV import + markitdown ingestion of scanned tap cards → tagged line inventory → export to the inventory format of ONE target primacy state + a notification letter template. Ship for a single state first to nail the exact required schema, then replicate.
30-day build
Pick ONE primacy state, obtain its official inventory template/schema and notification requirements, and run the KILL TEST: get 3 small systems (or one rural water association) to pre-pay or sign a paid pilot before building beyond a prototype. Build the CSV+markitdown import and state-format export against real tap-card samples.
60-day build
Harden the tagging UI, add the notification-letter generator and log, add cycle versioning, and onboard the pre-pay pilots. Recruit a rural water association or technical-assistance provider as a distribution partner. Instrument onboarding time (the true unit-economics variable).
90-day revenue plan
Convert pilots to paid $79/mo or $890/yr subscriptions; sign a white-label/multi-system deal with one association or engineering firm covering many systems; template the export layer for a 2nd and 3rd state to begin the 50-state replication.
Distribution path
Direct outreach to small-system operators via state primacy agency contact lists and the state drinking-water program's small-system list; rural water associations (NRWA state affiliates) and circuit-rider programs as channel partners; presence at state rural water conferences; content targeting operators searching 'LCRI inventory' / 'lead service line inventory template [state]'.
Pricing hypothesis
$79/mo or $890/yr per system for small systems; white-label/multi-system tier for associations and consultants priced per-system with a volume discount. Consider a flat one-time 'initial inventory build' setup fee to capture the front-loaded conversion labor.
Technical difficulty
Low-to-moderate. markitdown handles document conversion; the real work is per-state schema mapping and a clean review UI. No portal robotic submission is strictly required at MVP (export a file the operator uploads), which lowers risk versus the FMCSA-style direct-submission pattern.
Legal / regulatory risk
Low. Producing a compliance artifact the operator files themselves; no licensure required to build inventory software. Provide accuracy disclaimers (operator certifies the data). No platform owner to deplatform.
Platform dependency
None material — exports files to government systems; no marketplace/app-store gatekeeper. Dependency on state schema stability, which is manageable.
Founder fit
Very high. This is the founder's proven shape: a federal (and 50 state-primacy) mandate forces a defined class to file a structured submission, and a solo operator builds the compliance/conversion layer and charges per system per seat. His public-records, industrial-operations, and government-portal experience map directly; 50 near-identical state markets give the replication path he prefers.
Breakout potential
Moderate-to-high. Land one state, template the export, replicate across ~50 primacy states; expand into adjacent recurring water-system compliance (CCR Consumer Confidence Reports — also being revised, UCMR/PFAS monitoring, DWSRF-funded LSL replacement tracking). The same buyer has multiple recurring filings, enabling a multi-report platform for small systems.
Final recommendation
PURSUE, but gate the build on the pre-pay validation. The mandate and forced-filer class are FACT and the founder-fit is maximal, but the single biggest risk — that free state templates plus low record volume make conversion unnecessary — is real and cheaply testable. Get 3 small systems or one rural water association to pay before building past a one-state prototype. Prefer the association/consultant white-label channel to escape the smallest systems' tiny budgets.
Next action
Pick one primacy state, download its official LCRR/LCRI inventory template and notification requirements, and cold-outreach that state's rural water association plus 10 small-system operators to secure 3 paid pilots against a prototype built from real tap-card samples.