IBM Software Deals: AI Budgets Delay, Not Cancel, Enterprise Spend

What happened

IBM has pushed back against suggestions that artificial intelligence adoption is cannibalising its traditional software business, arguing instead that enterprise customers are deferring — not cancelling — significant software purchases. The company attributed the slowdown to a familiar budget-cycle dynamic: organisations are currently directing discretionary spend towards AI infrastructure and hardware, leaving established software renewals and expansions temporarily on hold.

Big Blue's leadership framed the pattern as a timing issue rather than a structural shift in demand, maintaining that the underlying appetite for its software portfolio remains intact. The implication is that once enterprises have made their foundational AI infrastructure investments, deferred software deals are expected to return to the pipeline.

Why it matters

For customer experience and service-design practitioners, IBM's framing is a useful lens on a dynamic playing out across enterprise technology procurement right now. When organisations concentrate capital on infrastructure bets — AI platforms, compute, data architecture — the budgets that fund customer-facing tooling, service orchestration software and experience platforms get squeezed. The result is not a loss of strategic intent but a delay in execution, which can quietly widen the gap between a company's CX ambitions and its operational reality.

From a behavioural economics standpoint, this is a textbook case of present bias operating at an institutional level: the tangible, near-term promise of AI capability captures budget attention, while the diffuse, longer-term returns from sustained CX investment are discounted. Leaders responsible for customer experience programmes should be alert to this pattern — deferred tooling investment has a compounding cost that rarely appears on the spreadsheet used to justify the AI hardware purchase.

The Renascence take

IBM's reassurance that deals are delayed rather than dead is, understandably, the message a vendor needs to give its investors. But for the enterprises doing the deferring, the distinction matters far less than IBM would like. A paused CX or service-platform upgrade is a paused improvement to the customer's experience — and customers do not wait on hold while procurement cycles resolve themselves.

The real risk here is not that AI is killing software deals — it is that organisations are treating AI infrastructure as a prerequisite for better customer experience rather than a complement to it. Budget sequencing that puts infrastructure first and experience tooling second will produce technically capable organisations that are still operationally slow to serve customers well. Customer-obsessed operators should resist the either/or framing entirely: the question is not AI hardware versus CX software, but how to sequence investment so that capability and experience improve in parallel. Deferred is not safe — it is just delayed regret.