Phoenix market

Phoenix’s shortage lives between proposed and approved

· 5 min read

Every conversation I have about Phoenix housing ends up in the same place: we are not entitling enough of it. People usually look for the shortage in land, capital or developers willing to build. Most of it sits in the gap between what gets proposed and what gets approved.

What a reduction costs

We recently went through a density modification with the City of Phoenix on our North Phoenix site. The arithmetic behind that kind of request is simple, and it is rarely stated plainly.

A project that pencils at 750 homes and gets approved at 400 does not become a cheaper project. Almost none of the cost that made it expensive goes away. The land is the same land. The offsite work, the utility connections (where there may be small savings), the traffic study, the years of carry, the architects, the attorneys and the entitlement process itself all cost close to what they cost whether you end up with 750 homes or 400. The only thing that changes is how many homes those fixed costs are divided across.

So each home costs more, and some of the cost ends up in the rent.

The point

Cutting density leaves the cost where it was and spreads it over fewer households, so each of them pays more rent.

Why the process is careful, and why that is fair

Neighbors have a real stake in what gets built next to them, and they should. Somebody who bought a house on a quiet street is entitled to ask what a new building will do to their traffic, their view and their evening. Those are legitimate questions. Treating them as obstruction is wrong, and in practice it is a good way to lose.

In return, I would ask that the conversation include the cost of saying no, or of saying yes to less. Somebody pays that cost, and they are usually not in the room: the household that will rent an apartment in this city in three years, at a price set by how much housing we built.

The neighborhood meeting

Developers complain about neighborhood meetings. I have come to think they are the most useful two hours in the entire entitlement process.

The objections you hear in the room are the ones that would otherwise show up later in writing, at a hearing or in a lawsuit. In the room you can still answer them. Later you can’t, because by then the objection has hardened into a position and somebody has attached their name to it.

Most of what people want to know is concrete: how tall, how much traffic, what happens to the view, what it looks like from their street, where the construction trucks go and for how long. Those questions have answers, and the plans that get approved usually belong to developers who gave them early and without boilerplate.

The most useful thing a developer can do is go to that meeting in person rather than send a consultant, explain the plan in plain terms, and take the questions.

The timing problem nobody controls

Our North Phoenix site sits near the TSMC corridor. A project of that scale raises a simple housing question: thousands of people will need somewhere to live within a reasonable drive of it.

Fabs get built on an announced schedule, with a completion date attached and enormous pressure to hit it. Housing gets built on an entitlement schedule, which runs at a different speed: it has no announced completion date and answers to a different set of incentives entirely.

When the two diverge, rents rise in the housing that already exists, because the new households arrive on the fab’s schedule and compete for the stock we have.

Conversion is one of the few tools that closes the gap quickly, because the structure is already standing, and that is a large part of why we are doing it. It won’t solve the whole problem. It is available now rather than in four years, though, and at the moment nothing matters more.

The North Phoenix site and its current status are on the projects page.