The Budget Number Is Not What You Think It Is

Most executives treat a project budget like a fixed truth. An amount of money required to deliver a defined outcome. The vendor quotes it. The board approves it. The program is measured against it.

That framing is costing you more than you realise.

A project budget is not a truth. It is an anchor. The first number set in a negotiation — and like all anchors, its primary function is to shape everything that comes after it.

Here is what that looks like in practice.

Scenario 1

Your vendor estimates internally that the implementation will cost $500K. They add $250K contingency and propose $750K on a time-and-material basis. You accept. They deliver at $700K.

You celebrate. Under budget. Well managed. Everyone is pleased.

The reality: assuming the original estimates were accurate and no scope was added, the vendor spent $200K more than the work required. You paid it without knowing. The budget was never a reflection of what the work should cost — it was a ceiling set high enough to look good when they came in under it.

The anchor did its job.

Scenario 2

The same vendor estimates $500K internally. This time, they challenge their team on the estimates, tighten the scope, and propose $400K. You accept. Mid-delivery, they identify a genuine gap and request an additional $50K with documented justification.

You are frustrated. This feels like a blowout. You approve it reluctantly. The project completes at $450K.

You have saved $250K compared to Scenario One. The work cost what it should have cost. And yet the experience felt worse — because the anchor was set honestly and the reality brushed against it.

What this tells you

The budget game is not neutral. It rewards vendors who set high anchors and punishes vendors who set honest ones. The executive who received Scenario Two got a better outcome and a worse feeling. The executive who received Scenario One overpaid by $200K and called it a win.

This is not a market failure. It is a rational response to how project budgets are evaluated. Vendors learn quickly that the number to manage is not the actual cost — it is the expectation set at the start.

Understanding this does not make you cynical. It makes you a more capable sponsor.

When you receive a budget proposal, the question is not “can they deliver under this number?” The question is: what assumptions is this number built on, and who benefits if those assumptions are generous?

Ask for the estimate that sits underneath the budget. Ask what contingency has been included and on what basis. Ask what the vendor’s internal target is, not just what they’re proposing to you.

The budget is where the program’s honesty is first established — or first obscured. Everything that follows is shaped by what happens at that point.

SP Singh provides independent ERP oversight and advisory to WA local government and Aboriginal corporations. He writes daily at spsingh.me.