What changed
HUD just pushed a new wave of CDBG-DR/CDBG-MIT awards for the 2024-25 disaster cycle: Manatee County FL $252.7M, Hillsborough County FL $709.3M, City of St Petersburg $159.9M, City of Chicago $426.6M, City of Houston $314.6M, Guam $500.8M (all FACT, USAspending). Each grantee must produce a HUD-approved Action Plan (FACT from award text) and then run 6-10 years of quarterly reporting through subrecipients (inference from standard CDBG-DR program rules).
Why now
These grantees are brand-new to CDBG-DR scale money (Manatee and St Petersburg have never administered a nine-figure HUD disaster grant — hypothesis, but first-time grantees are the norm in this program). They are standing up programs, hiring staff, and selecting subrecipients RIGHT NOW; the tooling decision gets made in the first 6-12 months of the grant. Miss this window and the consultant's spreadsheet stack gets entrenched for the grant's life.
Converging signals
Three signals meet at one point: (1) appropriated money already awarded (FACT, USAspending records cited), (2) a defined filer class — grantees and their subrecipient nonprofits/departments (FACT from award text), (3) a mandatory submission cadence — Action Plan + quarterly performance reporting into HUD's DRGR system (Action Plan FACT; DRGR/QPR mechanics inference from program rules). Multiple simultaneous FL grantees plus FEMA PA billions to the same jurisdictions compound the local density of forced filers.
Customer pain
Grantees must roll up activity, beneficiary, LMI national-objective evidence, and duplication-of-benefits documentation from 10-100 subrecipients every quarter, and every dollar is audit-exposed (HUD OIG clawbacks are the grantee's nightmare). Subrecipients are typically small nonprofits and municipal departments doing this in email + Excel + shared drives (inference — no complaint-thread evidence in input; labeled hypothesis, but consistent with how first-time grantees operate). Errors surface years later as disallowed costs.
Who pays
Primary: the grantee's program office, paid from its admin set-aside (up to 5% of grant ≈ $12M for Manatee alone — inference from program rules, not cited text). Secondary and faster: mid-size disaster-recovery consultants who win grantee admin contracts and need a subrecipient data-collection tool they don't have to build, and subrecipients themselves who carry their own admin allowance. The consultant/subrecipient route avoids county procurement.
Solved today
Big consultancies (Horne, IEM, ICF, Tidal Basin) staff the problem with bodies billing against the admin set-aside; Neighborly Software sells a purpose-built grantee case-management platform; everyone else uses spreadsheets and email (competitor facts are from general knowledge — hypothesis for current market share, but the firms' existence in CDBG-DR is well established).
Why current solutions are bad
Consultant labor is expensive and doesn't leave the grantee a system; Neighborly is priced and sold at grantee-enterprise level and is heavy for a nonprofit subrecipient that just needs to submit clean income docs and DOB certifications; spreadsheets fail audits. The gap is the bottom of the stack: a cheap, fast, validation-first intake layer for the subrecipient side.
Proposed product
A subrecipient-facing compliance portal: each subrecipient gets guided intake forms for activities, beneficiaries, expenditures; built-in LMI income-limit calculators (HUD income limits by county), duplication-of-benefits checklists with document upload, and automatic validation against national-objective rules; the grantee/consultant side gets a dashboard and one-click quarterly rollup export formatted for DRGR QPR entry. Not a DRGR integration (no public API — assume manual-entry-ready exports; inference).
MVP version
Single-grantee pilot: intake forms + document vault + LMI income verification calculator + DOB checklist + quarterly rollup export (CSV/PDF matching QPR structure). Skip dashboards, skip multi-tenant polish. Buildable solo with AI assistance in 6-8 weeks; founder has already shipped a production federal-portal filing product (FMCSA ELDT), which is exactly this shape one level down.
30-day build
Pull the public Action Plans and citizen-participation drafts for Manatee, Hillsborough, and St Petersburg (they must be published for comment); identify each grantee's named admin consultant and planned subrecipient programs; interview 3-5 Florida disaster-recovery consultants and 3 likely subrecipient nonprofits; build the LMI/DOB validation core as the demo.
60-day build
Working pilot deployed with one consultant or one subrecipient cohort under a FL grantee, priced as a paid pilot ($2-5k). Attend/monitor grantee subrecipient-onboarding workshops (public meetings) to get direct access to the filer class without procurement.
90-day revenue plan
Convert pilot to per-subrecipient pricing ($200-500/subrecipient/month, or $500-750/quarter) billed to the consultant or grantee admin budget; one grantee with 20 subrecipients at $300/mo is $72k ARR. Replicate the identical pitch to the other 2025 grantees in this feed (Houston, Chicago, Guam) — same program, same forms.
Distribution path
Named, public, finite buyer list: every CDBG-DR grantee is published with dollar amounts (USAspending, Federal Register); their consultants are named in public procurement records; their subrecipients are named in public Action Plans. Direct outreach + showing up at public subrecipient workshops. This is demonstrated-value selling to a list you can enumerate in an afternoon, which matches the founder's sales style.
Pricing hypothesis
Per-subrecipient per-quarter ($500-750) or per-grantee flat ($20-50k/yr from the admin set-aside). Anchor against consultant hours: one consultant reviewing one subrecipient's quarterly package bills more than the software costs for a year.
Technical difficulty
Moderate and well inside founder capability: forms, document storage, rule-based validation, exports. The hard part is domain fidelity (24 CFR requirements, income limits, DOB under the Stafford Act) — learnable from public HUD guidance, and getting it right IS the moat. No DRGR API means export-to-manual-entry, which is acceptable (that's how the ELDT product started thinking too).
Legal / regulatory risk
Low. The tool prepares and organizes documentation; it does not certify compliance. Standard SaaS terms disclaiming legal advice. Data handling includes PII (income docs) — needs solid security posture, but no license required to operate.
Platform dependency
HUD program rules and DRGR formats change slowly and publicly (Federal Register). No platform owner can deplatform a tool that prepares submissions to a government system.
Founder fit
Near-maximal on the stated thesis: public money flows to a defined filer class that must document and report on a deadline cadence, and the founder has already built and monetized exactly this shape against a federal portal (FMCSA ELDT, per-upload fee). Public-records skill helps him enumerate grantees, consultants, and subrecipients from published documents. The one mismatch: ELDT sold to private training schools; here the best-paying buyer is a county, which drags in procurement unless he routes through consultants/subrecipients.
Breakout potential
High within the niche: CDBG-DR produces dozens of new grantees per disaster cycle, each with a 6-10 year reporting tail, and the same subrecipient-intake engine extends to FEMA Public Assistance subapplicants (the $4.9B/$14.3B FL/TX FEMA awards in this feed prove adjacent volume) and state pass-through grant programs generally.
Final recommendation
PURSUE — but enter through the side door, not the front. Do not bid grantee RFPs. Validate in 2 weeks by reading the published Manatee/Hillsborough/St Petersburg Action Plan drafts and calling Florida DR consultants; build the LMI/DOB validation demo; sell per-subrecipient through consultants and subrecipient cohorts. Kill only if consultants uniformly say they bundle their own tooling and subrecipients have no independent budget.
Next action
Today: pull Manatee County's published CDBG-DR Action Plan draft (public comment requirement) and the county's procurement records to identify its admin consultant; list the first announced subrecipient programs; draft the outreach email to 5 FL disaster-recovery consulting firms offering a white-label subrecipient intake portal.