What changed
USAspending shows a $35,301,159,434 DHS/FEMA Public Assistance grant to Puerto Rico (recipient: Governor's Authorized Representative, award ASST_NON_4339DRPRP00000001) — the largest PA pot in the evidence set (FACT). Sister awards show the same forced-filer structure across jurisdictions: $21.99B to the US Virgin Islands, $4.9B/$2.9B/$2.4B/$2.3B to Florida, $3.5B Massachusetts, $3.6B Louisiana, $2.3B Pennsylvania (FACT, cited). Note honestly: DR-4339 is the 2017 Hurricane Maria disaster — the award is not new; what persists is that most of it is still being obligated/disbursed through subrecipient paperwork (inference).
Why now
PR PA funds move only as fast as municipalities can produce compliant documentation; heightened federal oversight of PR (276-style scrutiny, COR3 intermediation) means every dollar drawn requires a defensible paper trail (inference). Undrawn billions + documentation bottleneck = the paperwork layer IS the constraint. AI-assisted document assembly and translation only recently became good enough for a solo builder to ship a credible bilingual compliance tool (inference).
Converging signals
Three signals meet: (1) a $35.3B funded mandate (FACT, USAspending); (2) a defined filer class — 78 municipalities plus agencies as subrecipients under COR3 (structural inference from the PA program design); (3) known submission surfaces — FEMA Grants Portal and COR3's local portal (inference; portals named but not evidenced in input). Per the system's own rule, mandate+filer-class+portal is convergence even though the idea is unglamorous.
Customer pain
Municipal finance staff must produce Project Worksheets, procurement documentation, force-account labor records, quarterly reports, and reimbursement requests in a form that survives both COR3 and FEMA review; errors mean delayed or de-obligated funds (inference from PA program structure — no direct complaint evidence was provided in the input). Small PR municipalities have thin admin staff and work in Spanish while FEMA's requirements are English-first (hypothesis).
Who pays
Primary: the municipality, using FEMA management costs / Direct Administrative Costs — meaning federal money can pay for the tool itself (inference, standard PA mechanics). Secondary and likely easier: the PA consulting firms already billing municipalities (Horne, Tidal Basin, ICF and local shops), who would pay per seat/project to cut their own labor cost (hypothesis).
Solved today
Large disaster-recovery consultancies embedded since 2017 billing hourly or as a share of management costs; spreadsheets, shared drives, and manual assembly of Grants Portal uploads; COR3's own oversight systems (inference — incumbent consultant presence in PR PA is well established but not in the provided sources).
Why current solutions are bad
Consultant-heavy documentation is expensive (the 2-5% style fee the thesis says to undercut), slow, and leaves the municipality with no reusable system; nothing in the stack is Spanish-first or municipality-owned (hypothesis). The wedge is software that standardizes the reimbursement package so a municipal clerk — not a $200/hr consultant — does 80% of the assembly.
Proposed product
Spanish-first web app: intake wizard per FEMA project (PW), checklist engine keyed to PA documentation requirements (procurement, force account, insurance, EHP), document vault with completeness scoring, auto-generated bilingual reimbursement packages and quarterly-report drafts formatted for Grants Portal/COR3 upload. No portal API integration required at MVP — output is upload-ready packages, sidestepping the (likely nonexistent) public Grants Portal API (inference).
MVP version
One municipality's (or one consultant's) live PA project run end-to-end: checklist + vault + generated reimbursement package for a single PW category (e.g., Category A/B), fully in Spanish, in 4-6 weeks of AI-assisted build.
30-day build
Kill/validate first: 10 interviews — PR PA consultants, 2-3 municipal finance directors, one COR3-adjacent contact — to confirm (a) where packages actually fail review, (b) whether municipalities can spend DAC on software, (c) whether consultants would resell. Build checklist engine from public FEMA PAPPG + COR3 published guides. Recruit one design partner.
60-day build
Ship MVP with the design partner on a live project; produce one real reimbursement package accepted by COR3; document the before/after hours. Price test: per-project fee (~$1.5-3k) vs municipal subscription (~$500-1,000/mo).
90-day revenue plan
Convert design partner to paid; sign 2-3 consultants as resellers or 3-5 municipalities directly, leaning on the accepted-package case study. Realistic first revenue day 90-150 given municipal/consultant sales cycles — inside the founder's 180-day window but not fast.
Distribution path
Direct outreach in Spanish to municipal finance directors (78 targets — a finite, listable market), PR PA consultant firms as channel, COR3 vendor ecosystem, and the demonstrated-value motion: publish a free bilingual PA documentation checklist that ranks for what clerks actually search (hypothesis).
Pricing hypothesis
Per-project fee $1,500-3,000 or municipality subscription $500-1,000/mo, framed as DAC-eligible so federal funds cover it; consultant seat licenses $200-400/seat/mo. All hypothesis pending interviews.
Technical difficulty
Low-moderate: forms, checklists, doc storage, templated generation, Spanish localization. No portal automation needed at MVP. Hardest part is domain accuracy (PAPPG rules), not code.
Legal / regulatory risk
Low for the tool itself; the founder is not the applicant of record. Must avoid practicing as an unlicensed grant consultant vs selling software (hypothesis: fine line but manageable). Municipal contracts in PR may require local registration/comptroller filing — real friction, not fatal.
Platform dependency
None that can deplatform it — outputs target a government system with no platform owner. If COR3 changes required formats, templates need updating; that's maintenance, and per the scoring rules not platform risk.
Founder fit
Shape is exactly his proven ELDT pattern: mandate → defined filer class → submission layer → per-transaction fee, so thesis-fit is maximal. Two honest discounts: (1) no evidence he speaks Spanish or has PR presence — a Spanish-first product sold into PR's municipal-political ecosystem remotely is a genuine handicap (hypothesis); (2) buyers here are government offices or consultants, not private businesses like ELDT training providers — slower trust cycle. Net: high pattern fit, real go-to-market friction.
Breakout potential
Strong replication path: the identical product (minus translation) serves the $21.99B USVI pot and the multi-billion FL/LA/MA/PA state PA programs cited in evidence — 50+ near-identical markets, and every new declared disaster refills the pipeline (FACT for the award amounts; expansion path is inference).
Final recommendation
PURSUE-CONDITIONAL: strong thesis fit and hard-money demand, but do not build first. Spend 2 weeks on Spanish-language buyer interviews; proceed ONLY if (a) a consultant channel or local partner materializes, and (b) interviews confirm the documentation bottleneck is still live in 2026 rather than consumed by incumbent consultants. If PR access fails, pivot the same product to the USVI ($21.99B) or a mainland state PA program where he can sell in English — the evidence supports those equally.
Next action
This week: build the list of 78 municipal finance directors + the top 10 PA consulting firms active in PR (public COR3/FEMA contractor records), and send 20 Spanish-language outreach emails (AI-drafted) requesting 15-minute calls about how reimbursement packages get assembled today.