What changed
FACT (Federal Register, 2026-07-09): FEMA finalized new or modified Base Flood Elevations, base flood depths, SFHA boundaries/zone designations and regulatory floodways via Letter of Map Revision for a listed set of communities, revising the effective FIRMs and, in some cases, the FIS reports. INFERENCE: this is a routine, recurring notice type — not a new rule.
Why now
There is no 'now'. INFERENCE: LOMRs have been issued continuously on this exact notice schedule for decades. The trigger that produced this convergence is a standing administrative process, not a rule change. That is the single most important fact in this brief and it undermines the newness premise.
Converging signals
One primary source only: the FEMA 'Changes in Flood Hazard Determinations' notice. The two other demand_evidence items (FMCSA inspection-report disposition, IRS consistent-basis reporting correction) were retrieved by semantic similarity at 0.72-0.75 and are substantively unrelated to flood mapping — they share the surface grammar of 'a party must file something' and nothing else. They are NOT evidence of demand for this product and I am not scoring them as such.
Customer pain
FACT from source: communities whose FIRMs are revised must operate under the revised maps. INFERENCE (not stated in the notice): lenders must refresh flood determinations on affected loans; owners newly inside an SFHA with a federally backed mortgage face the mandatory-purchase requirement; owners who believe they are wrongly mapped in may seek a LOMA or LOMR-F. The pain is real but it is decades old and already served.
Who pays
Candidate buyers: (1) mortgage lenders/servicers — but they buy flood determination as a regulated deliverable (the Standard Flood Hazard Determination Form) under life-of-loan tracking contracts; (2) title companies and insurance agents; (3) property owners filing map amendments; (4) community floodplain administrators. HYPOTHESIS: only (2) and (3) are reachable by a solo operator, and neither is a strong buyer.
Solved today
HYPOTHESIS (high confidence, not from the provided source): CoreLogic, LERETA, ServiceLink Flood, and First American already sell life-of-loan flood zone determination with automatic re-determination on every map revision. That IS this product, sold under contract to the exact buyer named in the monetization plan, with the regulatory certification lenders require. FEMA itself publishes the National Flood Hazard Layer and a Map Service Center change feed for free.
Why current solutions are bad
It is not meaningfully bad. Incumbent determination vendors are boring and expensive, but they carry the compliance liability the lender is actually buying. A solo unbranded feed does not transfer that liability, which is most of the value.
Proposed product
As specified — parse effective LOMRs, geocode revised panels, diff against parcel and mortgage data, push in/out-of-SFHA notices, charge per map-amendment filing plus a lender subscription.
MVP version
Scrape the Federal Register LOMR notices, pull the corresponding revised panel geometry from FEMA's NFHL, spatially intersect against county parcel shapefiles, emit a per-parcel delta list. Genuinely buildable in a few weeks by this founder. The build is not the problem.
30-day build
Do not build. Spend 30 days on two disqualifying questions: (a) call five community banks and five independent insurance agencies and ask what they pay today for flood determination and whether they would switch; (b) confirm the eLOMA licensure gate below. If both come back negative, kill.
60-day build
Contingent on 30d. If a narrow buyer emerges (most likely: independent insurance agents wanting a farming list of newly-in-SFHA parcels for outbound quoting, or surveyors/floodplain consultants wanting lead lists of newly-in parcels who will need Elevation Certificates), build the delta list as a data product for that buyer only. Abandon the lender feed entirely.
90-day revenue plan
Under the narrowed shape: sell county-level newly-in-SFHA parcel lists to surveyors and insurance agents as a lead product at $200-500/county/revision. This is a lead-gen data product, not a compliance tool, and should be judged as one. Realistic first revenue is small and slow.
Distribution path
Weak. No forced buyer to cold-open with. Insurance agents and surveyors are reachable but low-value and fragmented. Lenders are not reachable without a vendor-management review, which is enterprise procurement in everything but name.
Pricing hypothesis
The proposed $75-150 per map-amendment filing assumes the founder can file the amendment. See legal_risk — he cannot.
Technical difficulty
Low-moderate. NFHL geometry, parcel data acquisition (paid, county-by-county, inconsistent), spatial diff. Parcel data licensing across many counties is the real cost and it is a per-county grind, not a one-time build.
Legal / regulatory risk
THE KILL SHOT. HYPOTHESIS (high confidence, must be verified, not stated in the source): FEMA's eLOMA is restricted to Licensed Land Surveyors and Professional Engineers — the submitter must certify elevation data under their license. A LOMA/LOMR-F requires an Elevation Certificate signed by a licensed surveyor. This is categorically different from the founder's FMCSA ELDT precedent, where any training provider could be given a submission pipe. Here the founder himself would have to be licensed, or would be reduced to reselling a surveyor's signature. Per the founder's own rule, heavy_compliance applies precisely when the founder must become licensed to operate. He must.
Platform dependency
Low. FEMA is not a platform owner that can deplatform him. Correctly NOT flagging platform_policy_risk.
Founder fit
The shape looks like his ELDT win and is not. ELDT: a mandate created a new filer class (training providers) with no incumbent and no licensure gate on the submitter. This: an ancient process, four entrenched national vendors owning the paying buyer, and a licensure gate on the filing itself. Pattern-matching on 'federal portal + per filing' without checking who is permitted to file is exactly how this founder would waste six months.
Breakout potential
Low as a compliance tool. Moderate as a national parcel-level flood-change dataset, but that is a data business competing with CoreLogic on their home ground.
Final recommendation
KILL as proposed. The public-money/forced-filer lens is the right lens and this idea fails it on inspection: the mandate is not new, the filer is the community (not a buyer), the profitable filing is gated behind a professional license the founder does not hold, and the one buyer with budget is under contract to four incumbents. The system's heuristic that government-portal mandates are maximal founder-fit (confidence 0.80) is a prior, and this is the case where fresh evidence overrides it — the heuristic should be amended to require that the founder be *permitted to file*. The only survivable residue is a newly-in-SFHA parcel lead list for surveyors and insurance agents, which is an ordinary data product worth perhaps a few thousand dollars a month and should be judged on its own unglamorous merits, not smuggled in under the FedMoney thesis.
Next action
Before any code: confirm or refute in one hour of reading whether eLOMA submission requires licensure and whether a LOMA requires a surveyor-signed Elevation Certificate. If confirmed, kill and record the lesson. If refuted, this brief is wrong and the idea deserves a rescore.