IBM Says Infrastructure Purchases Pulled Spending From Software in Preliminary Quarter
IBM's selected preliminary results put quarterly revenue at $17.2 billion, up 1%, with software up 5% and infrastructure down 7%. IBM said customers redirected quarterly capital spending toward servers, storage, and memory as they sought scarce infrastructure before expected price increases. The company also cited fast-changing cybersecurity concerns and large deals that did not close on schedule. These are management's explanations for one quarter, not proof that AI infrastructure is permanently crowding out software across the economy. LDS examines the practical signal: technology leaders need to distinguish temporary purchase timing from a durable reallocation before changing budgets, forecasts, or vendor strategy.
What happened
IBM's selected preliminary results put quarterly revenue at $17.2 billion, up 1%, with software up 5% and infrastructure down 7%. IBM said final results may differ slightly and scheduled its regular earnings call for July 22. The company said performance fell below its expectations, particularly in its Z mainframe business and associated transaction-processing software.
IBM said customers redirected quarterly capital spending toward servers, storage, and memory as they sought scarce infrastructure before expected price increases. Management also cited rapidly changing cybersecurity concerns and said numerous large deals did not close on the expected timetable. Reuters independently reported the preliminary figures and the same spending explanation.
Technical context
The investor letter documents IBM's results and management's explanation for the shortfall. It does not establish that AI spending permanently displaced software spending across the economy. Business Insider and Reuters framed the event as a broader budget-allocation signal, but that interpretation still needs confirmation from future quarters and other vendors.
| Signal | Near-term interpretation | Evidence needed for a durable conclusion |
|---|---|---|
| Server, storage, and memory purchases | Customers accelerated scarce infrastructure orders | Similar patterns across vendors and multiple quarters |
| Delayed software deals | Purchase timing hurt IBM's quarter | Renewal, pipeline, and close-rate trends after infrastructure orders normalize |
| Cybersecurity attention | Security concerns competed for executive focus and budget | Disclosed security spending and deal-conversion evidence |
| Stronger Red Hat performance | Some software categories remained resilient | Product-level growth and retention over time |
Editorial analysis
The useful data-science lesson is not that every software budget is shrinking. It is that infrastructure constraints can alter the timing and mix of enterprise technology expenditure. A company may pull a server purchase forward to secure supply while delaying an application or mainframe transaction, even if its annual technology budget remains broadly intact. That creates a sharp quarterly signal without proving a permanent change in workload economics.
For forecasting, teams should separate capacity acquisition from capacity utilization. Hardware orders measure what an organization secured; utilization, deployed workloads, software consumption, and realized business outcomes measure what it used. Treating those stages as one AI-spending metric can overstate demand and obscure which vendors actually capture durable value.
What to watch
IBM's completed results, management's full-year outlook, subsequent deal conversion, infrastructure supply and pricing, and comparable disclosures from software and hardware vendors will show whether this was a temporary procurement shift or a broader reallocation. Until then, the preliminary quarter is a meaningful warning signal, not a universal market verdict.
Key Points
- 1IBM's selected preliminary results put quarterly revenue at $17.2 billion, up 1%, with software up 5% and infrastructure down 7%.
- 2IBM said customers redirected quarterly capital spending toward servers, storage, and memory as they sought scarce infrastructure before expected price increases.
- 3LDS separates infrastructure purchases from utilization and software consumption before treating one quarter as a durable AI budget shift.
Scoring Rationale
An impact score of 7.0 reflects a material enterprise technology-spending signal, tempered by preliminary results and management-attributed causation.
Sources
Primary source and supporting public references used for this report.
Practice with real SaaS & B2B data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all SaaS & B2B problems
