Loading blog content, please wait...
Your Architect Wants to Draw; Your Consultant Wants You to Wait Two people you hire early in a project will pull you in opposite directions, and both of...
Two people you hire early in a project will pull you in opposite directions, and both of them are doing exactly what they should. The architect is ready to put pen to paper because that's the work you brought them in for. The consultant, if they're doing their job, is going to slow you down before a single line gets drawn.
That tension isn't a problem to fix. It's a sign the project has both halves it needs.
An architect gets paid to design, and most good ones genuinely love the part where the site turns into a building. You show up with a lot off Charlotte Avenue or a tired duplex in East Nashville, and their mind is already placing the massing, the setbacks, the way morning light hits the front units.
That momentum is valuable. You want a designer who's excited about your project, not one going through the motions.
But excitement about the drawing isn't the same as certainty about what should be drawn. An architect can produce a beautiful schematic for a building that the pro forma won't support, or that the zoning quietly won't allow at the density you're assuming. The plans look real, which makes them feel like progress even when the underlying question hasn't been answered yet.
The consultant's whole job is upstream of the design. Before you spend money on schematics, they want to know the deal pencils, the site can physically carry what you want, and the approvals path is realistic for this parcel in this part of town.
Waiting, in this context, isn't hesitation. It's sequencing.
The questions they're holding you on are the ones that get expensive to answer late: How many units does the zoning genuinely permit after setbacks and parking? Does the topography force a retaining wall that eats your margin? Is there a utility or easement issue that changes the buildable footprint?
Every one of those reshapes the design, so answering them before the architect draws saves you from paying to draw twice.
The friction usually shows up around week two or three, when the architect is ready to move and the consultant is still saying "let's confirm a few things first." You're paying both of them. It feels like one is slowing down the other, and it can be tempting to just let the drawings start so something visible is happening.
Visible isn't the same as valuable, especially early. A set of schematics you have to throw out because the density assumption was wrong is more expensive than a two-week pause that gets the assumptions right.
The healthy version of this collision is a consultant who defines the box the architect designs inside. Zoning limits, budget ceiling, unit mix the market will actually absorb, site constraints that are real and not theoretical. Once that box is clear, the architect isn't held back at all.
They're finally free to draw something that survives contact with reality.
Nashville rewards this sequencing more than a lot of markets, because our zoning and our terrain both hide surprises. A flat-looking lot in Sylvan Park can carry more slope than it shows. A commercial parcel near Wedgewood-Houston might read like an easy conversion until you look at the specific overlay and parking math.
The consultant's pause is where those get caught. It's cheaper to find them on a title report and a survey than in a redesign.
There's also the approvals reality. Whether you're going through a rezoning, a subdivision, or a straightforward permit, the assumptions baked into your first drawings tend to follow the project all the way to the finish line. Fix them at the start, and you're not fighting them at every stage after.
The move isn't to pick a side. It's to run them in order and let each one own their phase.
Bring the consultant in first, or at least early enough that the feasibility questions get answered before the design budget starts spending. Let them define what's buildable, what's approvable, and what the numbers can support. That's the front-end work our team at Arrt of Real Estate tends to sit inside, and it's the phase that quietly determines whether everything downstream goes smoothly.
Then hand the architect a clear brief and get out of their way. A designer working inside confirmed constraints produces something you can actually build, price, and finance. A designer working on guesses produces something you'll admire and then revise.
When you feel the pull to just let the design begin, ask a simple thing: what would we have to change about these plans if the zoning, the site, or the budget came back different than we assumed?
If the honest answer is "quite a bit," you're not ready to draw. That's the consultant's point, and it's worth hearing them out.
None of this means the architect is wrong to want momentum, and it doesn't mean the consultant is being cautious for its own sake. It means the project has a natural order, and the smoothest builds are the ones where nobody skips the first step to get to the fun one faster. Draw second.
Confirm first. The plans you end up with will be the ones you actually build.