What changed
FY26 Capital Fund Program money is landing now: USAspending shows a $724,303,359 CFP award to NYCHA and a $178,298,058 award to Puerto Rico's housing authority (FACT, cited). The award text itself states the CFP funds ~2,770 PHAs serving nearly one million units in all 50 states, with eligible activities governed by 24 CFR Part 905 (FACT). HUD also just published FY2026 Renewal Funding Inflation Factors for every PHA (FACT), confirming the annual PHA funding cycle is in motion.
Why now
Every CFP dollar comes with paperwork attached: activities must be specified in an approved 5-Year Action Plan before funds can be spent (FACT from award text; that this is form HUD-50075 submitted via HUD's EPIC system, with drawdowns through LOCCS, is INFERENCE). Statute imposes obligation/expenditure deadlines on CFP grants with recapture as the penalty (HYPOTHESIS from general knowledge of Section 9(j) of the 1937 Act — verify; the award text confirms only 'eligibility documentation under 24 CFR 905'). New grant year = every PHA's plan and deadline clocks reset now.
Converging signals
Three signals meet at one point, which per the system's own heuristic IS convergence: (1) appropriated money flowing (multiple FY26 CFP/Operating Fund awards on USAspending, FACT), (2) a defined compelled filer class (~2,770 PHAs, FACT from award text), (3) a named regulatory framework and plan requirement (24 CFR 905, approved 5-Year Action Plan, FACT). A high-confidence system lesson (0.79) says this government-portal mandate shape is the founder's best fit.
Customer pain
Small PHAs (a few dozen to a few hundred units) receive five-to-low-six-figure CFP grants but have no dedicated grant-admin staff (HYPOTHESIS, stated in convergence input; consistent with the long small-PHA tail implied by 2,770 agencies / ~1M units where NYCHA alone is a huge share). For them the 5-Year Action Plan, eligible-activity mapping, budget line items (BLIs), and obligation/expenditure tracking are an annual scramble handled by the ED or an outside consultant. Missed obligation deadlines risk recapture of the grant (HYPOTHESIS as to mechanism; the compulsion to plan/document is FACT).
Who pays
The PHA itself, out of the grant: CFP explicitly funds 'management improvements' and administration (award text lists management activities as eligible, FACT) — meaning the software can plausibly be paid for with the federal money it manages (INFERENCE; verify 905.200 admin cost treatment). Buyer is the Executive Director or finance/modernization coordinator of a small/mid PHA. At $1–4k/yr this sits under micro-purchase/simplified-acquisition thresholds, so no formal procurement (INFERENCE).
Solved today
Large PHAs use enterprise housing suites (Yardi PHA/Voyager, MRI/Tenmast, Emphasys, HAB — HYPOTHESIS, verify coverage of Capital Fund planning specifically). Small PHAs use spreadsheets, HUD's own EPIC screens, and fee-for-service consultants (e.g., Nan McKay-style firms) who charge for plan preparation (HYPOTHESIS — no consultant-spend evidence in the input; the system's forced-buyer rule says the class is already paying staff, a consultant, or a penalty).
Why current solutions are bad
Enterprise suites are priced and scoped for big authorities; EPIC is a data-entry portal, not a planning or deadline-management tool; consultants are episodic, cost more per year than software, and leave nothing behind. Nobody gives a 50-unit PHA a cheap standing system that says 'here is your compliant plan, here is what each project maps to in 905, here is your obligation clock' (INFERENCE — this gap is the core unverified bet; competitor scan is the first kill-test).
Proposed product
CapFund Copilot: web app where a PHA enters its grant amounts and project list; AI drafts the 5-Year Action Plan narrative in HUD-50075 structure, maps each project to a specific 24 CFR 905 eligible-activity/BLI code with the regulatory citation, produces the public-hearing/board-resolution artifacts, and runs a compliance calendar (plan approval, obligation and expenditure deadlines, P&E reporting) with escalating alerts. Output is EPIC-ready content; the founder does NOT need HUD's permission because the PHA submits via its own EPIC access (no platform owner can deplatform a document-preparation tool; direct API submission is not assumed).
MVP version
Single-tenant web app: grant + project intake form → generated 50075-format plan document and 905 activity mapping table → deadline dashboard with email alerts. No EPIC integration in v1 (copy-paste/upload artifacts). Built solo with AI assistance in 4–8 weeks; this is squarely inside the founder's proven ELDT-portal pattern minus the harder submission automation.
30-day build
Kill-test first: (1) desk-verify the paperwork chain — HUD-50075 forms, EPIC user guides, 905 subpart C obligation/expenditure rules (all public); (2) pull the public PHA contact list from HUD and interview 10–15 small-PHA EDs (fire-service/operations credibility helps here); (3) confirm what Yardi/MRI/HAB actually cover and what consultants charge; (4) build the 905 activity-mapping engine and plan generator against 3 real published 5-Year Plans (they are public records — founder strength).
60-day build
Working MVP seeded with 2–3 design-partner PHAs at $0–500 founder-deal pricing in exchange for testimonials; generate their FY27 draft plans; add the deadline dashboard; collect the 'this saved us a $6k consultant' quote.
90-day revenue plan
Direct email/call campaign to the small-PHA tail (contact data is public), state NAHRO chapter newsletters, and PHADA/NAHRO conference presence. Convert design partners to $1.5–2.5k annual subscriptions; target 10–20 paying PHAs (~$20–40k ARR) inside 180 days, timed to the next plan-submission cycle.
Distribution path
Direct outreach using HUD's public PHA directory (a public-records play, founder strength); state NAHRO chapters and PHADA as amplifiers; content SEO on '5-Year Action Plan template', 'CFP obligation deadline', 'EPIC submission' — low-competition queries (INFERENCE). Consultants themselves are a second channel: white-label the tool to the firms serving dozens of PHAs.
Pricing hypothesis
$1,500–2,500/yr per PHA flat (under micro-purchase threshold, payable from CFP management-improvement funds); consultant/white-label tier $5–10k/yr. 10% of 2,770 PHAs at $2k ≈ $550k ARR (INFERENCE from FACT count).
Technical difficulty
Low-moderate: document generation, a rules table encoding 24 CFR 905.200 eligible activities, and a deadline engine. The regulation is stable and public. Hardest part is domain correctness, not code — mitigated by using real published plans as ground truth.
Legal / regulatory risk
Low. Tool prepares documents the PHA reviews and submits itself; not legal advice if positioned as software + templates. No license required for the founder. Main risk: an AI-drafted plan with a wrong activity mapping causes a finding — mitigate with citation-per-line-item and human-review gating.
Platform dependency
HUD could redesign EPIC or the 50075 form (it periodically does), forcing template updates — maintenance burden, not existential. No deplatforming risk on a government system.
Founder fit
Near-maximal and the input's own lessons say so (0.79-confidence heuristic). This is the ELDT playbook replayed: federal mandate → defined compelled filer class → portal submission → per-seat fee. Founder's public-records skill covers the PHA directory and published plans; operations background matches the buyer's world (capital projects, modernization, physical plant).
Breakout potential
Moderate-high: the same PHA buyer must also file PHAS/NSPIRE, SEMAP, Operating Fund, and Annual Plan paperwork — land with Capital Fund, expand across the PHA compliance calendar. Adjacent expansion: the identical plan-and-deadline shape exists for EPA SRF subrecipients (multiple DWSRF capitalization grants in the evidence set, FACT they exist; the subrecipient paperwork parallel is INFERENCE).
Final recommendation
PURSUE, gated on a 2-week kill-test. The forced-filer structure is real and cited (2,770 PHAs, 24 CFR 905, approved-plan requirement, live FY26 money), founder fit is the proven ELDT shape, and the buyer can pay from the grant itself. The single unverified load-bearing assumption is the competitive gap for the small-PHA tail — verify by interviewing 10 small-PHA EDs and scanning incumbent feature lists before writing product code.
Next action
Download HUD's public PHA contact directory, filter to PHAs under ~400 units in 2–3 states, and book 10 ED interviews this week asking exactly two things: who prepared your last 5-Year Action Plan and what did it cost; what tracks your obligation/expenditure deadlines today.