Real Estate Development Only Works If the Rules Let It

Hello everyone! 👋

The more I learn about real estate development, the more I realize how little of it is just about the building itself.

At first glance, development feels like a design-and-construction problem. You find a site, come up with a concept, run the numbers, and build. Simple enough — at least on paper.

But once you look a little closer, that picture changes fast.

Because even if a site looks promising, even if the market looks strong, and even if the design looks great, none of it really matters unless the project can survive the rules around it. Zoning , entitlements , environmental review, public process, timing, political risk, and local approvals can shape a project just as much as architecture or construction cost.

That’s what made this topic interesting to me.

This part of development is less visible than cranes and renderings, but it might be even more important. It’s the layer that decides whether an idea stays an idea or actually becomes a project.

In this post, I want to share a simple way to think about that layer — from land pricing and residual value to entitlements, zoning, and why approval risk can completely change the economics of a deal.

Before anything else, land has to be priced rationally

There is one idea here that is both simple and incredibly useful:

A developer cannot just ask, “What is the seller asking for the land?” They have to ask, “What is the land actually worth to this project?”

That is where the land residual idea comes in.

The logic is straightforward. Start with what the finished project is expected to be worth. Then subtract what it costs to build. Then subtract the profit the developer needs for the deal to be worth doing. What is left over is the residual amount available for land.

For example, if a finished apartment building is worth $50M, and it costs $35M to build (including financing and indirect costs), and the developer requires a $7M profit (roughly 15% of cost), the most they can pay for the land is $8M.

Another way to say it is this:

This matters because overpaying for land is often where bad deals begin. A project can look exciting, but if the land cost already consumes the margin, the rest of the project has to work harder just to recover from that first mistake.

And yes, a developer can pay more than the residual suggests. But if that happens, there should be a very real reason for it — not optimism, not vague hope, and definitely not magical thinking.

Without entitlements, a project is still just an idea

Another idea that stood out to me is how brutally simple this part is:

Without permits, you do not really have a project yet.

More broadly, without entitlements, development is still stuck at the idea stage.

A Entitlement is basically the legal approval structure that allows a site or building to move forward. Without it, the project might exist in sketches, spreadsheets, and conversations, but not in a way that can actually proceed.

What I like about this part of development is how honest it is. It is not just about what you want to build. It is about what the government will legally allow you to build, under what conditions, through what process, and at what cost in time and money.

That is a very different question.

Entitlements are not just paperwork — they are cost and schedule

It is easy to treat permits and approvals as paperwork. In reality, they can become major cost drivers.

That happens directly through consultants, filings, redesigns, hearings, studies, and legal work.

And it also happens indirectly through time.

Because every extra month in entitlement review means more carrying cost, more uncertainty, more exposure to market changes, and more chances for the project assumptions to drift away from reality.

That last part matters a lot. A project delayed long enough is no longer the same project economically, even if the drawings still look similar.

California adds another layer: the state matters too

A really important point here is that development is not governed only by the city.

There is a hierarchy.

In California, state law sits above local implementation. Cities and counties do not get to ignore state rules just because a local project wants to move faster. They work within that larger framework.

That hierarchy matters because a site may look straightforward locally, but still be shaped by statewide environmental law, coastal regulation, building standards, or housing legislation.

So when developers talk about “the rules,” they are almost never talking about just one rulebook or one approval body.

CEQA can reshape the whole deal

If there is one law in this topic that can materially change how a California project moves, it is CEQA .

CEQA matters because it often sits between a discretionary project and its approval. Before a city or county signs off, the team may need to study traffic, noise, air quality, shade and shadow, historic resources, biological impacts, and other site-specific effects.

So CEQA is not just a box to check. It can determine what consultants you hire, what studies you pay for, what mitigation you promise, and how much redesign the project absorbs before approval.

What makes CEQA especially consequential is not just the report itself. It is everything the process pulls in behind it.

It can mean traffic engineers, acoustical consultants, air-quality analysis, biological review, legal coordination, and multiple rounds of public comment. It can force changes to circulation, building massing, access, hours of operation, landscaping, or mitigation commitments. It can stretch the approval clock long enough for financing costs, market assumptions, and political dynamics to change underneath the deal.

That does not make CEQA meaningless. It makes CEQA powerful.

And any approval process with that much leverage will be used strategically — sometimes to protect real environmental interests, sometimes to negotiate changes, and sometimes simply to slow a project down.

The coastal zone is not just geography — it is regulation

