What changed
FACT: DHS/FEMA obligated a $14,314,679,947 Public Assistance grant to the Texas Division of Emergency Management (TDEM) for repair/replacement of disaster-damaged facilities (USAspending award ASST_NON_4485DRTXP00000001_070). PA money is a pass-through: TDEM is the recipient, but the actual documentation burden falls on hundreds/thousands of local-government subrecipients who must justify every project to TDEM and FEMA.
Why now
INFERENCE: A freshly obligated multi-billion-dollar declaration means subrecipients are entering the project-formulation and documentation phase NOW, on FEMA's clock. FACT: The same recipient (TDEM) has multiple large disaster awards (e.g. $2.97B on 4332DRTXP), and parallel state EM agencies (FL $4.94B/$2.42B/$2.25B, CA $14.7B/$1.97B, PA $2.33B, LA $3.17B/$2.29B, MA $3.49B, PR $35.3B) show this is a recurring, replicable pattern across every disaster state.
Converging signals
FACT: (1) a specific obligated award amount, (2) a defined forced filer class (TX cities, counties, school districts, utility/special districts, eligible PNPs), (3) a mandatory federal documentation regime (RPA, damage inventories, Project Worksheets, procurement + force-account labor/equipment records, quarterly progress reports, reimbursement requests, closeout). Rule + filer class + portal meeting at one point.
Customer pain
HYPOTHESIS (widely documented in FEMA PA practice, not in this source text): subrecipients routinely lose reimbursement to de-obligation and audit findings because they fail to document procurement compliance (2 CFR 200), force-account labor/equipment time, and photo/receipt evidence contemporaneously. Small jurisdictions lack dedicated grant-management staff. The source asserts 'PA doc failures cause de-obligations, so willingness to pay is high' — flagged as inference, not fact.
Who pays
Local-government subrecipients directly (grant/finance/public-works/emergency-management staff), and the disaster-recovery consultants (Hagerty, Tidal Basin, Witt O'Brien's, ICF, CDR Maguire) who currently bill these jurisdictions a percentage of recovered funds. Both are reachable buyers who are NOT federal procurement offices.
Solved today
Today: manual spreadsheets, shoeboxes of receipts, generic photo apps, and expensive recovery consultants who take a percentage of the award or bill hourly. FEMA Grants Portal and TDEM's grant-management system are the submission destinations but provide no field-capture, evidence-organizing, or compliance-checklist tooling.
Why current solutions are bad
Consultants are expensive (often 2-5%+ of recovery or six-figure retainers) and scarce; spreadsheets don't enforce 2 CFR 200 procurement rules or tie geotagged/time-stamped evidence to a specific project; documentation gathered after the fact fails audit. Small jurisdictions get the worst service because their projects are too small for top consultants.
Proposed product
A micro-SaaS + mobile app: (1) field capture — geotagged/time-stamped photos, receipts (OCR), damage notes tied to a facility/project; (2) force-account labor & equipment time tracking with FEMA-rate schedules; (3) procurement-compliance checklists/wizards enforcing 2 CFR 200 thresholds and required documentation; (4) auto-assembled Project Worksheet packages and quarterly progress reports formatted for FEMA/TDEM submission; (5) a de-obligation-risk checklist per project. Positioned as 'keep the recovery consultant honest / do it without one.'
MVP version
Web + PWA mobile app for a single TX subrecipient: create projects, capture geotagged photo/receipt evidence, log force-account labor/equipment against FEMA equipment rates, run a procurement-documentation checklist, and export a clean, indexed PDF/ZIP reimbursement package mapped to Project Worksheet line items. No live portal API integration required at MVP — the deliverable is an audit-ready package the customer uploads. Founder's FMCSA ELDT experience shows he can add direct portal submission later if an interface exists.
30-day build
Interview 8-12 TX subrecipient grant/public-works staff and 2-3 mid-tier recovery consultants to confirm the exact pain, current tooling, and price tolerance. Pull FEMA PA Program & Policy Guide (PAPPG) and 2 CFR 200 to encode checklist logic. Build the data model (facility→project→category A-G→evidence/cost lines). Ship evidence-capture + force-account logging core.
60-day build
Add procurement-compliance checklist wizard, FEMA equipment-rate library, and the auto-assembled PW/reimbursement-package export. Recruit 3-5 design-partner jurisdictions (start with small cities/school & utility districts that lack in-house grant staff) for free/discounted pilots on real active projects.
90-day revenue plan
Convert pilots to paid at per-jurisdiction subscription plus per-project fee. Land a channel deal with one recovery consultant to deploy it across their subrecipient book (white-label or referral). Target first $2-5k MRR from a handful of jurisdictions/one consultant. Replicate the pitch to FL/LA/CA subrecipients under their existing obligated awards.
Distribution path
Direct outreach to TX city/county/school-district finance and emergency-management staff via public directories (highly reachable, public email); TDEM applicant briefings and TX municipal/county association channels; partnering with recovery consultants who resell/deploy it; content marketing on 'avoiding FEMA de-obligation' and PA documentation. Demonstrated-value selling, not relationship sales — fits founder.
Pricing hypothesis
Per-jurisdiction subscription $150-500/mo per active declaration, plus a per-project package fee ($50-150/PW) or a per-declaration flat tier. Anchor against consultant fees (percentage of award) — position as a fraction of one de-obligated project. Consultant/white-label tier priced higher per seat.
Technical difficulty
Moderate. Field capture, OCR, geotagging, time tracking, checklist engine, and PDF/ZIP assembly are all standard, solo-buildable with AI assistance. The hard part is domain encoding (PAPPG categories, 2 CFR 200 procurement rules, force-account/equipment rates) — knowledge work, not engineering risk. Live FEMA Grants Portal / TDEM GMS submission is uncertain (no documented public API) and is deliberately out of MVP scope.
Legal / regulatory risk
Low-to-moderate. The tool organizes and formats the customer's own documentation; it does not itself certify eligibility. Must avoid implying guaranteed reimbursement and avoid unauthorized 'grant administration' claims. No licensing required to operate. Standard software liability disclaimers.
Platform dependency
None on a deplatformable owner — submission is to a government system, so no marketplace/platform can cut off access. Dependency is on FEMA/TDEM form formats, which change slowly and publicly; and on app-store distribution if native mobile (mitigated by PWA).
Founder fit
Very high. This is exactly the founder's proven shape: public money flows, a defined forced-filer class must document/report to a government system, and a solo operator builds the submission/compliance layer and charges per filing/seat — the same pattern as his shipped FMCSA ELDT portal app. Bonus: his fire-service/emergency background and industrial-operations/systems-thinking map directly onto disaster-recovery field documentation.
Breakout potential
High. 50-state replication: every disaster declaration in every state creates the same subrecipient documentation burden against the same federal PAPPG regime (only the state portal/deadlines differ). The FL/CA/LA/PA/MA awards in the evidence are ready-made next markets. Expandable to HMGP mitigation grants, CDBG-DR, and other pass-through federal programs with identical subrecipient-reporting structure.
Final recommendation
PURSUE — validate then build. This is a top-tier fit for the founder's primary thesis: a defined forced-filer class, a mandatory federal documentation regime, an obligated multi-billion-dollar award, reachable non-procurement buyers, an incumbent consulting fee to undercut, and clean 50-state replication. The one real risk (per-jurisdiction WTP and de-obligation frequency) is cheap to test in 30 days of customer interviews before committing serious build effort.
Next action
Run 10-15 discovery calls this week with TX PA subrecipient staff (small cities, school & utility districts) and 2-3 recovery consultants to confirm the documentation pain, current spend, and price tolerance; in parallel, encode the PAPPG category + 2 CFR 200 procurement checklist as the product's core IP.