What changed
FACT: FEMA is continuously publishing Federal Register notices that finalize Letters of Map Revision, each of which revises the effective Flood Insurance Rate Maps — and in some cases the Flood Insurance Study reports — for a listed set of NFIP communities, adding or modifying Base Flood Elevations, base flood depths, SFHA boundaries, zone designations, and regulatory floodways (https://www.federalregister.gov/documents/2026/07/09/2026-13897/changes-in-flood-hazard-determinations). Six such 'Changes in Flood Hazard Determinations' notices appeared on 2026-06-11 alone and at least four more on 2026-07-09. INFERENCE: every one of those revisions silently moves some parcels into an SFHA and some out of it.
Why now
HYPOTHESIS, not fact from the source: nothing in these notices is new — FEMA has published them on this cadence for decades. The honest 'why now' is not a regulatory event but a capability event: the National Flood Hazard Layer is now published as machine-readable geospatial data, county parcel polygons are broadly available, and a solo operator can run continent-scale polygon diffs cheaply. The mandate is old; the ability to industrialize the response to it is what changed. I am explicitly NOT claiming a fresh deadline — the notices state these determinations are already finalized.
Converging signals
Three things meet at one point: (1) a recurring federal notice stream that names, in a structured table, exactly which communities' maps changed and when (21 FEMA flood-hazard notices in the input, all FORCED BUYER type); (2) a defined remedy paperwork path — a Letter of Map Amendment or LOMR-F on FEMA Form 086-0-27, requiring an Elevation Certificate signed by a licensed surveyor; (3) a party with a hard financial motive to use it — a federally-regulated lender must require flood insurance on a structure in an SFHA, so the owner either pays the premium or files to get out. Signals 1 and 2 are FACT from the notices and FEMA's published forms. Signal 3's magnitude is INFERENCE.
Customer pain
INFERENCE (no complaint threads or job ads in the evidence set to prove it — I am not going to pretend otherwise): a property owner discovers they are in an SFHA only when a lender or insurer tells them, usually at closing or renewal. They then must find a surveyor, commission an Elevation Certificate, assemble the LOMA package, and wait on FEMA. The surveyor's pain is different and probably the more monetizable one: surveyors do the elevation work well and the paperwork badly, and they have no systematic way to know which of their local parcels just got remapped. Nobody is sitting on a list of newly-affected parcels the day a LOMR lands.
Who pays
Ranked by reachability, not by size. (1) Land surveying and flood-zone-removal firms — they already sell LOMA packages and will pay per-seat or per-package for pre-filled forms plus a lead list of parcels newly inside the SFHA in their service area. (2) The property owner, one-off, $200-400 for a done-for-you filing on top of the surveyor's certificate fee. (3) Lenders, title companies, and portfolio owners for continuous flood-zone-change monitoring — the largest wallet and the slowest sale. Note the LOMA application itself carries no FEMA fee for most cases; the money the owner is avoiding is the flood insurance premium, and the money they must spend regardless is the surveyor's.
Solved today
FACT: FEMA operates an Online LOMC portal and publishes the forms. INFERENCE about the market: a cottage industry of flood-zone-removal firms already charges consumers roughly $500-1,000 all-in to handle a LOMA, and large flood-determination vendors (CoreLogic, LERETA, ServiceLink) sell lenders zone determinations and life-of-loan monitoring. Surveyors handle the certificate and hand the owner a PDF. Nobody in the input data proves any of this — treat competitor pricing as unverified until checked.
Why current solutions are bad
The process is reactive. The LOMR is published, and then months later an insurance renewal notice tells one owner at a time that their zone changed. The information needed to act — which specific parcels crossed the boundary — exists the day the notice publishes but is locked in a polygon diff nobody performs. That latency is the entire wedge.
Proposed product
A pipeline that watches the Federal Register FEMA notice feed, resolves each LOMR case number to its effective NFHL geometry, diffs the pre- and post-revision SFHA polygons, intersects the delta against county parcel layers, and emits a per-community list of newly-in and newly-out parcels with owner-of-record from public assessor data. On top of that: a filing workspace that pre-fills the LOMA/LOMR-F form, requests the Elevation Certificate from a partnered surveyor, and submits to FEMA's Online LOMC portal — the same shape as the founder's shipped FMCSA Training Provider Registry uploader.
MVP version
Pick ONE state with clean, free, statewide parcel data (Utah, North Carolina, and Wisconsin are good candidates — verify before committing). Ingest the last 24 months of FEMA LOMR notices for that state, run the polygon diff, and produce a real, verifiable list of affected parcels. Do not build the portal integration first. Sell the list. If three surveying firms will not pay $500 for 'here are the 400 parcels in your county that got remapped last quarter,' the filing product is dead and you have spent six weeks instead of six months.
30-day build
Validate the data spine, not the idea. Confirm you can programmatically retrieve prior and current NFHL geometry for a given LOMR case (this is the single biggest technical unknown — FEMA's effective NFHL is a current-state layer, and reconstructing the pre-revision boundary may require the LOMR's own attachments rather than a tidy versioned API). Get statewide parcel data for the pilot state. Produce one county's newly-in-SFHA parcel list and hand-verify twenty parcels against FEMA's Map Service Center. If the diff cannot be reconstructed reliably, stop — the whole product rests on it.
60-day build
Cold-call or email fifteen surveying firms and flood-zone-removal outfits in the pilot state with their county's list attached. Charge for the list immediately: $299 one-time or $199/month for ongoing alerts. The goal is not revenue, it is discovering whether the parcel list is the product and the filing tool is the upsell, or the reverse. Simultaneously map the Online LOMC portal's submission flow by filing one real LOMA end-to-end, manually, for a cooperative property owner.
90-day revenue plan
Ship the pre-filled form generator and the surveyor workspace. Target ten paying surveyor seats at $199-299/month, which is roughly $2-3k MRR — modest, real, and it proves the per-seat channel. Per-filing revenue ($200-400) should be treated as upside within the first 180 days, not as the 90-day number, because filing volume depends on surveyor adoption that has not happened yet.
Distribution path
Direct outbound to surveying firms with their own county's remapped-parcel list as the demo — this is the founder's stated selling style, demonstrated value rather than relationship sales. State surveyor association newsletters and the Association of State Floodplain Managers conference circuit. A free public 'did my parcel's zone change?' lookup for one state as the SEO and lead surface. Explicitly NOT: consumer ads, which would be ad-spend-heavy and are ruled out by the founder profile.
Pricing hypothesis
$199-299/month per surveyor seat including their county's change feed; $249 per prepared LOMA package filed on the owner's behalf; $1,500-3,000/month for lender or title-company portfolio monitoring once the data is proven. Undercut the $500-1,000 consumer flood-zone-removal fee by making the surveyor the channel rather than competing with them for the homeowner.
Technical difficulty
Moderate-to-high, and higher than the convergence description implies. The description assumes 'diff old vs. new SFHA polygons' is a straightforward operation. It may not be: FEMA's NFHL publishes the *effective* layer, and historical geometry per LOMR case is not obviously exposed as a versioned API. Parcel data is 3,000+ county authorities with wildly inconsistent licensing and quality — statewide aggregation exists in some states and is sold by vendors (Regrid, ReportAll) in others, at real cost. Geospatial correctness matters here in a way that is unforgiving: a false 'you are now in a flood zone' notice to a homeowner is a serious error.
Legal / regulatory risk
Real but manageable. Preparing a LOMA package is form preparation, not surveying — the Elevation Certificate must be sealed by a licensed surveyor or engineer, and the founder must not appear to be practicing surveying or engineering without a license. Publishing 'your parcel is now in an SFHA' to homeowners is a factual claim with financial consequences; get it wrong and you have an unfair-trade-practices problem in some states. Structure as a tool sold to licensed professionals, not as flood-zone advice sold to the public, and this mostly dissolves.
Platform dependency
Low. The submission target is FEMA's Online LOMC portal; there is no platform owner who can deplatform you, per the founder's own thesis. The genuine dependency is on FEMA's data publication continuing in machine-readable form, and on parcel-data licensing terms if you use a commercial aggregator.
Founder fit
High and specific. This is structurally identical to the shipped FMCSA ELDT product: read a federal instrument, identify who is forced to file, build the submission layer against a government portal, charge per transaction. Add the public-records and systems-thinking strengths and the geospatial work is squarely in range. The one genuine mismatch is that surveyors are a professional-services buyer with slow purchasing habits, not the impulse buyer the ELDT product had.
Breakout potential
Moderate. The parcel-change feed is the asset, not the form-filler. If it works, the same diff engine extends to any recurring federal geospatial designation — wetlands, critical habitat, coastal barrier resources, airport noise contours — each with its own forced-filer class. That is a real expansion path. It does not become a billion-dollar company; it becomes a durable $30-80k MRR data-and-filing business, which is what the founder said he wants.
Final recommendation
CONDITIONAL — pursue only as a four-week data-feasibility spike, not as a build. The public-money thesis is being applied loosely here: the founder's rule scores a FORCED BUYER mandate 8-10 on demand alone, but the buyer this brief actually targets (the remapped homeowner, the surveyor) is not the party the notice compels. The compelled party is the NFIP community, and selling to municipalities is exactly the enterprise-procurement channel the founder rules out. Strip that away and what remains is a genuinely interesting data product — nobody publishes the newly-remapped-parcel list — sold into a discretionary market with no complaint evidence, no hiring evidence, and no deadline. That can still be a good business. It is not the ELDT shape, and pretending it is will cause six months to be spent on the wrong assumption. Spend four weeks answering exactly one question: can the pre-revision SFHA polygon be reconstructed programmatically at scale? Everything else is downstream of that.
Next action
Take the LOMR case numbers from the 2026-07-09 notice (https://www.federalregister.gov/documents/2026/07/09/2026-13897/changes-in-flood-hazard-determinations), pick three cases in one state, and attempt to reconstruct the pre-revision SFHA boundary for each from FEMA's Map Service Center and NFHL. Timebox it to two weeks. If you cannot get the 'before' geometry without hand-digitizing a PDF, kill the idea and say so.