What changed
FACT (cited): On 2026-07-10 FEMA announced $9M+ across 14 Public Assistance projects in Mississippi from the January 2026 winter storm and past disasters, naming each subrecipient and dollar amount: $1.5M University of Mississippi, $1.3M New Albany Light Gas & Water, $1.3M Oxford, $965K Yalobusha County, $863K D'Iberville, $726K Batesville, plus electric power associations and small cities. Each named entity now must document costs, draw down through MEMA, file quarterly reports, and survive closeout/audit. INFERENCE: FEMA issues near-identical releases continuously across all states, so this press-release stream is a perpetually refreshing, pre-qualified lead list.
Why now
The press release timestamp IS the timing signal: an obligation announcement means the subrecipient is entering the drawdown/documentation window right now, which is exactly when they (or the consultants hunting them) need help. Reimbursement structure means the money only actually arrives if the paperwork survives — the pain is front-loaded and dated. Additionally, FEMA PA Direct Administrative Costs (DAC) are reimbursable (stated in input as monetization angle; treat the exact current DAC rules as a to-verify item), meaning the cost of documentation help can itself be paid from the award.
Converging signals
Three signals meet: (1) a continuous federal money flow (FEMA PA, plus the same pass-through shape visible in the cited EPA SRF capitalization grants to Ohio/Michigan/Tennessee and Treasury RESTORE grants to Mississippi DEQ — states receiving federal money that lands on numerous subrecipients); (2) a defined, publicly NAMED filer class with per-entity dollar amounts; (3) a documentation/portal burden (FEMA Grants Portal via MEMA pass-through — portal identity is inference) that small entities are ill-equipped to carry. The mandate + filer class + portal is the founder's proven convergence shape.
Customer pain
A $726K debris-removal reimbursement to Batesville, MS is life-or-money for that city's budget, but the city has no grants staff: they must assemble force-account labor/equipment records, procurement files compliant with federal rules, drawdown requests through the state, quarterly reports, and closeout — and clawback risk persists through audit years later. HYPOTHESIS (not in provided evidence): deobligations at closeout are common enough that fear of clawback drives spend; verify against OIG audit reports before selling on it.
Who pays
Two distinct buyers — keep them separate from the beneficiary. Phase 1 buyer: disaster-recovery/PA consulting firms and regional CPA firms who already sell documentation and closeout services to subrecipients and need to find them the day awards are announced; they pay for a lead/monitoring subscription. Phase 2 buyer: the subrecipient itself (city clerk, utility GM, county administrator) paying for a documentation workspace, potentially DAC-reimbursable. The beneficiary of the $9M is the subrecipient; the phase-1 buyer is the private firm chasing them — that separation is what makes this fast to sell.
Solved today
HYPOTHESIS (industry knowledge, no provided citation): incumbent PA consultants (Hagerty, Tidal Basin, IEM, Witt O'Brien's and many regional firms) staff BD people who manually watch FEMA releases and state EM agencies, and bill subrecipients hourly or as a percentage of recovered funds. Small subrecipients below consultant radar do it with spreadsheets and the county clerk's evenings.
Why current solutions are bad
Manual press-release watching is slow, unstructured, and misses the long tail (a $220K electric power association award is real money to a regional CPA firm but beneath a national consultancy's threshold). FEMA's raw data is public but fragmented: press releases, OpenFEMA datasets, and state pass-through records don't resolve to one entity view with contacts, award history, and timing. Nobody packages 'who just got obligated, this week, in your state, with whom to call.'
Proposed product
Phase 1 (the wedge): a monitoring/lead-data subscription — scrape all FEMA PA press releases + OpenFEMA PA project data nightly, entity-resolve subrecipients, enrich with contacts (clerk/administrator/GM emails from public sources), and deliver a filterable feed + weekly state-sliced alert email to consultants/CPA firms. Phase 2: a lightweight documentation/closeout workspace (cost capture, procurement-file checklist, drawdown/quarterly-report tracker) sold per-project to subrecipients or white-labeled to the same consultants. Phase 2 is where durable value lives — the adversarial check demands value beyond discovery, and discovery-only is the copyable part.
MVP version
A scraper for FEMA press releases + OpenFEMA PA (public assistance funded projects) API, a Postgres entity-resolution layer, and an Airtable-grade web feed with email alerts, seeded with 90 days of history. Founder already runs exactly this ingestion architecture in the Convergence Engine — the MVP is substantially a repurpose of existing code. 2-3 weeks solo.
30-day build
Build scraper + entity resolution + alert feed; backfill 12 months of PA obligations nationally; hand-build a list of 100 PA consulting and government-audit CPA firms; send 25 of them a free state-specific sample report ('every subrecipient obligated in MS/AL/LA in the last 60 days, with amounts and contacts') as the demand test.
60-day build
Convert sample recipients to paid monthly subscriptions; iterate on filters (state, award size, category of work); add state pass-through agency data for 2-3 states; interview 5 subrecipients from the feed about documentation pain to spec phase 2.
90-day revenue plan
Target 8-15 firm subscriptions at $199-$499/mo (revenue in the $2-6K MRR range) plus 1-2 white-label/custom-territory deals; begin phase-2 pilot with one consultant's client as the design partner, priced per project.
Distribution path
Direct outreach to a small, enumerable, publicly listable buyer universe (PA consultants, EM-focused CPA firms, state municipal leagues' associate members) using the product itself as the pitch — send them their own market's fresh leads. This is demonstrated-value selling, the founder's stated strength; no ad spend, no marketplace.
Pricing hypothesis
Lead/monitoring subscription $199-$499/mo per firm per region, national tier ~$999/mo; phase-2 documentation workspace $500-$2,500 per project or per-seat, positioned against consultant hourly rates and (to subrecipients) as DAC-reimbursable. Anchor against the consultants' percentage-of-award fees, not against SaaS comparables.
Technical difficulty
Low-moderate and squarely in-skill: scraping, entity resolution, public-records enrichment, alerting — the founder's existing Convergence Engine already does the hard parts. Phase 2 workspace is a standard CRUD app plus domain-correct checklists; the domain research (PA policy guide, procurement rules) is the real work, and his fire-service background gives unusual credibility in emergency-management rooms.
Legal / regulatory risk
Low for phase 1: aggregating public government data for B2B lead-gen has no licensure or finder-fee issue (fees here are for software/data, not contingent recovery of claims). CAN-SPAM hygiene on outreach. Phase 2: do not drift into contingent-fee 'we get you money' territory or grant-writing representations — sell documentation tooling and stay out of appeals/advocacy, which is where consultant-of-record and (in some states) licensure questions live.
Platform dependency
Sources are government publications (FEMA press releases, OpenFEMA API) — no platform owner can deplatform it; OpenFEMA is an official open-data API. Risk is format churn in press releases, mitigated by the structured OpenFEMA dataset as the backbone.
Founder fit
Near-maximal on the stated thesis: reimbursable public money + a named class who must document/file + a pass-through portal, monetized per subscription/per project — the same shape as his shipped FMCSA ELDT product, minus the portal-submission layer (FEMA Grants Portal automation is a later, riskier step). Recycling/scrap and fire-service operational background overlaps culturally with debris-removal and emergency-protective-measures work, which is most of this batch.
Breakout potential
The subrecipient graph generalizes: the same entity-resolution + monitoring engine extends to HUD CDBG-DR, EPA SRF subrecipients (see cited Ohio/Michigan capitalization grants that explicitly fund 'numerous subrecipients'), Treasury RESTORE, and state-declared disasters — a 'who just got public money and now owes paperwork' data company across programs, with the documentation workspace as the high-margin layer.
Final recommendation
PURSUE as a fast, cheap wedge test. This is the founder's exact thesis shape with FACT-grade money evidence ($9M named to a defined subrecipient class, continuously replenished nationwide), a two-sided monetization path, and an MVP that is largely a repurpose of infrastructure he already runs. The idea survives the adversarial checks (recurring not one-time, no licensure, no fee caps on software/data, claims are $200K-$1.5M not tiny) with one honest wound: the discovery layer alone is copyable. Gate the go/no-go on the 30-day free-sample test with consultants; commit to phase 2 only if ≥5 firms convert or explicitly demand the documentation layer.
Next action
Pull the OpenFEMA Public Assistance Funded Projects dataset plus the last 90 days of FEMA press releases, entity-resolve into a subrecipient table for MS/AL/LA, and email the resulting one-page 'fresh obligations' sample to 25 named PA consulting and government-audit CPA firms within 14 days.