What changed
On 2026-07-01 EPA published a PROPOSED RULE (UCMR 6) under the Safe Drinking Water Act requiring public water systems to collect national occurrence data on 30 unregulated contaminants — 7 ultrashort organofluorine compounds (incl. certain PFAS), 3 pesticide metabolites, 13 SVOCs, and 7 purgeable VOCs (FACT, Federal Register 2026-13263).
Why now
It is a proposed rule with an open comment period and two announced public webinars — the front edge of the cycle. UCMR runs on fixed 5-year cadences with hard per-system sampling calendars; every prior UCMR (1–5) became a mandatory monitoring obligation. Building the tool during the comment window means being first-to-market when the final rule sets the monitoring years.
Converging signals
Three signals meet at one point: (1) the SDWA rule, (2) a defined forced-filer class (all CWS/NTNCWS serving 3,300+ people plus a small-system sample), and (3) a federal reporting portal (EPA's SDWARS-style UCMR reporting system) plus state primacy agencies. That is the founder's exact target shape.
Customer pain
Each water system must sample specific contaminants at specific entry points on a specific schedule, contract certified labs, translate lab results into EPA's rigid data format, and submit on deadline — or face primacy-agency enforcement. Small and mid-size utilities have no dedicated compliance staff; the schedule logic and data-format validation are error-prone and the penalty for a missed/late sample is real (HYPOTHESIS on exact penalty; the mandatory-monitoring obligation is FACT).
Who pays
The water systems themselves (community + non-transient non-community water systems ≥3,300 people, ~6,000–10,000 systems — PIE is inference), plus the certified environmental labs and the compliance consultants who currently serve them and would white-label the tool.
Solved today
Prior UCMRs: EPA's own SDWARS web portal (manual data entry), spreadsheets, certified-lab portals that report on the system's behalf, and specialty environmental-compliance consultants billing hourly or per-system. Larger utilities use broad compliance suites (e.g. utility-billing/EH&S platforms) that are expensive and general.
Why current solutions are bad
Manual SDWARS entry is tedious and error-prone; spreadsheets don't track per-entry-point schedules or auto-flag missed windows; consultants are costly per-system and don't scale to the long tail of small systems; general compliance suites are over-built and priced for large utilities, leaving the mid/small market underserved.
Proposed product
A focused micro-SaaS: (1) onboard a water system (PWSID, entry points, population served, source type) → auto-generate the UCMR 6 sampling schedule and calendar reminders; (2) intake lab results (CSV/API from certified labs) → validate against EPA's data format and contaminant list, flag errors before submission; (3) generate a SDWARS-conformant submission file (and, once the final rule/portal spec is published, direct submission or a fill-and-file assist) with an audit trail; (4) a dashboard of per-system deadline status. Charge per system per year or per sampling event.
MVP version
Schedule-generator + data-validator + export. Encode the proposed UCMR 6 contaminant list and monitoring framework; take PWSID + entry points + population; output a sampling calendar and a validated, EPA-format occurrence-data file ready to upload to SDWARS. Skip live portal submission until the final rule and portal spec exist — validation + export delivers value on day one and avoids building against a moving target.
30-day build
Read the full proposed rule and the existing SDWARS data-element/format spec from UCMR 5. Build the contaminant list, sampling-frequency logic, and data-format validator. Stand up a landing page targeting 'UCMR 6 monitoring compliance.' Submit a comment on the rule (credibility + inbound). Interview 10–15 small/mid water-system operators and 2–3 certified labs to confirm workflow and price sensitivity.
60-day build
Ship the schedule generator + validator + export to first design-partner utilities and one lab. Add multi-system (portfolio) view for consultants and labs who manage many PWSIDs. Publish a free UCMR 6 schedule checker as a lead magnet to capture the forced-filer audience early.
90-day revenue plan
Convert design partners to paid annual seats; sign 1–2 labs or consultants to white-label/reseller deals (they own the customer relationships and pay per managed system). Revenue path: ~$300–$1,200/system/yr direct, or per-managed-system wholesale to labs/consultants. First revenue plausibly from consultants/labs who buy per-seat leverage before the final rule even lands.
Distribution path
Direct SEO/content on 'UCMR 6 compliance' + free schedule-checker tool; outreach to state primacy agencies' small-system technical-assistance programs and Rural Water Associations (state chapters reach thousands of small systems); reseller deals with certified environmental labs and drinking-water compliance consultants who already hold the relationships. Demonstrated-value selling (free checker → paid) fits the founder.
Pricing hypothesis
Per system per year ($300–$1,200 depending on size/entry points) or per-sampling-event fee; wholesale/white-label per-managed-system rate for labs and consultants. Undercut per-system consulting fees with software.
Technical difficulty
Moderate. The hard part is faithfully encoding EPA's contaminant list, sampling-frequency rules, and SDWARS data format — deterministic, well-documented from UCMR 5. No ML needed. Direct portal submission (later) may require handling EPA's electronic reporting interface; until then, validated export sidesteps it.
Legal / regulatory risk
Low-to-moderate. It's a proposed rule — scope/timing can change (monitoring is 'subject to the availability of appropriations'), so the product must be built to re-parameterize when the final rule lands. No licensing needed to build the tool; the founder is not the regulated party. Standard disclaimer that the system operator remains responsible for its filings.
Platform dependency
None of the deplatforming kind — it submits to a government system, not an app-store/social platform. Dependency is on EPA's SDWARS spec, which is a public, stable interface, not a gatekeeper.
Founder fit
Maximal. This is the founder's proven shape (FMCSA ELDT portal-filing app): a federal mandate forces a defined class to file to a government portal, and a solo operator builds the submission/compliance layer and charges per transaction/seat. Industrial-operations and public-records strengths map directly onto water-system compliance workflows.
Breakout potential
Strong replication surface: 50 state primacy agencies with parallel state-level reporting; adjacent SDWA obligations (Lead & Copper Rule Revisions, PFAS NPDWR compliance monitoring, Consumer Confidence Reports); and the same engine resells to every certified lab. UCMR recurs every ~5 years, creating a durable, resetting demand cycle.
Final recommendation
BUILD — but as a re-parameterizable schedule-generator + data-validator + SDWARS-export tool, and sell primarily through labs/consultants and small-system technical-assistance channels. Highest-tier founder-fit and a structural forced-buyer. Start now (comment window) so you're first when the final rule sets monitoring years; keep the MVP to export (not live submission) until the portal spec is final.
Next action
Pull EPA's UCMR 5 SDWARS data-element/format specification and the full UCMR 6 proposed-rule text; encode the contaminant list + sampling-frequency logic into a working schedule generator + format validator, and stand up a free 'UCMR 6 schedule checker' landing page to start capturing the forced-filer audience.