Loading blog content, please wait...
The Consultant Who Draws Your Plans and the One Who Tells You What to Build Are Not the Same Person You've got a lot under contract off Charlotte Pike, ...
You've got a lot under contract off Charlotte Pike, the survey's in your inbox, and your architect just sent over a first massing study that looks sharp. Townhomes, tucked density, a nice courtyard. It's a good drawing. The question you can't answer by looking at it is whether townhomes are the right thing to build there at all, and that question sits with a different person entirely.
This is one of the most common mix-ups we see in Nashville development, and it's an expensive one. People assume the person who can draw the building is also the person who can tell them what building to draw. Those are two separate jobs. Confusing them costs money, time, and sometimes the whole deal.
An architect is exceptional at a specific thing: taking a defined program and turning it into a buildable, permittable, good-looking set of plans. Give them a site and a brief that says "eighteen for-sale townhomes with two-car garages," and they'll solve it beautifully. Setbacks, grades, unit mix, elevations. That's real skill and you need it.
But notice what the architect started with. A brief. Somebody handed them "eighteen for-sale townhomes." Where did that come from? Should it have been twelve larger units at a higher price point? A small multifamily building held as a rental? A build-to-rent cluster instead of for-sale? Should you build at all, or is the smarter play to entitle the land and sell it?
That's development strategy, and it's upstream of the pencil ever touching paper. It's the difference between drawing the thing right and drawing the right thing. An architect who's honest will tell you they're not the one who sets the program. They execute it. When a builder or landowner treats the architect as the strategist by default, the plans come out gorgeous and the pro forma comes out underwater.
The instinct is to get plans first because plans feel like progress. Something tangible. You can show them to a lender, a partner, your spouse. But plans built on the wrong assumptions are just an expensive, detailed way of being wrong.
The strategic question comes first. What does this specific site, in this specific Nashville submarket, actually want to be? That answer depends on things a set of plans can't see: current absorption for the product type in that pocket, what's trading and at what per-unit price, where rents are landing this summer versus where they were, what the zoning and the Metro Planning process will actually allow versus what a variance would require, and what the numbers need to look like for a lender to say yes in a 2026 rate environment that is not the 2021 one.
Only after that gets settled does a program exist. And only then does an architect have a real brief to draw against. Do it in that order and the plans are cheaper too, because you're not paying for three redesigns as reality catches up with the concept.
This is the gap we fill at Arrt. Development consulting isn't design, and we're careful about that line. We don't draw your building. We help you decide what building is worth drawing, and whether the site supports it before you've spent real money finding out.
Practically, that means pressure-testing the concept against the market as it is right now, not as it was. It means running the pro forma with honest numbers, the ones that account for Nashville's current construction costs, the timeline through Metro's process, and a sale or lease-up that reflects today's demand rather than a hopeful memory of it. It means telling you when the highest and best use of your Nolensville Road parcel is not the thing you already fell in love with. Sometimes the most valuable thing we say is "build fewer, larger units" or "this is a hold, not a flip" or "the entitled land is worth more than anything you'd construct on it."
Then, once that strategy is locked, your architect has a real target. They can do their best work because someone did the "what" and "whether" first. The two roles stop stepping on each other and start reinforcing each other.
A simple test. If the discussion is about setbacks, elevations, unit layouts, materials, and code, you're in a design conversation, and your architect owns it. If the discussion is about product type, unit count, price point, hold versus sell, phasing, or whether the deal pencils at all, you're in a strategy conversation, and that's a different chair.
Watch for the moment they blur. It usually sounds like "well, we could probably fit twenty-two units on here," said while looking at a site plan. That's a design observation getting quietly promoted into a business decision. Fitting twenty-two units and selling twenty-two units at a price that works are not the same claim, and the drawing can't tell you which is true.
The zoning piece deserves the same separation. What's buildable under current zoning, what a rezoning realistically gets you, and how long Metro's process runs are questions of feasibility and risk, not aesthetics. If you want to see how the public side of that process is structured before you lean on anyone's read of it, Metro Nashville Planning publishes its rezoning and development review process directly.
When one person is quietly doing both jobs, nobody's checking the strategy against the market, because the strategist and the executor are the same set of eyes. You lose the second opinion that exists precisely to catch the expensive assumption before it gets drawn, priced, and permitted.
Keep the roles distinct and you get two things pulling in the same direction. Someone accountable for whether the deal makes sense, and someone accountable for making the approved concept beautiful and buildable. Bring the strategy conversation in early, before the first massing study, and the drawings you eventually pay for are drawings of the right thing. That's the whole game.