Convergence Radar Convergence Engine

← Feed

A

DR-Docs: Subrecipient compliance-documentation layer for CDBG-DR (LMI, duplication-of-benefits, QPR roll-up)

70/100

A per-beneficiary intake and documentation tool sold to the nonprofits, contractors, and small cities executing $10B+ in 2025 CDBG-DR awards, generating grantee-ready QPR/DRGR data, duplication-of-benefits checks, and LMI national-objective files that survive a HUD monitoring visit.

Build immediately β€” high demand, fast revenue, solo feasible. Β· created 2026-07-11 08:01 UTC

public recordssaasaifast cashlong-term

Scorecard

newness 4/10
convergence 8/10
demand evidence 9/10
existing spend 8/10
solo feasibility 7/10
speed to mvp 7/10
speed to revenue 6/10
distribution 6/10
competitive gap 6/10
expansion 9/10
founder fit 9/10

Opportunity brief

What changed
HUD obligated a new round of CDBG-DR/CDBG-MIT awards: $314.6M to City of Houston (FACT, USAspending B-25-MU-48-0001), $426.6M to Chicago, $709.3M to Hillsborough County, $252.7M to Manatee County, $500.8M to Guam, $159.9M to St. Petersburg β€” all in the provided evidence. Each grantee must now stand up subrecipient programs (housing rehab, business assistance, infrastructure) whose per-household/per-business accomplishment data rolls up into quarterly reporting.
Why now
The awards are freshly obligated; grantees are in the action-plan/program-launch window right now, which is exactly when subrecipient agreements are signed and reporting templates are chosen. Whoever is embedded in the intake/documentation workflow at program launch keeps the seat for the 6-year grant life. HYPOTHESIS: the 2025 cohort's compliance staffing is thinner than the money requires, as in every prior CDBG-DR cycle (supported by HUD OIG's long history of DOB/LMI findings, not by the supplied text).
Converging signals
Three signals meet at one point: (1) appropriated money already obligated (six awards >$150M each in evidence), (2) a defined filer class β€” grantee plus its subrecipients executing housing rehab, roads, water, business assistance (FACT from award text), and (3) a mandatory reporting apparatus β€” Action Plan and quarterly performance reporting into HUD's DRGR system (Action Plan FACT from companion items; DRGR/QPR mechanics are inference but standard for this program). Per the scoring rules, this mandate-shaped triple is convergence even though it is unglamorous.
Customer pain
Subrecipient nonprofits and small contractors must document, for every assisted household: income certification against LMI limits, duplication-of-benefits reconciliation against FEMA/SBA/insurance payouts, national-objective evidence, and accomplishment counts β€” then hand it to the grantee in a form that maps to DRGR activity codes. Today this is spreadsheets and shared drives; a single failed DOB file can force repayment. Pain severity is FACT-adjacent (the obligations are real and mandatory); the intensity of current tooling pain is HYPOTHESIS β€” no complaint/hiring evidence was supplied.
Who pays
Primary: subrecipients (nonprofits, housing developers, business-assistance operators) paying $200-500/mo or ~$25-50 per beneficiary record, funded from their admin/activity-delivery cost allowance β€” meaning federal money pays for the tool. Secondary: mid-size grantees (Manatee, St. Petersburg scale) that would rather hand subrecipients a standard intake tool than build one. Tertiary: the consulting firms (Horne, ICF, Tidal Basin class) that staff these programs and could white-label it.
Solved today
Large grantees buy Neighborly Software or hire disaster-recovery consultants who bill substantial fees against the grant; small grantees and nearly all subrecipients run Excel, PDF checklists, and email. The consultants' percentage-of-award billing is proof of existing spend and the competitive gap, per the scoring rules β€” the wedge is replacing consultant labor hours on documentation assembly with software.
Why current solutions are bad
Excel provides no DOB math, no audit trail, no LMI income-limit lookups, no DRGR-shaped export; consultants are expensive and their work product dies with the engagement; Neighborly is sold top-down to grantees via procurement and is heavyweight for a 4-person nonprofit subrecipient. Nobody sells bottom-up to the subrecipient layer.
Proposed product
A web app where a subrecipient case manager runs each assisted household/business through a guided intake: identity, income docs β†’ automatic LMI determination against HUD income limits; FEMA/SBA/insurance benefit entries β†’ DOB calculation worksheet with a signed reconciliation output; activity setup mapped to DRGR activity types β†’ one-click quarterly accomplishment export (CSV/PDF pack) the grantee can key into DRGR. Ships with a HUD-monitoring-visit file checklist per beneficiary. AI-assisted document extraction (pay stubs, award letters) is the labor-saving hook.
MVP version
Single-program build: LMI income-certification module (HUD income limits API/tables are public) + DOB worksheet + per-beneficiary document locker + QPR accomplishment export for housing-rehab activities only. 4-6 weeks solo with AI assistance. Validate the export format against the public DRGR user manuals and one friendly practitioner before writing code.
30-day build
Pull the action plans and subrecipient NOFAs for Houston, Hillsborough, Manatee, St. Petersburg (all public); list every named/likely subrecipient. Interview 5-8 subrecipient program managers and 2-3 independent CDBG-DR consultants (they are reachable on LinkedIn and at THDA/GLO-adjacent conferences) to validate the documentation workflow and price. Build the LMI+DOB core in parallel.
60-day build
Pilot with 1-2 subrecipients (free or $99/mo) in one Texas or Florida program; iterate the QPR export until their grantee accepts it. Publish a free 'CDBG-DR duplication-of-benefits calculator' and 'monitoring-visit checklist' as lead magnets β€” this founder sells through demonstrated value, and these artifacts demonstrate it.
90-day revenue plan
Convert pilots to $300-500/mo per subrecipient org; approach 2 boutique disaster-recovery consultancies with a white-label/reseller deal (they keep billing hours for judgment work, offload assembly). Target: 5-10 paying subrecipient orgs = $1.5-5K MRR by day 120-180, then replicate across the Florida cohort where three of the evidenced awards land.
Distribution path
Bottom-up and deadline-driven: public action plans name the programs; subrecipient award lists are public records (founder strength); direct outreach to named subrecipients timed to their quarterly reporting cycle; free DOB/LMI tools for SEO among a tiny, high-intent search population; consultant channel for scale. No procurement required at entry.
Pricing hypothesis
$300-500/mo per subrecipient org (unlimited beneficiaries) or $30/beneficiary record for small operators; grantee-level license $1.5-3K/mo for a template rollout across all their subrecipients. Priced far below one consultant-day per month, chargeable to grant admin costs.
Technical difficulty
Moderate and well inside the founder's lane: forms, document storage, rules-based calculations from public HUD tables, CSV/PDF export. No DRGR API integration exists or is required β€” DRGR is grantee-keyed, so the product exports grantee-ready data rather than submitting directly (this is a real limitation vs. his ELDT direct-submission model, stated as FACT about product shape).
Legal / regulatory risk
Low. The tool documents compliance; it does not certify it. Must avoid practicing 'grant administration' representations; standard disclaimers and SOC2-lite security posture (PII: income docs) are the real obligations. PII handling is a cost, not a blocker.
Platform dependency
None that can deplatform it β€” the 'platform' is a federal reporting regime with a 6-year spend window. Risk is program-lifecycle, not platform-policy: CDBG-DR is appropriation-driven, but disasters recur and $10B+ is already committed (inference on total; individual awards are FACT).
Founder fit
Near-maximal. This is exactly his proven ELDT shape β€” read the mandate, find the compelled filer, build the paperwork layer, charge per unit β€” applied to a filer class 100x better funded. Public-records skill locates every buyer; fire-service/emergency-management background gives credibility with disaster-recovery staff; no relationship-sales channel needed at the subrecipient tier. One honest deduction: unlike ELDT, there is no portal to submit into on the customer's behalf, so the moat is workflow + correctness, not portal integration.
Breakout potential
High within the niche: 20+ grantees in the 2025 cohort Γ— 10-100 subrecipients each (inference), a 6-year reporting tail per grant, and adjacent expansion into FEMA Public Assistance subrecipients (the $2.97B and $14.3B TDEM awards in evidence show the same pass-through structure) and CDBG-MIT. Fifty-state replication logic applies: each grantee is a near-identical market.
Final recommendation
PURSUE as a validation sprint, not a build commitment. The forced-buyer evidence is hard ($2.4B+ across six named CDBG-DR awards in the input alone), founder fit is near-perfect, and the subrecipient tier is structurally underserved. The single load-bearing unknown is whether subrecipients (vs. grantees) will pay β€” spend 30 days and ~$2K of runway on interviews and the LMI/DOB core before committing the full build.
Next action
Download the Houston, Hillsborough, and Manatee CDBG-DR action plans and subrecipient solicitations this week; build the list of named subrecipient organizations and book 5 interviews with their program/compliance managers.

