What changed
EPA published a proposed rule (May 20, 2026) extending the PFOA/PFOS MCL compliance deadline from 2029-04-26 to 2031-04-26 — but ONLY for systems that submit an extension request under SDWA 1416(f). The underlying MCLs are already final and binding, so monitoring/compliance is certain; the rule creates a NEW discrete filing on top of it (FACT, per the Federal Register document).
Why now
The public hearing was held 2026-07-07 and the comment period is open (FACT). Final-rule mechanics (how and to whom the extension request is submitted) are being defined now, so the window to build the tool ahead of the compliance/extension rush is open. Small community water systems have until 2029 to comply or must proactively file for the 2031 extension.
Converging signals
Three signals meet at one point: (1) a binding final MCL that forces monitoring on ~thousands of the ~50,000 community water systems; (2) a new proposed filing (the extension request) that only helps those who submit it; (3) a defined, under-staffed filer class (small community water systems) that already pays contract operators and rural water associations for compliance help. Adjacent EPA PFAS biosolids guidance (2026-07-06) and a $225M DWSRF capitalization grant to PENNVEST show the broader PFAS money/compliance flow.
Customer pain
Small community water systems typically have no dedicated compliance staff, must track sampling schedules, compare results against MCLs, produce public notification and Consumer Confidence Report disclosures, and now must decide whether/how to file an extension request — a decision with real financial consequences (capital treatment spend vs. a 2-year reprieve). Missing the extension window means being forced into 2029 compliance capital projects they can't fund.
Who pays
Beneficiary = the water system (avoids penalties / buys time). Buyer = the water system's operator, its contract-operations firm managing dozens of small systems, or the state rural water association serving them. Contract operators and RWAs are the highest-leverage buyers because one account covers many systems.
Solved today
Spreadsheets, state primacy-agency portals, generic environmental consultants/engineering firms billing hourly, and rural water association circuit riders. Larger utilities use enterprise compliance suites (too costly/heavy for a 500-connection system).
Why current solutions are bad
Consultants are expensive and don't scale across the long tail of tiny systems; state portals track submission but don't advise on whether to file the extension or assemble the package; spreadsheets miss deadlines. No affordable tool exists purpose-built for the small-system PFOA/PFOS extension decision + package.
Proposed product
A per-system compliance command-center: ingest each system's PFAS monitoring results, compare against the final MCLs and running-average trigger levels, flag systems that are exceeding/at-risk and should file the 2031 extension request, generate the extension-request package (with a compliance-plan narrative and supporting docs), and calendar the monitoring/public-notification/CCR deadlines with alerts. PE-certified elements are partner-signed, not self-signed.
MVP version
Start narrow: a monitoring-results tracker + MCL comparison engine + a rules-based 'should you file the extension?' flag + a fillable extension-request package generator, seeded with one state's primacy-agency process. Manual-assisted onboarding for the first 5-10 systems via a friendly contract operator or RWA.
30-day build
Read the proposed rule and SDWA 1416(f)/1450(a)(1) mechanics; map one state's primacy-agency submission process; build the MCL comparison + extension-flag logic; interview 5-10 small-system operators / contract operators / one state RWA to validate the buyer and package format; optionally file a public comment to build credibility and signal.
60-day build
Ship the package generator + deadline calendar; sign 1 contract-operations firm or RWA as a design partner covering multiple systems; line up a licensed PE partner for any certified submissions; template the state-specific layer so a second state can be added fast.
90-day revenue plan
Convert the design-partner operator/RWA to a paid multi-system account; onboard first per-system subscribers; charge a flat fee per extension-request package as final-rule mechanics firm up. Target first real revenue within 90-180 days, driven by the compliance/extension timeline rather than pure discretion.
Distribution path
Channel through state rural water associations (they exist in every state and serve exactly this long tail), contract-operations firms managing many small systems, and state AWWA sections. Publish a free 'do you need to file the PFOA/PFOS extension?' checker as a lead magnet; present at RWA meetings.
Pricing hypothesis
$1-4k/system/year subscription (inference) for tracking + alerts, plus a flat fee per extension-request package (e.g., $500-2,000, inference); multi-system operator/RWA accounts priced per-seat or per-system with volume tiers. Undercut per-hour consultant billing.
Technical difficulty
Moderate. Core logic (result ingestion, MCL comparison, running-average triggers, deadline calendaring, document generation) is well within solo AI-assisted build. Complexity is regulatory: each state primacy agency has its own process, and the federal extension mechanism is still being defined — so build the state layer as data/config, not hardcode.
Legal / regulatory risk
Low-to-moderate. Software/documentation is unrestricted, but some submissions may require a Professional Engineer certification — partner with a PE rather than sign. Avoid giving legal advice; frame outputs as decision-support and package preparation. Watch that final-rule mechanics may change the request format.
Platform dependency
None in the deplatforming sense — submissions go to EPA/state government processes, not a private platform that can ban the tool. Dependency is on state portal formats, which are public and stable.
Founder fit
Very high. This is the founder's proven shape: a federal mandate forces a defined class to file with a government system, and a solo operator builds the submission/compliance layer and charges per filing/per seat — exactly the FMCSA ELDT model he already shipped. Industrial/operations/public-records background maps directly to water-utility compliance.
Breakout potential
Strong. 50 near-identical state markets to replicate into once the first works; expands to the broader PFAS compliance stack (biosolids guidance, monitoring across all regulated PFAS, DWSRF/BIL-funded lead & PFAS project reporting), and to the wider small-water-system compliance calendar (Lead & Copper Rule, CCRs). The DWSRF capitalization grants ($225M to PENNVEST alone) show a large adjacent funded flow.
Final recommendation
PURSUE — high-conviction. This is a textbook forced-buyer + funded-mandate opportunity in the founder's proven government-portal shape, with a binding MCL (certain demand), a new discrete filing, a defined under-staffed filer class, a deadline-driven sales timeline, and clean 50-state replication. Sell through contract operators and rural water associations to solve the small-system willingness-to-pay risk. Validate buyer and package format in the first 30 days before over-building the state layer.
Next action
Interview 5-10 small community water system operators and at least one state rural water association / contract-operations firm this week to confirm who pays and what the extension-request package must contain, and read the proposed rule + one state's primacy-agency submission process end to end.