
IBM’s stock plunged because its preliminary Q2 data came in below market expectations. The deeper issue is that enterprise customers, facing tight AI infrastructure supply and possible price increases, shifted quarterly capital spending away from software, mainframe expansion, and some traditional IT projects toward servers, storage, and memory. If you are watching IBM stock, AI-related equities, enterprise software names, or the U.S. earnings season, the key is to separate three risks: one-off order delays, IBM’s own execution problem, and a broader structural change in enterprise IT budgets.

IBM’s stock did not collapse because the company suddenly lost its ability to generate profit. The selloff happened because three issues appeared at the same time: preliminary results missed expectations, management acknowledged a forecasting and execution gap, and the market began questioning whether AI spending is helping or hurting IBM’s software growth story. For you, the key question is not only how much the stock fell, but whether the valuation logic behind IBM has changed. If investors had been valuing IBM as a stable software and hybrid cloud company rather than as a cyclical mainframe business, the Q2 warning directly challenged that assumption.
According to IBM’s preliminary Q2 results, the company expects second-quarter revenue of $17.2 billion, up 1% year over year. Software revenue is expected to grow 5%, consulting revenue is expected to be flat, and infrastructure revenue is expected to decline 7%. Adjusted earnings per share are expected to be $2.93. Reuters reported that the market consensus compiled by LSEG was about $17.86 billion in revenue and $3.02 in adjusted EPS, meaning IBM was not shrinking, but its growth was far weaker than investors had expected.
| Metric | Preliminary Q2 Data | Why It Matters |
|---|---|---|
| Revenue | $17.2 billion | Below the roughly $17.86 billion consensus |
| Revenue growth | Up 1% year over year | Much weaker than the prior growth pace |
| Adjusted EPS | $2.93 | Below the roughly $3.02 consensus |
| Software revenue | Up 5% year over year | A clear slowdown from Q1 |
| Infrastructure revenue | Down 7% year over year | Mainframe and related businesses were under pressure |
The market reaction was also severe because IBM CEO Arvind Krishna acknowledged in his investor letter that the company had expected supply chain factors to affect customer behavior, but had not anticipated the scale of the enterprise capital-spending shift and had not adjusted its sales execution quickly enough. Reuters reported that IBM shares fell as much as about 25% after the update and weighed on sentiment across other software stocks.
This type of selloff is rarely caused by one number alone. It usually reflects three layers of expectation gaps:
It is also important to remember that IBM’s Q1 performance was not weak. In its first-quarter 2026 results, IBM reported 9% year-over-year revenue growth, 11% software revenue growth, and 15% infrastructure revenue growth. The company also continued to expect full-year revenue growth of more than 5% at constant currency. The sharp contrast between a strong Q1 and a weak preliminary Q2 is why the market quickly reassessed IBM’s full-year growth path.
Summary: The core issue behind IBM’s stock crash is not that IBM stopped making money. The issue is that investors discovered they may have been too optimistic about IBM’s software growth, AI transformation, and full-year guidance. The preliminary Q2 revenue shortfall alone does not explain the entire stock move. But when that shortfall is combined with slower software growth, weaker infrastructure revenue, delayed large transactions, and management’s admission that it did not react quickly enough, the market is not just adjusting one quarter of earnings. It is repricing IBM’s growth stability and execution credibility.

