What changed
FACT (grants.gov, DHS-26-MT-143-00-01): FEMA posted the FY2026 Pre-Disaster Mitigation Grant Program (CFDA 97.143), closing 07/22/2026. FACT (input): the federal award goes to states/territories/tribes as recipients, but the actual filers are subrecipient local governments, which must hold a FEMA-approved Hazard Mitigation Plan and submit subapplications through their state hazard mitigation officer.
Why now
FACT: a hard close date of 07/22/2026 exists. HYPOTHESIS: mitigation-plan expirations are continuous and uncorrelated with the NOFO calendar, so at any moment some fraction of the ~20,000 jurisdictions are ineligible and unaware — that is the recurring, non-deadline-bound wedge that keeps the product alive between funding cycles.
Converging signals
Three things meet at one point: (1) an appropriated federal mitigation program with a stated deadline; (2) a defined, enumerable filer class (subrecipient local governments); (3) a required submission with three distinct artifacts — a benefit-cost analysis, an EHP review packet, and an adopted, current mitigation plan — routed through FEMA GO and varying state HMO intake portals. HYPOTHESIS: the BCA is the single most common reason a subapplication is returned or scored down, because it demands loss-avoidance modeling that a public-works director has no training in.
Customer pain
HYPOTHESIS (not established by the provided sources — no complaint threads or job postings were supplied): a town of 8,000 has no grants officer. The BCA requires structure-level damage-frequency and loss-avoidance inputs; the EHP packet requires environmental and historic-preservation documentation; and the mitigation plan must be current on the submission date. Missing any one voids the subapplication after weeks of unpaid staff effort. FACT (input): all three artifacts are required, so the failure modes are structural, not speculative.
Who pays
Primary: the subrecipient local government itself (city manager, emergency manager, public-works director) paying a per-subapplication fee from the grant-writing line or from the award's own administrative allowance. Secondary and probably faster: the regional planning councils, councils of government, and independent grant consultants who already assemble these packets for a fee and would license the tool to do more of them per head. Tertiary: state hazard mitigation offices buying seats to reduce the volume of defective subapplications they must reject — but this is the procurement-shaped channel and should not be the first one.
Solved today
HYPOTHESIS: three ways. (1) A consultant assembles the packet for a fee, commonly quoted as a percentage of the award or a flat five-figure engagement. (2) A regional planning council does it as a member service. (3) Staff do it themselves in Word and Excel against FEMA's BCA Toolkit and a state HMO checklist, and frequently fail. FEMA supplies the BCA Toolkit free; it computes a benefit-cost ratio but does not gather the inputs, does not assemble the EHP packet, and does not monitor plan currency.
Why current solutions are bad
The consultant is expensive and does not scale below a certain award size, so small jurisdictions — the ones most likely to have a lapsed plan — are the ones least served. Doing it in-house is slow and error-prone. And nothing in the current stack watches the clock on plan expiry: a jurisdiction discovers it is ineligible when it applies, which is exactly too late, because plan re-adoption takes months of public process.
Proposed product
A three-part product, deliberately sequenced. (A) Plan-currency monitor: a per-seat subscription that tracks the adoption and expiry date of a jurisdiction's Hazard Mitigation Plan and alerts at 24, 18, and 12 months out with the re-adoption runway. (B) BCA data-prep workspace: guided intake that pulls the structure, hazard, and loss inputs a BCA needs, validates them against FEMA's methodology, and exports a Toolkit-compatible package plus the narrative. (C) EHP checklist packet assembler: the document set, per state HMO's intake variations. Sell (A) first — it is cheap to build, is not deadline-bound, and creates the list of buyers who will later need (B) and (C).
MVP version
The plan-currency monitor for one state. Assemble the roster of that state's jurisdictions with adopted plans and their approval dates from the state HMO's plan-status page and FEMA's approved-plan records, put it behind a simple lookup and an email alert, and give the free lookup away publicly. That is the demonstrated-value artifact the founder sells through. The BCA workspace follows for the second release.
30-day build
Pick two states with different portal shapes. Obtain the plan-status roster and approval dates for every jurisdiction in both. Ship a public, free 'is my mitigation plan current?' lookup covering both states. Read the FY2026 PDM NOFO end to end and one state's HMO subapplication intake instructions end to end, and write down every field each requires. Call ten emergency managers and five regional planning councils; do not sell, ask what killed their last subapplication.
60-day build
Build the BCA data-prep workspace against FEMA's published BCA methodology for the two or three most common project types (acquisition/demolition, elevation, culvert upsizing). Export a Toolkit-ready input package. Take three real subapplications through it with a consultant or a council of government as a design partner, at cost or free, in exchange for the right to say it worked.
90-day revenue plan
First revenue from the consultants and regional planning councils, not the towns — they buy faster, have a budget line, and do volume. Price the plan monitor as a per-seat annual subscription, the subapplication assembler as a per-subapplication fee. The 07/22/2026 close date is a real forcing event for this cycle, but do not build the business around catching it; the FY2027 cycle and the continuous stream of expiring plans are the durable demand. HYPOTHESIS: first paid subapplication within 120-150 days, first monitor subscription sooner.
Distribution path
The free plan-expiry lookup is the distribution: a jurisdiction that learns its plan lapses in 14 months has a problem with a name and a deadline, and the product that told them is the product they call. Beyond that: state hazard mitigation officer newsletters and the annual state mitigation conferences, the National Association of Counties and state municipal-league channels, and direct outreach to the regional planning councils, which are enumerable, publicly listed, and each serve dozens of jurisdictions. The founder's fire-service background is genuine standing with emergency managers — this is a community that checks whether you have ever been on a call.
Pricing hypothesis
Plan-currency monitor: $600-1,200 per jurisdiction per year, per seat. Subapplication assembler: $2,500-6,000 per subapplication, or a consultant/COG license at $8,000-20,000 per year for unlimited assemblies. The consulting alternative is priced far above this, which is the wedge. Do not price as a percentage of the award — it invites the comparison you want to avoid and creates a contingent-fee posture with a federal grant.
Technical difficulty
Moderate. The BCA is the hard part and it is a modeling problem, not an engineering problem: the founder must genuinely understand FEMA's benefit-cost methodology or the exports will be wrong in ways that get subapplications rejected and destroy the reference base. Budget real time for this, and consider paying a former state HMO staffer as a contractor — the founder has capital for exactly this. The plan monitor and the EHP assembler are ordinary document and data work. State HMO portal variation is a data-collection slog, not a technical barrier, and it is also the moat.
Legal / regulatory risk
Low to moderate, but real and worth naming precisely. The tool prepares a submission that a jurisdiction certifies to a federal agency. If the BCA export is systematically wrong, the exposure is reputational and contractual before it is legal, but a jurisdiction whose award is clawed back will look for someone to blame. Mitigate with clear terms: the software prepares inputs, the jurisdiction certifies. Do not offer a benefit-cost-ratio guarantee. This is not a licensed activity — the founder does not need to become certified to operate, so compliance is the moat rather than a burden.
Platform dependency
None meaningful. FEMA GO and state HMO portals are government systems; there is no platform owner who can deplatform the product. The genuine dependency is on FEMA's continued funding of mitigation programs and on the stability of the BCA methodology — a methodology revision forces a rebuild of the workspace. HYPOTHESIS: methodology revisions are infrequent and announced.
Founder fit
Very high, and for the reason the accumulated lessons predict (government-portal mandate shape, confidence 0.80). This is structurally the ELDT Training Provider Registry product: a federal program compels a defined class to submit to a government system, and a solo operator builds the submission layer and charges per filing. The founder has shipped exactly this once. He also has fire-service background, which is real credibility with the emergency-management buyer, and public-records fluency, which is what assembling the 50-state plan-status roster actually requires. The lesson that he now has capital and runway (confidence 0.90) applies: a 120-150 day ramp is acceptable and should not be penalized.
Breakout potential
Good, and it compounds in the right direction. The plan-currency roster — every jurisdiction, its plan status, its expiry — is a proprietary dataset assembled from scattered public records, and it gets more valuable and harder to replicate the longer it is maintained. Once one state's subapplication flow works, the other 49 are near-identical forms over the same federal requirement, which is the founder's preferred replication shape. The same assembler generalizes to the Building Resilient Infrastructure and Communities program, the Flood Mitigation Assistance program, and post-disaster HMGP subapplications, which share the BCA and EHP requirements. The ceiling is not enormous, but it is a durable seven-figure business held by one operator.
Final recommendation
BUILD, with the sequence inverted from the obvious one and with a 30-day kill gate before writing code. The opportunity is real and the founder-fit is close to maximal — this is the same shape as the product he has already shipped, against a federal program with a defined filer class and a required submission. But the demand evidence attached to this convergence does not support what it appears to support: the three USAspending awards are disaster-repair records surfaced by semantic similarity and are not evidence of anyone paying for mitigation subapplication preparation. Score demand from the NOFO, which is legitimate forced-buyer evidence, and from nothing else. Build the free plan-expiry lookup first because it is cheap, is not deadline-bound, generates the buyer list, and is the demonstrated-value artifact this founder sells through. Before building the BCA workspace, spend the 30 days confirming that regional planning councils and consultants will pay rather than compete — that single question decides whether this is a business or a grind.
Next action
Call five regional planning councils or councils of government and ask three questions: who assembles mitigation subapplications for your member jurisdictions, do they charge for it, and what killed the last one that failed. If they charge, they are the customer and the wedge is real. If it is a free member service, this idea is materially weaker and the plan-expiry monitor is the only thing worth building.