IBM Lowers Full-Year Revenue Guidance, Can It Still Be Valued Based on Stable Cash Flow?

TL;DR

· After issuing a warning on July 14, IBM experienced a one-day drop of approximately 25% and officially lowered its full-year revenue guidance on July 22.

· The market is divided on whether the AI infrastructure budget squeeze is a quarterly deferral or a loosening of the valuation anchor for traditional enterprise IT.

· Related subjects: IBM, enterprise software, IT services companies, AI servers, and the storage and memory industry chain.

Following IBM's warning on July 14, the stock experienced a one-day drop of approximately 25% and then officially lowered its full-year revenue guidance in its Q2 earnings report on July 22. What triggered the sell-off was not a slight revenue miss, but the company acknowledging that customers temporarily redirected their capital expenditures in the final weeks of June toward servers, storage, and memory needed for AI.

This statement is very sensitive to investors. Over the past few years, the market has been willing to give stable cash flow valuations to companies like IBM because mainframes, transaction processing software, and enterprise services do not fluctuate as dramatically as consumer electronics. However, this time the market discovered that even key systems in banks, airlines, and other industries could be temporarily pushed back when there is a tight supply of AI infrastructure.

IBM CEO Arvind Krishna acknowledged in an investor letter on July 14 that the company did not anticipate the extent to which customer capex was reshuffled at the end of June and described it as an execution error for the quarter. On the conference call, he provided a counter explanation, stating that much of the demand was "deferred, not lost," and that about a third of the significant capex slip had been completed in the first three weeks of the third quarter.

What the market needs to assess now is the distance between these two statements. Is this a quarterly mismatch amplified by supply chain panic, or an early signal that AI capex is beginning to compress the traditional annual revenue stream of enterprise IT?

The Flash Crash Pricing Zero-Sum Budget

IBM's total revenue in the second quarter was approximately $17.2 billion, a 1% year-over-year increase. Software revenue was around $7.8 billion, up by 5%. Infrastructure revenue was about $3.8 billion, down by 7%, with IBM Z mainframe revenue declining by 42% year-over-year. The company has adjusted its full-year constant-currency revenue growth expectation for 2026 from the previous "above 5%" to 4%-5%, while the free cash flow outlook remains an increase of approximately $1 billion year-over-year.

Merely looking at the guidance revision, it doesn't seem sufficient to explain the approximately 25% single-day drop. What truly triggered the reassessment is the structure. Mainframes are inherently a cyclical business, and the market can tolerate fluctuations, provided they do not harm the higher-quality software cash flow.

The issue this time is that customers are not simply buying fewer machines but reallocating their budget to snatch up servers, storage, and memory required for AI. The so-called capital expenditure reordering is when the money a company originally planned to use for system upgrades or software purchases is temporarily redirected to secure infrastructure capacity due to concerns about AI hardware shortages and price hikes.

This shift has transformed IBM's decline from a financial reporting error into a valuation anchor shakeup. If AI infrastructure becomes a priority in the enterprise budget, traditional IT companies, once seen as stable revenue streams, may need to be revalued.

Mainframe Decline Will Impact Software Revenue

Ordinary investors often misunderstand mainframes, thinking of them as obsolete hardware. In reality, IBM Z mainframes are still core equipment for many banks, airlines, insurance companies, and government systems handling crucial transactions, known for their reliability, security, high throughput, and high migration costs.

More importantly, mainframes are not merely hardware sales. They usually come bundled with transaction processing software, which handles high-frequency critical transactions, as well as long-term maintenance services. These software products have high gross margins and stable renewals, forming a part of IBM's software business quality.

Reuters cited IBM's CFO as saying that the mainframe hardware and transaction processing software make up the core host business stack, dragging IBM's growth by over 5 percentage points, compared to the previous expectation of around 1-2 percentage points. This statement should not be simply understood as software alone dragging down performance, but it indicates that the hardware cycle has now transmitted to the software and service revenue rhythm.

For the market, the danger signal is not IBM selling fewer mainframes but rather the convergence of hardware cycles, software licenses, and customer budget decisions being pierced by the AI supply chain impact in the same quarter. Revenue streams that were originally priced separately suddenly appear to be more interrelated.

This is also why investors are concerned about the pressure spilling over to some software and IT service companies. The market does not believe that all software will immediately decline but is rather revisiting a question: If customers overspend on AI budgets, which traditional system upgrades will be postponed?

Krishna and Idlet's Counterargument Boundary

Krishna's counterargument focuses on reframing "demand disappearance" as "transaction timing delay." He emphasizes that there is no evidence of customers migrating from mainframes, the z17 project is still strong at its inception, Red Hat's growth rate is also improving, and some delayed transactions have been completed in early Q3.

This narrative can help soften even the most extreme pessimistic view. If the delayed orders from Q3 and the second half of the year continue to materialize, Q2 will look more like a short-term misalignment caused by AI hardware supply constraints, compounded by IBM's own execution lag.

CFRA analyst Brooks Idlet also leans in this direction. He assesses that IBM's software issue is more likely a reflection of the company's hardware issues rather than a trend in the software industry as a whole. The purpose of this view is to attempt to break the chain of spillover effects between "IBM's plunge" and the "software industry budget crisis."

However, the rebuttals have not completely eliminated the risk. IBM has already acknowledged that customers shifted their budgets toward AI infrastructure at the end of the quarter. Zero-sum budget relationships have occurred at least with some major customers in some time windows. The only difference is whether it will happen again.

If the supply of AI servers, memory, and storage remains tight, customers may postpone traditional system projects more than once. A single deferral can be recovered, but multiple deferrals will alter the annual growth pace and could potentially depress the market's valuation multiples for stable income.

Order Fulfillment Will Determine Valuation Recovery

The recent IBM plunge cannot simply be attributed to "AI killing the mainframe." The current evidence supports a more specific judgment: AI supply constraints magnified IBM's mainframe cycle and execution issues in Q2, leading the market to reassess the stability of traditional enterprise IT revenue.

The validation will come in Q3 and the second half of the year. If Krishna's mentioned delayed demand continues to convert, dragging down mainframe-related hardware and transaction processing software, and the full-year growth still falls within the new guidance range, the market will attribute this shock more to a timing issue. By then, about 25% of the July 14 drop may have included excessive panic.

Conversely, if the delayed orders are not fulfilled smoothly, or more enterprise software and IT service companies mention in their financial reports that customers are postponing traditional projects for AI infrastructure, Idlet's "IBM-specific hardware issue" explanation will be weakened. At that point, the market will no longer be trading on IBM's individual misstep, but rather on the continued squeeze of AI capital expenditures on traditional enterprise IT budgets.

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia