What changed
FACT: EPA finalized enforceable PFAS MCLs (PFOA/PFOS at 4.0 ppt, 2024-04-26) and finalized designating PFOA/PFOS as CERCLA hazardous substances (2024-05-08). FACT: EPA proposed UCMR 6 (2026-07-01) requiring public water systems to collect national occurrence data on seven ultrashort organofluorine PFAS. The collision: mandated monitoring now generates the exact record that can establish Superfund liability and downstream tort exposure.
Why now
FACT: UCMR 6 is a fresh 2026 proposal moving into a multi-year monitoring window, while the CERCLA hazardous-substance designation is already final. HYPOTHESIS: utilities are entering a window where they are legally compelled to test but have no standardized playbook for handling a positive result — the pain is landing in the next 12-24 months as monitoring schedules publish. FACT: EPA also proposed (2026-05-20) extending PFOA/PFOS MCL compliance deadlines to 2031, signaling ongoing regulatory churn utilities must track.
Converging signals
FACT: two final rules (PFAS NPDWR + CERCLA designation) plus a proposed monitoring rule (UCMR 6) plus biosolids guidance (2026-07-06) all target the same substances at the same regulated party. The rule, the forced-filer class (public water systems), and the liability regime meet at one point: the compelled sample result.
Customer pain
HYPOTHESIS (strongly supported by the regulatory structure): utilities must sample under UCMR 6, but a positive PFOA/PFOS detection is simultaneously a CERCLA-relevant fact, a public-notification trigger, and discoverable litigation evidence. General counsel and utility directors fear self-generating the record that funds their own liability. FACT: the substances tested are the substances designated hazardous — the overlap is exact, not speculative.
Who pays
Public water utilities (community + non-transient non-community systems), their certified environmental labs, and the environmental/municipal law firms and consultants that already advise them. Larger utilities (serving 3,300+) are the first-wave forced buyers named in UCMR 5/6.
Solved today
HYPOTHESIS: utilities lean on outside environmental counsel (billed hourly), large environmental consultancies (Jacobs, AECOM, Arcadis), and lab-provided data portals that handle sampling logistics but NOT liability posture. No focused product ties the monitoring workflow to a result-triggered legal/notification playbook.
Why current solutions are bad
HYPOTHESIS: hourly counsel is expensive and reactive; consultancies are enterprise-priced and slow; lab portals report numbers without advising on the CERCLA/tort consequence or documenting source attribution (was the PFAS from the utility's operations or an upstream discharger it can point to?). The evidentiary framing that determines whether a utility is a victim or a defendant is left ad hoc.
Proposed product
A SaaS + guided-service product: (1) a UCMR 6 monitoring compliance tracker (sampling schedule, method/lab requirements, deadline calendar, submission checklist to EPA's SDWARS system); (2) a result-triggered playbook engine — when a detection crosses a threshold, it generates the notification sequence, preserves chain-of-custody documentation, and produces a source-attribution work file (upstream discharger identification, historical use records) that positions the utility as a downstream receiver, not the polluter; (3) a liability-posture dossier that outside counsel can pick up. Sell the monitoring tool broadly; upsell the liability module.
MVP version
A UCMR 6 sampling-schedule + deadline tracker with a document vault and a templated result-triggered notification/chain-of-custody playbook for PFOA/PFOS, seeded with the actual EPA rule text and methods. Buildable solo in 6-10 weeks; the legal-template content is the hard part and needs one environmental-attorney contractor to review.
30-day build
Interview 15-25 water-utility operators/directors and 3-5 municipal environmental attorneys to validate the liability fear and willingness to pay. Map UCMR 6's proposed sampling requirements and EPA SDWARS submission mechanics. Draft the result-triggered playbook logic. Secure one environmental attorney as a paid content reviewer.
60-day build
Build the tracker + document vault + PFOA/PFOS playbook. Pilot free with 3-5 small/mid utilities. Line up a state rural-water association or AWWA state section as a distribution channel.
90-day revenue plan
Convert pilots to paid seats; launch per-system annual subscription. Target first revenue from 5-15 utilities and/or a white-label deal with a lab or a mid-size environmental consultancy that wants the liability-posture layer without building it.
Distribution path
State rural water associations and AWWA state sections (they train and sell to exactly these operators), certified PFAS labs (channel/white-label), and environmental law firms (referral/co-sell). Content marketing on 'what to do when your PFAS test comes back positive.' NOT ad-spend-dependent; NOT enterprise procurement (selling to individual utilities and the associations that serve them).
Pricing hypothesis
HYPOTHESIS: $2,000-$8,000/yr per water system for the tracker+playbook (scaled by system size), with a higher-touch liability-dossier tier at $10k-$25k per event or as a managed add-on. White-label to labs/consultancies at a per-system wholesale rate. Anchored against hourly environmental counsel that runs $300-$600/hr.
Technical difficulty
Moderate. The software (scheduler, vault, rules engine, document generation) is standard solo-buildable web app work. The genuine difficulty and moat are the accurate, attorney-reviewed legal/notification content and staying current with EPA rulemaking — a content/regulatory-tracking burden, not an engineering one.
Legal / regulatory risk
REAL and material: the product borders on legal advice and evidence handling. Must be positioned as a documentation/workflow tool used under the utility's own counsel, not as legal advice or as a tool to conceal/spoliate evidence. Any framing that suggests destroying, withholding, or manipulating mandated data is unlawful and off-limits — the product must be about accurate documentation, timely lawful notification, and legitimate source attribution. Founder should not himself need a law license if he stays in the workflow/documentation lane with attorney-reviewed templates.
Platform dependency
None meaningful — submissions go to EPA/state government systems (SDWARS, state primacy portals), which cannot deplatform a compliance tool. No app-store or platform-owner risk.
Founder fit
HIGH. This is the founder's proven shape: a federal mandate forces a defined class (public water systems) to file/submit to a government portal, and a solo operator builds the submission/compliance layer and charges per seat. Adds an industrial/public-records/compliance-monitoring angle he is strong in. The main stretch vs. his FMCSA ELDT play is the legal-content sensitivity, which needs one attorney contractor — fundable given he has capital.
Breakout potential
HIGH ceiling: UCMR 6 covers all larger public water systems nationwide (tens of thousands of forced filers), and the same tool replicates to state PFAS programs (e.g., Florida DEP PFAS) and to biosolids/wastewater operators facing the parallel PFOA/PFOS guidance. Land water-utility monitoring, expand to wastewater/biosolids and to state-specific liability regimes — 50 near-identical state markets.
Final recommendation
PURSUE as a validation sprint, scoped as a compliance/documentation workflow tool — NOT as 'help utilities hide data.' Strong forced-buyer structure and textbook founder-fit, but two things must be proven before building: (1) that utility directors/counsel will pay a new vendor for a liability-posture layer, and (2) that the ethical/legal positioning holds. Build the neutral UCMR 6 monitoring tracker first (clearly sellable and low-risk) and treat the liability module as the differentiated upsell validated in interviews.
Next action
Run 20 discovery interviews with water-utility operators/directors and 3-5 municipal environmental attorneys in the next 2-3 weeks to confirm willingness to pay and to lock the ethical/legal framing; in parallel, extract UCMR 6's proposed sampling requirements and SDWARS submission mechanics from the Federal Register text.