What changed
HUD obligated $709,324,000 in CDBG-DR/CDBG-MIT funds to Hillsborough County FL (FACT, USAspending award B-25-UU-12-0002), $252,711,000 to Manatee County (FACT), and $159,884,000 to the City of St. Petersburg (FACT) — a dense Tampa-Bay cluster of 2024-25 hurricane-recovery grantees, each of which must now stand up subrecipient programs and reporting pipelines. Parallel FEMA PA obligations to Florida DEM ($4.94B, $2.89B, $2.25B — FACT) show the same region is simultaneously processing a second, larger reimbursement paperwork stream.
Why now
CDBG-DR grantees must publish an Action Plan (FACT from award text) and then begin drawing funds and reporting; the subrecipient agreements (cities, nonprofits, contractors under the county) are being executed over the next 6-12 months. Whoever is embedded in the documentation workflow when the first draws happen keeps the seat for the 6-year life of the grant. The window to sell is while programs are being designed, not after.
Converging signals
(1) A funded mandate: $709M+ landed on one county (FACT, cited). (2) A defined filer class: county grantee plus subrecipient municipalities/nonprofits/contractors who must document eligible activities and beneficiaries (structural inference from CDBG-DR program design). (3) A known portal and cadence: HUD DRGR quarterly performance reports (inference — standard for all CDBG-DR grants). (4) A replicable cluster: Manatee, St. Petersburg, Chicago, Guam awards in the same tranche (FACT, cited). Rule + filer class + portal converge on one workflow.
Customer pain
Subrecipients are small city departments and nonprofits that must produce LMI beneficiary income documentation, duplication-of-benefits (DOB) analyses, procurement/Davis-Bacon files, and quarterly progress data in a HUD-auditable format — or face repayment findings. The county grantee must monitor all of them and roll their data into DRGR QPRs. This is done today in spreadsheets and email, and HUD OIG audit findings against prior CDBG-DR grantees are overwhelmingly documentation failures (HYPOTHESIS — consistent with program history, not evidenced in input).
Who pays
Primary: the county grantee out of its admin set-aside (CDBG-DR allows roughly 5% for administration — HYPOTHESIS on the exact cap, but an admin budget is structural), paying per-subrecipient seats. Secondary: subrecipients directly (a $250-750/mo tool is below micro-purchase procurement thresholds). Tertiary: the disaster-recovery consultants (Horne, IEM, Tetra Tech class) who staff these programs and resell tooling.
Solved today
Consultants billing hourly or a percentage of the award, plus Excel/SharePoint; larger grantees license Neighborly Software or Salesforce-based case management for homeowner programs. Subrecipient-level compliance rollup for infrastructure/public-services activities is the least-served layer (HYPOTHESIS).
Why current solutions are bad
Consultant-run spreadsheets don't give the county real-time visibility across 20-50 subrecipients, produce QPR data late, and evaporate when the consultant contract ends. Enterprise grant platforms are priced and procured at the county level and ignore the subrecipient's day-to-day evidence collection (income docs, DOB worksheets, photos, invoices).
Proposed product
A subrecipient compliance workspace: guided checklists per activity type (housing rehab, infrastructure, public services), LMI income-verification and DOB worksheet automation with document storage, Davis-Bacon/Section 3 file tracking, and one-click quarterly rollup formatted for the grantee's DRGR QPR entry. County dashboard on top; per-subrecipient pricing underneath. AI-assisted document extraction (income docs, invoices) is the labor-saving hook.
MVP version
For ONE activity type (e.g., housing rehab or public facilities): subrecipient portal with the HUD-required evidence checklist, DOB worksheet, beneficiary income calculator, document vault, and a QPR-ready export. Built solo on FastAPI/Postgres in 4-8 weeks; no DRGR integration needed at MVP (DRGR entry stays manual-but-prefilled — DRGR has no public write API, inference).
30-day build
Pull Hillsborough/Manatee/St. Pete draft Action Plans and public subrecipient lists as they publish; interview 5-10 CDBG-DR administrators and 2-3 consultants from prior FL disasters (Ian/Michael programs at Rebuild Florida) to validate the least-served activity type; build the DOB + beneficiary-doc module against a real prior QPR.
60-day build
Pilot with one subrecipient or one consultant team free-for-90-days in exchange for workflow access; harden the QPR export against the county's actual reporting template; publish a free 'CDBG-DR subrecipient compliance checklist' lead magnet targeting the named FL grantees.
90-day revenue plan
Convert pilot to paid ($500-1,000/mo per subrecipient or $15-30k/yr county license covering all subrecipients); sign the first consultant reseller. Realistic first revenue day 90-150 given government-adjacent buyers; the founder's runway covers this.
Distribution path
Named-account outreach — the buyer list is literally published on USAspending and in each county's Action Plan (grantee staff, then their subrecipients as agreements are announced). Second channel: the small bench of CDBG-DR consultants who serve every disaster and can carry the tool into multiple grantees. No ad spend; demonstrated-value demos fit the founder's sales style.
Pricing hypothesis
Per-subrecipient subscription $500-1,000/mo (billable to grant admin funds), or county-level license ~$25k/yr; optional per-beneficiary-file fee mirrors his proven ELDT per-upload model. Undercuts a 2-5% consulting fee by an order of magnitude while making the consultant more profitable — sell to them, not against them.
Technical difficulty
Moderate. Forms, checklists, document storage, income/DOB math, exports — squarely in solo-plus-AI range. Hardest part is encoding HUD compliance rules correctly; mitigate by shadowing one consultant and starting with one activity type. No DRGR write access exists (inference), so exports/prefill, not portal automation — weaker than his ELDT wedge on that one axis.
Legal / regulatory risk
Low for the founder: he sells software, not grant advice; no license required. Product errors that cause a HUD finding are a liability/reputation risk — handle with disclaimers and by positioning as documentation tooling, not compliance certification.
Platform dependency
HUD DRGR and program rules are stable, decade-old infrastructure; no platform owner can deplatform a tool that organizes a grantee's own records. Rule changes per Federal Register allocation notice are a maintenance task, not a dependency risk.
Founder fit
Very high. This is exactly his proven ELDT shape — read the mandate, find the compelled filer class, build the paperwork layer, charge per filing/seat — applied to a bigger money flow. Public-records fluency, operational credibility with county/emergency-management people (fire-service background), and demonstrated government-portal product delivery all apply. Matches the system lesson (confidence 0.79) that government-portal mandate opportunities score highest for him.
Breakout potential
Every presidentially declared disaster mints a new cohort of CDBG-DR grantees (Chicago $426M and Guam $500M are in this same tranche — FACT), and the adjacent FEMA PA reimbursement stream ($14.3B Texas, $4.9B Florida — FACT) is the same documentation problem 10x larger. One product, replicated per disaster, indefinitely.
Final recommendation
PURSUE — top-decile fit for the primary thesis. The mandate is funded and cited, the filer class is named, the buyers are geographically clustered and publicly listed, and existing spend (consultant fees from admin set-asides) is structural. Validate the Neighborly/consultant incumbency question in week 1 before writing code; if subrecipient-level whitespace is confirmed, this is his best-shape opportunity in the pool.
Next action
This week: download Hillsborough County's draft CDBG-DR Action Plan (public comment is mandatory), extract the planned programs and admin budget, and book calls with two Rebuild Florida-era subrecipient administrators and one DR consultant to ask exactly one question: 'what tool did your subrecipients use for beneficiary files and QPR data, and what did it cost?'