What changed
EPA awarded the Indiana Finance Authority a $170,671,000 IIJA DWSRF capitalization grant restricted to lead service line replacement (FACT, USAspending ASST_NON_03E03316_068), on top of an earlier $69,506,000 IN tranche (FACT, ASST_NON_02E03316_068) — roughly $240M that IFA must now push out as low-interest financing to eligible public water systems for LSL identification, planning, design, and replacement.
Why now
The money is appropriated and sitting at the state; it only moves when water systems file loan applications and supporting documentation. The award text itself says funds cover 'identification, planning, design, and replacement' — i.e., paperwork-heavy pre-construction work is explicitly fundable. Parallel LSLR tranches to WI ($148M+$87M), PA ($225M+$76M), MN ($88M), TN ($49M) prove this is a repeating 50-state pattern, so a template built once in Indiana has immediate replication targets (all FACT via cited awards).
Converging signals
Three signals meet at one point: (1) appropriated federal money at a state agency (FACT), (2) a defined filer class — Indiana public water systems that want the financing and must document LSL inventories and replacements (class is FACT from award text; the ~780 CWS count is INFERENCE from the input), (3) a state submission channel (IFA SRF — exact portal/forms unknown, flagged as a gap to verify). Same shape as convergence 4284, so newness is low but the thesis is corroborated, not weakened.
Customer pain
Small and mid-size water systems (often 1–5 staff, no grant writer) must assemble SRF loan applications, preliminary engineering coordination, LSL inventories, and post-award replacement/disbursement documentation to touch this money. HYPOTHESIS grounded in structure: the forced-buyer mandate is the demand evidence here — no complaint threads or job ads were provided, and per the scoring rules none are required for a funded mandate with a defined filer class.
Who pays
Primary: Indiana community water systems (utilities bill this as a project cost — SRF planning/design costs are award-eligible per the grant text, meaning the tool can effectively be paid for out of the loan itself). Secondary: the engineering and funding-consultant firms that prepare these packages for multiple systems and would use it as leverage — one license, many clients.
Solved today
Consultants and engineering firms prepare SRF packages, typically billing hourly or a percentage of the award; the smallest systems either lean on Indiana Rural Water Association circuit riders or simply don't apply. LSL inventory itself is served by incumbent SaaS (120Water — headquartered in Indiana — and BlueConduit).
Why current solutions are bad
Consultant fees scale with award size, not effort; small systems get deprioritized because their projects are too small to be worth a consultant's time — which is exactly the long tail a per-filing software product can serve profitably. Inventory SaaS incumbents stop at the inventory; the loan application and post-award reimbursement/documentation trail is still hand-built.
Proposed product
A guided filing engine for the IFA SRF LSLR program: intake wizard that ingests the system's existing LSL inventory (including 120Water/State exports), generates the loan application package, PER coordination checklists, and the recurring post-award documentation (replacement records, disbursement requests, Davis-Bacon/AIS attachments). Charge per filing package and per post-award documentation cycle. Explicitly NOT an inventory-prediction tool — do not fight 120Water on their ground; sit downstream of the inventory on the money paperwork.
MVP version
One Indiana-specific artifact: the complete IFA SRF LSLR application package generator (forms + required attachments checklist + inventory-data import), validated against the actual IFA submission requirements, plus a manual white-glove first delivery for 2–3 pilot systems. Founder must first pull IFA's current intended use plan / project priority list to get the real forms and the real applicant list — that PPL is also the sales lead list.
30-day build
Verify the actual IFA SRF submission process and forms (this is the biggest unknown — flagged); download IFA's project priority list and Indiana's LSL inventory data to build a ranked list of systems with lead lines that have NOT yet applied; interview 5 systems and 3 consultants from that list; build the package generator against one real application.
60-day build
Deliver 2–3 paid pilot packages (white-glove pricing $2,500–5,000 each, positioned against percentage-fee consultants); harden the generator; sign one multi-client engineering/consulting firm as a channel user.
90-day revenue plan
5–10 paid filing packages and/or 1–2 consultant-firm licenses; begin cloning the template for Wisconsin and Pennsylvania (both funded, cited) so the second state ships in weeks, not months.
Distribution path
Direct, list-driven outreach — the filer class is enumerable from public data (EPA SDWIS + Indiana LSL inventories + IFA PPL), which suits a founder who sells by demonstrated value: send each target system a pre-filled snapshot of its own inventory and eligible funding. Channel: Indiana Rural Water Association and AWWA Indiana section; consultant firms as multipliers.
Pricing hypothesis
$2,500–5,000 per application package (vs. consultant percentage fees on six-to-seven-figure awards); $200–500/mo or per-submission for post-award replacement documentation; state-clone pricing identical per state.
Technical difficulty
Low-to-moderate: document assembly, data import, checklist logic — well inside solo AI-assisted range. The hard part is domain accuracy (SRF rules, cross-cutting federal requirements), not code.
Legal / regulatory risk
Low. Preparing filings as a service/tool is unlicensed activity; the founder does not become a regulated party. Modest risk of being perceived as unauthorized practice of engineering if the tool drifts into PER content — keep it to the funding/documentation layer.
Platform dependency
Government submission channel — no platform owner can deplatform it (per scoring rules, no platform_policy_risk). Risk is process change if IFA alters forms; that is maintenance, not existential.
Founder fit
Maximal shape-match: this is precisely his proven ELDT play — read a mandate, find the compelled/incentivized filer class, build the submission layer, charge per filing — applied to water infrastructure, adjacent to his industrial-operations and public-records strengths. Scored 9 accordingly (lesson 'government-portal mandate opportunities fit this founder best', confidence 0.79, applies directly).
Breakout potential
High on the replication axis: the cited awards alone show WI, PA, MN, TN, MI, GA running the same program with the same paperwork burden — a 50-state clone path with near-identical product. Expansion also runs vertically into non-LSLR DWSRF/CWSRF filings.
Final recommendation
PURSUE as a validation sprint, not a blind build. The funded mandate is hard evidence ($240M IN, cited), founder fit is maximal, and the 50-state clone path is visible in this same batch. The one thing that kills it is filing volume/consultant capture — resolvable in two weeks with public data (IFA PPL + application counts) and five phone calls before writing product code. Treat 4284 and this as ONE opportunity with Indiana as beachhead or fast-follow.
Next action
Pull the Indiana Finance Authority SRF intended use plan and project priority list; count actual LSLR applicants and identify who prepared each application; if >100 credible unserved systems remain, start the pilot outreach list the same day.