What changed
FACT (per FEMA press release, 2026-07-10): FEMA approved $30M+ across 13 South Carolina projects — $29.7M Public Assistance including $8.1M to Roper Hospital (a private nonprofit) for COVID emergency protective measures, $13.8M+ across three SCDOT projects, $4.3M to Greenville County for debris removal, $1.2M to Aiken Electric Cooperative, plus $140K HMGP and $160K BRIC. The notable structural fact: private-sector entities (a hospital, an electric co-op) sit in the same award batch as governments, and every one of these obligations now carries a substantiation, procurement-compliance, and closeout burden.
Why now
Every PA obligation starts a paperwork clock: cost substantiation, procurement documentation under 2 CFR 200, quarterly reporting through the SCEMD pass-through, potential appeals, and closeout. The demand_evidence shows this is not a one-state blip — COVID-era PA reimbursement awards alone include $2.35B (North Carolina), $2.89B + $1.53B (Florida), $3.57B (Louisiana), $1.80B (Georgia) — all explicitly covering 'certain private non-profit organizations.' Closeout and audit exposure on those dollars is happening NOW, and de-obligation risk (FEMA clawing money back for bad documentation) is the claimant's nightmare. HYPOTHESIS: national PA obligations run to billions/yr on an ongoing basis — the source batch supports recurrence but the national figure is inference from the cited multi-billion state awards.
Converging signals
(1) A fresh $30M obligation batch naming specific subrecipients including private nonprofits [FEMA press release]; (2) multi-billion-dollar PA reimbursement awards across at least five states with the same private-nonprofit claimant class [USAspending]; (3) the founder's proven FMCSA-portal pattern: a government process compels a defined party to document/submit, and the software layer monetizes per transaction. The rule (Stafford Act PA + 2 CFR 200), the filer class (subrecipients), and the portal (FEMA Grants Portal via state pass-through — inference, standard PA mechanics) are three signals at one point.
Customer pain
A hospital that just got $8.1M obligated must now defend every invoice, payroll record, and procurement decision through closeout or risk de-obligation. Counties running debris-removal claims must reconcile load tickets against monitoring records. Co-ops must document force-account labor and mutual-aid costs. None of these entities does this often enough to have in-house muscle; they either hire consultants at hourly/percentage rates or under-document and eat clawbacks. Separately, PA consultants have no timely, entity-resolved feed of WHO just got obligated — press releases and OpenFEMA data are fragmented and lag.
Who pays
Two distinct buyers (distinguish beneficiary from buyer): PRIMARY WEDGE — disaster-recovery consulting firms pay for an obligation-triggered lead feed (new awards, entity-resolved, with subrecipient type, program, amount, disaster number, contact enrichment). SECONDARY — private-nonprofit subrecipients (hospitals, co-ops, universities, utilities) pay fixed fees for documentation/closeout packages; governments can treat this as Direct Administrative Cost (DAC), which FEMA reimburses — the tool's cost is itself claimable (FACT that DAC/management costs are reimbursable under PA; the specific $7.3M SCDOT 'management costs' award in the source demonstrates management costs get funded).
Solved today
Large consultancies (Hagerty, Tidal Basin, Witt O'Brien's, ICF) staff PA claims on hourly or percentage arrangements; smaller subrecipients use spreadsheets plus the free FEMA Grants Portal; consultants find clients via relationships and by manually watching press releases. OpenFEMA publishes obligation data free but raw, lagged, and not entity-resolved or contact-enriched.
Why current solutions are bad
Consulting fees consume a meaningful slice of awards and don't scale down to a $1.2M co-op claim. The free Grants Portal is a submission system, not a documentation-assembly or audit-defense tool. Raw OpenFEMA data requires engineering effort no regional consulting shop will spend. Nobody alerts a consultant same-day that Roper Hospital just had $8.1M obligated — the founder can.
Proposed product
Phase 1 (data product): 'PA Radar' — a monitored pipeline over OpenFEMA PA-funded-projects data + FEMA press releases + state EMD announcements, entity-resolved (EIN/UEI matching), classified by subrecipient type (PNP hospital, co-op, county, DOT), with alerting and contact enrichment. Sold as a monthly subscription to PA/grant consultants and restoration contractors. Phase 2 (documentation layer): AI-assisted claim-package builder — ingest invoices, payroll, load tickets, procurement records; map them to PA cost categories; generate substantiation binders and closeout checklists formatted for Grants Portal submission. Fixed per-project fee.
MVP version
OpenFEMA ingestion + entity resolution + daily email/Slack alert digest with a filterable web table (founder already runs exactly this ingestion/dedup/alert architecture in the Convergence Engine). 2-4 weeks of AI-assisted build. Validate by giving 5 PA consultants a free month and asking what an obligation-day lead is worth.
30-day build
Build PA Radar MVP on OpenFEMA datasets (PublicAssistanceFundedProjectsDetails updates roughly daily); backfill Helene + 2024-2025 disasters; hand-build the SC/NC/FL/GA target list of PNP subrecipients from the cited awards; cold-outreach 25 PA consulting firms with a sample alert ('here are the 13 SC projects obligated July 10, with contacts').
60-day build
Convert 3-5 consultants to paid ($300-600/mo). Interview their delivery pain to spec the documentation layer. Pilot one fixed-fee closeout package with a small PNP (a co-op or rural hospital) sourced from the radar itself — the founder's fire-service and emergency-management credibility is the door-opener.
90-day revenue plan
Target: $2-5K MRR from 5-10 consultant/contractor seats plus one $5-15K documentation engagement. Expand feed to HMGP/BRIC award tracking (both present in the source batch) as an upsell.
Distribution path
Direct outreach to a finite, listable market: PA consultants, disaster-restoration contractors, and state municipal/co-op/hospital associations. The radar itself generates the prospect list (every new obligation names a prospect). Founder's fire-service background gives authentic standing in emergency-management communities (IAEM, state EMD conferences). No ad spend required.
Pricing hypothesis
Lead feed: $300-600/mo per firm (undercuts the cost of one BD hour per week). Documentation packages: $5K-25K fixed per project scaled to award size — deliberately far below the 2-5% consulting take on a multi-million-dollar claim; for government subrecipients, positioned as DAC-reimbursable so net cost approaches zero.
Technical difficulty
Low-to-moderate for Phase 1: public API ingestion, entity resolution, alerting — squarely within the founder's demonstrated stack. Phase 2 is harder: PA cost-category mapping and 2 CFR 200 procurement rules require real domain study, but it's rules-encoding, not novel tech. No portal write-access needed initially (Grants Portal submission is done by the subrecipient; the product prepares the package).
Legal / regulatory risk
Moderate and manageable. Key constraint: contingent-fee arrangements are disfavored/problematic in federal grant work — price fixed-fee or subscription, never a percentage of recovery. Not insurance adjusting (PA is a federal grant, not an insurance claim), so public-adjuster licensure should not apply — HYPOTHESIS to verify per state before selling documentation services in SC/FL/LA. No PII beyond business contact data in Phase 1.
Platform dependency
OpenFEMA is a public-data commitment with published datasets; no platform owner can deplatform a tool built on it. Grants Portal access in Phase 2 is the customer's own credential.
Founder fit
Very high. This is the FMCSA pattern generalized: government process compels a defined party to document and submit; founder builds the paperwork layer and charges per transaction. Bonus alignments: fire-service background = native credibility with emergency managers; public-records fluency = the data pipeline is his home turf; the Convergence Engine itself is proof he can build monitored ingestion systems. Matches the accumulated lesson (confidence 0.79) that portal-mandate shapes score highest for this founder.
Breakout potential
Strong replication path: PA is nationwide and perpetual (every declared disaster), and the same radar+documentation shape extends to HMGP, BRIC, CDBG-DR (HUD), and the state pass-through reporting layer. A wedge with PNPs (hospitals, co-ops) — underserved because big consultants chase big government clients — could become the category default for sub-$5M claims.
Final recommendation
PURSUE the Phase-1 lead-intelligence wedge now; treat the documentation layer as the 60-90-day follow-on once paying consultants confirm the pain. This is FACT-grade money flow ($30M this batch, multi-billion COVID PA cited in evidence), a defined actor class that cannot skip the paperwork, an existing paid-consultant market proving spend, and a build the founder can ship in weeks on infrastructure he already operates. The honest risks are sales-side (relationship industry, free-data commoditization), not demand-side — which is the right kind of risk for a fixed-fee, low-burn entry.
Next action
Pull OpenFEMA's Public Assistance Funded Projects dataset today, reproduce the 13 SC awards from the press release as a validation test, entity-resolve the five named subrecipients, and send that one-page 'obligation day' sample alert to 10 PA consulting firms asking if they'd pay $400/mo for it nationwide.