By Habib Lawal, Mount Holly, NJ
The Meeting That Sets the Tone
The first conversation with a city official tells me almost everything about how a project will go. Some meetings are about rules: zoning, permits, timelines, approvals. Those are necessary, but they are not the ones that predict success.
The meetings that matter are the ones where someone from the city asks what I actually want to build and why, not just what I am allowed to build. When that question shows up early, the partnership usually works. When it never shows up, I know I am in for a longer fight than the paperwork alone would suggest.
Both Sides Are Solving Different Problems
A city and a developer are not working toward the same goal, even when they want the same outcome. A city is thinking about tax base, housing stock, public safety, and how a project will look in a council meeting five years from now. A developer is thinking about financing, timelines, construction costs, and whether the numbers still work after a year of delays.
Neither of those priorities is wrong. The partnerships that fail are the ones where each side assumes the other understands their constraints automatically. I have learned to say the quiet part out loud early: here is what makes this deal work for me, here is what I need from your side to make it happen, and here is where I have room to move.
Cities that do the same in return make everything faster. The ones that treat their own priorities as self-evident end up negotiating the same points three times with three different departments.
Trust Is Built Before the Groundbreaking
By the time a shovel goes into the ground, the real work of the partnership is already done. Trust gets built in the months of back-and-forth before that: the site visits, the revised plans, the calls that answer a question a city staffer did not know how to ask directly.
I have found that showing up consistently, even for the small meetings that do not feel urgent, matters more than any single presentation. A city official who has seen me follow through on minor commitments is far more willing to go to bat for me on the bigger ones. That is not a strategy I designed on paper. It is just what happens when you treat every interaction as part of the same long relationship instead of a separate transaction.
Flexibility Has to Run Both Ways
A good partnership has room to adjust. Construction costs change. Timelines slip. Community feedback sometimes points toward a different design than the one in the original proposal. A city that treats every adjustment as a violation of the original agreement makes a developer defensive, and a defensive developer stops bringing problems forward early, which is exactly when a city needs to hear about them.
The partnerships I value most are the ones where a city will say, “let’s figure out how to make this work,” instead of pointing back to the original terms as if nothing could ever move. I try to offer the same thing in return. If a city needs to adjust something on their end, I would rather solve it together than treat it as a breach.
What I Look for Before I Commit
Before I take on a project with a municipality, I look for a few signals. Is there one clear point of contact, or will I be chasing down five departments for every decision? Does the city have a track record of seeing projects through, or does leadership turnover tend to stall things halfway? Is there an actual willingness to listen to what a project needs, or is the city looking for a developer who will simply agree to everything on paper?
None of these are deal breakers on their own. But together, they tell me whether I am walking into a partnership or a series of disconnected approvals that happen to share a project name.
Why I Keep Coming Back to This Work
Working with a municipality is slower and more complicated than working with a private buyer. There are more people in the room, more processes to follow, and more ways for a good project to stall over something that has nothing to do with the building itself.
I still prefer it. A project done with a city has a chance to do something a private deal rarely does: change how a neighborhood functions for the people who already live there. That is worth the extra meetings. It is worth the patience. And it is the reason I would rather build a slower, better partnership with a city than take the faster path somewhere else.