Why the Budget, Not the Energy Code, Is What Stops Housing
After 500+ developer conversations, the roadblock to new housing is not the energy code, it is the budget. Why cost-conscious compliance beats no project.
We spend a lot of time here talking about cutting costs, and that can look strange coming from a firm that is obsessed with doing things the right way. The honest answer is that after talking with more than 500 development companies over the last four years, one thing has become impossible to ignore. The biggest roadblock to new housing is not the energy code. It is the budget. A strict code looks beautiful on paper, but if it kills the numbers, the project never gets built, and a project that never gets built helps no one.
The Real Roadblock
Ask what stops housing from getting built and the easy answer is regulation. The energy code gets named a lot, because it is visible, it is technical, and it adds line items you can point at. But across hundreds of developer conversations, the code is rarely the thing that kills a deal.
The budget is. A development pencils or it does not. When the pro forma is tight, it does not matter how elegant the energy design is. If the cost to comply pushes the project underwater, the project dies, and the units that would have housed people simply never exist.
That reframes the whole question. The goal is not the most efficient building that could theoretically be drawn. The goal is a building that clears code and still gets financed. Those are different targets, and confusing them is how good intentions end up producing nothing at all.
The Perfection Trap
There is a habit in this industry of letting technical perfection get in the way of financial reality. It is easy for experts to get tunnel vision, and we catch ourselves doing it too. Triple-pane windows are genuinely excellent. So is a deep continuous insulation package and an aggressive air tightness target. On the right project, all of it is worth specifying.
The trap is treating the best available spec as the required spec. Every upgrade that is added out of habit rather than need is money that comes off the budget somewhere else, and on a tight deal that money is often the difference between breaking ground and shelving the plans.
The discipline is knowing what the project actually needs to comply, and stopping there. Yes, triple-pane windows are amazing. You know what is even better on a deal that barely pencils? A project that actually breaks ground. The best building nobody builds loses to the good building that gets financed every time.
When the Higher Spec Still Wins
Cost discipline is not an argument for the cheapest possible building. There are projects where the higher spec is the right call, and the point is to know which one you are on before you commit.
When a certification or program requires it. Passive House, an aggressive stretch or specialized code target, or an incentive program can make the higher spec mandatory rather than optional. There the premium is the price of entry, not waste.
When the operating savings clearly pay it back. On buildings the developer holds long term, a heavier envelope or better equipment can earn its cost back in utility savings and comfort. If the owner keeps the asset, the math can favor spending more up front.
When the spec buys margin the project needs. A better window or a tighter envelope is sometimes the cheapest way to clear a target, because it unlocks savings elsewhere in the model. In that case the higher spec is the cost-optimized answer, not the indulgent one.
When durability and marketability justify it. Acoustics, resale, tenant demand, and long-term maintenance are real reasons to build above code. Those are business decisions, made on purpose, not upgrades added because they looked good on a checklist.
The Decision Framework
None of this is an argument against building well. It is an argument against letting the pursuit of the absolute best kill the thing that actually matters, which is getting housing built. A modern, cost-conscious building is still a massive upgrade over the leaky 1950s neighborhood sitting right next door. Sometimes the best is not what the project needs. What it needs is to exist.
That is why the work is finding the least-cost path to compliance, not the most impressive one. And that path is not the same on any two projects. A different team, a different building, a different budget, and the cheapest way to clear code moves. The only way to know what your project actually needs, rather than what the spec sheet says it could have, is to model it. That is the whole reason we run a free feasibility study before anyone commits a dollar to the envelope.
Do that, and the energy code stops being the villain. It becomes one more constraint you design against, on a budget, so the building gets built instead of admired on paper.