What changed
FACT (from the Federal Register text provided): HUD has published a proposed rule that would rescind its April 23, 2024 final rule 'Floodplain Management and Protection of Wetlands; Minimum Property Standards for Flood Hazard Exposure; Building to the Federal Flood Risk Management Standard,' acting under Executive Order 14148, which revoked the executive order underpinning that rule. The proposal would generally restore 24 CFR part 55 to its pre-April-2024 state while MAINTAINING flexibilities from the 2024 rule related to floodways, categorical exclusions, exemptions from part 55 applicability, and the decisionmaking process. It is a PROPOSED rule with the comment period open; the input records EFFECTIVE: n/a.
Why now
HYPOTHESIS: the resulting regime is not simply 'the old rule back.' It is a hybrid — old baseline elevation/standards, retained 2024 flexibilities on floodways, categorical exclusions, applicability exemptions, and decisionmaking. That hybrid is precisely what a reviewer cannot look up in either the old guidance or the 2024 guidance, because it exists in neither. Every checklist, template, and consultant SOP in circulation encodes one of the two pure regimes. FACT: the rule text itself states the hybrid character ('would restore ... although it would maintain flexibilities'). The window is the interval between a final rule and the moment HUD Exchange republishes its templates — historically months, and HUD's own template refresh is free when it lands.
Converging signals
Three things meet at one point, and I will be honest that only the first is documented in the input. (1) FACT: a federal rule rewrites the applicability and decisionmaking process of part 55. (2) INFERENCE: the actor class is HUD responsible entities — CDBG and HOME entitlement communities, public housing authorities, state HUD-assisted program administrators, and developers of HUD-assisted properties. The provided text names part 55 applicability and the decisionmaking process; it does NOT name the actor class. I assert the class from the structure of part 55, which is executed by responsible entities that receive HUD funds. (3) INFERENCE, and weaker: the destination is HUD's HEROS environmental review system. HEROS is not named anywhere in the provided source. Do not treat the portal claim as established.
Customer pain
HYPOTHESIS throughout — the input contains no complaint threads, no job postings, and no PRA respondent count. A responsible entity performing a part 55 review must determine whether the project site sits in a 100-year or 500-year floodplain, whether an exemption or categorical exclusion applies, and if not, execute the eight-step decisionmaking process, which includes early and final public notice, alternatives analysis, and a written finding. It is document-assembly work with a legal consequence: a defective floodplain record is a finding in a HUD monitoring review and can jeopardise the release of funds. What the rule change does is invalidate the reviewer's mental model of step one — is this project even in scope — at the exact moment the paperwork must still go out on deadline.
Who pays
Two candidate buyers, and only one is reachable. The environmental-review CONSULTANT is the buyer: the regional firms and solo NEPA practitioners who perform part 55 and 24 CFR part 58 reviews under contract to cities and PHAs. They bill per review, they carry the professional liability, they feel a standards change immediately, and they buy tools with a corporate card. The responsible entity itself — the city, the PHA — is the wrong buyer: municipal procurement, annual budget cycles, and a free federal alternative sitting on their desk. Sell to the consultant, not the city.
Solved today
HYPOTHESIS: today the review is done in HEROS (HUD's free web system, which structures the environmental review and stores the record), assisted by Word templates from HUD Exchange, a manual lookup against FEMA's National Flood Hazard Layer or the FEMA Flood Map Service Center, and the reviewer's own accumulated judgement. Large firms have internal checklists. Nobody I can document from the provided input is paying for a dedicated part 55 tool.
Why current solutions are bad
The flood-hazard determination is a manual map lookup transcribed by hand into a narrative. The eight-step record is prose assembled from a template. Neither is hard; both are slow, and both are exactly the kind of task where a reverted-plus-flexibilities standard produces a wrong answer that survives until a monitoring visit two years later. That is the wedge: not speed, but 'this record reflects the standard in force on the date you signed it.'
Proposed product
A per-review web tool for consultants. Input a parcel address or APN. It queries FEMA's National Flood Hazard Layer for the flood zone, base flood elevation, and floodway status, and captures the map panel and effective date as evidence. It then routes the reviewer through the decisionmaking sequence AS AMENDED — encoding the retained flexibilities on floodways, categorical exclusions, and applicability exemptions against the restored baseline — and refuses to let the reviewer skip a step without recording why. Output is a formatted decisionmaking record with the public-notice drafts, the alternatives narrative scaffold, the map evidence, and a versioned citation to the regulation text as of the review date. The defensible asset is not the map call; it is the encoded rule-diff and the dated citation trail.
MVP version
Parcel-to-flood-zone lookup against the FEMA NFHL, a stepper that implements the amended sequence, generated Word/PDF public notices and the written finding, and a per-review evidence bundle. Deliberately NOT in the MVP: HEROS integration. HEROS is an inference, not a fact, and I have not confirmed it exposes any submission API. Build to export a document the consultant pastes into HEROS. Automate the portal only after a real consultant confirms the paste step is the bottleneck.
30-day build
Do not write the product. Read the actual proposed rule and the current part 55 text side by side and produce the rule-diff as a document — what reverted, what flexibility survived, what the decisionmaking sequence now is. Publish it free. That document is simultaneously the market test, the content asset, and the thing you would have had to build anyway. In parallel, file a comment on the docket (this puts your name in the public record the practitioners read) and interview fifteen consultants found via HUD Exchange trainings and the NEPA practitioner community. Ask what they charge per part 55 review and how many they do a year. If the answer is 'four reviews a year at $900 each,' the market is too small and you stop here, having spent thirty days and no capital.
60-day build
Only if the interviews clear a bar — say, ten firms doing thirty-plus reviews a year each — build the FEMA NFHL lookup and the record generator against the pre-2024 sequence with the retained flexibilities. Recruit five of the interviewed consultants as design partners at zero cost in exchange for using it on a live review. Instrument which steps they abandon.
90-day revenue plan
Convert design partners at a per-seat annual price. Revenue in ninety days is unlikely and I will not pretend otherwise: the rule is a proposal with no effective date, and consultants will not change a workflow for a rule that has not landed. Realistic first revenue is on final-rule publication, whenever that falls. Budget for a build that sits idle waiting for the Federal Register.
Distribution path
HUD Exchange training attendee lists, the NEPA and environmental-review practitioner listservs, direct outreach to the firms named as environmental consultants in city RFP awards (public records — squarely in the founder's wheelhouse), and the rule-diff document as the top-of-funnel. No paid acquisition; the audience is a few thousand people worldwide.
Pricing hypothesis
Per-seat annual subscription, roughly $1,200–$2,400 per reviewer per year, or $75–$150 per generated record for occasional users. Anchor against the consultant's billed hours on a single review, not against HEROS, which is free and always will be.
Technical difficulty
Low. FEMA publishes the National Flood Hazard Layer as a public map service. Document generation is templating. The genuinely hard part is not code — it is correctly encoding a regulation that has not been finalised, and being right about it, because being wrong produces a defective federal record for a paying customer. That is a legal-research burden, not an engineering one, and it recurs every time HUD touches part 55.
Legal / regulatory risk
Meaningful and under-appreciated. The product asserts a regulatory determination that a professional signs and a federal agency audits. If the tool applies the wrong floodplain standard and a monitoring review flags the record, the consultant's exposure becomes an argument about the tool. This is not the ELDT case, where the founder transmits a certificate someone else attested to. Here the software is generating the substantive finding. Mitigate with explicit 'reviewer of record' attestation, dated regulation citations, and errors-and-omissions coverage. Do not skip the insurance.
Platform dependency
None meaningful. FEMA's map service is a public federal data source. There is no platform owner who can deplatform a tool that produces a document. If HEROS integration is ever pursued, that dependency is on a federal system with no commercial incentive to exclude anyone.
Founder fit
Genuinely high on shape and lower on substance. The shape — a regulation compels a class to produce a document, and a solo operator builds the document layer and charges per unit — is exactly the ELDT pattern the founder has already executed, and the accumulated lesson that government-portal mandate opportunities fit him best (confidence 0.80) applies directly. Public-records skill maps onto finding the consultant list. But two things differ from ELDT. The ELDT mandate created a NEW filing obligation with a hard compliance date and a filer class that could not operate without filing. This rule REMOVES burden — it is a rescission — and the obligation it touches already existed and is already served by a free federal system. The founder's edge was building a submission layer where none existed. Here the submission layer exists, it is HUD's, and it costs nothing.
Breakout potential
Bounded. The natural expansion is the whole of 24 CFR part 58 environmental review — historic preservation, endangered species, noise, contamination — of which floodplain is one screen. If the record generator wins on floodplain, the same buyer needs the other seven. That is a real product with a real ceiling somewhere in the low seven figures of annual revenue. It does not compound and it does not become large.
Final recommendation
CONDITIONAL — investigate for thirty days, do not build. The founder-fit is real and the shape is the one he has already proven he can execute, which is exactly why this deserves a disciplined look rather than reflexive enthusiasm. But the central premise inverts on inspection: this is a deregulatory rescission with no effective date, aimed at an obligation that a free federal system already services. Three of the five kill arguments — free incumbent, wrong-direction mandate, no deadline — are structural and are not resolved by building better software. The one thing that could rescue it is the hybrid-standard confusion, which is genuinely real and genuinely temporary, and which is worth exactly one document and fifteen phone calls to test. Spend the thirty days. Publish the rule-diff. If consultants tell you they do thirty-plus part 55 reviews a year and hate the record assembly, build it. If they shrug and say HEROS is fine, you have lost a month and gained a public-records asset and a comment in a federal docket, which is a cheap way to be wrong. Do not skip to the build because the shape looks like ELDT. ELDT had a compliance date and no incumbent.
Next action
Read the full text of the proposed rule at the Federal Register URL alongside the current 24 CFR part 55, and write the plain-English rule-diff: what reverts, which flexibilities survive on floodways, categorical exclusions, and applicability exemptions, and what the decisionmaking sequence becomes. Publish it. Then use city RFP award records to build a list of environmental-review consultants and call fifteen of them with one question: how many part 55 reviews did you do last year, and what did you bill for each.