What changed
A Missouri disaster declaration has PA reimbursement funding with a deadline that is 'nearing' (FACT: 'Missouri disaster briefings set as funding deadline nears' — Columbia Daily Tribune), forcing local subrecipients to document incurred costs to draw down federal money before it lapses.
Why now
An active declaration with a stated, nearing deadline creates a compelled filer class RIGHT NOW; FEMA also has adjacent programs open (CAP-SSSE closes 08/11/2026; Pre-Disaster Mitigation closes 07/22/2026 — grants.gov), and reporting on victims 'still waiting for assistance' (DCReport.org) confirms the drawdown process is a live pain point.
Converging signals
(1) Reimbursable public money with a deadline, (2) a defined forced-filer class (municipalities, counties, school districts, nonprofits, utilities that incurred costs), and (3) a portal/forms burden (FEMA Grants Portal + Missouri SEMA) meeting at one point.
Customer pain
Local finance/grants staff must reconstruct damage inventories, assemble project worksheets, and compile procurement + expense records under deadline pressure, with clawback risk if the documentation fails FEMA audit — a slow, error-prone, high-stakes manual slog.
Who pays
Local finance/grants directors and emergency managers at subrecipient entities, and disaster-recovery consultants (white-label) who currently do this billing a percentage of the award.
Solved today
Spreadsheets, generic file folders, overworked in-house staff, or expensive recovery consultants who take a percentage of the reimbursement; FEMA's Grants Portal handles submission but not cost capture, worksheet assembly, or audit-proofing.
Why current solutions are bad
Manual capture misses documentation FEMA later disallows (clawback), consultants are expensive and scarce during a surge, and the free portal assumes the paperwork is already assembled — the hard part is the pre-submission organization, exactly what's unserved.
Proposed product
A cloud tool that ingests cost/expense/procurement records, maps them to PA categories (A–G), assembles a defensible project worksheet + supporting-document package, flags missing audit-critical items, and tracks per-project deadlines/clawback risk. Not a portal bot — a documentation/administration layer feeding the portal.
MVP version
A single-declaration workspace: upload expenses/invoices/procurement docs, tag by PA category and project, an audit-readiness checklist that flags gaps, and a deadline dashboard — output a print/export-ready worksheet + document index. Start with the Missouri declaration as the design partner.
30-day build
Interview 8–12 MO subrecipient finance/grants staff and 2–3 recovery consultants; validate the exact worksheet fields and top disallowance reasons; build the upload + PA-category tagging + audit-checklist core.
60-day build
Ship deadline/clawback-risk alerts and the export package; onboard 2–3 paying pilot entities or one consultant reselling to their book; refine checklist from real FEMA disallowance patterns.
90-day revenue plan
Convert pilots to paid per-project/per-seat subscriptions; sign one disaster-recovery consultant on a white-label seat license; template the product to replicate to the next active declaration state.
Distribution path
Direct outreach to subrecipient finance/emergency-management staff named in disaster briefings; partner with/resell through disaster-recovery consultants and state municipal-league / association channels; content targeting 'FEMA PA documentation' searches.
Pricing hypothesis
$300–$1,500/project or $200–$500/seat/month during an active recovery; white-label consultant license at a higher flat/seat rate — undercuts a 2–5% award-percentage consulting fee.
Technical difficulty
Moderate — document upload, tagging, checklist rules, and export are standard SaaS; the moat is the domain rule set (PA categories, audit-critical documents, disallowance patterns), not the code.
Legal / regulatory risk
Must not misrepresent as FEMA-affiliated; outputs must be audit-defensible (clawback exposure sits with the subrecipient, so frame as documentation assistance, not a compliance guarantee). No licensure required to organize documents.
Platform dependency
Low — submits to/feeds a government system with no platform owner who can deplatform it; risk is FEMA changing forms/portal, which is a maintenance cost, not an existential one.
Founder fit
Very high — public-records + industrial-operations + government-portal integration is the founder's proven FMCSA-shaped pattern (read a mandate → identify forced filers → build the submission/documentation layer → charge per transaction/seat).
Breakout potential
High replication: every federally declared disaster in all 50 states spawns a near-identical subrecipient filer class; the same engine re-skins per state SEMA and per declaration, and expands into hazard-mitigation (CFDA 97.143) and CAP-SSSE reporting.
Final recommendation
BUILD — strong founder-fit, forced-filer demand with a deadline, and 50-state replication; wedge in on the Missouri declaration, sell to under-served small subrecipients and consultants, and treat per-disaster recurrence as the key risk to design against (multi-declaration + mitigation-program expansion).
Next action
Pull the current Missouri declaration's applicant list and briefing schedule, then interview 8–12 subrecipient finance/grants staff to confirm the exact worksheet fields and top FEMA disallowance reasons before building the checklist engine.