What changed
FACT: FEMA approved $16M+ for 20 Tennessee recovery/mitigation projects (Jan 2026 winter storm, Tropical Storm Helene and other disasters): $14.6M Public Assistance across 17 projects plus $1.4M HMGP, with named small subrecipients — Cumberland EMC $5.3M, Wilson County $3.5M, Duck River EMC $1.5M, Cocke County $1.1M, Harriman Utility Board $703K, Cheekwood Estate $640K (FEMA press release, 2026-07-10). Each obligated project drags a multi-year documentation, quarterly-reporting, and closeout tail behind it, with clawback (de-obligation) as the penalty for bad records.
Why now
FACT: the demand_evidence shows this is not a Tennessee one-off — USAspending records show FEMA PA reimbursement awards to single state recipients of $1.5B and $2.9B (Florida), $2.35B (North Carolina), $2.3B (Pennsylvania), $1.8B (Puerto Rico), all of which pass through to thousands of local subrecipients who carry the documentation burden. INFERENCE: PA obligates roughly $10B+/yr nationally (stated in input as inference). Every new disaster declaration mints a fresh class of small, unprepared, forced documenters, so the entry point recurs continuously.
Converging signals
Three signals meet at one point, which per the system's own scoring rule constitutes convergence: (1) a funding mechanism (PA/HMGP reimbursement under 2 CFR 200) that compels documentation; (2) a defined filer class (named co-ops, counties, utility boards, nonprofits in the press release); (3) a mandatory portal path (FEMA Grants Portal via the TEMA state pass-through). The national USAspending awards confirm the same structure repeats in every state.
Customer pain
FACT (from the mandate structure in the input): subrecipients must produce project worksheets, force-account labor/equipment cost documentation, 2 CFR 200-compliant procurement records, quarterly progress reports, and closeout packages, and badly documented costs are de-obligated — i.e., a rural co-op that already spent $5.3M on storm repair can be forced to give money back years later. HYPOTHESIS (well-supported by GAO/OIG audit history but not in the provided sources): small subrecipients run this on spreadsheets, paper timesheets, and one overloaded finance clerk, and de-obligations for documentation failures are common audit findings.
Who pays
The subrecipient itself (co-op general manager, county mayor/road superintendent, utility board) — distinct from the beneficiary question because here beneficiary and buyer coincide, which is the clean case. Critically, the input states management/administrative costs (Category Z) are themselves FEMA-reimbursable, so the tool can be effectively free to the buyer after reimbursement — a rare 'FEMA pays for your compliance software' pitch. Secondary buyers: PA consultants who want a white-label field-capture tool, and state recipient agencies (slower, procurement-bound — do not lead with them).
Solved today
(a) FEMA's free Grants Portal — but it is a submission system, not a field-capture system; it does not generate the daily force-account labor/equipment logs or procurement files, it only receives what the subrecipient managed to assemble. (b) Disaster-recovery consultants (Tidal Basin, Hagerty and similar) billing hourly or a share of the award as Direct Administrative Costs — proof of existing spend, and exactly the 2-5%-fee incumbent the thesis says to undercut with software. (c) Spreadsheets and shoeboxes at the small end. HYPOTHESIS: consultants concentrate on large applicants; sub-$5M subrecipients are economically unattractive to them and are the underserved wedge.
Why current solutions are bad
Grants Portal solves submission, not evidence creation — the audit failure happens in the field months earlier (missing equipment hours, no procurement memo, no photos), and no free FEMA tool captures that contemporaneously. Consultants are effective but expensive, episodic, and scarce right after a big disaster when every jurisdiction wants them at once. Spreadsheets fail 2 CFR 200 audit tests years later when staff have turned over.
Proposed product
An audit-ready PA documentation workspace for small subrecipients: disaster/project setup mapped to PA categories A-G plus Z; mobile-friendly daily force-account labor and equipment logs using FEMA equipment rate codes with photo/GPS attachment; a 2 CFR 200 procurement-compliance checklist that generates the required justification memos as the purchase happens; a document vault organized by project worksheet; quarterly-report and closeout-package export formatted for Grants Portal upload. Not a portal bot — the durable value is contemporaneous evidence capture and clawback prevention (the 'document/administer' layer the claimable-money thesis identifies as durable, vs mere discovery).
MVP version
Web app (FastAPI/Postgres — the founder's stack) with four screens: project setup, daily labor/equipment log entry with photo upload, procurement checklist with generated memo PDFs, and a one-click closeout binder export (PDF + indexed zip). Seed it with FEMA's published equipment cost codes and the 2 CFR 200.317-327 procurement decision tree. No Grants Portal integration in v1 — export files a clerk uploads; this avoids any dependency on FEMA system access while matching its structure.
30-day build
Build the MVP (30-45 days, solo AI-assisted — well within demonstrated capability). In parallel, run the validation channel that costs nothing: FEMA press releases and USAspending name every newly obligated subrecipient with dollar amounts — this convergence engine already ingests them. Call the six named TN subrecipients (a co-op GM will take a call; the founder's fire-service and utility-adjacent operational credibility is a real door-opener here) and ask one question: 'what does your closeout and audit-defense workload look like, and who is doing it?' Target: 10 discovery calls, 3 design partners.
60-day build
Pilot with 2-3 TN subrecipients on their OPEN projects (obligated ≠ finished: quarterly reports, remaining large-project documentation, and closeout are still ahead of them). Price the pilot as a paid per-project fee (~$2,500) framed as Category-Z reimbursable. Simultaneously approach 2-3 small PA consultants with a white-label offer — they bring the disaster-onset relationships the founder lacks.
90-day revenue plan
Convert pilots to per-project fees ($2,500-$7,500 by project size) or annual subscription ($5K-$10K per subrecipient covering all open projects). 5 paying subrecipients ≈ $25-40K. When the next disaster declaration lands anywhere in the Southeast, run the playbook at onset — day-one outreach to affected counties/co-ops when documentation pain is at maximum and nothing is yet written down. Recurrence engine: the same monitoring this system already does becomes the sales-lead feed.
Distribution path
(1) Named-target outreach from FEMA press releases and USAspending — every prospect is public, named, and has a stated dollar amount at stake; (2) state rural electric co-op associations and county associations (TN Electric Cooperative Association, county services associations) — one association endorsement reaches all members; (3) white-label through small PA consultants; (4) TEMA and state pass-through agencies as referrers (not buyers) — states get audited on subrecipient monitoring and want their subrecipients documented. Demonstrated-value sales fit: a sample closeout binder generated from a prospect's real project data is the demo.
Pricing hypothesis
Per-project fee ($2,500-$7,500 tiered by obligated amount) or $5K-$10K/yr per subrecipient — deliberately an order of magnitude under consultant DAC billings, and positioned as FEMA-reimbursable management cost so net buyer cost approaches zero. HYPOTHESIS: reimbursability collapses price resistance; must verify Category Z treatment of software subscriptions with a pilot customer's state PA coordinator before leaning on it in marketing.
Technical difficulty
Low-moderate: forms, file storage, PDF generation, checklist logic, and export formatting. No government-portal write integration required in v1 (the human uploads exports to Grants Portal), so no API-access gatekeeping. The hard part is domain fidelity — encoding PA categories, equipment rate schedules, and 2 CFR 200 procurement rules correctly — which is research effort, not engineering risk, and plays to the founder's public-records/regulation-reading strength.
Legal / regulatory risk
Low. Input states: no licensure needed for software/documentation tooling for PA subrecipients; public-adjuster rules implicate individual claims advocacy, which this is not. 2 CFR 200 procurement rules govern how governments buy the tool — keep pricing under micro-purchase/simplified-acquisition thresholds to avoid competitive bids. Stay a documentation tool, not a representation service, to avoid any advocacy line.
Platform dependency
None that can deplatform: FEMA Grants Portal is a government system with no platform owner enforcing app policies, and v1 doesn't even integrate with it. Dependency risk is policy-shaped instead: PA program rules change (e.g., procedure updates) requiring content maintenance — a moat for whoever keeps current, not a kill risk.
Founder fit
Near-maximal under the stated thesis: public money flowing (reimbursement) + compelled documentation + government portal + per-filing monetization is exactly the FMCSA ELDT shape he has already shipped and charged for. Bonus overlaps the thesis doesn't even require: fire-service background means he speaks emergency-management natively (PA categories, force-account, mutual aid are his culture), and industrial-operations experience matches the buyer persona (utility/road-department operations people, not IT departments).
Breakout potential
High within the niche: PA is national and perpetual (INFERENCE: $10B+/yr, thousands of subrecipients per major disaster), HMGP/BRIC/CDBG-DR are adjacent documentation regimes with the same buyer, and the white-label consultant channel scales without headcount. The demand_evidence's multi-billion state-level awards (FL, NC, PA, PR) show 50 replicable state markets. Not a venture-scale platform — a durable $0.5-3M/yr solo business with expansion optionality.
Final recommendation
PURSUE — this is among the highest founder-fit shapes the engine has surfaced: FACT-grade money ($16M TN batch, multi-billion national PA flows per USAspending), a named compelled class, a portal, per-project monetization, reimbursable buyer spend, and a repeat of the founder's proven FMCSA pattern with better tailwinds (recurring disasters, 50-state replication). The decisive unknowns are sales-stage timing (onset vs closeout) and whether the free/consultant path is 'adequate' for sub-$5M subrecipients — both are resolvable with ~10 phone calls before writing code. Kill criteria: if 8 of 10 subrecipient calls say TEMA/consultants fully cover them at no net cost, or if closeout/audit-defense pain can't sell outside the immediate post-disaster window, stop.
Next action
Call the six named Tennessee subrecipients (start with Cumberland EMC, $5.3M, and Wilson County, $3.5M) this week and ask who is assembling their force-account documentation, quarterly reports, and closeout packages, what it costs, and what they fear at audit. Three design-partner yeses → build the 45-day MVP.