What changed
FACT (per input): FEMA posted the FY2024 & FY2025 Building Resilient Infrastructure and Communities (BRIC) NOFO, CFDA 97.047, opportunity DHS-25-MT-047-00-98, closing 07/23/2026, on Grants.gov. A funded, dated federal grant cycle with a defined downstream filer class now exists.
Why now
FACT: there is a hard close date of 07/23/2026. INFERENCE: subapplications must clear a state emergency management agency's internal deadline weeks-to-months earlier, compressing the real buying window into late 2025/early 2026 — which is now. A subapplication that misses the state cut-off is worth zero, so willingness to pay peaks immediately before the deadline.
Converging signals
Three signals meet at one point: (1) appropriated federal money flowing through a named program (BRIC, CFDA 97.047); (2) a compelled filer class — local governments, tribes, and special districts filing subapplications to a state recipient; (3) a specified federal portal (FEMA GO, FACT per input) plus 50+ heterogeneous state intake systems. CRITICAL NOTE FROM THE INPUT ITSELF: this convergence is explicitly the same product as convergence id 2782 (PDM). That is not a defect — BRIC and PDM share the subapplication form set, the BCA requirement, the EHP requirement, the HMP prerequisite, and the identical filer class. Two funded programs, one codebase, one buyer. Duplication here is evidence of product-market leverage, not of a repeated idea.
Customer pain
HYPOTHESIS (not proven by the provided source text): a small-town floodplain administrator or public works director must produce a FEMA-compliant benefit-cost analysis, an Environmental & Historic Preservation record, proof of a current local Hazard Mitigation Plan, and a scope/budget narrative — then repeat quarterly financial and performance reporting for years post-award. FACT from the input: the paperwork set is exactly that. The pain is inferred from the paperwork burden, not from any complaint thread in this input.
Who pays
The subapplicant jurisdiction (city, county, tribe, special district, levee/drainage/fire district) pays per subapplication. Secondary and probably faster-closing buyer: the grant-writing and engineering consultancies that already assemble these packages and bill the jurisdiction — they buy seats to raise throughput. Tertiary: state hazard mitigation officers (SHMOs) who want clean intake, but that is a procurement sale and should NOT be the primary channel.
Solved today
HYPOTHESIS: three ways — (a) a grant-writing or engineering consultant assembles the package for a fee or a percentage of the award; (b) an overloaded staffer assembles it manually using FEMA's BCA Toolkit spreadsheet and Word templates; (c) the jurisdiction does not apply at all. None of this is evidenced in the provided source text; it is inference from the paperwork description.
Why current solutions are bad
INFERENCE: consultants are expensive and capacity-constrained near deadlines; the FEMA BCA Toolkit is a standalone desktop artifact that does not connect to the narrative, the EHP record, or the HMP; nothing carries the subapplication data forward into the mandatory post-award quarterly reports, so the same facts are re-keyed for years. The reporting tail is where a per-seat subscription lives.
Proposed product
A web app that (1) intakes project facts once — asset, hazard, location, damage history, proposed mitigation, cost; (2) computes a FEMA-methodology benefit-cost ratio with a defensible, exportable calculation trail; (3) generates the EHP documentation checklist and assembles supporting records; (4) verifies and links the jurisdiction's current FEMA-approved Hazard Mitigation Plan; (5) emits the completed subapplication package in the format the specific state's intake system requires; (6) after award, reuses the same record to generate quarterly financial and performance reports. One codebase serves BRIC and PDM (and, INFERENCE, HMGP after any declared disaster — the same BCA and EHP requirements attach).
MVP version
Scope to one state and one project archetype. Build the BCA engine for the highest-volume archetype (INFERENCE: acquisition/elevation of repetitive-loss structures, or culvert/drainage upsizing) with an auditable calculation trail, plus the EHP checklist and package export for that one state's intake format. Do not build FEMA GO submission automation in v1 — the state, not the subapplicant, is the FEMA GO filer. The subapplicant files to the STATE. Build to the state's form, not the federal portal.
30-day build
Verify, do not assume. Read the FY24/25 BRIC NOFO end to end and the current FEMA BCA methodology. Pull 20-40 funded prior subapplications via state public-records requests (the founder's public-records strength directly applies) to learn the real form set and the real failure modes. Call 15 state hazard mitigation officers and ask one question: what makes you send a subapplication back? Their rejection reasons are the product spec. In parallel, identify the 20 consultancies advertising BRIC/PDM package assembly and learn their fee structure.
60-day build
Build the BCA engine plus one state's package export. Recruit 5 design partners from the consultancy list at a discounted seat price in exchange for real subapplications run through the tool before the state cut-off. Instrument every rejection and re-file.
90-day revenue plan
Charge per subapplication assembled, invoiced at package export, against the 07/23/2026 close. Consultancy seats convert to annual subscriptions once post-award quarterly reporting begins. Revenue within 180 days is plausible; revenue within 90 days depends entirely on landing consultancies rather than jurisdictions, because a city's purchase order for new software takes longer than 90 days.
Distribution path
Direct outreach to state hazard mitigation officers for a referral listing (they want fundable subapplications and have no incentive to gatekeep tooling); the state floodplain managers' associations and ASFPM conference circuit; consultancy partnerships. NOT government procurement. INFERENCE: SHMOs publish subapplicant contact lists and prior award lists — a clean, public, addressable buyer list exists.
Pricing hypothesis
$1,500-$4,000 per subapplication assembled (anchored well under a consultant's percentage-of-award fee), plus $250-$600/month per consultancy seat covering unlimited subapplications and post-award quarterly reporting. HYPOTHESIS on both figures; validate against actual consultant fees discovered in the 30-day plan.
Technical difficulty
Moderate and front-loaded. The BCA engine must reproduce FEMA's published methodology exactly enough that a state reviewer accepts the number; a wrong BCR is a rejected application and a dead reference customer. This is a correctness problem, not a scaling problem — well suited to a solo AI-assisted build, but it is not a weekend. Per-state form divergence is real recurring integration cost.
Legal / regulatory risk
Low. No license or certification is required to prepare a grant application on a client's behalf. Real exposure is professional: if the tool produces a BCR that survives to award and is later disallowed on audit, the jurisdiction has a grievance. Mitigate with an auditable calculation trail, explicit assumption disclosure, and contractual disclaimer that the jurisdiction certifies the submission.
Platform dependency
None in the deplatforming sense — there is no platform owner who can revoke access to a government form. The dependency is POLITICAL, and it is the single largest risk here: BRIC is a discretionary appropriation and FEMA has previously moved to curtail it. HYPOTHESIS (I cannot verify this from the provided source, and it must be checked before any build): the BRIC program has faced cancellation, clawback, and litigation. The Grants.gov listing being 'posted' with a 07/23/2026 close is the only status evidence in the input. VERIFY PROGRAM VIABILITY BEFORE WRITING CODE.
Founder fit
Very high on shape, and unusually high on substance. This is exactly the ELDT pattern — a federal program compels a defined class to file a package into a government system, and the founder builds the submission layer and charges per filing. Beyond the shape: the fire-service background maps onto hazard mitigation and emergency management as a domain, gives him credibility with the exact buyer, and shortens the cold-call. The public-records strength is the acquisition channel for prior subapplications and subapplicant lists. The one mismatch: BCA methodology fidelity demands more domain depth than an ELDT certificate upload, and 'sells through demonstrated value' works better on consultancies than on city councils.
Breakout potential
Strong, for a specific structural reason. The BRIC/PDM overlap the input flags means one product serves two funded programs; adding HMGP (INFERENCE: triggered by every presidential disaster declaration, same BCA and EHP requirements) makes the addressable filing volume disaster-driven and continuous rather than one annual cycle. Fifty states as near-identical replication targets. The post-award quarterly reporting tail converts one-time filers into subscribers.
Final recommendation
PURSUE — conditionally, and with one gate before any code. The shape is the founder's thesis executed almost perfectly: appropriated federal money, a defined and enumerable filer class, a mandatory document set, a government portal, a deadline, and an incumbent consultant billing a percentage of the award to undercut. The fire-service background and public-records skill are unusually well matched. The BRIC/PDM duplication the input flagged is the strongest point in the brief, not a redundancy: one build, two funded programs, and HMGP waiting behind them. But the demand rests on ONE Grants.gov listing, and BRIC is discretionary money, not a statutory mandate — which is the precise respect in which this differs from ELDT. GATE: spend one week confirming (a) that BRIC and PDM funding is actually live and will disburse, (b) what incumbent BCA and grant-management tools already exist, and (c) whether consultancies bill percentage-of-award (in which case they are the buyer) or hourly (in which case they are the enemy). If BRIC is politically dead, pivot the same codebase to HMGP, which is disaster-triggered and far harder to cancel. If those three check out, this is the best-fitting opportunity the profile can produce.
Next action
Before anything else: verify BRIC/PDM program viability and appropriation status — confirm the DHS-25-MT-047-00-98 listing is live and unencumbered by cancellation or litigation. Then, in the same week, file public-records requests with three state emergency management agencies for their last cycle's subapplication packages and reviewer rejection notes, and call five state hazard mitigation officers with one question: what makes you send a subapplication back?