What changed
FACT: Florida's AG announced nearly $2B in previously delayed FEMA funds is releasing to Florida (Florida's Voice). FACT: USAspending shows multiple billion-dollar DHS/FEMA Public Assistance awards obligated to state emergency-management divisions (FL $1.53B, $2.89B, $2.25B, $4.94B, $2.42B; GA $1.60B; PR $1.80B; LA $3.57B; NC $2.35B), each a pass-through to local/tribal/nonprofit subrecipients who must file federally standardized documentation to draw the money.
Why now
FACT: The FL backlog is disbursing 'now' per the trigger; GAO (gao-26-107772) confirms the structural bottleneck — of ~$11.1B FEMA-obligated for Puerto Rico only ~$2.7B disbursed, i.e. money is obligated but stuck behind documentation/administration. HYPOTHESIS: as each state's delayed backlog releases over the next few quarters, a fresh cohort of subrecipients hits the same documentation wall simultaneously, creating a recurring, deadline-driven demand pulse.
Converging signals
Three signals meet at one point: (1) a large pool of obligated-but-undisbursed PA money, (2) a defined forced-filer class (counties, municipalities, school districts, hospitals, private non-profits), and (3) a federally standardized submission process (Grants Portal / FEMA GO) that is near-identical across all 50 states.
Customer pain
FACT (inferred from GAO + FEMA PA program mechanics): subrecipients lose real dollars when Project Worksheets, force-account logs, or 2 CFR 200 procurement documentation are deficient — funds are deobligated or clawed back on audit. Assembling packets is manual, spreadsheet-driven, and error-prone, and small local governments/nonprofits lack dedicated grants staff. NOTE: specific complaint threads were not in the input; pain is inferred from program structure and the GAO disbursement gap, not from cited user complaints.
Who pays
Day-one buyer: subrecipients drawing PA money — county/municipal governments, school districts, hospitals, and private non-profits. Secondary buyers (often the better wedge): the disaster-recovery consultants and grant-management firms (e.g. Hagerty, Tidal Basin, Witt O'Brien's) who currently bill a percentage of the award and could white-label the tooling.
Solved today
Today: expensive PA/disaster-recovery consultants billing hourly or a % of award; internal staff wrestling FEMA Grants Portal + Excel templates; generic grant-management suites (not FEMA-PA-specific). Some large jurisdictions run enterprise emergency-management platforms.
Why current solutions are bad
Consultants are costly and scarce, pricing out small subrecipients; generic tools don't emit FEMA-format schedules or enforce 2 CFR 200 procurement rules; manual assembly causes the exact documentation deficiencies that trigger deobligation. The GAO disbursement gap is evidence the current process leaves money stuck.
Proposed product
A Public Assistance packet assembler: per-cost-category intake wizard (Categories A–G), force-account labor/equipment timekeeping that emits FEMA-format schedules, invoice/receipt OCR mapped to cost lines, a 2 CFR 200 procurement-compliance checker, RFI/deadline tracker, and one-click export formatted for the state's Grants Portal submission. Launch on Florida forms/workflow first, then clone per state (only cover forms/portal specifics differ).
MVP version
Florida-only: intake wizard for the 2–3 highest-volume cost categories (Cat B emergency protective measures, Cat A debris, Cat C–G permanent work), force-account labor/equipment schedule generator matching FEMA templates, invoice OCR-to-cost-line mapping, and a deadline/RFI tracker. Export = FEMA-format PDFs/spreadsheets the user uploads to Grants Portal (no direct portal API integration required for v1).
30-day build
Interview 8–12 FL subrecipient grant coordinators + 2–3 recovery consultants to confirm the packet-assembly pain and current spend; map the exact FEMA PA templates and 2 CFR 200 checkpoints; build the force-account schedule generator and intake wizard skeleton.
60-day build
Ship FL MVP to 3–5 design-partner subrecipients (or one consultant white-labeling it across their client book); add invoice OCR + procurement checker; validate exports against a real Grants Portal submission with a friendly jurisdiction.
90-day revenue plan
Convert design partners to paid; target the consultant/white-label channel for volume (one firm = many subrecipients). Line up state #2 (GA or NC per the awards data) once FL workflow is proven. First revenue plausibly from a consultant seat license or a per-project fee.
Distribution path
Direct outreach to FL county/municipal emergency-management and grants offices (public contacts); state emergency-management association channels/conferences; and — highest-leverage — partnering with existing PA consultants who want to serve smaller clients profitably via software. Content: 'don't lose FEMA money to deobligation' checklists targeting the FL cohort now drawing down.
Pricing hypothesis
Per-project fee ($750–$3,000 per PA project depending on complexity) or per-seat annual subscription ($3,000–$12,000/yr for a jurisdiction), plus white-label licensing to consultants (revenue share or flat per-seat). Anchored well below a 2–5% consulting fee on a six/seven-figure project.
Technical difficulty
Moderate. Form logic, schedule generation, and OCR-to-cost mapping are solo-buildable with AI assistance. Difficulty is domain accuracy (FEMA templates, 2 CFR 200 rules) not engineering scale. No direct government-portal API needed for v1 (export + manual upload sidesteps integration).
Legal / regulatory risk
Low-moderate. Product prepares documentation the subrecipient files themselves — no licensure required to assemble packets (unlike legal/CPA claims work). Must be careful NOT to certify compliance or give legal advice; position as document-preparation tooling with the subrecipient as filer of record. No finder-fee/claims-adjusting licensure implicated because this is grant-drawdown paperwork, not a claim against a settlement fund.
Platform dependency
Low. Exports to a government portal — no private platform owner can deplatform it. Dependency is on FEMA template stability, which changes slowly and predictably.
Founder fit
Very high. Matches the proven FMCSA-ELDT pattern (read a federal mandate → identify forced filers → build the submission/compliance layer → monetize per transaction). Founder's public-records, systems-thinking, and government-portal-integration experience apply directly; fire-service/industrial-ops background gives credibility on force-account labor/equipment logging and emergency-management buyers.
Breakout potential
Strong. 50 near-identical state markets to clone into; recurring demand with every declared disaster (not a one-time event); natural expansion into adjacent FEMA programs (Hazard Mitigation Grant Program, BRIC — both appear in the FEMA releases) and into the audit/appeal workflow. White-label channel compounds via consultants.
Final recommendation
PURSUE — validate fast. This is a textbook founder-fit forced-filer/claimable-money shape with hard, cited money evidence (billions obligated, disbursement demonstrably stuck) and a 50-state replication path. The single biggest unknown is buyer willingness-to-pay-for-software vs. hire-a-consultant; resolve it in 30 days via subrecipient + consultant interviews before heavy build. Lead with the consultant white-label channel to sidestep public procurement friction.
Next action
Interview 8–12 Florida PA subrecipient grant coordinators AND 2–3 disaster-recovery consultants this week to confirm packet-assembly pain, current spend, and appetite for a per-project tool vs. white-label — while pulling the exact FEMA PA templates and 2 CFR 200 checkpoints to scope the FL MVP.