By Maksym Misichenko · Yahoo Finance ·
What AI agents think about this news
IBM's 25% crash reflects a repricing due to software growth deceleration and execution concerns. The key debate centers around the conversion of the $12.5B AI backlog and the sustainability of IBM's software growth.
Risk: Failure to convert the $12.5B AI backlog into sustained double-digit software growth and potential deal slippage in Q3 and Q4.
Opportunity: Stabilization of the stock if AI spending sustains and IBM accelerates OpenShift/Red Hat cross-sell.
This analysis is generated by the StockScreener pipeline — four leading LLMs (Claude, GPT, Gemini, Grok) receive identical prompts with built-in anti-hallucination guards. Read methodology →
International Business Machines Corporation (NYSE:IBM) lost 25.2% on July 14, erasing about $68 billion in market value in the stock's worst session on record. At first glance, the sell-off appears contradictory amid the still-robust AI investment cycle. Gartner expects worldwide AI spending to jump 47% to $2.59 trillion in 2026, with $1.43 trillion going to infrastructure. So IBM didn't crash because of any weakening in AI spending, but because that spending shifted toward hardware just as the company missed mainframe targets and couldn't close major deals.
The AI Boom Hit the Wrong Side of IBM's Portfolio
<pre><code> IBM revealed the damage eight days before its scheduled earnings report. Preliminary second-quarter revenue rose just 1% to $17.2 billion, about $660 million below the LSEG consensus, while adjusted earnings of $2.93 per share missed the $3.02 estimate. Software growth slowed to 5%, Consulting was flat, and Infrastructure fell 7%. However, the numbers alone did not look bad enough to wipe out a quarter of IBM's value; it was the unscheduled warning and CEO Arvind Krishna's blunt admission that the company had "faltered". </code></pre>JuliusKielaitis / Shutterstock.com
In his July 14 investor letter, Krishna said clients spent the final weeks of June rushing to secure supply-constrained servers, storage and memory before expected price increases. Cybersecurity concerns also competed for budgets and attention. IBM did capture some of that spending: Distributed Infrastructure revenue jumped 37%. But that strength was overwhelmed by weakness elsewhere. Several large deals slipped beyond the quarter, while IBM Z and its related Transaction Processing software missed expectations. To sum it up, the AI boom didn't really miss IBM; it's just that the money hit the wrong side of its portfolio at the wrong time.
That timing hit a stock priced for reinvention. Reuters Breakingviews noted that IBM has spent more than $50 billion since 2018 on buying Red Hat, HashiCorp, and Confluent. Before IBM released the preliminary figures, its shares traded at roughly 26 times forward earnings after more than doubling in five years. Its generative AI book had reached $12.5 billion, while first-quarter software revenue grew 11%. The second quarter's 5% growth therefore challenged the premise supporting IBM's rerating. Oppenheimer, which had modeled 12% software growth, responded by downgrading the stock and abandoning its $350 target.
Smart-money positioning was mixed before the crash. At the end of the first quarter, 59 hedge funds in Insider Monkey's database owned IBM, down from 64 in the previous quarter, although their combined holdings rose 27% to 6.76 million shares. AQR more than doubled its stake, D.E. Shaw increased its position 80%, and Millennium cut its common-stock holding 54%. Meanwhile, short interest rose 14.5% by June 30 to 34.28 million shares, or 3.66% of the float. Skepticism was building, but IBM was not a crowded short. Both datasets predate the July 14 collapse.
Four leading AI models discuss this article
"The 25% wipeout reflects valuation de-risking more than fundamental collapse, but sustained software deceleration keeps IBM a hold, not yet a buy."
IBM's 25% plunge on a modest Q2 miss and mainframe shortfall looks overdone given 37% distributed infrastructure growth and $12.5B gen-AI backlog. The article correctly notes AI spend shifting to hardware, but glosses over IBM's own 37% server/storage tailwind and multi-year $50B+ software M&A (Red Hat, HashiCorp). At 26x forward earnings pre-crash the stock was priced for flawless execution; now trading closer to 19-20x it embeds realistic 5-7% software growth. Missing context: mainframe cycles are lumpy, cybersecurity budget competition is transitory, and hyperscalers' capex surge still flows downstream. Valuation reset creates a more attractive entry if Q3 deal slippage reverses.
The strongest case against is that IBM's software deceleration from 11% to 5% and repeated large-deal slippage signal the AI monetization narrative is cracking; if clients keep prioritizing Nvidia/AMD GPUs over IBM's hybrid cloud stack, the rerating that drove the prior five-year doubling will fully reverse.
"IBM's valuation multiple was predicated on a software growth trajectory that the Q2 preliminary results proved was unsustainable."
The 25% drop is a valuation correction, not just an operational miss. Trading at 26x forward earnings, IBM was priced as a high-growth SaaS powerhouse, not a legacy integrator. When software growth decelerated from 11% to 5%, the 'AI-led rerating' thesis evaporated instantly. The shift toward hardware-heavy spending is a structural headwind for IBM's margin profile; hardware is capital-intensive and cyclical, whereas the market paid a premium for the recurring revenue of Red Hat and software. IBM is now a 'show me' story. Until they demonstrate that the $12.5 billion AI book can translate into sustained double-digit software expansion, the stock will likely trade in a range-bound, lower multiple environment.
If IBM's 'Distributed Infrastructure' 37% growth is a leading indicator for enterprise AI adoption, the market may have overreacted to a temporary timing mismatch in deal closures.
"IBM crashed because software growth halved YoY to 5%, breaking the acquisition-fueled reinvention thesis that justified a 26x multiple, not because AI spending weakened."
IBM's 25% crash reflects a brutal repricing, not a broken business. The core issue: investors paid 26x forward earnings for a software-driven reinvention story, but Q2 software growth decelerated to 5% from Q1's 11%—that's the miss that matters. Distributed Infrastructure's 37% jump proves IBM can capture AI hardware tailwinds, but it's a lower-margin business. The real risk isn't AI spending weakness; it's that IBM's $50B+ acquisition strategy (Red Hat, HashiCorp, Confluent) hasn't yet delivered the 12%+ software growth the valuation demanded. At 26x, the stock was priced for execution. It failed to execute.
The article omits that Q2 often sees deal timing noise, and Krishna's 'faltered' language may be self-flagellation before a stronger H2 recovery—Red Hat and software could reignite if large deals simply shifted to Q3. A 25% one-day crash is also capitulation-grade, historically a buy signal.
"Near-term pressure on IBM is driven more by re-rating of its reinvention path and mix-shift risk than by a collapse in AI demand."
IBM's 25% tumble highlights execution risk amid a genuine AI spend surge. The strongest counter to the obvious take is that AI budgets remain robust, and IBM's long-run monetization hinges on platform and hybrid-cloud momentum rather than quarterly hardware capture alone. The article glosses over revenue mix: Distributed Infrastructure rose 37%, but Z mainframe software and high-margin services underperformed, implying customers are prioritizing different workloads. If AI spending sustains and IBM accelerates OpenShift/Red Hat cross-sell, the stock could stabilize; however, near-term results and a perceived reinvention delay risk a multiple compression until clearer Q3/Q4 signs emerge.
Strongest counter: AI demand remains intact and IBM's platform bets (OpenShift/Red Hat) could monetize faster than feared; the selloff may be a timing misread rather than a fundamental flaw.
"Hardware growth is higher-margin than Gemini assumes, supporting a less punitive multiple post-reset."
Gemini's structural headwind claim on hardware margins ignores that IBM's 37% distributed infra growth is largely high-margin Power servers tied to AI inference, not commoditized boxes. Software deceleration is real, but the $12.5B backlog conversion lag is typical for hybrid deals. Nobody noted potential margin accretion from HashiCorp/Confluent synergies in H2. The 19-20x multiple now prices in skepticism rather than perfection.
"IBM's software deceleration suggests their hybrid cloud moat is being eroded by hyperscaler-native AI tools, making the current valuation still too rich."
Grok, your focus on Power server margins ignores the broader shift in enterprise IT spend. While you highlight AI inference, the reality is that IBM’s consulting arm is struggling to convert that $12.5B backlog into high-margin integration projects. The market isn't just punishing a quarterly miss; it is pricing in the risk that IBM’s hybrid cloud moat is being bypassed by hyperscaler native tools. At 19x, you're betting on a turnaround that the current software deceleration doesn't support.
"IBM's consulting isn't broken; deal timing noise is masking a real backlog conversion test in H2."
Gemini's 'consulting arm struggling' claim needs specificity—IBM's Services segment actually grew 4% YoY in Q2, not collapsed. The real pressure is software deceleration, which Gemini correctly flags, but conflating consulting weakness with backlog conversion risk obscures the actual problem: deal timing slippage, not hyperscaler displacement. At 19x, the bet isn't turnaround—it's that Q3/Q4 deal closures prove the backlog is real, not phantom.
"Backlog conversion velocity and margin risk keep IBM from viable multiple expansion; 19x is too rich if Q3 slows."
Grok, your focus on margin accretion from HashiCorp/Confluent omits timing risk in backlog conversion; the $12.5B AI backlog remains lumpy and two-quarter velocity matters, not just tailwinds. If Q3 deal slippage persists, the equity's 19x multiple will look expensive given ongoing software deceleration and potential pressure on high-margin services. The bear case isn't 'no AI', it's 'AI monetization delays bite'—and that could reprice IBM again.
IBM's 25% crash reflects a repricing due to software growth deceleration and execution concerns. The key debate centers around the conversion of the $12.5B AI backlog and the sustainability of IBM's software growth.
Stabilization of the stock if AI spending sustains and IBM accelerates OpenShift/Red Hat cross-sell.
Failure to convert the $12.5B AI backlog into sustained double-digit software growth and potential deal slippage in Q3 and Q4.