What changed
FACT: In April 2024 EPA finalized enforceable MCLs for six PFAS (PFOA/PFOS at 4.0 ppt) — a binding nationwide drinking-water regulation (federalregister.gov/2024-07773). This forces thousands of public water systems into monitoring, treatment decisions, public notification, and reporting. FACT: EPA funds a technical-assistance-and-training pipeline explicitly for rural/small/tribal wastewater systems (grants.gov 362798).
Why now
FACT: The MCLs are final and carry compliance/monitoring deadlines, so the paperwork burden is landing NOW and TA grantees are actively being funded to shepherd small systems through it. HYPOTHESIS: These grantees are staffing up manually and lack a standardized packet tool, creating a narrow window to become their default tooling before EPA or a large consultancy fills it.
Converging signals
Three signals meet: (1) a binding federal rule creating a forced compliance class, (2) a federally-funded intermediary paid to serve that class, and (3) a documented complaint that basic compliance data/tools are priced out of reach for small operators ($124-250/mo grant databases cited on r/grantwriting). The leverage point is selling to the funded intermediary, not the broke utility.
Customer pain
FACT (complaint): small operators find even $124-250/mo tooling prohibitive. HYPOTHESIS: TA grantees must manually produce near-identical compliance packets (sampling plans, monitoring schedules, treatment-selection rationale, public-notice and reporting templates) for hundreds of tiny systems — labor-intensive, error-prone, and non-scalable within a fixed grant budget.
Who pays
PRIMARY BUYER (hypothesis): EPA-funded TA grantees / RCAP-style intermediaries and state rural-water associations, paying with grant dollars to multiply their federally-paid engagement capacity. SECONDARY: small systems directly at a token per-system fee. The BENEFICIARY (small utility) is distinct from the BUYER (the funded intermediary).
Solved today
HYPOTHESIS: TA staff assemble packets by hand from Word templates, EPA guidance PDFs, and spreadsheets; some hire consultants. FACT: generic grant/compliance databases exist but are priced for larger orgs, not small operators.
Why current solutions are bad
Manual assembly does not scale across hundreds of near-identical small systems on a fixed grant; it is slow, inconsistent, and caps how many systems one grantee can serve. A standardized generator turns each engagement from hours of drafting into minutes of guided input.
Proposed product
A guided web tool that intakes a system's size/source/PFAS results and outputs a complete, MCL-keyed compliance packet: monitoring/sampling plan, monitoring schedule, treatment-selection rationale, public-notice language, and reporting templates — white-labeled to the TA grantee's brand, priced per-system.
MVP version
A form-driven document generator producing a single vetted PFAS compliance packet (sampling plan + monitoring schedule + public-notice + reporting template) as a branded PDF/DOCX, built from the final-rule requirements. Land ONE TA grantee as a design partner and generate real packets for their systems.
30-day build
Run the KILL TEST: interview 3+ current TA grantees to confirm (a) grant terms permit licensing third-party software/subcontracting and (b) EPA has NOT already handed them a free equivalent toolkit. Simultaneously map the exact document set the final rule + state primacy agencies require.
60-day build
Build the guided generator against real requirements; co-design templates with the design-partner grantee; produce packets for a pilot cohort of their systems; validate accuracy with a compliance reviewer.
90-day revenue plan
Convert the design partner to a paid per-system white-label license (or an annual seat), then replicate to 2-3 additional grantees / state rural-water associations. Revenue is grant-funded, so budget exists once the tool proves it multiplies capacity.
Distribution path
Direct outreach to the finite, enumerable list of EPA TA grantees, RCAP regional partners, and state rural-water/primacy associations; demonstrated-value demo (generate their packet live). Not a broad ad play — a countable buyer list.
Pricing hypothesis
Per-system white-label fee (e.g. $50-150/system) or an annual grantee seat/site license ($5-25k) that lets them generate unlimited packets within a grant. Model chosen to fit grant-budget line items.
Technical difficulty
Low-to-moderate: templating + rules engine keyed to published federal requirements; solo AI-assisted build is feasible. The hard part is REQUIREMENTS ACCURACY (correct forms per state primacy agency), not code.
Legal / regulatory risk
Moderate: outputs feed regulatory compliance, so template errors carry liability — mitigate with disclaimers, human-in-the-loop review, and grantee sign-off. No licensure required to produce document templates (founder is not certifying compliance himself).
Platform dependency
None material — submits/exports documents, no platform owner can deplatform it; not a government-portal bot subject to policy risk.
Founder fit
Strong: matches the founder's proven public-money / forced-filer + government-mandate shape and industrial/records strengths, sold via demonstrated value to a reachable funded buyer — not enterprise procurement. Slightly outside the pure per-portal-filing pattern (this is packet generation, not portal submission), but the same monetization logic.
Breakout potential
Moderate-to-high: once one grantee workflow is standardized, replicate across the full national TA network and adjacent state programs, and expand the packet library to other small-system rules (lead-and-copper, etc.). 50-state / multi-grantee replication path.
Final recommendation
BUILD — conditional on passing the KILL TEST. The forced-compliance class + funded intermediary + documented affordability gap is exactly the founder's primary thesis, with a countable buyer paying in grant dollars. Do NOT write code until 3 grantee interviews confirm no free EPA toolkit exists and grant funds may license software.
Next action
Contact 3 current EPA TA grantees / RCAP regional partners (via grants.gov 362798 award recipients) to confirm (a) no existing free EPA PFAS compliance toolkit and (b) grant funds permit licensing third-party software; capture their current packet-production workflow as design input.