What changed
FACT (cited): Missouri SEMA is holding applicant info sessions for FEMA Public Assistance for the late-April storms, meaning a PA application window is live right now. The RPA (Request for Public Assistance) is typically due within 30 days of declaration, and applicants then face months of damage inventories, project worksheets, and cost documentation.
Why now
The window is open and time-boxed: applicants who miss the RPA deadline forfeit reimbursement entirely, and those who file badly face de-obligation/clawbacks in later audits. Info sessions are the state telling us applicants are confused enough to need briefings — that is the demand signal, published by the pass-through agency itself.
Converging signals
Three signals meet at one point: (1) a declared disaster creating a defined filer class (MO local governments, counties, eligible nonprofits, utilities), (2) a hard federal paperwork regime (RPA, damage inventory, project worksheets in FEMA Grants Portal), and (3) a live state pass-through process (SEMA sessions) proving the filers are being mobilized now. This is the funded-mandate shape the founder's thesis targets, in its reimbursement variant.
Customer pain
A small city public-works or county EM director must, on top of storm recovery, file an RPA in ~30 days, then assemble force-account labor/equipment logs, contracts, photos, and cost records to FEMA's evidentiary standard. Small applicants have no grants staff; errors surface years later as clawbacks. HYPOTHESIS: the pain is worst for applicants too small to attract the big PA consultants.
Who pays
Primary buyer: the applicant jurisdiction (city, county, PNP, rural utility) — and critically, FEMA reimburses applicant management/administrative costs (DAC and management-cost provisions), so the toolkit fee can be structured to be substantially reimbursable, collapsing price resistance. Secondary buyer: regional engineering/PA consulting firms who chase these events and would white-label an intake/inventory tool to serve more small applicants per staffer.
Solved today
Big applicants hire PA consultants (Hagerty, Tidal Basin, Witt O'Brien's/Ambipar, IEM, ICF) who bill hourly or as a share of the award — proof of existing spend. Small applicants rely on free SEMA briefings, FEMA's assigned Program Delivery Managers, and spreadsheets/shoeboxes of receipts.
Why current solutions are bad
Consultants are uneconomical below a certain award size, so small jurisdictions get the free path — which is generic guidance, not a system that captures their specific labor logs, photos, and costs in the format FEMA accepts. The result is missed deadlines, under-claimed force-account costs, and audit exposure years later.
Proposed product
A guided PA applicant workspace sold per jurisdiction per event: (1) deadline tracker keyed to the declaration (RPA, exploratory call, damage inventory, project deadlines), (2) damage-inventory builder with photo/geotag capture and FEMA category (A–G) mapping, (3) force-account labor/equipment cost logs matching FEMA schedules, (4) document checklist and export package shaped for Grants Portal upload and future audit. Not a portal bot initially — a preparation/documentation layer, which avoids Grants Portal integration risk while matching the founder's proven read-the-mandate→build-the-filing-layer pattern.
MVP version
A web app (founder's stack: FastAPI + Postgres) with the MO event pre-loaded: deadline calendar, guided damage-inventory forms, cost-log templates, and a one-click 'applicant binder' PDF/ZIP export. Plus a free RPA-deadline email alert as the lead magnet. Buildable AI-assisted in 2–3 weeks.
30-day build
Ship MVP; attend/monitor the SEMA info sessions; pull the declared-county list and scrape/compile the applicant universe (public records — founder strength); email/call EM directors and city clerks in declared counties with the free deadline alert; convert to paid workspaces. Interview 5 PA consultants about white-label.
60-day build
Harden the cost-documentation module with a real applicant's data; add FEMA category templates; land 5–15 paid jurisdictions; sign 1 consultant white-label pilot; document the DAC-reimbursability argument as sales collateral (with a disclaimer it's the applicant's determination).
90-day revenue plan
Target 10–25 jurisdictions at $1,500–$3,500/event plus 1–2 consultant white-labels at $10k+; replicate playbook to the next declared disaster in any state — declarations recur monthly nationwide, so the MO window is the beachhead, not the business.
Distribution path
Direct outreach to the finite, public, named filer class (declared counties' EM directors, city clerks, PNP administrators); presence around SEMA sessions; SEO on 'FEMA PA deadline Missouri'; white-label through PA consultants and municipal leagues/associations of counties. No ad spend needed — the buyer list is a public record.
Pricing hypothesis
$1,500–$3,500 per jurisdiction per event (small enough for purchase-card/no-bid thresholds), consultant white-label at $10k–$25k/event or per-seat. Framed against a 2–5% consultant fee and against the DAC reimbursement that can offset it.
Technical difficulty
Low-moderate: forms, checklists, file handling, PDF export, deadline logic. No Grants Portal API exists publicly — deliberately avoid portal automation in v1, so difficulty stays solo-feasible. Hardest part is encoding PA program rules correctly (PAPPG), which is documentation work the founder is suited to.
Legal / regulatory risk
Modest and manageable: must not practice as an unlicensed grant 'agent' making eligibility representations — position as software/templates plus the applicant's own filings. No finder-fee structure (flat fees), so fee-cap rules around claims don't bite. Federal procurement rules don't apply to a sub-$5k software purchase in most jurisdictions. HYPOTHESIS: DAC reimbursability of the fee needs verification per PAPPG before marketing it as such.
Platform dependency
None that can deplatform: FEMA Grants Portal is the destination, not a platform owner with approval power; v1 doesn't even integrate with it.
Founder fit
Near-maximal: this is the FMCSA ELDT pattern (mandate → defined filer class → submission burden → per-transaction fee) applied to reimbursement money, plus his fire-service background gives instant credibility with emergency managers — the actual buyers. Systems thinking, public records, and low-budget direct outreach are exactly the required skills.
Breakout potential
High: PA is a permanent, recurring, nationwide program (every declared disaster creates a fresh cohort of forced filers with the same paperwork), and the same toolkit extends to FEMA mitigation grants (HMGP/BRIC-successor) and state-level disaster programs. The white-label channel to consultants scales without headcount.
Final recommendation
PURSUE. This is the founder's proven shape — a funded mandate with a defined, publicly enumerable filer class, a hard deadline, existing spend (consultants), and a reimbursable price point — with a recurring nationwide replication path. Score-limiting caveats: only one source (a news item, no award figure), and the free-support path must be beaten on documentation quality, not discovery.
Next action
Today: verify the declaration number and RPA deadline on fema.gov/disaster and SEMA's site, register for the next SEMA info session, and pull the declared-county applicant list from public records to size the reachable buyer universe before writing any code.