What changed
FACT: In April 2024 EPA finalized the first enforceable National Primary Drinking Water Regulation for six PFAS, setting PFOA and PFOS at 4.0 ppt (federalregister.gov/documents/2024/04/26/2024-07773). This forces thousands of public water systems to monitor and, where exceeded, install treatment. UCMR 5 (2021-27858) separately compels systems serving 3,300+ people plus a sample of smaller systems to collect PFAS occurrence data — a defined forced-filer class with deadlines.
Why now
FACT: The PFAS MCL is now enforceable with compliance/monitoring deadlines running through the mid-to-late 2020s, and IIJA money is actively flowing — the input cites live DWSRF capitalization grants ($225M PENNVEST, $75.8M PENNVEST, $68.4M Washington DOH, $56.8M Michigan EGLE) plus a dedicated Technical Assistance & Training line for small/rural/tribal systems (grants.gov/362798). The obligation and the money exist in the same window.
Converging signals
FACT: Three signals meet at one point — (1) an enforceable rule creating a compelled class (PFAS MCL/UCMR 5), (2) a class of buyers structurally unable to self-fund the work (small/rural/tribal utilities), and (3) a separate federal TA&T funding line that pays intermediaries to serve exactly those systems. The non-obvious bridge is that payment is rerouted from the broke utility to a funded intermediary.
Customer pain
FACT (rule text) + INFERENCE: Small systems must test for 29 PFAS and potentially design/fund treatment they have no in-house chemist, engineer, or grant-writer to handle. HYPOTHESIS: the acute pain is procedural — sampling plans, MCL gap analysis, and SRF/grant applications are specialized paperwork these operators cannot produce, and missing them risks violation. This intensity is asserted, not yet proven by complaint threads in the input.
Who pays
The realistic buyer is the EPA TA&T prime grantee (e.g., RCAP, national/state rural water associations, university environmental-finance centers) that already holds the funding and needs delivery capacity — you subcontract to them per system served. Secondary: state DWSRF/technical-assistance programs. The utility is the beneficiary, NOT the payer.
Solved today
FACT/INFERENCE: Today this is delivered by in-house staff of existing TA grantees (RCAP, Rural Water, environmental finance centers) and by engineering/consulting firms billing the utility or the SRF project. For the smallest systems, much goes undone or is handled ad hoc.
Why current solutions are bad
INFERENCE: Grantees are capacity-constrained relative to the thousands of systems now in scope, and full-service engineering firms are too expensive for a 500-connection system and uninterested in the paperwork tier. The gap is a cheap, repeatable, productized intake/assessment/application packet — not a custom engineering study.
Proposed product
A repeatable PFAS-compliance service kit for small systems: (1) standardized sampling/monitoring plan template mapped to UCMR 5 / MCL requirements, (2) an MCL gap assessment that ingests the system's sample results and flags exceedances and deadlines, (3) a pre-built treatment-and-funding application packet (DWSRF/BIL PFAS set-aside, TA&T-eligible). Delivered as a productized service under a grantee's TA umbrella, with light software (intake forms, template automation, a tracking dashboard) as the margin lever.
MVP version
A documented intake workflow + fillable templates + a spreadsheet/lightweight web tool that turns a system's PFAS sample data and basic profile into a gap report and a draft grant-application packet. No heavy build required to start — the wedge is domain packaging, not code.
30-day build
Run the KILL TEST first: call ~15 small/rural/tribal water systems and 3 named TA grantees (RCAP regions, state Rural Water associations, an environmental finance center) and confirm whether they will route TA&T dollars to an outside PFAS specialist or only use in-house staff. Simultaneously codify the sampling-plan, gap-assessment, and application templates from the public rule + SRF program docs.
60-day build
Sign a subcontract or LOI with one TA grantee (or a state technical-assistance program). Deliver the packet for 3–5 systems the grantee already serves as a paid pilot. Capture unit economics (hours per system, price per deliverable).
90-day revenue plan
Invoice the grantee per system delivered (target 5–15 systems). Standardize into a fixed per-system fee and expand to adjacent grantees / a second state, replicating the same packet.
Distribution path
Direct outreach to TA&T prime grantees and state rural-water/technical-assistance programs (a small, named, reachable list), plus environmental finance centers. Not consumer, not procurement-office cold sales — you serve the intermediary who already has the money and the relationships.
Pricing hypothesis
Per-system deliverable fee (est. $1,500–$6,000 per small system for sampling plan + gap assessment + application packet), billed to the grantee/TA program; optional per-seat/per-year software license to grantees who want to self-serve the templates.
Technical difficulty
Low-to-moderate. The hard part is domain packaging (correctly mapping the rule, monitoring schedule, and SRF eligibility), which the founder's public-records/industrial/compliance strengths fit. Software is thin at MVP.
Legal / regulatory risk
Moderate: some deliverables (treatment DESIGN, engineering certifications) may require a licensed PE — scope the product to sampling plans, gap analysis, and grant/application paperwork and explicitly hand engineering design to a licensed partner. Federal grant subcontracting has compliance rules (procurement, allowability) the grantee already manages.
Platform dependency
None on a commercial platform; you submit to/through government and grantee systems. Dependency is on federal appropriations continuing (TA&T + DWSRF/BIL set-asides) and on grantees' willingness to subcontract.
Founder fit
High. This is the founder's proven shape: a federal mandate forces a class to act, and a solo operator builds the paperwork/submission layer and monetizes per transaction. Industrial/water and public-records strengths apply directly. The one deviation from his best pattern is that the buyer is a grantee intermediary, not a direct per-filing SaaS customer.
Breakout potential
Moderate-to-high. If the funding-flip proves out, the same packet replicates across ~50 states and dozens of grantees, and expands to lead-service-line and other emerging-contaminant obligations riding the same SRF/TA money.
Final recommendation
PURSUE CONDITIONALLY — but gate everything on the 30-day kill test. This fits the founder's primary public-money/forced-buyer thesis and the money is real and appropriated, but the whole business hinges on one unverified assumption (grantees will pay an outside specialist). Do not build until at least one grantee confirms in writing they will subcontract or direct TA funds to you.
Next action
Make the kill-test calls this week: 3 named TA&T grantees (start with your regional RCAP and state Rural Water association) + a state technical-assistance program — ask directly, 'Will you route TA&T dollars to an outside PFAS specialist to produce sampling plans and treatment-grant packets for the small systems you serve?' A single yes with a pilot system is the green light.