What changed
FACT (signals): a new frontier-model tier (GPT-5.6 and peers) claims materially better performance-per-dollar, which HYPOTHESIS collapses the unit cost of bulk invoice OCR and cost-line reconstruction. INFERENCE: work that was uneconomic when a human had to review thousands of pages of closeout documentation per project becomes viable for one operator.
Why now
FACT (demand_evidence): FEMA is actively obligating large Public Assistance sums — $1.5B to Georgia for Helene, ~$11.1B obligated for Puerto Rico grid (only $2.7B disbursed), plus fresh multi-million approvals across NC/SC/GA/WY/ND in July 2026. INFERENCE (from convergence + GAO patterns): a large share is deobligated or written off years later on procurement/documentation findings. The cost shift in document AI is the 'why now' on the supply side; the live award wave is the 'why now' on the demand side.
Converging signals
Three signals meet: (1) huge PA sums legally owed but lost to documentation gaps; (2) 2 CFR 200 procurement deobligations that claw money back years after spend; (3) frontier-model economics that make retroactive substantiation reconstruction cheap. FACT the money and the cost-shift are cited; HYPOTHESIS that the deobligated pool is large and recoverable at scale.
Customer pain
A city, county, tribe, or nonprofit spent real cash on disaster response/rebuild, expected federal reimbursement, and had it deobligated or denied for missing invoices, weak procurement documentation, or cost-line mismatches. The money is gone from their budget and the internal staff who could fight it are gone or overwhelmed. PAIN evidence in the pool is thin/institutional (one r/EmergencyManagement thread), so demand rests on the CLAIMABLE-MONEY figures, not complaint volume — noted honestly.
Who pays
Local governments, tribal governments, and private nonprofits (PNPs) that already incurred eligible costs and were deobligated — paying a percentage of funds successfully re-obligated. The BENEFICIARY and BUYER are the same entity here, which simplifies the sale.
Solved today
Incumbent disaster-recovery consulting firms (Hagerty, Tidal Basin, Witt O'Brien's, IEM, CDR Maguire) run PA appeals and recovery on contingency or T&M, backed by large staffs of ex-FEMA reviewers. Smaller applicants often do nothing — they eat the loss because retaining a national firm for a single closed project isn't worth it to either side.
Why current solutions are bad
The big firms cherry-pick large active projects; the long tail of already-closed, smaller deobligations is uneconomic for them to chase manually and invisible to the applicant. That neglected tail is exactly where cheap document reconstruction changes the math.
Proposed product
A contingency recovery service (not pure SaaS): ingest an applicant's deobligation/DR letters, project worksheets, and cost documentation; use frontier-model OCR + cost-line mapping to reconstruct the missing substantiation and cross-walk spend to eligible PA categories and 2 CFR 200 procurement requirements; auto-draft the appeal/request-for-reconsideration package for a human (the founder + a fractional PA/grants specialist) to finalize. Monetize as % of re-obligated funds. A white-label 'reconstruction engine' for the incumbent firms is a credible pivot/second revenue line.
MVP version
Pick 2-3 states hit by Helene (GA/NC/SC) with dense PA activity. Manually source 5-10 deobligated projects via public records / FEMA appeals data / direct outreach to small PNPs and towns. Build the doc-ingestion + cost-line reconstruction pipeline against real closeout packages and produce one polished appeal package on contingency to prove recovery.
30-day build
Validate the mechanics: FEMA PA appeal timelines and deadlines (appeals are 60 days from the determination — CONFIRM whether re-obligation is even available on the targeted projects; this is a potential kill), 2 CFR 200 procurement standards, and what 'reconstruction' can and cannot fix. Line up a fractional ex-FEMA PA specialist for sign-off. Build the ingestion→cost-line→draft pipeline on sample documents.
60-day build
Sign 3-5 applicants on pure contingency (zero upfront to them = easy yes). Submit first appeal/reconsideration packages. Approach 1-2 regional recovery consultants about licensing the reconstruction engine per-project.
90-day revenue plan
First re-obligations land → first contingency invoices. Note: FEMA obligates to the state Recipient, then disburses — cash timing is slow, so first revenue realistically skews to the 120-180d end, not 90d.
Distribution path
Direct outreach to county/municipal finance directors, tribal grants offices, and PNP administrators in recently-declared disaster states (public FEMA declaration and applicant lists); state emergency-management associations; and white-label deals with existing recovery firms. Sell through a demonstrated recovery, not relationship sales — exactly the founder's mode.
Pricing hypothesis
15-30% contingency of funds re-obligated (verify no state/federal cap on such contingency fees for public grants — some jurisdictions restrict contingency arrangements on federal awards). White-label: per-project reconstruction fee or seat license to consultants.
Technical difficulty
Moderate on the AI (document OCR + cost-line mapping is now commoditized). HARD on the domain: PA eligibility, appeal procedure, and 2 CFR 200 procurement findings are where recovery actually succeeds or fails — the software drafts, but a knowledgeable human must be right about the rule.
Legal / regulatory risk
Representing an applicant in a FEMA appeal is generally consulting, not legal practice, but the line blurs near formal disputes/litigation — structure as documentation/appeal-package preparation with the applicant as filer. Contingency-fee legality on federally-funded work needs verification per jurisdiction.
Platform dependency
None deplatformable — the counterparty is FEMA/the state Recipient, a government system, not a platform owner.
Founder fit
HIGH. Public-money recovery, government-portal/filing shape, public-records sourcing, systems thinking, and AI-assisted document work all match the founder's proven FMCSA-style edge. The gap vs. his ideal is that this is a service with a longer, contingency-gated cash cycle rather than a card-today micro-SaaS.
Breakout potential
Real: 50-state replication, every disaster cycle refreshes the pool, and the reconstruction engine is a sellable asset to the incumbent consulting industry. Ceiling is set by how much deobligated money is actually recoverable within deadline — unproven.
Final recommendation
PURSUE AS A VALIDATED PROBE, not a build-first bet. The economics and founder-fit are strong, but the entire thesis hinges on one unverified fact: whether meaningful deobligated PA money is still procedurally recoverable within appeal windows. Spend the first 2-3 weeks killing or confirming that with a real FEMA PA specialist before writing production code. If recovery windows are open, this is a high-fit, replicable, defensible service.
Next action
Interview an ex-FEMA PA appeals specialist (or a boutique recovery consultant) to confirm: (a) that deobligated/closed projects retain a viable appeal or re-obligation path, (b) the true deadline mechanics, and (c) whether contingency fees on federally-funded PA work are legally permissible in target states.