Small sites are where feasibility gets interesting.

On larger parcels, there is usually more room to solve design problems. You can absorb inefficiencies with a ramp, structured parking, internal circulation, or a larger footprint. But on very small sites, every constraint becomes more important. A few feet can change the entire outcome.

Recently, I was looking at a tiny listing in Edgewater: a 4,950 SF lot. The site is actually about 50 SF short of the minimum lot size, which means it would already need a variance.

Most people would probably look at a parcel like this and say:

“Wait for assemblage. You’ll never make the parking work.”

That may be the right answer.

But I wanted to test the edge case.

Explore the live experiment here:
Hotel vs. Multifamily Feasibility Study

The Question

For this site, I wanted to test a simple feasibility question:

What can I build if I keep all required parking on the ground floor?

That may sound like a small constraint, but on a 4,950 SF parcel, it becomes the main driver of the project.

The site may have theoretical density, but the real question is whether that density can actually survive the physical layout.

Can the parking fit?

Can cars circulate?

Can the building stack efficiently above it?

Can the project avoid a ramp entirely?

Those questions can change the answer very quickly.

The Programs Compared

I ran a quick comparison between two uses: multifamily and hotel.

For the study, the assumptions were:

Multifamily

150 units per acre

1.5 parking spaces per unit

Hotel

300 keys per acre

0.5 parking spaces per key

At first glance, both uses seem possible.

By density alone, the site could theoretically support approximately:

17 residential units

or

34 hotel keys

But density is only one part of the story.

The more important question is what happens when parking is added back into the geometry.

When Parking Changes the Answer

Once the parking requirement is included, the feasibility changes quickly.

In the multifamily scenario, the site fits:

7 units

11 cars

In the hotel scenario, the site fits:

20 keys

10 cars

Same site.

Same general massing logic.

Very different outcome.

The hotel scenario performs better on this parcel because the parking requirement is much lower relative to the number of keys. At 0.5 spaces per key, the hotel program can carry significantly more usable density while still keeping parking on the ground floor.

The multifamily option has density on paper, but the parking ratio consumes the site much faster.

Theoretical Density vs. Buildable Geometry

This is the part of feasibility that is easy to miss in early conversations.

A site may appear to allow a certain number of units or keys based on density calculations, but that does not mean the building will actually work.

The geometry has to cooperate.

Parking, circulation, setbacks, floor plates, structural logic, and access all have to be tested together. On small sites, these are not secondary details. They are often the main feasibility drivers.

That is why a use that looks less obvious at first can sometimes become more compelling once the layout is tested.

In this case, the initial assumption might be that multifamily is the more natural use. But after testing parking and geometry together, the hotel scenario becomes much more interesting.

That does not mean hotel is automatically the right answer. There are still questions about market demand, operations, entitlement risk, construction cost, financing, and exit value.

But it does mean the conversation changes.

Instead of only asking:

“What is allowed?”

we can ask:

“What actually fits?”

And more importantly:

“What creates the best development logic for this specific site?”

The Takeaway

Small sites force clarity.

They expose the difference between zoning capacity and physical feasibility. They show how parking ratios can quietly determine the highest and best use. And they remind us that development is not just about what a code table allows.

It is about what can actually be drawn, parked, built, and operated.

For this 4,950 SF site, the difference was significant:

Multifamily: 7 units, 11 cars

Hotel: 20 keys, 10 cars

Same parcel. Same constraint. Different outcome.

That is why I like testing these scenarios early.

Sometimes the best insight is not hidden in the pro forma.

Sometimes it is hiding in the parking layout.

Explore the live experiment here:
Hotel vs. Multifamily Feasibility Study