Budgets
The IT budget squeeze: why ambition without a roadmap leads to frustration
Tom Leyden · 5 May 2025
Every IT leader I’ve ever worked with has lived the same year. The business demands better systems, better security, better data — and then tells you to do more with less.
The temptation is to read this as bad faith. It’s not. Business stakeholders aren’t trying to be unreasonable; their expectations reflect genuine needs — productivity, customer insight, regulatory compliance. The problem is that the case for the spend hasn’t been made in language they can defend.
What goes wrong without a roadmap
Without a defensible roadmap tying every dollar to a business outcome:
- Cuts hit the wrong things. Visible costs get trimmed; hidden risks (technical debt, fragile integrations, end-of-life platforms) survive — until they don’t.
- Investment cases stall. A funding ask that can’t be tied to revenue, margin, or risk reduction loses out to one that can.
- Innovation gets shelved in favour of maintenance. “Keep the lights on” always wins the argument when there’s nothing else on the page.
What gets lost
The opportunity cost isn’t just project delay. It’s engineer engagement (your best people don’t stay to maintain mediocrity), competitive position (your faster-moving competitors compound), and exec confidence (the next ask gets harder, not easier).
The fix isn’t a louder pitch
The fix is a roadmap that does three things:
- Connects every line item to a business outcome the CFO can repeat without help.
- Sequences spend so the early wins fund the later bets.
- Names the risks of not spending in concrete, P&L language.
Once that exists, the budget conversation changes shape. You stop defending IT and start co-investing with the business.
If you’re heading into the next planning cycle and the conversation already feels uphill, that’s the signal. A two-week Tech Strategy Review usually surfaces the missing roadmap — and gives you the case to take into the boardroom.