A feasibility study is supposed to tell you if a development concept works. The real value shows up when it tells you the concept needs to change. In Raleigh, a first-pass site plan often looks strong on paper. Then zoning limits, site conditions, or cost realities push the numbers in a different direction. Below are the issues that most often force a developer to rework a concept before it reaches formal review.
Start the Feasibility Study With Clear Go-or-Change Benchmarks
Before you test a concept, set the numbers that define success. Decide on a minimum usable floor area. Set a target unit count. Pick the project type you actually want to build, whether that’s multifamily, mixed-use, or single-family lots. Set an investment range you’re willing to work within.
These numbers give you a baseline. Once the study starts pulling in real site data, zoning limits, and cost figures, you can compare the results against that baseline. If the concept falls short, you’ll know right away. Maybe the unit count drops below what makes the deal work. Maybe the usable floor area shrinks once setbacks and stormwater requirements come into play.
Without a baseline, a feasibility study becomes a list of findings with no clear conclusion. With one, you get a straight answer: keep the concept, shrink it, reposition it, or replace it with something else entirely.
Compare a By-Right Concept With a Rezoning-Dependent Alternative
Look at two versions of your concept side by side. One fits within what current zoning allows. The other depends on a rezoning approval.
Raleigh’s Unified Development Ordinance sets specific rules for building height, setbacks, street frontage, and the pattern of development allowed on a given site. A concept that fits inside those rules can move forward with far less uncertainty. A concept that needs a rezoning carries a different kind of risk. Rezoning approval isn’t guaranteed. It takes time. It can bring conditions you didn’t plan for.
Running both versions through the feasibility study gives you a clear picture. You’ll see the yield gap between the by-right option and the rezoning-dependent one. You’ll also see how much time and cost separates them. That comparison often changes which concept a developer decides to pursue first.
Identify the Small Changes That Create a Cost Cliff
Some changes to a development program cost what you’d expect. Others cost far more than they should, given how small they look on paper.
Add one more building to a site plan, and you might trigger a full traffic study you didn’t need before. Push a project past a certain unit count, and a different tier of stormwater review can kick in. Change the proposed use from office to residential, and the required parking ratio might shift enough to eliminate a row of units.
These jumps don’t scale evenly. A small increase in building area can trigger a much larger increase in review requirements. Spotting these cliffs early, while the development program is still on paper, gives you the chance to adjust before the number of required studies and supporting improvements grows past what the project can support.
Stress-Test the Development Concept Against a Lower Yield
Most first-draft concepts get modeled at their best possible layout. Full unit count. Maximum building area. Every square foot of rentable space accounted for.
That layout rarely survives contact with the actual site. Run the numbers again at a lower yield. Cut the unit count by 10 or 15 percent. Shrink the building footprint to account for a wider buffer or an unexpected easement. Reduce the rentable square footage to reflect a more realistic core-to-floor ratio.
If the project still works at that lower number, you have a concept with some room to absorb bad news. If it doesn’t, you’ve learned something important before spending money on design and permitting. A concept that only works at its best-case numbers isn’t a concept you can rely on.
Preserve an Alternate Concept When the Preferred Plan Fails
Keep a second concept ready while the feasibility study moves forward. A smaller footprint. A different mix of uses. A phased approach that builds out over two or three stages instead of one.
Raleigh’s site review process pulls in several municipal disciplines at once, including transportation, stormwater, and utilities. Each one can raise a question that affects the preferred concept. If one of those questions turns into a real problem, having a fallback ready means you’re not starting from zero.
This doesn’t mean building out two full sets of drawings. It means keeping the second concept far enough along that you know its rough numbers, its rough footprint, and its rough timeline. That’s enough to make a fast decision if the first concept runs into a wall it can’t get past.
Frequently Asked Questions
Can a Feasibility Study Recommend a Smaller Development?
Yes. A study can show that a reduced or revised concept gives you a more realistic balance between what you can build, how much uncertainty you’re carrying, and what the project costs.
Does a Feasibility Study Guarantee Approval in Raleigh?
No. A feasibility study works with the information available at the time. It doesn’t guarantee zoning approval, site plan approval, permit approval, financing, or construction approval.
What Is the Difference Between a Feasibility Study and a Raleigh Sketch Plan Review?
A feasibility study supports your own internal decision-making. Raleigh’s Sketch Plan Review is a voluntary process that lets you discuss a site-specific concept with a team of city staff from different departments before you submit a formal application.
When Should a Feasibility Study Be Updated?
Update the study after any major change: a different proposed use, a change in property boundaries, a revised development program, new acquisition terms, updated regulations, or any other major assumption that shifted since the last version.
What Happens When a Key Feasibility Assumption Cannot Be Confirmed?
Document the uncertainty. Assign it a risk range instead of guessing at a single number. Then test the concept against an alternative that accounts for that uncertainty, rather than treating an unconfirmed assumption as a settled fact.
