Your AI Budget Has an Opportunity Cost. What Gives Way?
For many leadership teams, the immediate question is no longer whether AI deserves investment. They have already decided it does.
The harder moment comes when that decision meets the portfolio that was already there.
Transformation programmes are underway. Cybersecurity commitments have been made. Core systems need modernising. Regulatory work cannot simply stop. Data, architecture and change teams are already supporting multiple priorities.
Now AI needs more funding, more specialist capacity and more organisational attention.
That does not mean every pound invested in AI requires a pound to be cut elsewhere. Budgets can grow. AI can reduce costs and release capacity elsewhere.
If AI productivity is being used to justify a permanent reduction in roles, contractor or supplier capacity, or recurring operating cost, first ask what the productivity evidence actually supports about the workforce decision. The AI Restructuring Business Case Stress Test then provides a structured way to assess whether the proposed amount, timing and mechanism are supported by the evidence.
When AI becomes a portfolio reallocation decision
The shift happens when scaling AI draws on resources that are already supporting other commitments. Enterprise data, architecture, security, integration, engineering and business change capacity can all become constraints.
Deloitte's 2026 research lists data quality and availability, technology and AI talent, legacy-system integration and difficulty moving beyond pilots among the barriers organisations face as they scale digital and AI investment.1
A leadership team can reasonably say all of the following:
- accelerate AI
- protect cybersecurity
- finish the transformation already underway
- modernise critical platforms
- meet regulatory commitments
- do not increase the technology budget indefinitely
None of those instructions is irrational.
The problem is that together they may not describe a portfolio the organisation can actually support.
If the available funding and capacity cannot support everything leadership still wants to protect, the organisation has crossed an important line.
The AI investment decision has become a portfolio reallocation decision.
The question is no longer only:
How much should we invest in AI?
It is also:
What are we willing to change in the portfolio to make that investment possible?
This is already showing up in budgets. In Deloitte's 2026 survey of 100 US private-company leaders, 50% expected internal budget reprioritisation to be the primary source of funding for digital and AI investment over the following 12 months.1
You can reallocate a portfolio without explicitly choosing a new one
The cleanest response would be to make those trade-offs explicitly.
Organisations do not always get there in one decision.
Instead of stopping a programme, they may trim several budgets, move milestones or spread scarce specialists across more work. Projects remain approved. Business cases remain valid. Nobody has formally withdrawn support.
That creates a harder question when the incumbent still makes sense: should it still be protected to the same extent?
Yet the portfolio has changed.
Imagine leadership protects an accelerated AI programme and a major transformation already underway. Finance trims other lines, shared architecture capacity is spread further, and a data-platform milestone slips.
On paper, both priorities remain protected.
In reality, those resources may no longer support either priority in the form leadership originally approved.
Plans will always move. Teams will always rebalance work.
The problem becomes strategic when those adjustments change which outcomes the available funding and capacity can realistically support, rather than merely changing how an agreed portfolio is delivered.
At that point, leadership is no longer just managing deviations from plan within its chosen portfolio. It may be operating a materially different portfolio without having chosen it as a whole.
Not stopping anything does not mean the organisation avoided the trade-off. It may only mean the trade-off became harder to see.
The obvious options may not be the real choice
Making the reallocation explicit still does not make the answer obvious.
One reason is that the portfolio cannot always be divided neatly into "AI" and "everything else." Some investments that appear to compete with AI for funding may also be part of what makes AI possible.
BCG's research into IT spending found organisations increasing investment in AI and GenAI alongside cloud services, security infrastructure and analytics while reducing spend in more mature categories. It describes cloud and security as important prerequisites for scaling transformative technologies such as AI.2
Deloitte's 2025 Tech Value Survey found that 47% of AI investors also invested in ERP, compared with 21% of non-AI investors, a pattern Deloitte says seems to underscore ERP's role as a backbone for integrating AI into operations.3
Imagine a portfolio containing:
- an AI scale-up programme
- a data-platform programme the AI work depends on
- an ERP modernisation already underway
- mandatory cybersecurity work
- a scarce architecture team supporting all four
Leadership's first discussion might produce three intuitive directions:
- accelerate AI and slow ERP
- protect ERP and phase AI more gradually
- protect both by finding additional funding
What changes when you apply the constraints
More funding does not create more architecture capacity quickly enough.
Reducing the data-platform programme releases budget but also delays the data domains the AI programme needs.
Slowing the whole ERP programme releases some architecture capacity. But it also delays a cutover already close to completion, while still not releasing enough data-engineering capacity to accelerate every planned AI use case.
Mandatory cyber work cannot simply be traded away.
A different portfolio now becomes plausible:
- Protect the data platform and mandatory cyber work.
- Complete the ERP cutover already close to delivery.
- Defer the next architecture-heavy ERP wave.
- Accelerate the AI use cases whose data domains are already available.
- Phase the AI use cases that depend on delayed data domains.
That is not automatically the right answer.
The initial option "accelerate AI and slow ERP" treated AI and ERP as whole-programme choices.
The later portfolio does not. It protects one part of ERP and defers another. It accelerates some AI use cases and phases others. It protects the enabling work and mandatory commitments that make those choices feasible.
Leadership is no longer deciding at the level of whole programmes, but at the level of the particular commitments that can realistically coexist.
Before you accept a headline trade-off
The example above suggests three questions worth asking before leadership accepts a headline choice such as "AI versus ERP":
What is actually binding?
Do not assume the budget is the limiting factor. The real constraint may be architecture capacity, data engineering, specialist talent, change capacity, sequencing or another constraint that sits beyond headline budget and headcount.
Which commitments really compete, and which depend on each other?
An investment that looks like a candidate to cut may enable the priority leadership is trying to accelerate. Data, security, integration or platform work can sit on both sides of the apparent trade-off.
Are we comparing the right units?
A programme that looks indivisible at executive level may contain waves, milestones or use cases that can be treated differently once the binding constraints and dependencies are visible.
These questions do not determine the answer. They test whether leadership is looking at the real choice.
Across a large portfolio, the difficulty is doing this across many interacting commitments at once: understanding which sets of commitments the organisation can actually support together, what each set protects and gives up, and how the available choices change when an important assumption changes.
For example, if the most important AI capabilities suddenly need to be live six months earlier, the architecture and data constraints do not disappear. Leadership may need to defer the next ERP wave further and accelerate only the AI use cases whose dependencies can be met inside the new deadline. The set of commitments that can coexist may change.
A priority is not yet a portfolio decision
Even if leadership agrees that AI is a major strategic priority, that does not uniquely determine the portfolio.
Funding, capacity, mandatory commitments and dependencies narrow which commitments can actually be supported together. More than one workable portfolio may still remain.
Constraints expose what can coexist. Leadership still has to decide what it wants to protect.
The consequential question is:
Which portfolio are we willing to commit to, knowing what that choice protects and what has to give way?
Making the choice explicit
The question is not whether AI deserves investment, but which commitments the organisation can realistically support together, and what leadership is willing to change when they cannot all coexist.
TransparentChoice helps leadership teams examine these choices by comparing workable portfolios against their priorities and constraints.
If you are working through a similar decision, we can explore it together in a 30-minute Decision Review. No preparation is needed, and you do not need to have the alternatives fully worked out.
You can also read more about how TransparentChoice approaches portfolio decisions.
References
- Deloitte, "Private Companies Shift Digital and AI Investment from Exploration to Implementation", 2026. ↩
- Boston Consulting Group, "AI Shifts IT Budgets to Growth Investments", 2025. ↩
- Deloitte, Tech Value Survey analysis on AI technology investment and ROI, 2025. ↩
💚 If you enjoyed this article, please consider following us. It’s a small gesture that means a lot to us and encourages us to keep sharing what we learn. See the ways to follow us below ↓