What changed
EPA awarded a $49,339,000 IIJA capitalization grant to the Virginia State Board of Health for DWSRF-eligible lead service line replacement (FACT, USAspending). This is the third state LSL/SRF instance in this batch — parallel awards exist for Indiana ($69.5M and $170.7M), Minnesota ($88.4M), Pennsylvania ($225.3M and $75.8M), Tennessee ($49.2M and $85.0M), Wisconsin ($87.4M, $148.1M, $48.3M, $81.2M), Michigan and Ohio (FACT, USAspending). The same federal money → state SRF → subrecipient-utility paperwork pattern now confirms in every state observed.
Why now
The money is already appropriated and sitting at state finance authorities — utilities cannot draw a dollar of it without producing an application package (planning/design/construction docs), then a stream of post-award compliance filings. HYPOTHESIS (well-known regulatory context, not in source text): the Lead and Copper Rule Improvements push utilities toward mandatory replacement programs on a fixed timeline, so demand for LSLR financing — and its paperwork — rises for the next several years. Each state's annual Intended Use Plan cycle creates recurring application windows, i.e., recurring deadlines that sell the product for you.
Converging signals
Three signals meet at one point: (1) a funded federal mandate ($49.3M VA award, FACT); (2) a defined filer class — Virginia public water systems seeking LSLR financing (FACT that the recipient will finance eligible PWS projects; ~1,100 VA waterworks is inference); (3) a state portal/program (VDH Office of Drinking Water SRF — inference) that only accepts money in exchange for documents. The identical structure repeating across IN, MN, PA, TN, WI, MI, OH (FACT, USAspending) is a fourth signal: this is a 50-state template, not a one-off.
Customer pain
A small water system (often 1-5 staff, no grant writer) must produce an SRF application with engineering, environmental, financial-capability, and lead-inventory documentation, then — if funded — Davis-Bacon wage compliance, American Iron & Steel certifications, disbursement requisitions, and progress reports (paperwork list is inference from standard SRF practice, not in source text). Today they either pay an engineering consultant a percentage-of-project fee to shepherd this or they simply don't apply and the money passes them by. States themselves struggle to get small-system applications in the door (hypothesis).
Who pays
Primary: small/mid public water systems and the local authorities that own them (they have a funded project on the line worth 100-1000x the software fee). Secondary and probably faster: the civil/environmental engineering firms and SRF consultants who prepare many applications a year and would use the tool across clients. Tertiary (later): state SRF set-aside budgets that pay for small-system technical assistance — a contract channel, not a procurement-office SaaS sale.
Solved today
Consultants billing hourly or a percent of project cost; state technical-assistance circuit riders (free but capacity-limited); Word/Excel/PDF checklists from the state program. On the adjacent LSL-inventory problem there are funded SaaS incumbents — 120Water, Trinnex leadCAST, BlueConduit — which proves utilities do buy software for lead-rule compliance, but those products center on inventory/sampling, not on the loan application and award-administration paperwork (competitor scope is inference; existence is fact from general knowledge — verify).
Why current solutions are bad
Consultant fees consume grant value (a 2-5% shepherding fee on a $2M project is $40-100k); free TA providers are oversubscribed; every state's forms differ but 80% of the underlying content (system data, inventory, project scope, financial capability) is identical and re-typed by hand each time. Nobody has productized the application+award-admin layer for the small-system tail because each state looks too small to a VC-backed company — which is exactly why it fits a solo operator who replicates state by state.
Proposed product
A guided web app that (1) intakes a utility's system data, lead inventory status, and project scope once; (2) generates the state's SRF/LSLR application package (VDH first) with completeness checks against the program's checklist; (3) tracks IUP windows and deadlines; (4) after award, generates the recurring compliance artifacts — requisition packets, progress reports, AIS/Davis-Bacon cert templates — on a calendar. Charge per application package plus a monthly award-administration subscription for the life of the project. Founder has done exactly this shape before against the FMCSA ELDT registry: read the mandate, find the forced filer, build the submission layer, charge per transaction.
MVP version
Virginia-only: encode VDH ODW's current LSLR/DWSRF application checklist and forms into a guided intake + document-package generator (PDF/Word output that matches what the program office expects — no state-side integration needed, which sidesteps procurement entirely). Include a deadline tracker seeded with the next IUP application window. 4-8 weeks of AI-assisted build; the hard work is reading the program guidance, which is the founder's proven strength.
30-day build
Pull VDH ODW program guidance, application forms, and the current project priority list (public records — founder strength). Interview 5-10 VA small systems and 3-5 engineering firms that appear repeatedly on past SRF priority lists (public documents reveal exactly who applies and who their engineers are — a ready-made prospect list). Build the intake→package generator for the VA forms.
60-day build
Pilot with 2-3 systems or one engineering firm on real applications for the next funding round; charge from day one ($1.5-3k per application package, hypothesis pricing). Add the post-award compliance calendar/artifact generator. Collect testimonial evidence tied to a funded application.
90-day revenue plan
Convert the pilot channel: sell per-application packages to systems on the VA priority list that haven't applied, and multi-client licenses to consultants. Begin encoding state #2 (Pennsylvania — $301M across two awards, FACT — or Wisconsin, $364M across four awards, FACT) using the same core with a state-specific form layer. Target: 5-15 paid application packages plus 3-5 award-admin subscriptions.
Distribution path
Deadline-driven outbound to a public, named universe: state SRF priority lists and past IUPs name every plausible buyer and their engineer. Email/call sequences keyed to the application window ('the LSLR window opens in X weeks — here's your gap list'). Partnerships with rural water associations (each state has one) as a credibility channel. No ad spend, no marketplace, no app-store risk.
Pricing hypothesis
$1,500-3,000 per application package (versus a consultant's $10-40k+ or 2-5% fee); $200-400/mo per active award for compliance administration for the 2-4 year project life; consultant multi-seat license $500-1,000/mo. All hypothesis — validate in the 30-day interviews.
Technical difficulty
Low-moderate: document generation, checklist logic, deadline calendar, per-state form templates. No government-side API integration required for v1 (packages are submitted by the applicant through whatever channel the state uses); that removes the single hardest dependency. The real difficulty is domain encoding per state — tedious, not hard, and exactly what AI-assisted document analysis accelerates.
Legal / regulatory risk
Low. Generating and organizing documents is not engineering practice or law practice, but the product must not sign or seal engineering deliverables (PE-stamped plans stay with the utility's engineer) and should disclaim application-outcome guarantees. No license required to operate (hypothesis — confirm VA has no grant-writer registration requirement, unlikely).
Platform dependency
None that can deplatform: the counterparty is a state program office, not a platform owner. Risk is form/process churn per state — which is actually a moat, since keeping 50 states current is the recurring value.
Founder fit
Maximal on the system's own thesis. This is the ELDT playbook transplanted: federal mandate → forced/compelled-by-funding filer class → paperwork layer → per-filing monetization. Founder's public-records skill directly generates the prospect list; industrial-operations background gives credibility with water-system operators that a generic SaaS founder lacks; no relationship-sales required because the deadline and the gap-list do the selling.
Breakout potential
High: ~50 near-identical state markets (FACT that at least 8 states show the same award structure in this batch), each with recurring annual cycles and multi-year award-administration tails; the same engine extends to Clean Water SRF (Michigan/Ohio CWSRF awards in evidence, FACT) and to other pass-through programs. The per-award subscription creates compounding recurring revenue as funded projects accumulate.
Final recommendation
PURSUE — this is the closest structural match to the founder's proven ELDT edge in the current pool, with hard appropriated-dollar evidence in at least 8 states and a defined, publicly-named buyer universe. Gate it on two week-1 checks: (1) confirm 120Water/Trinnex do NOT already cover SRF application+award administration; (2) confirm from VDH's published IUP that application volume and cycle timing support selling packages within ~90-120 days. If both pass, build the VA MVP.
Next action
Pull the current VDH Office of Drinking Water IUP, LSLR application forms, and project priority list; simultaneously audit 120Water's and Trinnex's published feature scope for application/award-admin coverage. Both are free public-records tasks completable this week.