By Habib Lawal, Mount Holly, NJ
The Builder’s Instinct Versus the Strategist’s Question
Ask most people what a developer does, and they picture someone walking a job site in a hard hat, checking on framing and finishes. That’s part of it. But the work that actually decides whether a project succeeds happens long before anyone picks up a hammer.
A builder asks: can this get done? A strategist asks: should this get done, and under what terms? Those are different questions, and confusing them is where a lot of projects quietly go wrong. I came into real estate from an engineering and technology background, not a construction background, and that order of operations is the first thing I had to unlearn and then relearn correctly.
Where the Habit of Just Building Breaks Down
Construction is a known problem. You can estimate materials, labor, and timelines with real precision once a design is locked. What you cannot estimate with a tape measure is whether the neighborhood wants what you’re building, whether the city will support it, or whether the numbers still work if interest rates move or a permit takes four extra months.
Those questions are not technical. They’re strategic. They involve reading a market, understanding what a municipality actually needs versus what it says it needs in a planning document, and knowing how to structure a deal so it survives the version of events that doesn’t go according to plan.
The Trade-Off Nobody Names
Here’s the trade-off people don’t say out loud: moving fast on construction and moving carefully on strategy pull against each other. Every month spent underwriting, modeling scenarios, and talking to a city is a month a crew isn’t on site. It feels like lost time. It isn’t.
A project that starts digging before the strategy is settled usually pays for that head start later, in change orders, in disputes with a municipality over scope, in financing that no longer matches the project that got built. I would rather lose weeks up front than lose months mid-project trying to fix a decision I rushed.
What Strategic Thinking Actually Looks Like on a Deal
In practice, thinking like a strategist means treating a development the way you’d treat any business case. Before I look at a site plan, I want to understand the exit: who buys this, who rents it, who uses it, and what has to be true in the surrounding area for that demand to hold up in five years, not just this year.
It also means being honest about downside. What happens to this deal if rates rise, if a key tenant doesn’t materialize, if the city changes its priorities halfway through approvals? A builder’s mindset tends to assume the plan holds. A strategist’s mindset plans for the version where it doesn’t, and builds in the room to absorb that.
And it means paying attention to who else has a stake in the outcome. A development doesn’t exist in isolation. It sits inside a community, inside a city’s longer-term plans, inside the financial lives of the people who’ll live or work there. Treating that as part of the business case, not an afterthought to it, is what separates a project that holds its value from one that doesn’t.
Why I Treat Every Project Like a Business Case
I came to real estate watching my own family lose a home to foreclosure, without a clear sense of what options existed at the time. That experience is part of why I take the financial and strategic side of this work seriously. Buildings are physical, but the decisions that determine whether they help or hurt the people around them are financial and strategic first.
If you’re getting into development, or sizing up someone who already is, the question worth asking isn’t how good their crews are. It’s whether they can tell you, clearly, what happens to the project if the easy assumptions don’t hold. That answer tells you a lot more than the finishes ever will.