Another point that stood out to me is how a map can change a project before any design work even begins.

The coastal zone is a good example of that. Once a site falls within that regulatory geography, another layer of rules comes into play. And those rules can affect height, design, review requirements, and the basic range of what is feasible.

I like this example because it shows that location is not just about market access or views. It is also about regulatory identity.

Two sites can look similar in a sales package and still carry very different approval realities.

Zoning quietly decides what is even possible

Zoning is one of those terms people hear all the time, but its real power is easy to underestimate.

At a practical level, zoning answers questions like: What use is allowed here? How much can be built? How tall can it be? How far back does it need to sit? What kind of project belongs on this parcel?

That is why zoning is not just background information. It is the first filter on what can be built here at all.

The traditional model in much of the US is Euclidean zoning, which separates uses into categories like residential, commercial, and industrial. But cities are also layering in more flexible ideas, including incentive zoning and mixed-use patterns, especially where they want more housing or more active urban environments.

That makes zoning feel less like a static map and more like a living negotiation between legacy rules and current policy goals.

There is a big difference between by-right and discretionary

This may be the most practically important distinction in the whole topic.

Not all projects go through the same approval path.

Some are by-right, or ministerial. That means the project is already allowed under the rules, and staff simply checks whether it complies with the applicable codes. There is no policy judgment there. The question is basically binary: does it conform or not?

Others are discretionary, which means a decision-making body has to review and approve the project. That introduces more time, more cost, more uncertainty, and more room for public opposition or political risk.

This difference matters a lot because the same site can feel entirely different depending on which side of that line the project falls.

A by-right project is still work, but it offers more predictability.

A discretionary project might offer more upside, but it also carries much more process risk.

Discretionary approval gets expensive because nothing else stands still

What makes discretionary approval hard is not just that it takes longer.

It is that the whole deal stays exposed while the clock is running.

Construction bids can rise. Interest rates can move. Rents and exit values can soften. Equity partners can change their terms. Staff comments or public hearings can force redesign. Neighborhood opposition can turn a manageable process into an appeal fight.

So the real cost is not just delay. It is carrying cost plus the risk that the original deal no longer pencils by the time approval arrives.

That is why experienced developers are usually very careful about taking on projects that require complex discretionary approvals unless the upside clearly justifies the risk.

Architects are involved earlier than people think

I also liked the reminder that architects are not only there at the end to make a project look good.

They often get brought in early to answer a much more practical question:

What can actually fit here?

That means they help with feasibility, massing, constraints, and translation. They help turn a rough idea into something visible enough for developers, investors, lenders, and consultants to react to realistically.

That role feels especially important because development decisions often happen before anyone has a polished set of drawings. At that stage, the architect is helping test reality, not just compose aesthetics.

A parcel is governed by layers, not a single yes-or-no rule

One thing that becomes obvious after looking at this topic is that no single map or single department tells the whole story.

A site can be shaped by:

• state law,
• local zoning,
• community plans,
• overlay zones,
• building code,
• environmental review,
• and the approval type itself.

That means site analysis is really layered analysis.

This is why development feels so different from the outside versus the inside.

From the outside, a site can look like an opportunity. From the inside, it looks like a stack of constraints that need to line up well enough for the opportunity to become real.

The hidden skill is knowing when not to force the deal

The more these pieces come together, the clearer one thing becomes:

A lot of development skill is not just about imagining a project. It is about knowing when the site, rules, timing, and economics align well enough to justify moving forward.

That means:

• not overpaying for land,
• not underestimating approvals,
• not ignoring entitlement timing,
• not assuming public process will go smoothly,
• and not pretending that every attractive site is actually buildable in a profitable way.

In that sense, the rules are not just obstacles. They are filters.

And sometimes the smartest thing a developer can do is not push harder — it is recognize earlier that the deal is weaker than it first appeared.

A few practical lessons I’m taking away

If I had to reduce this topic into a few takeaways, they would be these:

• A site is only worth what the finished project can support after costs and profit.
• Entitlements are part of the project, not an afterthought that happens in the background.
• Time is a real development cost that changes the math while you wait.
• CEQA can shape a deal far beyond simple environmental checkboxes.
• Zoning quietly controls more than most people realize about urban development.
• By-right and discretionary projects may look similar from far away, but they behave very differently in real life.
• The best development decision is often not redesigning the deal — it is refusing to fool yourself about it.

That last one might be the most valuable of all.

Because in development, discipline is not only about saying yes to the right site.

It is also about saying no before the wrong site gets too expensive.