Why So Much Housing Never Gets Built (Even When It Should)
Affordable housing doesn't get built for a lot of reasons. Land costs too much. Construction costs too much. Subsidy programs are competitive and oversubscribed. Local opposition slows or stops projects. Capital is available but not always patient enough for the timelines the process requires.
Each of these is real. Each contributes to the gap between how much affordable housing gets built and how much is needed. And each has attracted real attention from policy makers, investors, and advocates working to close that gap.
But there's a category of housing that's even harder to account for: housing that was never proposed because the decision to pursue it was never made. Housing that could have worked, in a market with available subsidy and viable sites, but that never entered the pipeline because the development team didn't have the capacity to evaluate it seriously.
This is the housing that never gets built even when it should — and it's more common than the public conversation about affordable housing acknowledges.
The decision that happens before any visible decision
Every affordable housing project that gets built starts with a decision that leaves no public record: a development team decides that a site is worth pursuing. Before the zoning application, before the program allocation, before the groundbreaking — someone evaluated a site and concluded that a viable deal was possible.
For every project that gets built, there are many sites that didn't make it through that initial evaluation. Some failed because they were genuinely infeasible — the land cost was too high, the program fit was wrong, the site conditions were prohibitive. Others failed for less fundamental reasons: the team didn't have bandwidth to evaluate them carefully, the relevant program information wasn't accessible, the site arrived at the wrong moment in the project cycle.
The housing that results from these non-decisions is invisible. It's not a cancelled project or a denied application. It's a project that was never proposed, never evaluated seriously, never given a real chance to exist. In aggregate, these non-decisions represent a substantial share of the gap between what the affordable housing system could produce and what it actually does.
Why lean development teams are the chokepoint
Affordable housing development is not a large-team business. Most active affordable housing developers — including organizations that produce dozens of deals per year — operate with acquisitions teams measured in single digits. A senior acquisitions director, an analyst or two, and enough administrative support to keep the pipeline organized.
That team can evaluate a finite number of sites per year at any reasonable level of rigor. When site volume exceeds evaluation capacity, triage happens — and the sites that get triaged out are not necessarily the worst sites. They're often the sites that arrived at the wrong time, in markets that the team knows less well, or in the queue position behind something that was taking longer than expected.
This capacity constraint doesn't show up in any policy analysis of why housing doesn't get built. It doesn't appear in funding gap analyses or construction cost studies. But practitioners feel it acutely, and it has direct consequences for how much housing gets produced.
The programs that exist but aren't fully utilized
The capacity constraint is compounded by a program utilization problem. Affordable housing subsidy programs — state and local soft loan programs, density bonus provisions, adaptive reuse incentives, opportunity zone equity — exist in many markets in forms that would enable deals that currently don't happen.
The barrier isn't that the programs don't exist. It's that development teams don't always know about them, don't always understand which sites they apply to, and don't always have the capacity to do the additional work of identifying and pursuing them.
A development team that evaluates a site against the two programs it knows well and concludes the deal doesn't pencil may have missed a third program that would have changed the outcome. That's not negligence — it's the natural result of operating in a complex information environment with limited staff and limited time.
The infrastructure gap
The systems that support affordable housing development — the information infrastructure, the workflow tools, the data resources — have not kept pace with the complexity of the task or the scale of the need.
Development teams are doing sophisticated financial analysis in spreadsheets. Program information is scattered across agency websites and informal networks. Site evaluation criteria are documented inconsistently or not at all. Institutional knowledge lives in the heads of senior staff who are perpetually stretched.
This infrastructure gap is solvable. Not completely, and not quickly — the complexity of affordable housing development is real and some of it is inherent. But the difference between the current state of the art and what's possible with better tools is large enough to materially affect how much housing gets built.
The housing that doesn't get built isn't always a policy failure or a market failure. Sometimes it's an execution failure — a deal that should have happened but didn't, because the infrastructure to make it happen efficiently wasn't in place.
Closing that gap doesn't require new programs or new capital. It requires better execution infrastructure. That's a more tractable problem than most discussions of the housing crisis acknowledge.
Alpha Deal is building the execution infrastructure for affordable housing development — reducing the friction that prevents viable projects from being evaluated, advanced, and built.