Three roles, three different questions, and the difference is mostly about when they start. The strategist asks whether you should do this at all. The development manager runs the project from the brief to handover and answers for the decisions along the way. The project manager delivers the building once there is something to build. Titles are not standardised across the industry and scopes are set by the appointment, so read what a contract actually says rather than what the role is called — but the shape below is the common division, and hiring the wrong one for the stage you are at buys competent work on the wrong question.
Where each role starts
Picture the life of a project as one line, from an owner's first idea through to keys in hand.
The strategist works before the line begins. Should this site be bought, held, repositioned or sold? What kind of deal is it? Their output is a decision and the evidence behind it, and their most valuable answer is sometimes no.
The development manager picks up at the brief and stays to the end. They set the objective, build the consultant team, run due diligence, take the feasibility to a decision, carry the planning process, drive the design to a full set of drawings, run the tender, oversee construction and close the project out. Theirs is the one seat that sees the whole line.
The project manager typically takes the baton around the point where the drawings are settled and a builder is being appointed, though plenty of appointments start them earlier. Programme, cost control, contract administration, site delivery, defects, handover. It is hard work, and it is deep rather than wide. It usually starts where the big decisions have already been made.
What the development manager actually owns
The difference is not activity. It is who carries the decision points.
A project has a handful of moments where it either proceeds or changes shape. The feasibility is signed off before anyone takes it further. The permit is secured and its conditions accepted, knowing those conditions carry cost. The drawings are locked before tender, because tendering an unfinished scope is how variations are born. The builder is appointed and the contract awarded. Then the project is closed out and handed over properly.
Those are the points where most of a project's cost gets committed, long before anyone is on site. Construction still brings changes of its own, but by then the expensive decisions are largely behind you. The development manager's job is to arrive at each one with the evidence to decide, and to say so plainly when that evidence is not there. The decision itself stays with the owner, which is the point: the role exists to make sure the call is made on something solid, not to make the call for you, and not to promise how the project turns out. Running the programme is the easy half. Carrying the gate is the job.
Do I need one on a small project?
Often, no — and it is worth being honest about that. If you own one building, the works are contained, no permit is required, and you have an architect and a builder you have used before, a good project manager and a clear scope may be the whole answer. Paying for a management layer you do not need is its own kind of waste.
You need a development manager when the decisions cross disciplines and the order matters. A change of use that triggers a permit. A site where the planning outcome changes what is worth building. A project where the consultant team does not exist yet and someone has to work out which specialists the site actually triggers, and in what sequence. That is the test: not the size of the budget, but how many decisions depend on each other.
What does it cost?
Start with an honest answer: there is no authoritative published benchmark for development management fees in Australia, and the percentages that circulate online are less useful than they look. Several of the widely repeated ranges describe the whole consultant team rather than the development manager alone, and others are drawn from overseas markets. Treat any single number you find as a starting point for a conversation, not a rate card.
What is consistent is the shape. The Australian development-feasibility publisher Feasly describes development management as charged in one of three ways: as a percentage of total development cost or of project revenue; as a fixed fee for an agreed scope; or as a base fee plus a performance component tied to a profit hurdle. It also notes the pattern that matters most to a smaller owner — the percentage falls as the project gets bigger, so a small project attracts a higher rate than a large one, because the work does not shrink in proportion to the budget.
Two adjacent roles are quoted more consistently, and they make useful anchors. OwnerDeveloper puts a superintendent — who administers the building contract during construction — at 1 to 3 per cent of construction value, or A$10,000 to A$100,000 and above depending on project size and scope. Aprao puts project management on developments above A$3 million in gross development value at about 1 to 2 per cent of build cost. Both are indicative market ranges published by industry sources rather than any official standard, and the fee that binds you is the one in your appointment.
Read the base before you read the percentage. A fee quoted on total development cost and a fee quoted on construction cost are not comparable numbers, because total development cost includes the land. On a site where the land is the expensive part, a percentage of total development cost can be a far larger sum than the same percentage of construction alone. Two proposals can look almost identical on their headline rate and be a long way apart once the base is applied. So ask what the number is calculated on before you compare anything — and be aware that published ranges do not always say.
Then watch for stacking. A development management fee on cost, a project management fee on the construction budget, and a performance fee on profit are three separate charges, and one project can carry all three at once. Each may be reasonable on its own terms. Added together they can take a real bite out of a margin that looked comfortable in the feasibility, which is why they belong in the model as their own lines rather than buried in a single professional-fees allowance.
What a development manager is not
Not the builder. The builder holds the construction contract and carries the construction risks that contract allocates to it; the development manager sits on the owner's side of that table.
Not the designer. The architect leads the design, with the consultant team carrying their own disciplines.
Not your financier. Capital and lending questions belong with licensed partners — Axis does not lend and does not broker finance.
And not the person who signs the consultant contracts on Axis-run projects. The owner engages and pays each consultant directly. That keeps the advice the owner receives independent of who is being paid to give it.
How Axis runs it
Axis Development Management runs that full line as a managed project. The gates above are real checkpoints, not status labels. A stage does not advance until the evidence behind it is on the table and the owner has signed off. Where a permit is required, the Pivot Planning workstream nests inside the planning stage and runs the council process within the wider programme.
If you are earlier than that and still deciding whether the project is worth starting, that is the strategist's question, and an Axis Quick Scan answers it against the deal's archetype from A$49.95. Our team confirms every report before it ships.
This article is independent decision support — not financial, legal, tax or planning advice. Contract and procurement questions belong with your lawyer, and cost plans with a quantity surveyor.
Verdict: hire a strategist to decide, a development manager to own the decisions between the brief and handover, and a project manager to deliver the build — the expensive mistake is buying delivery when what you needed was a decision.