Loading blog content, please wait...
Three Dead-End Questions That Kill a Development Deal Before It Starts A good development deal and a bad one often start with the same lot, the same bud...
A good development deal and a bad one often start with the same lot, the same budget, and the same ambition. What separates them is usually the questions the developer asked at the front end. Some questions open doors.
A few of them quietly walk you into a wall.
Here are three that come up constantly, usually from capable, sharp people who are asking the wrong thing at the wrong moment. The trouble is that they feel like the right questions. They sound like due diligence.
They just happen to point you down a path that costs you time, money, or both before you ever pull a permit.
This feels like the natural first question, and it's the one that gets asked in a parking lot with a tape measure before anybody's read the zoning.
The problem is that "how much" is the answer, not the question. What you actually want to know is what the lot wants to become. A flat quarter-acre in East Nashville zoned RS5 can technically hold a single home, but if the parcel sits near a corridor that's seen upzoning activity, the smarter play might be waiting on a rezone, or buying the parcel next door and building two.
"How much can I build here" locks you into the lot's current rules the moment you ask it.
Ask what the highest and best use is given the neighborhood's direction, the setbacks, the slope, and what's actually selling two streets over. That question keeps your options open. The square-footage question closes them before you've looked at anything.
Developers who lead with maximum density often end up overbuilding for the block. A fourplex on a street of restored bungalows in Lockeland Springs isn't a win just because the zoning allowed it. The exit is the point, and the exit is set by the buyers who actually shop that street.
Everyone wants the number. It's the question a lender asks, the one your spouse asks, the one you ask yourself at 11pm. But when it's the first thing you solve for, it tends to drive every decision after it, and that's where deals go sideways.
Here's why it's a dead end in the wrong spot: construction cost is downstream of a dozen decisions you haven't made yet. Site prep, utility connections, the grading on a Nashville hillside lot, whether you're building to rent or to sell, the finish level the neighborhood supports... all of that moves the number. Chase a target build cost first and you start cutting from the wrong places, usually the ones buyers notice.
The better sequence is to pin down what the finished product needs to be and what it'll realistically sell or rent for, then back into what you can afford to spend. Cost isn't the first lever. It's the last one, and it only makes sense once the top line is real.
When a developer calls with a hard build budget and no clarity on the end product, the honest answer is that the budget is a guess dressed up as a plan. We'd rather slow that conversation down than hand over a number that falls apart the first time a utility quote comes back.
This is the one that sounds like optimism and functions like a trap.
"Can we make this work" almost always means "I already want this, help me justify it." And a lot of people in this business will happily oblige, because the answer to "can we make it work" is technically yes on nearly any deal if you stretch the assumptions far enough. Inflate the rent.
Shave the timeline. Assume the rezone goes through. Pretend the retaining wall is cheaper than it is.
You can make almost anything pencil on paper.
The question that actually protects you is the opposite one: what would have to be true for this to fail? If you can't answer that, you don't understand the deal yet. Maybe it fails if the comps don't hold.
Maybe it fails if the permit timeline runs long, which in Nashville it can. Maybe it fails if you can't get the right finish in at the right cost. Naming those first tells you whether the deal has a thin margin or a real one.
A deal that only works under best-case assumptions isn't a deal. It's a wish with a spreadsheet attached. The ones worth doing still look decent when you run them pessimistic.
This is honestly where a development consultant earns their keep. Not by telling you the lot is great, but by pressure-testing the thing you already like until you either trust it or walk. At Arrt of Real Estate, the version of this conversation that helps most is usually the one where we're pushing back, not cheerleading.
Notice the pattern in all three. "How much can I build," "what will it cost," and "can we make this work" are all questions that assume the deal is already a deal. They ask about execution before anyone's confirmed there's something worth executing.
The front-end questions that actually move you forward are quieter. What does this block want to become. What's the realistic exit.
What breaks this if it breaks. Those don't feel as productive because they don't produce a number you can put in a text to your partner. They produce something more useful, which is a clear read on whether you should keep going at all.
The best developers we work with aren't the ones with the biggest budgets or the boldest ideas. They're the ones who stay curious a little longer before they commit, who treat the first few questions as a filter instead of a formality. That patience at the start is usually what shows up as margin at the end.