What Developers Actually Want From a Town Planner

Developers are a different audience to your average homeowner client, and they want a different conversation. They're not looking for reassurance they're running a numbers game, and planning is one variable in a much bigger equation involving finance, construction cost, and program. Having sat on both sides of this in-house at a developer and as an external consultant here's what developers actually want, whether they say it out loud or not.

Tell me if this stacks up before I spend real money

Developers don't want a planner who says yes to everything. They want someone who'll run the numbers on yield, overlay constraints, and policy settings before a single concept plan gets drawn, and tell them honestly if a site doesn't work at the density they're assuming. A planner who flags a fatal flaw in week one saves a developer far more than one who quietly hopes it'll sort itself out at VCAT. Feasibility-stage honesty is worth more than approval-stage optimism.

What's this going to do to my program?

Every month a permit is delayed is a month of holding costs, finance costs, and opportunity cost. Developers don't care about statutory day counts they care about the real-world date the shed goes up or the first settlement happens. What they want is a planner who understands their program, builds the planning pathway around it, and flags early if a heritage overlay or a notice period is going to blow out their timeline, so it can be priced into the deal rather than discovered halfway through construction finance approval.

Where's the risk, and how do we manage it?

Developers are used to risk they just want it identified and quantified, not hidden. A good planner tells them plainly: this is a discretionary use, here's the likelihood of conditions, here's what a VCAT appeal would cost in time and dollars, here's the fallback position if the preferred scheme doesn't get up. Developers make decisions on risk-adjusted numbers. Give them the inputs and they'll make the call.

Can you actually add value, not just process paperwork

The best planners on a development team aren't just permit administrators they're finding the upside. That might mean identifying a code variation that adds another unit, spotting a policy pathway that avoids a car parking shortfall, or negotiating a condition down before it becomes a $200k basement redesign. Developers want a planner who's commercially literate enough to know when a planning outcome is actually a cost outcome, and who fights for the version of the scheme that makes the deal work.

Don't make me chase you

Developers are managing multiple consultants, multiple sites, and multiple deadlines at once. They don't have time to follow up on where an RFI response is at. What they want is a planner who proactively reports progress, flags problems before they're asked, and treats their project with the same urgency the developer feels about their own capital sitting on the table.

The common thread across all of this: developers want a planner who thinks like part of the deal team, not an external gatekeeper. Someone who understands that planning risk is really just another form of commercial risk, and treats it that way.

At Equinox, that's exactly the approach feasibility-first advice, straight talk on risk and timeframes, and planning strategy that's built around what actually makes a project stack up.

Working through a feasibility or a tricky planning pathway? Get in touch.