IBM’s Preliminary Q2 Revenue Miss Revives Software Spending Concerns

What Happened

IBM disclosed that its preliminary second-quarter revenue was $17.2 billion, below the roughly $17.9 billion analyst expectation cited in the brief. The company said several large transactions did not close before quarter-end after customer capital spending priorities changed in the final weeks of June.

Chief Executive Officer Arvind Krishna said the company did not catch the change in customer purchasing rhythm quickly enough. The supplied brief frames the shortfall as a deal-timing and budget-reallocation problem rather than evidence that customer demand disappeared.

Why Software Was Hit

According to the brief, some enterprise customers redirected budget away from software and mainframe areas and toward servers, storage, and memory. The stated reason was concern about future price increases and supply constraints in hardware resources.

This mattered because IBM had expected its z17 mainframe cycle to support infrastructure performance. Instead, the preliminary figures showed software revenue up 5% year over year, consulting roughly flat with 1% constant-currency growth, and infrastructure revenue down 7%. The weak z platform and related transaction-processing software sales were described as part of the quarterly gap.

AI Spending Signal

The most decision-useful read is that AI infrastructure demand may be changing how enterprises rank technology budgets. If customers need compute, storage, and memory first, some software and mainframe purchases may be delayed even when the long-term project pipeline still exists.

That distinction matters. A delayed order can return in a later quarter; a structural budget shift can pressure future software growth. The brief does not prove which one is happening. It says markets will watch later quarters to determine whether IBM’s delayed transactions close or whether enterprise technology spending is changing more deeply.

Market Reaction

The brief says IBM shares fell more than 20% in premarket trading after the update. It also notes that, if such a move carried into regular trading, it could become IBM’s largest single-day decline since Black Monday in 1987.

The pressure spread to other enterprise software and cloud names mentioned in the brief: Accenture was down about 6%, ServiceNow about 4.5%, and Microsoft nearly 2%. Those moves suggest investors treated IBM’s warning as a broader enterprise software spending signal, not only a company-specific disappointment.

Practical Checks

The first check is whether IBM later converts the delayed large deals into revenue. If management is right that demand was postponed rather than lost, follow-through in later quarters would matter more than the initial miss alone.

The second check is whether hardware shortages and AI infrastructure demand keep pulling budget away from mature enterprise software. The third check is whether IBM’s z17 cycle and related software ecosystem recover, because the brief identifies that area as an important part of the gap.

Evidence Limits And Risk

This article is based only on the supplied event brief, which cites Wall Street News as the source and provides the event URL. It does not independently verify IBM filings, analyst models, or live market prices, and it does not add outside figures beyond the brief.

This is not financial advice. Market prices can move quickly, preliminary company figures can change, and a single quarter does not prove a lasting technology-spending trend. Readers should compare later IBM disclosures, customer spending commentary, and broader enterprise software results before drawing firm conclusions.

For readers who follow AI, infrastructure, and crypto-adjacent market narratives, OKX can be used as one place to continue market research through the provided link: OKX official destination with code 7nfg8123. No reward, ranking, registration, or investment outcome is implied.