IBM’s preliminary Q2 weakness was concentrated in software growth and infrastructure revenue, not in a complete breakdown across the whole company. When you read IBM’s earnings data, you should not conclude from 1% revenue growth alone that the company has lost its competitiveness. Nor should you conclude from Red Hat’s continued growth that the risks are exaggerated. The real question is which businesses remain resilient, which businesses dragged down the quarter, and whether those headwinds can affect full-year guidance.
In software, IBM expects Q2 revenue to grow 5% year over year. That is still positive growth, but it is a clear slowdown from the 11% software growth reported in Q1. More importantly, IBM said Transaction Processing was affected by IBM Z mainframe performance, while several large transactions did not close within the company’s expected timeline. In other words, IBM’s software business did not suddenly lose all demand. The problem is that some high-value contracts and mainframe-related software revenue did not arrive on schedule.
| Software-Related Item | Preliminary Q2 Performance | What to Watch |
|---|---|---|
| Total software revenue | Up 5% year over year | Slower than Q1, disappointing to the market |
| Red Hat | Up 11% year over year | Hybrid cloud base remains resilient |
| Transaction Processing | Below expectations | Affected by IBM Z mainframe cycle |
| Large software transactions | Several delayed | Need confirmation on whether they shift to H2 |
| Acquired businesses | Confluent and others add growth | Not enough to fully offset near-term weakness |
Red Hat remains the most important stabilizer in IBM’s software narrative. IBM had already reported 13% Red Hat growth in Q1, and the preliminary Q2 data still showed 11% growth for Red Hat. This suggests that hybrid cloud and enterprise open-source demand did not suddenly disappear. At the same time, IBM completed its acquisition of Confluent in March 2026, aiming to bring real-time data streaming, AI agents, and hybrid cloud data infrastructure into its long-term growth framework. The problem is that capital markets care not only about long-term strategy, but also about near-term revenue recognition and full-year execution.
The infrastructure weakness is more direct. IBM’s preliminary Q2 data showed infrastructure revenue falling 7% year over year, with IBM Z mainframe-related performance below company expectations. IBM’s mainframe business has a clear product-cycle pattern. New mainframe launches can generate strong demand, but procurement by large enterprises and financial institutions tends to be concentrated, complex, and sensitive to budget timing. If customers suddenly shift quarter-end budgets toward AI servers, storage, or memory, IBM Z and related software orders can be pushed out.
That said, IBM’s infrastructure business was not uniformly weak. The company said distributed infrastructure grew 37%, with about $500 million of backlog in Power and Storage projects. It also said the z17 program was running at about 130% of the comparable point in the prior cycle. This suggests that demand for the products may not have disappeared. The real issue lies in current-quarter revenue recognition, mainframe-related transaction timing, and changes in customer budget priorities.
On margins, IBM expects GAAP gross margin of 57.7%, down 100 basis points year over year, and non-GAAP operating gross margin of 59.4%, down 70 basis points. Non-GAAP pre-tax margin is expected to be 19.2%, up 30 basis points year over year. In other words, revenue pressure is clear, but cost control and business mix still supported part of IBM’s profitability.
If you use U.S. stock research tools to track earnings-driven names like IBM, it is better to connect price action with segment-level revenue changes. A single-day stock move tells you about market emotion. Software, infrastructure, free cash flow, and full-year guidance tell you whether the valuation can recover.
Summary: IBM’s preliminary Q2 weakness is mainly about growth quality and revenue mix, not simply about profit. Software revenue still grew, but the growth rate slowed meaningfully from Q1. Red Hat remained resilient, but Transaction Processing and IBM Z-related revenue were clear drags. Infrastructure revenue fell overall, but Power, Storage, and backlog still offered some support. The official earnings report needs to confirm whether delayed transactions are only a timing issue, or whether customer demand and budget structure have shifted in a more lasting way.

