What changed
FEMA awarded over $7.7M in Public Assistance grants to the City of St. Louis, its school district, and local churches for tornado recovery (FACT: Business Journals headline, cited). Each award creates an immediate, non-optional documentation burden: force-account labor/equipment logs, procurement records compliant with 2 CFR 200, insurance offsets, quarterly reports, and a closeout package — with deobligation (clawback) as the penalty for doing it badly.
Why now
The awards are already obligated, so the paperwork clock is running now. Private-nonprofit churches and small districts have no grants staff, and the PA lifecycle runs 3-7 years per project — a subscription window that starts the day of obligation. Critically, Direct Administrative Costs are themselves FEMA-reimbursable (up to ~5%), so the buyer can pay for the tool with grant money rather than their own budget (FACT per program structure as stated in input; exact DAC treatment should be verified against current PAPPG before quoting it in sales copy — marked hypothesis until verified).
Converging signals
Three signals meet at one point: (1) a named, funded mandate ($7.7M obligated in one metro, FEMA PA ~$10B+/yr nationally — the national figure is inference); (2) a defined compelled-filer class (subrecipients: city, school district, PNP churches); (3) a specific portal and pass-through (FEMA Grants Portal + Missouri SEMA). Adjacent retrieved awards (EPA CWSRF/DWSRF capitalization grants of $49M-$138M flowing to state agencies and then to numerous subrecipients) confirm the same structural pattern — federal money landing on states and creating subrecipient reporting burdens — though they are a different program and cited only as shape evidence, not direct demand.
Customer pain
A church that just received a FEMA PA award has never heard of 2 CFR 200, doesn't know force-account labor must be logged contemporaneously, and will discover at closeout — years later — that undocumented costs get deobligated. GAO and DHS OIG audits repeatedly find deobligations driven by documentation and procurement noncompliance (HYPOTHESIS: consistent with program reputation, not evidenced in the provided input). The pain is not filling a form; it is surviving an audit 3-7 years after the storm.
Who pays
The subrecipient itself (church, small district, small municipality) — and effectively FEMA pays, because documentation/management costs are reimbursable as DAC. Secondary buyers: the state pass-through (SEMA) buying seats for its applicant pool, and small disaster-recovery consultants who want a white-label tool instead of spreadsheets. Beneficiary and buyer are the same party here, which is the clean case.
Solved today
Large applicants hire disaster-recovery consultancies (Hagerty, Tidal Basin, Witt O'Brien's) billing hourly or a percentage of the award; small subrecipients use spreadsheets, paper timesheets, and whatever the SEMA applicant briefing handed them, or hire nothing and eat the deobligation. Generic grants-management SaaS (AmpliFund, eCivis) targets grantor agencies and large grantees, not a $400k-project church.
Why current solutions are bad
Consultants are uneconomical below roughly $1M in awards, so the long tail of small subrecipients — exactly the class named in this award — is unserved. Spreadsheets fail the contemporaneous-documentation standard, and the free FEMA/SEMA guidance explains the rules but does nothing to capture the evidence. The failure is silent until closeout, when it becomes a clawback.
Proposed product
A PA-project workspace per subrecipient: mobile-first force-account labor/equipment logging (photo + timestamp evidence capture), procurement-compliance checklists keyed to 2 CFR 200 thresholds with document upload gates, insurance-offset tracking, quarterly-report generation matching Grants Portal fields, and a closeout-package assembler that flags gaps years before FEMA does. AI layer: extract costs from invoices/timesheets and map them to eligible PA cost categories, with every claim traceable to a source document.
MVP version
For one disaster (the St. Louis DR): a guided web app covering force-account labor logs, contractor invoice capture, a 2 CFR 200 procurement checklist, and an exportable quarterly-report/closeout binder (PDF + spreadsheet matching Grants Portal expectations). No portal integration needed at MVP — the deliverable is the audit-ready evidence package. Build with founder's existing FastAPI/Postgres/Claude stack in 4-6 weeks.
30-day build
Verify DAC reimbursability language in the current PAPPG (this is the killer sales line and must be exact). Pull the public FEMA declaration and applicant data for the Missouri DR; attend/obtain SEMA applicant-briefing materials. Interview 5-8 small subrecipients (churches via their denominational networks, the school district's finance office). Ship the MVP evidence-capture and checklist flow.
60-day build
Pilot with 2-3 St. Louis-area PNP subrecipients free-or-cheap in exchange for testimonial and a worked example of a clean quarterly report. Build the closeout-binder generator. Approach 2-3 small disaster-recovery consultants about white-label use — they extend reach without founder doing relationship sales.
90-day revenue plan
Convert pilots to paid ($1,500-$5,000 per project per year depending on award size, framed as 'reimbursable as DAC and a fraction of the 5% cap'). Replicate outreach to the next 2-3 federally declared disasters using the public declaration/award lists — the go-to-market is itself a public-records automation, the founder's strength.
Distribution path
Public records are the channel: every declaration, applicant briefing, and obligated project is published. Direct outreach to named subrecipients within days of obligation; SEMA/state EM agencies as amplifiers (they want fewer failed closeouts); denominational and municipal-league newsletters; white-label through small consultants. No ad spend, no marketplace, no platform gatekeeper.
Pricing hypothesis
Per-project annual subscription tiered by award size ($1,500 small PNP project → $5,000+ municipal project), or per-seat for consultants. Anchor against the 2 CFR 200 alternative: a consultant's hourly bill or a 5-6 figure deobligation. The DAC-reimbursable framing converts price objections into paperwork.
Technical difficulty
Low-to-moderate for the founder: forms, document capture, checklist logic, PDF generation, AI invoice extraction — all inside his demonstrated stack. The hard part is domain fidelity (PAPPG eligibility rules, procurement thresholds), which is learnable from public FEMA policy documents and matters more than code.
Legal / regulatory risk
Low for documentation software. Two real lines to hold: do not drift into representing appeals or first-level arbitration (stay a documentation tool, or partner with counsel), and do not give eligibility 'determinations' — frame outputs as documentation against FEMA's published criteria. One structural risk worth naming: 2026 federal discussion of FEMA reform/devolving disaster cost-share to states could reshape the program (HYPOTHESIS) — though devolution to 50 state processes would arguably increase paperwork fragmentation and help this product.
Platform dependency
None in the deplatforming sense — the 'platform' is a federal grant program. Program-structure risk (FEMA policy changes) exists but there is no gatekeeper who can revoke access; the MVP doesn't even require portal integration.
Founder fit
Near-maximal. This is the FMCSA ELDT shape transposed: a federal program compels a defined class to document and submit, and the founder builds the compliance layer monetized per project. Bonus fits: fire-service background gives genuine credibility with emergency-management buyers and the vocabulary of disaster response; public-records automation is the distribution engine; recycling/industrial ops background maps to force-account equipment/labor logging. The primary-thesis lesson (confidence 0.79) applies directly.
Breakout potential
FEMA PA obligates ~$10B+/yr across thousands of subrecipients in every state (inference); expansion paths include HMGP/BRIC mitigation grants, CDBG-DR documentation, and the state-disaster-program long tail. Each new declaration is a new cohort with the same forced deadline. A wedge product for small PNPs can grow into the system of record consultants standardize on.
Final recommendation
PURSUE as a top-tier candidate. This is the founder's proven pattern (compelled filer class + government system + per-transaction monetization) applied to a recurring ~$10B/yr program with an unserved small-subrecipient tail, a self-funding price objection (DAC reimbursability), and a public-records-driven distribution channel. The 3-7 year project lifecycle gives recurring revenue per customer, and the founder's capital covers the 60-90 day validation ramp. Gate the build on two verifications: exact current PAPPG DAC language, and 2-3 St. Louis pilot conversations proving small PNPs will pay.
Next action
Within 7 days: (1) verify DAC reimbursability wording in the current FEMA PAPPG; (2) pull the Missouri disaster declaration's public applicant/obligation list; (3) contact the awarded churches and school district (they are named in the cited article) for problem interviews before building anything.