Bridging Mind & Machine Back to home

What could getting it right first save you?

Unclear requirements and late changes quietly eat into budgets, timelines and results. Enter your project and see what the research says is typically at stake, from a home renovation to a major project.

Your project

Takes about 30 secondsNo sign-up neededEvery number names its source
Whole dollars, for example 50,000
$2,550 to $5,700
is typically at risk from unclear requirements and late changes on a project this size.
Conservative: Typical:

Want to keep more of it?

Get early access Find out more
Money
Time
Effort
Quality

How to read this: the conservative figure counts only the cost of unclear requirements; the typical figure counts all the waste research finds on projects like yours. Both are research averages, not a quote or a guarantee, and your results will vary with the project and how it's run.

Why late changes cost more

The same mistake costs more to fix the later it's found. If fixing it while setting requirements costs 1 unit:

Requirements
1×
Design
3–8×
Build
7–16×
Testing
21–78×
In use
29–1,500×
Source: J. M. Stecklein et al., Error Cost Escalation Through the Project Life Cycle, NASA, 2004. Bar lengths are illustrative; the "in use" range runs well beyond the scale shown.

From world-famous projects to your own

Large, complex project

Sydney Opera House and Berlin Brandenburg Airport

  • Sydney Opera House: budgeted at A$7 million, finished at A$102 million and 10 years late. Construction began before the drawings were complete.
  • Berlin Brandenburg Airport: budgeted at €2.83 billion, finished at €6.5 to €7.3 billion and 9 years late. Building carried on while the design kept changing, and the smoke extraction system had to be redesigned.
The lesson: settle what you need before you build.
Sources: Guinness World Records, largest proportional increase in cost for a building project; CNN, Berlin Brandenburg Airport opening coverage, 2020.
Medium business

A $500,000 new business system

  • 30% of new business systems go over budget and 22% finish late.
  • The top causes are unexpected extra technology needs (55%) and expanded scope (51%): both requirements problems.
  • Poor requirements typically waste 5.1% of project spend, and all poor project performance about 11.4%.
About $25,500 to $57,000 at risk.
Sources: Panorama Consulting, ERP Report, 2026; Project Management Institute, Pulse of the Profession: Requirements Management, 2014.
Small business

A $50,000 new service or process

  • Small projects succeed far more often than large ones, yet 39% still run late, over budget or fall short.
  • Across all projects, 11.4% of every dollar is wasted through poor project performance.
  • Poor requirements alone typically waste 5.1% of project spend.
About $2,550 to $5,700 at risk.
Sources: Standish Group, CHAOS Report, 2015; Project Management Institute, Pulse of the Profession, 2020 and Requirements Management, 2014.
Personal project

A $20,000 home renovation

  • 72.7% of Australian renovators hit unexpected costs, and almost 60% have had to pause a renovation for money reasons.
  • Redoing work averages 6.4% of contract value in direct costs and a further 5.9% in indirect costs, with client changes and gaps in the plans among the main causes.
About $1,280 to $2,460 at risk.
Sources: Budget Direct, Home Renovation Survey, 2024 (1,000+ Australian homeowners); P. E. D. Love and D. J. Edwards, Calculating total rework costs in Australian construction projects.

Where the savings come from

Upfront thinking pays for itself. Across real development projects, the best results came from investing about 8% to 19% of effort in understanding the whole system first, and each extra dollar put into that thinking returned about $3.50.

Source: E. C. Honour, Systems Engineering Return on Investment, PhD thesis, University of South Australia, 2013.

Projects with strong systems engineering were nearly four times as likely to perform well: 57% compared with 15%. BMM puts that thinking in your hands, scaled to the size of the job.

Source: J. P. Elm and D. R. Goldenson, The Business Case for Systems Engineering Study, Carnegie Mellon University SEI, 2012.

Ready to get it right first?