The shift in enterprise AI budgets toward servers, storage, and memory is fundamentally a change in purchasing priority, not proof that companies no longer need software. To deploy AI at scale, enterprises must first secure compute capacity, data storage, memory capacity, networking, and security. When hardware supply is tight or prices are expected to rise, CIOs and finance teams often prioritize infrastructure purchases. Planned spending on software, mainframe expansion, or consulting projects can then be delayed. IBM’s Q2 pressure reflects this kind of quarter-end budget reprioritization.
In Arvind Krishna’s letter to IBM investors, he said that in the final weeks of June, customers shifted quarterly capital spending toward servers, storage, and memory to secure supply-constrained infrastructure before expected price increases. This wording matters. IBM did not simply say demand was weak. It said customers spent money on different IT priorities.
The AI budget shift can be understood through the following chain:
The impact on IBM is two-sided. On one hand, IBM’s traditional strengths include enterprise software, mainframes, consulting, and hybrid cloud services. When customers prioritize hardware supply chains, IBM’s mainframe and software contracts may be postponed. On the other hand, IBM also has Power, Storage, Red Hat, automation, security, and data platform businesses. If customers continue building hybrid cloud, data governance, and AI applications after buying hardware, IBM may still capture later-stage software and services spending.
| Enterprise Budget Shift | IBM Businesses Under Pressure | IBM Businesses That Could Benefit |
|---|---|---|
| Priority on servers | IBM Z expansion, some consulting projects | Power Systems, hybrid infrastructure |
| Priority on storage | Some software contracts delayed | IBM Storage, data management |
| Priority on memory | Mainframe-related budgets squeezed | Future AI data platform demand |
| Higher cybersecurity spending | Non-urgent software purchases delayed | Security, automation, consulting |
| Tighter overall IT spending | Large contracts slow down | High-ROI projects prioritized |
This is why IBM’s warning affected sentiment toward software and IT services stocks more broadly. The market is not only worried about IBM. It is worried that AI infrastructure capex is absorbing budgets that would otherwise go to traditional software. Reuters Breakingviews argued in its commentary on IBM’s AI spending challenge that technology companies face a harder task repositioning themselves in the AI boom, especially those that have relied on steady software and enterprise IT spending.
However, you should not turn one quarter of data into a sweeping conclusion that enterprise software is entering a long-term decline. A more reasonable approach is to watch three signals. First, do the delayed large transactions return in Q3 or Q4? Second, do Red Hat, automation, data platforms, and other modern software products continue to grow? Third, do peer companies report the same “hardware first, software later” pattern in their earnings calls? If only IBM shows the problem, the company’s execution issue is more important. If the pattern appears across the industry, enterprise IT budgets may be entering a new phase.
Summary: The AI budget shift does not mean enterprises have stopped digital transformation. It means companies are buying hardware first during a period of tight AI infrastructure supply. Servers, storage, and memory are prerequisites for AI deployment, so they can receive higher priority in quarterly budgets. IBM is under pressure in the short term because mainframes, related software, and large contracts were affected by purchasing sequence changes. Whether IBM suffers longer-term damage depends on whether it can recapture later-stage spending through Red Hat, data platforms, automation, storage, and consulting.
IBM’s valuation reset reflects three simultaneous changes: revenue growth expectations moved lower, confidence in stable software growth weakened, and management execution came under scrutiny. If you only look at how much IBM stock fell, it may seem like an emotional selloff. But from a valuation perspective, the market is recalculating whether IBM should still be valued like a stable software company, or more like a legacy enterprise IT business that remains exposed to mainframe cycles and customer budget shifts.
IBM’s prior rerating was built on three ideas: software revenue was becoming a larger part of the business, Red Hat was supporting hybrid cloud growth, and AI plus enterprise automation would create new demand. The strong Q1 performance reinforced this view. In Q1, IBM still expected full-year 2026 revenue growth of more than 5% at constant currency and about $1 billion of year-over-year free cash flow growth.
The preliminary Q2 data forced the market to revisit those assumptions:
| Prior Market Assumption | Q2 Problem | Valuation Impact |
|---|---|---|
| Software growth is stable | Software growth slowed from 11% in Q1 to 5% | Lower software valuation premium |
| Mainframe cycle is manageable | IBM Z-related business missed expectations | Higher cyclical risk |
| AI boosts enterprise IT | AI hardware spending first squeezed software budgets | AI narrative became more complex |
| Management execution is reliable | Several large transactions did not close as planned | Lower execution premium |
| Full-year guidance is credible | Q2 growth fell far below full-year target pace | Higher risk of guidance reduction |
Analysts are also reassessing IBM’s near-term growth path. Investor’s Business Daily noted in its Wall Street reaction to IBM’s stock drop that some firms cut ratings or price targets, while others viewed the issue as more concentrated in mainframes and short-term order timing rather than a collapse of IBM’s long-term strategy. In other words, the market has not reached one single conclusion. The debate is whether the Q2 issue is a temporary shock or a structural slowdown.
The valuation reset is also tied to IBM’s identity as a potential AI beneficiary. Over the past two years, markets have been willing to pay higher valuations for AI infrastructure, cloud computing, enterprise software, and automation companies. But IBM’s warning shows that AI does not benefit every technology company in the same way at the same time. GPU, memory, server, and data center hardware companies may benefit first. Software, consulting, and traditional IT services companies may face budget delays unless they can prove that their products are essential to AI deployment.
When analyzing IBM stock, you can break the valuation question into four variables:
There is also a trading-cost angle. Earnings-driven stocks often move sharply before the open, after the close, and after earnings calls. If you actively track or trade U.S. stocks like IBM, your actual cost is not only the stock price movement. It can also include platform fees, external institutional fees, transaction activity fees, and fractional-share order fees. Biya charges $0 commission for U.S. stock trading, while platform fees, external institutional fees, and other charges are subject to the fee center and the order page. For users who meet the applicable service conditions, it is important to check fee structure, order type, and personal risk tolerance before trading.
Summary: IBM’s valuation reset means the market is no longer pricing the company only as a successful software transformation story. Investors are putting mainframe cycles, budget pressure, order execution, and full-year guidance risk back into the model. If the official earnings report shows delayed orders returning in the second half, Red Hat remaining stable, and free cash flow intact, the stock may see valuation repair. If IBM cuts full-year revenue guidance or cannot explain how long the budget shift will last, its valuation base may remain under pressure.
IBM’s official Q2 earnings report is not mainly about repeating the preliminary $17.2 billion revenue figure. The real task is to answer three questions: Will full-year guidance be adjusted? Can delayed orders be recognized in the second half? And how long will the AI-driven shift toward servers, storage, and memory last? If you are watching IBM stock, do not focus only on whether official EPS is slightly above or below the preliminary number. You need to connect order commentary, segment revenue, free cash flow, and management’s tone on the earnings call.
IBM has scheduled its second-quarter earnings call for July 22, 2026, at 5 p.m. Eastern Time. Because the company has already disclosed some preliminary numbers, the most important incremental information will come from full segment results, full-year outlook, and management’s answers during Q&A.
| Official Earnings Focus | Key Question | Positive Signal | Negative Signal |
|---|---|---|---|
| Full-year revenue guidance | Can IBM still grow more than 5% at constant currency? | Guidance maintained with a clear H2 path | Guidance cut or explanation unclear |
| Free cash flow | Is the roughly $1 billion year-over-year increase still intact? | Cash flow target unchanged | Earnings or working capital pressure rises |
| Software revenue | Is 5% growth only a temporary slowdown? | Red Hat, data, and automation remain stable | Mainframe-related software keeps dragging |
| Infrastructure revenue | Can the IBM Z shortfall be repaired? | Backlog supports second-half recovery | Mainframe demand remains weak |
| Large transactions | Have delayed orders been rescheduled? | Clear timing for contract closure | Customers cancel or reduce purchases |
| Margins | Can cost control offset slower revenue? | Adjusted margin remains resilient | Gross margin and operating leverage worsen |
On the earnings call, the most valuable information will not be broad AI strategy language. You should listen for specific operating explanations. Which industries were involved in the large transactions that did not close? Was the customer budget shift concentrated in June, or did it continue into July? Were server, storage, and memory purchases mainly early buying, or will they remain a priority for several quarters? If the z17 program is tracking ahead of the prior cycle, why was IBM Z revenue still below expectations in the quarter?
After the official report, you can organize IBM’s possible stock path into three scenarios:
For individual investors, the first market reaction often comes through the stock price. But the more useful question is whether the price already reflects the risk. If you use Biya U.S. stock trading fees to evaluate actual transaction costs, you should also review the specific fees and trading rules shown on the order page. High-profile earnings stocks can be volatile, so trading decisions should not rely only on a one-day price drop or social media commentary.
Summary: IBM’s official Q2 earnings report needs to turn a preliminary warning into verifiable operating answers. You should focus on full-year revenue guidance, free cash flow targets, software segment trends, IBM Z and infrastructure orders, the timing of delayed large transactions, and management’s view on how long AI budget shifts may last. If the official report provides a credible recovery path, the market may treat the crash as a quarterly shock. If the answers remain vague, IBM stock may continue to trade around lower earnings expectations and a lower valuation base.
When dealing with a U.S. stock like IBM, whose price is driven by earnings and enterprise IT budget changes, you need to turn headlines into trackable indicators: revenue expectation gaps, segment revenue, order timing, free cash flow, full-year guidance, and trading costs. For users who meet the applicable service conditions, Biya can be used to check U.S. stock quotes, track related stock information, and review fee structure through the order page. Service availability depends on the user’s location, identity verification status, platform rules, and applicable laws and regulations. Public market information, trading rules, and fee structures can help you make more informed decisions, but they do not constitute investment advice. Earnings-driven stocks may move sharply before the open, after the close, and after earnings calls, so you should understand order types, fee details, and your own risk tolerance before trading.
IBM’s preliminary Q2 data is a partial result released before the company completes all financial closing procedures, so the official report may include small adjustments. The official earnings report usually provides full segment revenue, balance sheet data, cash flow statements, full-year guidance, and earnings-call commentary, making it more important for judging IBM’s outlook.
IBM’s stock crash means the market is reassessing the quality of the company’s growth, but it does not automatically mean IBM’s fundamentals have fully deteriorated. You need to separate order delays, one-quarter budget shifts, mainframe cycle volatility, and long-term demand weakness. The final judgment should be based on official earnings, full-year guidance, and future order trends.
A single quarter of weaker-than-expected results does not mean IBM will immediately cut its dividend. The more important indicators are free cash flow, payout coverage, debt levels, and future board decisions. IBM reported in Q1 that it had increased its quarterly dividend for many years, but any future dividend decision should be based on official company announcements.
Red Hat is still growing, but its incremental contribution was not enough to fully offset weakness in IBM Z, Transaction Processing, and delayed large transactions. Different business lines have different revenue scales, profit margins, and recognition timing, so one resilient business cannot always cover pressure across the broader segment.
Whether AI budget shifts continue to pressure IBM software revenue depends on whether software projects resume after hardware purchases are completed. If spending on servers, storage, and memory was mainly early procurement, software orders may recover in later quarters. If enterprises keep compressing traditional IT budgets, IBM’s software growth pressure may be more persistent.
Individual investors analyzing IBM stock should focus on software growth, Red Hat growth, IBM Z orders, free cash flow, full-year revenue guidance, and valuation changes. A large stock-price drop does not automatically make the valuation attractive. You still need to judge whether earnings forecasts may be cut further and whether trading costs match your personal risk tolerance.
*本文仅供参考,不构成 BiyaPay 或其子公司及其关联公司的法律,税务或其他专业建议,也不能替代财务顾问或任何其他专业人士的建议。
我们不以任何明示或暗示的形式陈述,保证或担保该出版物中内容的准确性,完整性或时效性。