Kill arguments (adversarial)

Competitors

β€’ Neighborly Software (link) β€” Dominant grantee-side CDBG/CDBG-DR case-management platform; sells top-down via procurement; the main foreclosure risk if a grantee mandates it for subrecipients (existence FACT; positioning from general knowledge, not supplied evidence).
β€’ Horne LLP / ICF / Tidal Basin (disaster-recovery consultants) (link) β€” Bill professional-services fees against grant admin budgets to run these programs β€” proof of existing spend and the fee pool to undercut; also potential white-label channel.
β€’ AmpliFund / eCivis (grants management suites) (link) β€” Generic grant-management SaaS; handles award tracking but not CDBG-DR-specific DOB/LMI beneficiary documentation β€” the specificity gap is the wedge.

Source citations (facts)

β€’ HUD CDBG-DR award to City of Houston β€” $314,645,000 obligated for disaster relief/recovery/mitigation; subrecipient activities include housing rehab, infrastructure, business assistance; intended beneficiaries are LMI households (FACT).
β€’ HUD CDBG-DR award to Hillsborough County β€” $709,324,000 CDBG-DR/CDBG-MIT obligation β€” evidence the 2025 cohort spans many grantees, supporting replication (FACT).
β€’ HUD CDBG-DR award to City of Chicago β€” $426,608,000 CDBG-DR/CDBG-MIT obligation to a second major-city grantee (FACT).
β€’ HUD CDBG-DR award to Manatee County β€” $252,711,000 obligation to a mid-size county grantee β€” the most reachable buyer profile (FACT).
β€’ HUD CDBG-DR award to City of St. Petersburg β€” $159,884,000 obligation; with Hillsborough and Manatee, three Florida-cohort programs for geographic clustering of early sales (FACT).
β€’ FEMA Public Assistance grant to Texas Division of Emergency Management β€” $14.3B pass-through to local-government subrecipients β€” evidence the same subrecipient-reporting structure exists in adjacent programs for expansion (FACT as to award; expansion fit is inference).

Actions