What changed
USAspending shows FEMA Public Assistance obligations to the State of Florida Division of Emergency Management measured in billions per declared disaster: $2.25B (DR-4399), $2.42B (DR-4337), $4.94B (DR-4486), $2.89B (DR-4673) and $1.53B (DR-4834) — all FACT, cited. Florida is the pass-through grantee; the money only reaches local governments and eligible private non-profits after they assemble and file compliant reimbursement claims (inference from PA program structure, not in source text).
Why now
The obligations are already made — the spend exists whether or not anyone builds the tool. Florida has recurring hurricane declarations, so the filer class regenerates every season, and FDEM runs its own state-side process (FloridaPA.org) on top of FEMA Grants Portal (inference). Multiple open disasters mean thousands of active Project Worksheets in-flight right now, each with documentation, procurement-compliance, quarterly-reporting and closeout burdens.
Converging signals
Three signals meet at one point: (1) massive obligated federal money to a single state grantee (FACT, USAspending); (2) a defined compelled filer class — FL cities, counties, special districts, PNPs (inference); (3) a known submission surface — FEMA Grants Portal plus FDEM's state portal (inference). Per the system's own scoring rule, a funded mandate naming a filer class and a submission IS convergence even though it is unglamorous.
Customer pain
HYPOTHESIS grounded in program structure: PA reimbursement is notoriously slow and documentation-driven — subrecipients lose eligible dollars to missing procurement records, mislabeled force-account labor, and failed closeouts, and small jurisdictions have no grants staff. The alternative is hiring a disaster-recovery consultant who typically bills hourly or a percentage of the recovered award. No complaint-thread evidence was provided in the input; the pain claim rests on the mandate structure, not on observed chatter.
Who pays
Primary: small/mid Florida municipalities, special districts (fire, water, mosquito control) and PNPs (churches, private schools, rural hospitals) that must file to get reimbursed. Secondary and possibly better: the disaster-recovery consultants and municipal accountants who serve dozens of subrecipients and would use the tool to serve more clients per head. Neither is boardroom enterprise procurement; small-jurisdiction purchases at a few hundred dollars a month typically fall under purchasing-card / small-purchase thresholds (hypothesis).
Solved today
Large jurisdictions hire national consultants (Hagerty, Tidal Basin, Witt O'Brien's/Ambipar, ICF) — proof of existing spend, often priced as a percentage of the award or six-figure hourly engagements. Small jurisdictions muddle through with spreadsheets, the FEMA PA Program and Policy Guide PDF, and overworked finance clerks; many under-claim or fail audits years later (hypothesis — consultent-market facts are industry knowledge, not in the provided sources).
Why current solutions are bad
Consultants are economically misaligned (percentage fees consume the recovery) and unavailable to the long tail — a 6,000-person town with a $900k claim can't get a national firm's attention. DIY is error-prone: PA eligibility, procurement compliance under 2 CFR 200, and duplication-of-benefits rules are exactly the kind of rule-bound document assembly a solo AI-assisted product handles well. The software layer that turns receipts, payroll records and contracts into a compliant Project Worksheet package does not exist at a small-jurisdiction price point (hypothesis — competitor scan required in the 30-day plan).
Proposed product
A Florida-focused PA claim assembler: subrecipient uploads invoices, timesheets, contracts, photos and insurance docs; the system classifies costs into PA categories (A–G), checks 2 CFR 200 procurement compliance, flags duplication-of-benefits, and emits a submission-ready Project Worksheet documentation package formatted for FEMA Grants Portal upload plus FDEM's state-side requirements, then tracks quarterly reporting and closeout deadlines per project. Charles operates it concierge-style at first (his ELDT model: he runs the filing layer, charges per submission).
MVP version
A pipeline for ONE cost category (Category B emergency protective measures or Category A debris removal — highest volume, most formulaic): document intake → AI extraction and cost classification → compliance checklist → generated PW support package as PDF/ZIP matching Grants Portal upload structure, plus a deadline tracker for quarterly reports. No portal API integration needed — the deliverable is the compliant package the applicant (or Charles as their agent) uploads. Buildable solo with AI assistance in 6–8 weeks.
30-day build
(1) Kill-check the competitive landscape properly: demo Crisis Track, AC Disaster tools, Tidal Basin's tech, and check what FDEM already gives subrecipients free. (2) Interview 10 FL subrecipients from FEMA's public applicant lists for the cited disasters plus 3 independent PA consultants — validate that package assembly (not portal access) is the bottleneck and what a worksheet is worth. (3) Build the Category A/B extraction-and-package pipeline against real published PW examples. Founder has capital, so pay for a PA-consultant advisor's hours to pressure-test outputs.
60-day build
Run 2–3 free/cheap pilot claims end-to-end with real subrecipients from an open FL disaster (there are multiple active, per the cited awards). Deliverable: a package their FDEM/FEMA rep accepts without kickback. Convert pilots into case studies with dollar amounts. Add quarterly-report and closeout-tracker modules, which create recurring revenue between disasters.
90-day revenue plan
Convert pilots to paid: $250–$500 per Project Worksheet package concierge, or $299–$799/mo per active subrecipient, or a white-label seat for small PA consultancies at $1k–$2k/mo. First revenue realistically day 90–150 given government invoicing lag — inside the 180-day window, and the founder can fund the ramp. One county with 30 PWs at $400 each is a $12k account; the cited multi-billion obligations imply thousands of PWs statewide (inference).
Distribution path
Direct and demonstration-led, matching the founder's style: Florida League of Cities, FL Association of Counties, and special-district association listservs and conferences; FEMA's public applicant lists for each cited disaster ARE the lead list (public records — founder strength); LinkedIn outreach to city clerks/finance directors post-declaration; partnerships with the mid-tier CPA firms that audit municipalities. After a named storm, every affected jurisdiction is in-market simultaneously — the declaration is the marketing calendar.
Pricing hypothesis
Per-filing (per PW package, $250–$500), per-disaster subscription per subrecipient ($2.5k–$10k depending on claim size), or consultant white-label seats. Anchor against the consultant alternative: 3% of a $2M recovery is $60k, so a $7.5k software-plus-concierge engagement is a 90% cost cut — the wedge the scoring guidance says to take.
Technical difficulty
Moderate and well inside founder capability: document extraction, rules-encoded checklists (PA Program and Policy Guide is public), PDF/package generation, deadline tracking. No government API required for v1 — Grants Portal has no public API (hypothesis), so the product assembles what a human uploads, exactly like the founder's ELDT play before he automated submission. Hurricane-season load spikes are manageable at this scale.
Legal / regulatory risk
Low-moderate: the tool prepares documentation; the subrecipient certifies and submits. Must avoid practicing law/appearing to guarantee eligibility — clear disclaimers, and mirror the ELDT agent-of-the-filer model. No license required for grant-writing/claim-prep support (hypothesis — verify FL rules on public adjusting: PA claims to FEMA are NOT insurance claims, but insurance-proceeds coordination sits adjacent to public-adjuster territory, so stay on the FEMA-package side of the line).
Platform dependency
Depends on FEMA Grants Portal and FDEM processes persisting — they are statutory infrastructure with no deplatforming risk (per scoring guidance, no platform_policy_risk on government submission surfaces). Policy risk: FEMA reform proposals could restructure PA delegation to states (hypothesis), which would change formats but not eliminate the documentation burden — Florida's state-managed model arguably deepens the moat for a state-specific tool.
Founder fit
Near-maximal. This is structurally identical to his proven ELDT play: read a mandate, identify the compelled filer class, build the package/submission layer, charge per filing. Adds his fire-service background (credibility with emergency managers — he speaks the language of the exact buyer), public-records skill (lead lists from FEMA applicant data), and operational credibility with small-government blue-collar buyers. Primary-thesis shape: public money flowing + forced paperwork.
Breakout potential
High: the identical product replicates state-by-state — the input itself shows Texas ($14.3B, $2.97B), California ($14.7B, $1.97B), Pennsylvania ($2.3B), Massachusetts ($3.5B), Maryland ($3.3B), Oregon ($1.98B), Puerto Rico ($35.3B) with the same PA structure (FACT, cited). Adjacent expansions: HMGP/BRIC mitigation grant packaging, CDBG-DR documentation, insurance-coordination modules. Fifty near-identical markets, one rulebook (44 CFR + 2 CFR 200).
Final recommendation
PURSUE — this is the founder's primary-thesis shape with billions in already-obligated, cited money behind a compelled Florida filer class, a proven-by-him monetization model (per-filing agent), and a 50-state replication path. The two honest risks are government sales friction and the possibility that FEMA/FDEM handholding already absorbs the pain for small applicants; both are cheaply testable in 30 days with interviews before committing the build. Rank A-tier conditional on interview validation.
Next action
Pull FEMA's public applicant/PW lists for the cited open FL disasters (DR-4486, DR-4673, DR-4834), identify 10 small subrecipients with active unclosed projects, and book interviews this week asking one question: 'What did the last Project Worksheet cost you to assemble, and who did the work?' Simultaneously demo Crisis Track and FDEM's free applicant resources to map what a paid tool must beat.