What changed
EPA awarded Michigan EGLE a $56,811,000 IIJA DWSRF capitalization grant (FACT, USAspending ASST_NON_03E03285_068), on top of $105.9M and $68.2M CWSRF capitalization grants to the same agency (FACT). EGLE must lend this to eligible public water systems, which can only access it by submitting SRF project plans and supporting documentation (award text confirms financing goes to 'eligible public water systems' for 'planning, design, and construction'; the specific project-plan/IUP paperwork is inference). Separately, Michigan's state Lead and Copper Rule requires distribution-system materials inventories and ongoing (~5%/yr) lead service line replacement with annual reporting to EGLE (HYPOTHESIS/inference — widely reported as the nation's strictest state LCR, but not in the provided source text; must be verified against Mich Admin Code R 325.10604f before build).
Why now
The money is already appropriated and sitting at EGLE — the spend exists whether or not anyone builds the tool (FACT: three capitalization grants totaling ~$231M to Michigan EGLE in the demand evidence). SRF project plans are due on an annual IUP cycle, and the state LCR creates a recurring annual reporting obligation rather than a one-time inventory (inference). Parallel IIJA DWSRF awards to Indiana, Minnesota, Wisconsin, Pennsylvania, Tennessee, Virginia, Ohio, North Carolina and Georgia (all FACT, cited) prove the identical mandate exists in 50 near-identical state markets.
Converging signals
Three signals meet at one point, which per the system's scoring rubric IS convergence: (1) appropriated federal money passing through a state agency ($56.8M DWSRF + CWSRF grants, FACT); (2) a defined compelled class — Michigan public water systems that must file to borrow, plus all systems that must inventory/report LSLs under the state rule (class FACT from award text; LCR specifics inference); (3) a state submission surface — EGLE's SRF program and the MiEnviro portal (portal identity is inference, verify in week 1).
Customer pain
Small community water systems (the majority of Michigan's ~1,390 CWSs — count is inference) have no grant writer and no software; they either pay an engineering consultant that bills a percentage of the project or hourly, or they leave SRF money unclaimed and fall out of LCR compliance. The paperwork is repetitive, template-driven, deadline-bound, and annually recurring — exactly the shape software eats. Note honestly: no complaint threads or job postings were provided as evidence; per the forced-filer rubric that absence does not negate demand, but it does mean willingness-to-pay for SOFTWARE (vs. consultants) is a hypothesis to test in the first 30 days.
Who pays
Two reachable buyers: (a) the water system itself — small MI utilities with an operating budget and a compliance officer/operator, list publicly available from EGLE/SDWIS; (b) the civil/environmental engineering consultancies that prepare SRF project plans for dozens of systems each and would pay for a tool that cuts prep time per filing. Neither is a government procurement office — this is selling to subrecipients and the consultants who serve them, which the founder has already done profitably in the FMCSA ELDT business (analogous shape: mandate → filer class → portal → per-filing fee).
Solved today
Consulting engineers (Fishbeck, OHM Advisors, F&V — hypothesis on specific names) prepare SRF project plans for fees commonly in the tens of thousands or a percentage of the award (hypothesis; consistent with SRF norms). LSL inventories are handled with spreadsheets at small systems or with enterprise platforms (120Water, BlueConduit, Trinnex leadCAST) at larger ones (competitor existence is FACT of the market, not from provided sources).
Why current solutions are bad
Consultant fees are disproportionate for small systems and don't cover the recurring annual reporting tail; enterprise LSL platforms price and sell for large utilities and statewide contracts, leaving sub-10k-population systems on spreadsheets. Nobody packages the SRF financing paperwork AND the annual LCR reporting in one cheap per-utility subscription.
Proposed product
A Michigan-specific compliance workspace: imports the system's service-line data (spreadsheet/GIS export), maintains the EGLE-format LSL inventory, tracks the replacement-percentage clock, generates the annual LCR report, and assembles SRF project-plan document packages (needs/alternatives narrative, cost tables, environmental checklist scaffolding) ready for the utility's engineer to review and stamp. Ships filings to EGLE/MiEnviro in the exact required format. Explicitly NOT the engineer of record — it's the paperwork layer under the PE, same as the ELDT app is the submission layer under the training provider.
MVP version
(1) EGLE-format LSL inventory generator + annual replacement report from a CSV upload, because that piece needs no PE stamp and recurs annually; (2) an SRF project-plan document assembler producing the EGLE submission checklist and draft narrative. Built solo with AI assistance in 30-60 days; the founder funds data acquisition (EGLE inventory formats, IUP guidance docs — all public records, his strength).
30-day build
Verify the inference chain from primary sources: pull Michigan's LCR rule text, EGLE's LSL inventory template, current IUP/project-plan guidance and MiEnviro submission mechanics (all public). Interview 10 small-system operators and 5 MI consulting engineers (MRWA conference/contact list) to price the pain. Build the inventory→report generator against EGLE's real template.
60-day build
Pilot with 3-5 small systems and 1-2 engineering firms at founding-customer pricing; generate their actual annual filings. Add the SRF project-plan assembler. Collect the artifact that sells: 'this system's annual report, done in an afternoon for $X instead of a consultant invoice.'
90-day revenue plan
Convert pilots to paid: target 15-25 utilities at ~$3-5k/yr or 3-4 consultancies at ~$10k/yr multi-seat, timed to the next IUP submission window and annual LCR reporting deadline (deadline dates to be confirmed in the 30-day verification). $50-100k ARR from Michigan alone is the credible 180-day case; first cash within 90-120 days is plausible given founding-customer deals, not guaranteed.
Distribution path
Demonstrated value, no relationship sales: EGLE's SRF applicant lists and SDWIS inventory of MI systems are public records — direct, specific outreach ('here is your system's current inventory status, here is your generated draft'). Michigan Rural Water Association and MI-AWWA section as amplifiers; consulting engineers as a channel (they resell capacity, you sell them leverage).
Pricing hypothesis
Utilities: $3-5k/yr subscription covering inventory upkeep + annual LCR report + one SRF project-plan package (additional packages per-filing). Consultants: $10-15k/yr multi-client seat. Undercuts a single consultant engagement while recurring — the wedge the rubric describes (software undercutting percentage-of-award consulting).
Technical difficulty
Moderate and squarely in the founder's lane: document generation, data normalization from messy utility spreadsheets, public-records mining, and (if MiEnviro allows) portal submission automation — the exact skill demonstrated on the FMCSA TPR. Hardest part is data messiness in old utilities' records, not the software.
Legal / regulatory risk
Low-moderate. Key line to respect: SRF project plans carry professional-engineering content — the product must position as preparing documents FOR the utility and its PE, never as engineering services, or it risks unlicensed-practice complaints from the consultants it undercuts (hypothesis, manageable by design). The founder never needs a license to operate the paperwork layer.
Platform dependency
The 'platform' is a state government submission process — no deplatforming risk per the rubric. Real dependency risk is regulatory: if Michigan or EPA relaxed LSL rules the recurring tail shrinks, but federal LCRI is tightening, not loosening (inference).
Founder fit
Maximal under the primary thesis: appropriated public money + a state rule compelling a defined filer class + a state portal + per-filing/per-seat monetization, in an industrial/operations domain (water infrastructure) where his fire-service and industrial-operations background reads as credibility, replicating a business shape he has already shipped and monetized (FMCSA ELDT → TPR). Michigan-first also matches 'state opportunity is often better' — then the cited Indiana/Wisconsin/Minnesota/Pennsylvania awards are the replication map.
Breakout potential
High: 50 states × ~50k community water systems nationally (inference), each under federal LCRI baseline requirements with state variations; the state-by-state playbook (ingest rule + template + portal, re-skin) compounds. The realistic ceiling for a solo operator is a $1-3M ARR multi-state niche platform or acquisition by 120Water/Trinnex-class incumbents.
Final recommendation
PURSUE, gated on one week of primary-source verification. The funded mandate is hard fact with named money and a compelled filer class; founder fit is as close to maximal as this system defines it; the two kill arguments are testable within 30 days for near-zero cost (read the MI rule + EGLE templates; ask EGLE whether a statewide inventory tool is procured or planned; ask 5 consultants what they'd pay). If Michigan's annual reporting tail is real and EGLE has not centrally procured a tool, build the MVP.
Next action
Pull Michigan's Lead and Copper Rule text and EGLE's current LSL inventory template + SRF project-plan guidance from public records TODAY; confirm (a) the annual reporting obligation and its next deadline, (b) MiEnviro submission mechanics, (c) whether EGLE already provides systems a mandated software tool. Then call the Michigan Rural Water Association to line up 10 small-system operator interviews.