Loading blog content, please wait...
The Development Consultant You Pay by the Hour vs the One You Pay by the Project You're staring at a fee proposal for a small infill project off Charlot...
You're staring at a fee proposal for a small infill project off Charlotte Pike, and there are two lines that matter. One says $250 an hour. The other says $18,000, flat, for the whole thing. Same consultant, same scope, two completely different ways to buy the same expertise. And the choice between them says more about your project than most people realize.
We get asked about this constantly, and the honest answer is that neither structure is "better." They solve different problems. What trips people up is picking the billing model that fits their comfort level instead of the one that fits the work in front of them.
Hourly is you buying access to a brain. You call, they think, the meter runs. It's clean, it's transparent, and it scales exactly to how much you use. If you've got a specific question about whether a rezoning is worth chasing on a lot near Wedgewood-Houston, hourly lets you get an expert opinion without committing to a full engagement.
Project-based is you buying an outcome. You're not paying for hours, you're paying for a deliverable and the judgment behind it: a feasibility read, a full pro forma, an entitlement strategy from raw site to shovel. The consultant carries the risk of how long it takes. If the county planning meeting drags or the survey comes back weird, that's on them, not your invoice.
That last part is the real fork in the road. Hourly puts the risk on you. Project puts it on the consultant. Everything else follows from there.
Hourly works when your questions are narrow and the scope genuinely isn't clear yet. You're kicking tires on a couple of parcels, you want a gut check on a pro forma you built yourself, you need someone to sit in on one meeting with Metro and tell you whether the answer you got was good news or a polite no.
It also works when you already know a lot and just need to plug specific holes. If you've developed before and you understand Nashville's process but you're not sure how the new impact fees pencil out for your unit count, you don't need a full engagement. You need ninety minutes and a straight answer.
The catch is that hourly rewards clarity and punishes vagueness. If you don't know exactly what you're asking, the meter runs while you and the consultant figure out what you're even trying to solve. That's not the consultant padding hours. That's the honest cost of an undefined problem. Hourly is a scalpel. It's the wrong tool if you're not sure where to cut.
Project-based is what you want when the work is real, the stakes are real, and you need someone accountable to the finish line rather than the clock. Ground-up multifamily. A site that needs entitlements before it's worth anything. A deal where the feasibility question isn't "yes or no" but "yes, if we solve these seven things in this order."
The value here isn't just the deliverable. It's that a flat fee aligns everyone. When we're paid by the project, we have no reason to stretch it and every reason to move it. If a zoning path can be shortcut, we take the shortcut, because our incentive is your outcome, not our hours. That alignment is worth more than the price difference on almost any project big enough to need a consultant in the first place.
It also removes the thing that makes people hesitate to call. Under hourly, some clients ration their questions because every text costs money. That's exactly backward for development, where the cheap questions early are the ones that prevent expensive surprises after you own the dirt. Project-based means you call when you need to call. No mental math before every phone call.
The real question isn't "which is cheaper." It's "how defined is the work, and who should carry the risk of it running long?"
If your scope is tight and you're capable of steering it, hourly is efficient and you'll likely spend less. If your scope is fuzzy, or the project is large enough that a stalled feasibility stage could cost you months, project-based buys you a partner with skin in the game. A flat fee on a $6 million ground-up build is not the same purchase as an hour of advice on a lot you might not even buy.
There's a hybrid worth knowing about, too, because it's how a lot of thoughtful engagements actually start. You buy a small block of hourly time up front, use it to define the scope together, and then convert to a project fee once everyone knows what the project actually is. That way you're not paying a flat rate to solve an undefined problem, and you're not stuck on a meter once the work gets serious. We do this often, and it's usually the right call when someone shows up with a site and a hunch instead of a plan.
We don't lead with a rate card. We lead with the work. Tell us what you're trying to build and where, and we'll tell you honestly whether you need three hours of straight talk or a full project engagement, because quoting you a flat fee for something that should've been a phone call helps nobody, and it's not how we want to work with you.
Development is unforgiving about sequence. The impact fees, the entitlements, the feasibility math, all of it has an order, and getting the order wrong is where Nashville deals stall. Metro's own development and permitting resources will show you the process steps, but they won't tell you which battles are worth fighting on your specific site. That judgment is what you're buying, whether you buy it by the hour or by the project.
Pick the billing model that matches how defined your work is and how much risk you want to hold. Then pick a consultant who'll tell you the truth about which one you actually need.