What changed
FACT (MLive headline, cited): a federal major disaster declaration was approved for Michigan after spring floods and storms, activating FEMA assistance for the designated counties. This starts the Public Assistance clock: Requests for Public Assistance are due ~30 days from county designation (standard FEMA rule — INFERENCE until verified against the specific FEMA-DR notice), followed by damage inventories, project worksheets, force-account labor records, procurement-compliance documentation, insurance documentation, and quarterly reporting through closeout, all flowing through FEMA Grants Portal with Michigan State Police EMHSD as the pass-through recipient.
Why now
The filing window is open RIGHT NOW and is short. Every eligible applicant must submit an RPA within roughly 30 days or forfeit reimbursement; documentation begun late (especially force-account labor and emergency procurement records) is the classic cause of deobligation at audit years later. The deadline sets the sales timeline for the founder — no demand-generation needed, only reaching a publicly enumerable list of designated-county applicants.
Converging signals
Three signals meet at one point: (1) a live mandate — the Michigan declaration (FACT: news headline); (2) a defined filer class — local governments, counties, school districts, eligible private nonprofits in designated counties, plus EMHSD as recipient; (3) a portal and paperwork regime — FEMA Grants Portal / state pass-through forms with hard deadlines. Prior-cycle spend proves the money is real: USAspending shows a $1.69B DHS grant to the State of Michigan for repair/replacement of disaster-damaged facilities under a previous Michigan declaration (DR-4494), and multi-billion PA awards to Florida ($1.53B, $2.89B) and Puerto Rico ($1.80B) prove the program recurs at scale nationwide (all FACT: cited USAspending awards).
Customer pain
A township clerk or school-district finance director in a designated county has never (or rarely) done FEMA PA. They must file an RPA in ~30 days, then produce cost documentation to federal standard: force-account labor/equipment logs, contracts compliant with 2 CFR 200 procurement, insurance offsets, photos, and quarterly reports through a closeout that runs years. Under-documentation means reimbursement is reduced or clawed back at audit. The free help (FEMA-assigned Program Delivery Managers, EMHSD applicant briefings) explains the rules but does not build the records — the applicant still has to capture, organize, and retain everything correctly. HYPOTHESIS: the acute pain concentrates in small subrecipients too small for the big consultants to court.
Who pays
Beneficiary and buyer largely coincide here, which is unusual and good: the subrecipient (local government, school district, PNP) receives the reimbursement AND can pay for the tool, because FEMA Public Assistance reimburses Direct Administrative Costs — grant-management tooling and documentation labor tied to specific projects is a recoverable cost category. Second buyer: disaster-recovery consultants and grant writers serving multiple applicants, who would white-label a per-applicant workspace. Third (later) buyer: anyone paying for a declaration-alert data feed. Small subrecipient purchases at $1.5k–$5k typically fall under micro-purchase/small-purchase thresholds — no RFP, a credit card or simple PO (HYPOTHESIS on thresholds per entity; verify Michigan local purchasing policies).
Solved today
Large applicants hire disaster consultants (Hagerty, Tidal Basin, Witt O'Brien's, IEM) who bill hourly or as a share of managed grant value — proof of existing spend, not a reason to fold. Mid-size use spreadsheets plus the free FEMA PDMG guidance. Small townships and PNPs mostly improvise: paper timesheets, photos on phones, invoices in email — and get haircut at reconciliation. Niche software exists (e.g., Juvare's Crisis Track for damage assessment) but is agency-oriented and underpenetrated at the township/school-district tier (HYPOTHESIS on penetration).
Why current solutions are bad
Consultants are uneconomical below ~$1M in claims; the free path explains rules but produces no artifacts; spreadsheets fail 2 CFR 200 audit standards years later when memories and staff have turned over. Nothing cheap exists that (a) alerts each applicant to ITS deadlines by county designation date, (b) walks non-experts through force-account and procurement documentation as costs are incurred, and (c) assembles the closeout-ready package.
Proposed product
'PA Filing Kit' — a lightweight web app sold per declaration per applicant: (1) county-designation-aware deadline tracker (RPA, exploratory call, damage inventory, quarterly reports) with email/SMS alerts; (2) guided cost-capture: mobile-friendly force-account labor/equipment logs, procurement-compliance checklists, photo/receipt vault, insurance-offset worksheet — mapped to project-worksheet categories; (3) export: a clean, auditor-ready document package per project. Deliberately DOCUMENT-SIDE: it does not submit into Grants Portal (no public API; keep humans on the submit button) and does not advise on appeals (stays clear of practice-of-law — preparation/organization only, per the stated legal constraint). Secondary product: a declaration-alert feed (new FEMA-DR designations → named applicant lists) sold to consultants.
MVP version
Two weeks of build: static deadline-calculator + alert engine keyed to the actual Michigan DR county-designation dates, plus templated cost-capture forms (force-account labor, equipment, materials, contracts) with a photo/receipt upload vault and a one-click ZIP/PDF export. Seed the prospect list from the declaration's designated counties — every eligible applicant is publicly enumerable via county websites and EMHSD applicant-briefing rosters.
30-day build
Verify the actual FEMA-DR number, designated counties, and RPA deadline from the FEMA declaration notice (the 30-day figure is inference until then). Build the MVP. Attend/monitor EMHSD applicant briefings (public). Direct outreach — email and phone — to clerks, finance directors, and emergency managers in designated counties, and to every PNP category (utilities, private schools, nonprofits) that qualifies. Offer the kit at a launch price with a 'your cost is reimbursable as DAC' one-pager. Parallel: contact 10 regional disaster consultants and grant writers about white-label seats.
60-day build
Convert briefing-window urgency into 10–30 paying applicant accounts. Add quarterly-report reminders and the project-worksheet package export. Close 1–3 consultant white-label deals (multi-applicant pricing). Start the declaration-alert feed as a simple monitored product for consultants — FEMA declarations are public and structured.
90-day revenue plan
Target: $15k–$50k. 20 applicants × $1.5k–$2.5k per-declaration subscriptions plus 2 consultant white-labels at $5k–$10k. Then replicate: every new major disaster declaration in any state is the same product with a new county list — the one-time-event risk for THIS declaration is answered by the recurrence of the program itself (Florida and Puerto Rico multi-billion awards cited as evidence the pipeline never stops).
Distribution path
The buyer list is public and finite: designated counties → their local governments, school districts, and eligible PNPs. Channels: EMHSD applicant briefings, Michigan Municipal League and Michigan Townships Association newsletters/associations, direct outreach to clerks, and consultant white-label. The founder's fire-service background is real credibility with emergency managers — he speaks the language of after-action documentation and mutual aid, which shortens trust with exactly this buyer (FACT: founder profile).
Pricing hypothesis
$1,500–$2,500 per applicant per declaration (framed as reimbursable DAC), or $99–$199/mo ongoing 'disaster-ready' subscription between events; consultant white-label $5k–$15k per declaration for multi-applicant workspaces; declaration-alert feed $200–$500/mo. Anchor against consultant alternatives billing tens of thousands.
Technical difficulty
Low-to-moderate: forms, alerts, file vault, PDF/ZIP export, county-date logic. No Grants Portal integration attempted (no public API; submission stays human). The hard part is domain fidelity — encoding PA documentation categories and 2 CFR 200 procurement checklists correctly; FEMA's PA Program and Policy Guide is public and makes this a reading problem, not an access problem.
Legal / regulatory risk
Low if scope is held: software and documentation preparation carry no licensure requirement (FACT per input's legal-constraints line). The bright line is appeals representation and eligibility advice, which edge toward practice of law — the product organizes and prepares, the applicant or their counsel decides and submits. Avoid the household/IA side entirely: it adds PII exposure and vulnerable-claimant dynamics for tiny per-claim value; PA subrecipients are institutions.
Platform dependency
None in the deplatforming sense — the counterparty is a government program. Real dependency is programmatic: FEMA PA rules change (e.g., simplified procedures thresholds), which is maintenance, not existential.
Founder fit
Near-maximal. This is the founder's proven FMCSA shape — read the mandate, identify the compelled filer class, build the paperwork layer, charge per filing — pointed at a live 30-day window. His fire-service background gives unusual credibility with emergency managers, and his public-records/automation strengths cover the declaration-alert feed. The applicable lesson ('government-portal mandate opportunities fit this founder best', confidence 0.79) supports this, and fresh evidence here is stronger than the prior.
Breakout potential
High within the niche: the product is declaration-agnostic. Every major disaster declaration in 50 states re-runs the playbook with a fresh forced-buyer list; the alert feed compounds into the prospecting engine. Ceiling: this stays a niche multi-hundred-account business unless it grows into ongoing grant-management (closeout runs 3–7 years, creating natural retention).
Final recommendation
PURSUE — this is the founder's proven pattern with a live deadline, hard-cited prior spend ($1.69B to Michigan alone under a comparable declaration), a publicly enumerable forced-buyer list, and a buyer whose tool cost is itself reimbursable. Hold two disciplines: ship the document-artifact layer (not just alerts), and sell to PA subrecipients and consultants only — skip the household IA side. Verify the actual DR notice and deadlines on day one.
Next action
Today: pull the FEMA declaration page for this Michigan DR (declared counties, PA/IA designations, exact RPA deadline), download the EMHSD applicant-briefing schedule, and build the designated-county applicant prospect list. Ship the deadline-alert + cost-capture MVP within 14 days and start outreach before the RPA window closes.