Australian property consultants optimise for billable hours, deliverable volume, and engagement duration. Meanwhile, 69% of construction projects fail to deliver on budget because no one optimised for the outcome you hired them to deliver: structural correctness at inception. The consultants aren’t incompetent. The incentive structure is broken.
I’ve spent 40+ years watching property projects fail in slow motion. A developer hires consultants. The consultants deliver what was requested. The project still fails.
The problem isn’t competence. It’s what they’re optimising for.
Property consultants structure their work around metrics that benefit their business model, not your project’s survival. They optimise for billable hours, scope expansion, and deliverables. What they don’t optimise for is preventing your project from joining the 69% of Australian construction projects that run over budget.
Why Do Hourly Fees Lead to Misaligned Incentives?
Hourly billing creates structural misalignment even before work begins.
When consultants bill by the hour, they are penalised for efficiency. The faster they solve your problem, the less they earn. More meetings, more revisions, more workshops mean more profit.
This isn’t about ethics. I’ve worked with honest consultants who want to help. The issue is systemic. The fee structure rewards the wrong behaviour.
You need someone who eliminates structural vulnerabilities before capital is committed. You get someone whose income depends on stretching timelines and maximising touchpoints.
The incentive is to stay involved, not to solve the problem.
Key Point: Hourly billing penalises efficiency and rewards prolonged engagement, creating a direct conflict between consultant profitability and project success.
What Metrics Do Consultants Actually Optimise?
I’ve reviewed hundreds of consultant reports. They’re full of activity metrics:
- Number of stakeholder meetings held
- Percentage of deliverables completed on schedule
- Compliance with process frameworks
- Volume of documentation produced
These metrics optimise for the appearance of progress, not for structural correctness.
The true indicators of project health are harder to measure:
- Have we identified the constraint that will kill this project within 18 months?
- Have we structured agreements so that success for one party requires success for all?
- Have we transferred risk to parties best equipped to manage it?
These questions don’t generate billable hours. They produce outcomes.
When Australian property development experts identify poor due diligence and inadequate planning as primary causes of failure, they’re pointing to this problem. Consultants optimise for planning activity, not planning quality.
Key Point: Activity metrics produce impressive reports but don’t predict project survival. The questions that determine success don’t fit standard deliverable templates.
Why Does Optimising Individual Components Lead to Project Failure?
Most consultants optimise individual components.
The financial model is optimised. The construction schedule is optimised. The stakeholder engagement process is optimised. Each specialist improves their domain in isolation.
The project fails regardless.
Failure doesn’t stem from any single component. It stems from interdependencies that no one examined. The financial model assumed a construction timeline that didn’t account for NSW or Queensland DA approval sequences. Stakeholder engagement created commitments the design couldn’t deliver within budget.
Optimising components while ignoring system dynamics is why Australian megaprojects overrun their initial costs by an average of 30%, with projects like Sydney Metro blowing out by $12 billion.
I don’t optimise components. I engineer the conditions under which the entire system succeeds.
This requires seeing the project as a whole before work begins. It requires identifying which decisions at the outset eliminate chaos at the end. It requires understanding that the quality of questions determines the quality of outcomes.
These capabilities don’t fit within specialist silos or hourly billing structures.
Key Point: Component optimisation ignores system dynamics. Projects fail at the interfaces of interdependencies, not within specialist domains.
Why Do 70% of Projects Fail Despite High Confidence?
70% of projects fail despite high confidence in planning and control.
Developers aren’t going in blind. They hire consultants, follow best practices, and implement project management frameworks. They feel confident.
Only 31% of Australian construction projects deliver within 10% of budget.
Confidence and competence have decoupled. Consultants deliver what was requested. Processes are followed. Reports confirm everything is on track.
The project fails anyway because confidence was built on the wrong foundation.
You get perfect execution of a flawed strategy. Immaculate documentation of a project structurally doomed from inception. Consultants who did exactly what their scope required, whilst the underlying assumptions that would kill the project went unquestioned.
Confidence in the process is not the same as correctness in the setup.
Key Point: High confidence doesn’t prevent failure when it stems from process compliance rather than structural correctness.
What Does Correctness at Inception Look Like?
I’ve seen enough failed projects to recognise the pattern. Projects that fail have different surface problems but the same underlying cause.
They were set up incorrectly.
The risk wasn’t allocated to parties who could control it. Incentives weren’t aligned. The critical path wasn’t critical. Assumptions weren’t stress-tested. Interdependencies weren’t mapped.
These aren’t execution failures. They’re design failures. They occur in the phase when consultants are most involved.
Correctness at the outset means recognising that every project contains the seeds of its own failure. Your job is to find them before they germinate.
This requires asking different questions.
Not “What’s the projected IRR?” but “What assumption, if incorrect, makes this project unrecoverable?”
Not “Have we completed stakeholder mapping?” but “Have we structured agreements, so everyone’s success depends on the same outcome?”
Not “Is the schedule optimised?” but “Where are the interdependencies that will cascade into delays we can’t absorb?”
These questions don’t fit standard consulting methodologies. They require judgement based on pattern recognition across hundreds of projects. They require seeing failure forming before others recognise turbulence.
Most consultants haven’t developed this capability because their business model doesn’t reward it.
Key Point: Correctness means identifying structural vulnerabilities at inception by asking about failure modes, not projected success metrics.
What Is the Financial Cost of a Poor Setup?
When projects go wrong, the cost isn’t just the overrun.
The Grattan Institute reports that Australian governments have spent $34 billion more on transport projects completed since 2001 than initially estimated. 48% of Australian infrastructure projects fail to deliver on budget.
These numbers represent value destroyed because Australian projects weren’t set up correctly from the start.
Every failed project I’ve recovered from could have been prevented. Not through better execution, but through better structure at inception.
The developers who called me weren’t lacking in consultants. They had plenty. What they lacked was someone optimising for the right outcome.
By the time I’m brought in, expensive mistakes have already been made. Capital is committed. The timeline is set. The contractual structure is locked. I recover the project, but I can’t recover the value destroyed by starting wrong.
Prevention is cheaper than recovery. Recovery is cheaper than failure. Most consultants aren’t incentivised to prevent failure.
Key Point: Poor project setup costs Australian projects tens of billions annually. Prevention costs a fraction of recovery, yet consultant fee structures don’t reward it.
What Should You Demand from Consultants?
If I were hiring consultants today, I’d structure the relationship differently.
- Pay for outcomes, not hours. Tie compensation to the project meeting its targets, not to deliverable volume.
- Demand consultants identify assumptions that could kill the project, not validate the assumptions you’ve made.
- Require mapping interdependencies across the entire system, not optimising specialist domains in isolation.
- Expect designs where aligned incentives replace the need for trust, rather than governance frameworks that assume goodwill.
- Measure them on preventing problems from arising, not on documenting problems after they emerge.
Hire people whose reputation depends on project success, not on engagement duration. People who’ve built credibility by preventing failures, not by managing them.
This requires a different commercial structure, scope, and value evaluation.
It optimises for the outcome that matters most.
Key Point: Outcome-based fees, a focus on prevention, and system-level thinking create alignment. Most consulting relationships lack all three.
Frequently Asked Questions
How do I know if my consultant is optimising for the wrong outcome?
Look at their fee structure and what they measure. If they bill hourly and report activity metrics (meetings held, deliverables completed, documentation produced), they’re optimising for engagement duration. If they’re paid for outcomes and focus on identifying failure modes, risk allocation, and structural vulnerabilities, they’re optimising for project success.
What’s the difference between planning activity and planning quality?
Planning activity is measurable, process-driven work: stakeholder workshops, documentation, and compliance frameworks. Planning quality means asking whether assumptions are stress-tested, whether risk is allocated to parties who control it, and whether interdependencies are mapped. You get reports on activity. Quality prevents failure.
Why do component specialists miss system failures?
Each specialist optimises their domain without considering interdependencies. The financial model doesn’t account for regulatory timelines. The design doesn’t align with stakeholder commitments. Specialists work in silos. Projects fail at the interfaces between silos.
What questions should I ask before hiring a consultant?
Ask how they are paid and what determines their success. Ask what percentage of their previous projects met the original budget and timeline targets. Ask how they identify structural vulnerabilities before committing capital. Their answers reveal whether they optimise for your outcome or for their engagement.
How much does poor project setup cost compared to proper structure?
The Grattan Institute reports $34 billion in cost overruns on Australian transport projects since 2001. 65% of Australian infrastructure projects incur cost overruns averaging 9% to 20% after contracts are awarded. Prevention through proper structure costs a fraction of recovery or failure.
What does outcome-based consulting look like in practice?
Compensation is tied to meeting project targets (budget, timeline, scope). Work focuses on stress-testing assumptions, mapping failure modes, and designing aligned incentive structures. Success is measured by prevention, not process compliance.
Are all hourly consultants misaligned with project success?
The fee structure creates misalignment, not individual intent. Honest consultants operating on an hourly basis face systemic incentives that reward prolonged engagement. The structure penalises efficiency, regardless of individual ethics.
How do I transition from activity metrics to outcome focus?
Stop measuring completed deliverables and meetings held. Start measuring whether assumptions are validated, risks are properly allocated, and structural vulnerabilities are identified before capital commitment. Shift compensation from hours billed to targets met.
Key Takeaways
- 69% of Australian construction projects fail to deliver on budget because consultants optimise for billable hours and deliverable volume, not structural correctness at the outset.
- Hourly billing creates systemic misalignment: consultants are penalised for efficiency and rewarded for prolonged engagement.
- Activity metrics (meetings, documentation, process compliance) optimise for the appearance of progress, not for project survival.
- Component optimisation ignores system dynamics. Projects fail at the interdependencies between specialist domains, not within them.
- High confidence doesn’t prevent failure when it stems from process compliance rather than structural correctness.
- Poor project setup has cost Australian governments $34 billion in transport project overruns since 2001. Prevention through proper structure costs a fraction of the cost of recovery.
- Outcome-based fees, a focus on prevention, and system-level thinking create alignment that hourly billing and specialist silos destroy.
If your next Australian property development project can’t afford to join the 69% that fail to deliver on budget, we should talk.
I don’t optimise for engagement duration. I engineer conditions for project success by identifying structural vulnerabilities before capital is committed and by designing systems in which failure becomes costly to achieve.
Book a strategic consultation where I’ll review your project setup, identify assumptions that could kill it, and determine whether it’s set up for survival or sophisticated failure.
Schedule a Project Structure Review
About the Author
Steve Chandler is a third-generation property developer with over 40 years of practical experience in residential, commercial, industrial, medical, infrastructure, and public building projects throughout Australia.
As CEO of LEFTA Group of Companies, Steve specialises in property development advisory, consultancy, strategy, and training, with particular expertise in residential projects ranging from 30 to 80 apartments.
Professional Experience
Steve’s career started in 1980, giving him four decades of hands-on involvement in all aspects of property development. His experience covers:
- Project feasibility study and risk evaluation
- Development strategy and implementation
- Contract negotiation and project recovery
- Regulatory compliance and approval from authorities
- Budget management and cost control
Throughout his career, Steve has established a systematic method for spotting structural weaknesses in project setup stages, helping to prevent cost blowouts before they happen.
Teaching and Knowledge Sharing
Steve has shared his expertise as a lecturer at TAFE NSW, teaching property development principles to aspiring developers. He authored “From Building Worrier to Building Warrior: Taking The Worry Out Of Building” (available on Amazon), which documents research into renovation loan patterns and budget management strategies.
His teaching philosophy focuses on turning theoretical knowledge into practical, actionable strategies that avoid common development failures.
Specialisation and Methodology
Steve’s approach to property development highlights:
- Conduct thorough research upfront before acquiring property.
- Comprehensive feasibility assessments covering 15-20 cost categories
- Choose risk relocation instead of risk avoidance
- Complete project documentation to prevent scope creep.
- Strategic contract structuring with protective special conditions
His methodology relies on pattern recognition from decades of observing what distinguishes successful projects (22% that stay on budget) from failed ones (78% that experience cost overruns).
Industry Acknowledgement
Steve’s expertise is highly valued by property developers tackling complex, high-stakes projects where standard methods fall short. His work concentrates on:
- Preventing budget blowouts through intervention during the setup phase
- Revitalising struggling projects through strategic restructuring
- Guiding developers in conducting professional-grade feasibility analyses
- Engineering project conditions where success is guaranteed
Geographic Focus
Based in Australia, Steve’s expertise is rooted in the Australian property development scene, including NSW regulatory rules, standard building contracts (NSW Fair Trading, Master Builders Association, Housing Industry Association), and Australian tax considerations for property development.
Contact Details and Additional Information
Steve Chandler works with property developers through LEFTA Group of Companies, offering strategic advice, project consultation, and professional mentorship for those dedicated to approaching property development as a profession rather than speculation.
His insights are shaped by hands-on involvement in hundreds of projects across residential, commercial, and mixed-use developments, along with research into industry-wide trends of success and failure.
Conflict-of-Interest & Commercial Disclosure: LEFTA Corporation Pty Ltd advises clients across Australia and may seek future joint-venture opportunities at some of the sites discussed. Views expressed are personal and do not represent any current client mandate.
General Advice Disclaimer: This article is based upon the personal experiences of the Author. No portion of this article is intended to provide legal, financial or professional advice. The information contained herein is not a substitute or replacement for the services of qualified professionals, legal, financial and insurance experts. The Author, its publisher, agents, servants, contractors, employees and representatives will, under no circumstances, be liable for any special or consequential damages that result from the use of, or any attempt to use, the information contained herein. You are solely responsible and accountable for any actions, decisions and results by your use of the information contained herein. You agree not to attempt to hold the Author and LEFTA Corporation Pty Ltd liable for any such decisions, actions or results, at any time, under any circumstances.
