What changed
FEMA obligated $1.69B to the State of Michigan for local-government repair/replacement of disaster-damaged facilities (FACT, USAspending award 4494DRMIP00000001). The same award shape recurs at massive scale: PA $2.33B, MA $3.49B, FL $4.94B/$2.42B/$2.25B, PR $35.3B, CA $14.7B/$1.97B, MD $3.29B, NJ $3.25B/$2.30B, LA $3.17B/$2.40B/$2.29B (FACT, cited). Each dollar is a pass-through: the state is grantee, but hundreds of local subrecipients must document damage, procurement, insurance, and progress to the state and FEMA to actually get reimbursed.
Why now
Over $80B in cited open PA obligations across a dozen states means thousands of active permanent-work projects are in the documentation/closeout pipeline right now. FEMA deobligates funds when procurement files fail 2 CFR 200 audits or deadlines lapse — the loss event is ongoing, not future. (The mechanism of deobligation is well-established FEMA practice; the specific deobligation rate is HYPOTHESIS, not in the source text.)
Converging signals
Three signals meet at one point per the forced-filer pattern: (1) appropriated money already obligated (USAspending awards, FACT), (2) a defined filer class — local-government subrecipients rebuilding facilities, (3) a defined submission path — FEMA Grants Portal plus the state EM agency's grant system (e.g., Michigan State Police/EMHSD). Rule + filer class + portal = structural convergence.
Customer pain
A small city public-works or finance office runs a multi-year federal reimbursement project with no dedicated grants staff. They must keep procurement records audit-ready under 2 CFR 200, file quarterly progress reports, request time extensions before deadlines, and assemble closeout packages — across FEMA's portal AND the state's system. Failure means delayed reimbursement or clawback of money already spent. (Pain mechanism is FACT from the mandate structure; intensity/frequency for a given city is INFERENCE — no complaint-thread evidence was provided.)
Who pays
Primary: subrecipient local governments (city/county finance directors, emergency managers, DPW directors) paying per active project. Secondary: the small/mid PA consulting firms serving them, paying per client-project. Notably, FEMA PA reimburses subrecipient management/administrative costs, so the subscription is itself likely a recoverable grant-management cost (HYPOTHESIS — verify DRRA Section 1215 management-cost eligibility before using in sales copy).
Solved today
Big subrecipients hire disaster-recovery consultants (Tetra Tech, Hagerty, Witt O'Brien's/Ambipar) who bill hourly or as a share of the award. Small subrecipients use spreadsheets, shared drives, and the state EM office's patience. Generic grant-management suites (eCivis/Euna, AmpliFund, Neighborly) target grantor agencies and large grantees, not a $2M-culvert town.
Why current solutions are bad
Consultants are proof of spend but priced for big awards — a town with three small projects can't justify them. Spreadsheets don't know FEMA's rules: no deadline engine for time extensions, no 2 CFR 200 procurement checklist tied to each contract, no closeout-package completeness check. The state's portal tracks submissions, not the subrecipient's internal readiness.
Proposed product
Per-project web app: import project (from Grants Portal export or manual entry), get a milestone/deadline timeline (period of performance, quarterly reports, extension request windows), a document checklist per phase (damage documentation, insurance, procurement file with 2 CFR 200 items per contract, force-account labor logs), automated email/SMS deadline alerts, and a one-click closeout binder (PDF/ZIP assembled in FEMA's expected structure). AI assist drafts extension justifications and flags missing procurement elements.
MVP version
Single-state (Michigan, riding DR-4494) read-only tracker: manual project setup, the deadline engine, the 2 CFR 200 procurement checklist, alerts, and the closeout binder generator. No portal write-integration needed at MVP — this is checklist + calendar + document assembly, which sidesteps the hardest integration risk entirely.
30-day build
Build MVP against FEMA PA Program and Policy Guide (PAPPG) requirements. Pull the Michigan DR-4494 applicant list (public briefings/state EMHSD records) to build the exact prospect list of subrecipients. Interview 5-8 Michigan city finance/DPW officials and 2-3 small PA consultants to validate the checklist against real audit findings.
60-day build
Pilot with 3-5 Michigan subrecipients free-for-60-days; convert to paid. Publish a '2 CFR 200 procurement file for FEMA PA' self-audit checklist as lead-gen. Approach MI chapters of GFOA/municipal league and the state EMHSD (they benefit when subrecipients file clean paperwork — potential distribution ally, not customer).
90-day revenue plan
Convert pilots at $99-$299/project/month; land 2-3 consultant firms at multi-project pricing. Replicate prospect-list playbook into one more state from the cited list (FL or LA — chronic disaster volume). Target: 20-40 paying projects by day 120-150.
Distribution path
Direct outreach to a finite, public, named buyer list (declared-disaster applicant lists are public records — founder's public-records strength). Content SEO on high-intent queries ('FEMA PA closeout checklist', 'time extension request'). Partnerships with small PA consultants who resell it into clients. Municipal league newsletters. No ad spend required.
Pricing hypothesis
$99-$299 per active project per month until closeout (small city with 4 projects ≈ $4.8-14K/yr), consultant tier $79/project at volume. Anchor against consultant hourly rates and against the cost of a single deobligated project. Likely reimbursable as a management cost (verify).
Technical difficulty
Low-to-moderate: rules engine + checklist + calendar + document storage + PDF assembly. The domain knowledge (PAPPG, 2 CFR 200) is the real build, and it's public-document work the founder is proven at. No government-portal write access needed for v1, so no integration gatekeeper.
Legal / regulatory risk
Low. Not legal or accounting advice if framed as workflow tooling; standard disclaimers. No PII beyond business contacts. No license required to operate — compliance knowledge is the moat, not a burden on the founder.
Platform dependency
None that can deplatform it. FEMA Grants Portal has no public API (INFERENCE), but v1 doesn't depend on it; document/checklist layer sits outside the portal. Policy risk: FEMA periodically revises the PAPPG, which is maintenance work, not existential risk.
Founder fit
Maximal under the stated thesis: appropriated public money + compelled filer class + defined portal/paperwork = exactly the ELDT-proven shape (read the mandate, find who's forced to file, build the paperwork layer, charge per unit). Bonus: fire-service background gives native credibility with emergency managers, and industrial-ops background matches the public-works buyer's world.
Breakout potential
Every federally declared disaster in every state produces the same filer class on the same rules — 50-state replication with near-zero product change (rules are federal; only state-portal quirks vary). Adjacent expansion: HMGP (mitigation grants), CDBG-DR documentation, then the consultant-facing multi-project tier as the wedge widens.
Final recommendation
PURSUE. This is the founder's exact proven shape with hard appropriated-money evidence: $80B+ of cited open PA obligations, a defined compelled filer class (local-government subrecipients), defined paperwork (PWs, 2 CFR 200 files, quarterly reports, closeout), and a checklist-first MVP that needs no portal integration. Main risks are sales velocity into local government and market timing within each declaration — both testable in 30 days with the public Michigan applicant list before any significant build spend.
Next action
Pull the DR-4494 Michigan applicant/subrecipient list from EMHSD public records this week and book 5 interviews with subrecipient finance/DPW staff; simultaneously verify whether a per-project software subscription is reimbursable as a PA management cost — if yes, that line becomes the entire sales pitch.