What changed
FACT (usaspending.gov): DHS/FEMA has obligated enormous Public Assistance (PA) pass-through grants to state/territory emergency-management agencies — e.g. $21.99B to the Government of the Virgin Islands (award 4340DRVIP), $35.30B to Puerto Rico (4339DRPRP), $14.74B and $1.97B to California OES, $4.94B to Florida DEM, $2.33B to PEMA (Pennsylvania), plus a dozen more $2-17B awards across TX, NY, NJ, LA, MA, NC, WA, MD, MI, OR. Each is a grantee that must pass money to hundreds/thousands of subrecipients who individually document damage and file for reimbursement.
Why now
These awards are active/period-of-performance grants with obligated (already-appropriated) money that subrecipients must document and claim to actually receive; the paperwork burden — Project Worksheets, procurement/cost substantiation, quarterly reports, RFRs — is a live, recurring workflow across dozens of open disaster declarations right now.
Converging signals
Three signals meet at one point: (1) a funded federal mandate (PA program) with obligated dollars; (2) a defined forced-filer class (subrecipient agencies, municipalities, utilities, PNPs and their contractors); (3) a specific government portal (FEMA Grants Portal / Grants Manager + state PA systems) with prescribed forms (PWs, RFRs). This is the founder's primary public-money/forced-filer shape.
Customer pain
INFERENCE (well-documented industry reality, not proven in the provided source text): PA reimbursement is notoriously slow and document-heavy; subrecipients routinely lose or delay reimbursement because of incomplete damage documentation, non-compliant procurement records (2 CFR 200), and disorganized cost backup. Deobligation and clawback on audit are common. Small subrecipients lack dedicated grant staff.
Who pays
Subrecipient organizations that must file: city/county public works, school districts, water/sewer/electric utilities, private non-profits (hospitals, fire companies, houses of worship), and the disaster-recovery consultants/contractors who prepare filings on their behalf. The consultants are the fastest-moving buyer — they run many claims and feel the labor cost directly.
Solved today
INFERENCE: Today it is (a) FEMA's own Grants Portal with manual data entry, (b) big disaster-recovery consulting firms (Hagerty, Tidal Basin, Witt O'Brien's, IEM, ICF) charging a percentage of the award or hourly, or (c) internal grant staff assembling documents in spreadsheets and shared drives. HYPOTHESIS: no cheap self-serve document-assembly tool dominates the small-subrecipient tier.
Why current solutions are bad
Consultants are expensive (percentage-of-award or high hourly) and prioritize large clients; the federal portal is a data-entry endpoint, not a document-assembly/QA tool; spreadsheets produce non-compliant, deobligation-prone packages. Small subrecipients are underserved and overpay or under-recover.
Proposed product
A web SaaS that ingests a subrecipient's damage photos, facility inventories, invoices, contracts and payroll, structures them to FEMA PA categories (A-G), runs a compliance checklist (procurement method, cost reasonableness, insurance offset, EHP flags), and outputs a portal-ready Project Worksheet package and Request-for-Reimbursement bundle with an audit-defensible document index. Not a portal-submission bot at first — a package assembler + compliance QA layer that the filer or their consultant uploads.
MVP version
Single-disaster, single-state pilot: a project workspace where a subrecipient uploads documents, tags them to PA categories and a specific project, gets an automated completeness/compliance checklist, and exports a structured PW + RFR PDF/zip package with a document register. Claude-assisted extraction of amounts/dates/vendors from invoices to pre-fill cost summaries. Manual portal upload by the user.
30-day build
Interview 15-20 disaster-recovery consultants and small subrecipient grant managers (start with PEMA/4506DRPAP subrecipients — reachable, English, in-region for the founder). Nail the exact PW + RFR document schema and the top 10 deobligation triggers. Build the document-tagging + checklist core against FEMA's published PA Program and Policy Guide (PAPPG).
60-day build
Ship the assembler MVP with Claude-assisted invoice/cost extraction and a PAPPG-derived compliance checklist. Onboard 2-3 design-partner consultants who each run multiple claims; price as a paid pilot. Add a shareable audit document-register export.
90-day revenue plan
Convert design partners to paid per-project or per-seat plans; target the consultant channel (each consultant = many projects). First revenue from per-project package fees and consultant seats. Publish a 'FEMA PA deobligation-avoidance checklist' lead magnet for inbound.
Distribution path
Direct outreach to disaster-recovery consulting firms and independent PA grant consultants (they aggregate demand); state emergency-management subrecipient applicant briefings (FEMA runs Applicant Briefings per declaration — a captive audience of forced filers); LinkedIn/industry groups for emergency management; content targeting 'FEMA PA reimbursement' and 'deobligation' search terms.
Pricing hypothesis
Per-project package fee ($300-1,500/project depending on category count) and/or per-seat SaaS for consultants and agencies ($150-500/seat/mo). Avoid percentage-of-award (regulatory/optics risk and closes slower). Consultant seat plans are the durable ARR.
Technical difficulty
Moderate. Document management, tagging, template generation, and LLM-assisted extraction are well within solo AI-assisted build. Hard part is domain fidelity (PAPPG rules, procurement compliance, category logic), not engineering. No portal API integration required for MVP (manual upload), which removes the riskiest technical dependency.
Legal / regulatory risk
Low-moderate. The tool assembles the filer's own documents; it does not itself become a licensed/certified entity. Avoid making guarantees about award outcomes. Percentage-of-award pricing could invite scrutiny — avoid it. No platform deplatforming risk (government portal). Must be careful not to give legal/accounting advice.
Platform dependency
None in the deplatforming sense — outputs go to a government portal no private platform controls. Dependency is on FEMA form/PAPPG stability, which changes slowly and predictably.
Founder fit
Very high. Exact public-money/forced-filer shape the founder targets; he has already shipped a federal-portal filing product (FMCSA ELDT) and monetized per-filing. Fire-service and industrial-operations background maps directly to damage assessment, facilities repair, and procurement documentation. State pass-through (PEMA in-region) is a reachable beachhead with 50-state replication.
Breakout potential
High. Every disaster declaration nationwide recreates the identical filer class and forms; win one state/consultant and replicate across dozens of open declarations and future disasters. Adjacent expansion into Hazard Mitigation (406/HMGP), CDBG-DR, and insurance-claim documentation. Recurring disasters = renewable demand, not one-shot.
Final recommendation
PURSUE, with a consultant-first go-to-market. This is a near-ideal instance of the founder's primary thesis: obligated federal money, a defined forced-filer class, prescribed forms, a specific portal, and proven founder capability in exactly this shape. De-risk by validating small-subrecipient willingness-to-pay early and leading with the consultant channel to shorten the sales cycle. Do not build portal auto-submission until the assembler proves demand.
Next action
Book 15-20 discovery calls this month with PA disaster-recovery consultants and PEMA-region subrecipient grant managers to confirm the exact PW/RFR document schema, top deobligation triggers, and per-project willingness-to-pay before writing product code.