Loading blog content, please wait...
The One Number in a Development Consultant's Bid That Tells You If They Get It When you're weighing bids from development consultants on a Nashville pro...
When you're weighing bids from development consultants on a Nashville project, most people compare total fees first. That's fair, but it hides the number that actually tells you whether the consultant understands your site. This post is for land buyers, small developers, and investors trying to read a bid past the bottom line.
The number that tells you the most is the contingency allowance. Not the total fee. Not the hourly rate. The contingency.
A contingency is the money set aside for the stuff nobody can name yet but everybody knows is coming. On a development project in Nashville, that includes the surprises hiding under the dirt, the Metro review comment you didn't plan for, the utility connection that costs three times what the seller told you. A consultant who has actually walked sites in Davidson County knows those things happen. So they build a number for it.
Here's the tell. A bid with no contingency, or a contingency buried so low it's basically decoration, is a bid written to win, not to work. It looks cheaper on paper. It is almost never cheaper in real life. The consultant either doesn't know what your site is going to throw at them, or they know and they're hoping you won't ask. Either way, you learn something.
There's no single right percentage, and anyone who quotes you one flat number for every project is guessing. Raw land in Cane Ridge with no infrastructure is a different animal than an infill teardown in East Nashville with utilities at the curb. But the range tells a story.
On a straightforward project with good site data already in hand, a lean contingency can make sense. On a site with unknowns, steep grade off a hillside lot, a creek buffer, an old septic field, karst limestone that Middle Tennessee is famous for, a thin contingency is a warning. The consultant is either assuming the best case on every unknown, or they haven't looked closely enough to know the unknowns exist.
What you want to see is a contingency that matches the actual risk of your specific parcel. Ask the consultant to walk you through how they landed on the number. A good one will point at real features of your site. "You've got a section that grades steeply toward the back, so I padded the site work line." That's a person who read your dirt. A vague "we always do ten percent" is a person who read a template.
The instinct to pick the cheapest qualified bid is completely reasonable. You're managing a budget and every dollar has a job. The problem is that in development, the lowest number on the page is often the least complete picture of the project.
When a consultant leaves contingency out, the money doesn't disappear. It shows up later as a change order. It shows up as a call three months in that starts with "so we found something." By then you've already committed, the meter is running, and you have less use than you did the day you signed. The bid felt cheaper right up until it wasn't.
A consultant who builds in an honest contingency is telling you they'd rather have the awkward conversation now, while you can still walk, than the expensive one later, when you can't. That posture is worth more than a few points off the fee.
This one question separates the pros fast. Ask a consultant what happens to the contingency money if the project runs clean and you never touch it.
The answer you want is simple. It stays yours. Contingency is your money set aside for your risk, not padding the consultant pockets when things go smoothly. If the answer gets slippery, or the contingency is quietly folded into a fixed fee they keep no matter what, you've learned how they think about your money. A consultant who treats the contingency as a shared, transparent line is thinking like your advisor. A consultant who treats it as guaranteed income is thinking about their own.
Transparency here also tells you how they'll behave when something does go sideways. People who are clear about money before the work starts tend to stay clear when the work gets hard.
Step back and the contingency line is doing something bigger than covering surprises. It's a window into whether the consultant actually studied your project or just priced a generic one.
A real bid should feel specific to your parcel. It should reflect the flood zone status you can check on the FEMA Flood Map Service Center, the slope of the land, the zoning you're working under, the utility situation, the environmental questions a site in Nashville can raise. When the contingency ties to those specifics, the whole bid tends to be honest. When the contingency is a round number floating free of any detail, the rest of the bid is usually just as generic underneath the fancy formatting.
You don't need to become a development expert to read this. You just need to ask two things. How did you get to the contingency number, and what happens to it if we don't spend it. The answers, and the confidence behind them, tell you almost everything about whether this person gets your project.
None of this means the total fee doesn't matter. It does. So does the scope, the timeline, the references, and whether you actually trust the person across the table. But of all the numbers on the page, the contingency is the one that's hardest to fake and easiest to overlook.
Start there. A consultant who can explain their contingency in plain terms, tied to the real features of your Nashville site, has already shown you how they'll handle everything else. That's the number that tells you if they get it.