Timing clarification: IBM’s 2Q26 earnings call is today, Wednesday, July 22, 2026, at 5:00 p.m. ET—not tomorrow. This is an unusual earnings event because IBM pre-announced preliminary results on July 14, so the headline quarter is largely known. The investment debate has shifted decisively to the full-year outlook, the durability of software growth, and management’s explanation of the late-quarter execution failure.
IBM enters the call having already reset expectations. Its July 14 pre-announcement projected 2Q revenue of $17.2 billion and operating EPS of $2.93, below then-consensus expectations of approximately $17.86 billion and $3.01, respectively. The stock fell from $290.23 on July 13 to $217.07 on July 14 (about 25%) and closed at $210.54 on July 21—roughly 27% below its pre-warning level.
The key question is not whether IBM missed 2Q estimates—the preliminary release already answered that. It is whether the shortfall reflects:
A credible reaffirmation of the full-year framework, supported by evidence that delayed transactions are progressing, would likely be constructive given the sharp stock reset. A guide-down—or an explanation that remains vague on the size and timing of the recovery—would reinforce fears that the miss is structural.
| Metric | 2Q26 preliminary result | YoY change | 2Q25 actual |
|---|---|---|---|
| Revenue | $17.2B | +1% | $17.0B |
| Operating EPS | $2.93 | +5% | $2.80 |
| GAAP EPS | $2.27 | -2% | $2.31 |
| Software revenue | — | +5% | +10% |
| Consulting revenue | — | Flat | +3% |
| Infrastructure revenue | — | -7% | +14% |
| Operating gross margin | 59.4% | -70 bps | 60.1% |
| Operating pre-tax margin | 19.2% | +30 bps | 18.8% |
| YTD free cash flow | $4.8B | Essentially flat | $4.8B |
Source: IBM’s July 14 preliminary-results letter; historical comparison from IBM’s 2Q25 earnings release.
The segment mix matters more than the modest EPS growth:
Management’s core explanation is that, during the final weeks of June, customers redirected quarterly technology budgets toward servers, storage, and memory to secure supply-constrained infrastructure ahead of anticipated price increases. IBM also cited rapidly evolving cybersecurity concerns distracting customers and said that numerous large deals did not close on expected schedules.
This explanation has two implications:
The customer spending did not disappear; it was reallocated or delayed. IBM said the z17 program remains historically strong, with program-to-program performance near 130% and 85% of installed MIPS customers maintaining or expanding capacity. It also pointed to strong Distributed Infrastructure performance—up 37%, with roughly $500 million of backlog exiting the quarter.
If delayed Z and Transaction Processing commitments are merely pushed into 3Q or 4Q, then the issue is recoverable. That outcome would preserve the thesis that the z17 cycle, increased AI inference workloads, and mainframe software monetization can still support medium-term growth.
The warning exposed a more fundamental problem: IBM’s highest-margin mainframe hardware and transaction-processing revenues may be increasingly vulnerable when CIO budgets are constrained by AI-related compute, memory, and security spending. In that case, “timing” becomes a softer description for a longer purchasing-cycle reset.
The call needs to establish whether the June behavior was narrowly concentrated in a handful of delayed transactions or broad across industries, regions, and customer types.
IBM’s software segment remains central to its valuation. In 1Q26, management raised its full-year software outlook to 10%+ constant-currency growth, underpinned by Red Hat, data, automation, acquisitions, and Transaction Processing monetization.
The 2Q pre-announcement challenges that confidence—but it does not invalidate every component of the software thesis.
What to listen for: Red Hat growth and bookings; Data growth excluding acquisitions; Transaction Processing trends; annual recurring revenue; software bookings or transaction conversion; and whether management still stands behind 10%+ full-year software growth.
IBM Consulting grew only 1% at constant currency in 1Q26, though signings improved 6% and management expected revenue growth to accelerate as the year progressed. The preliminary 2Q result—flat reported revenue and 1% constant-currency growth—indicates that acceleration has not yet materialized.
IBM’s positive argument is that GenAI is becoming embedded in the business: at the end of 1Q, management said GenAI represented about 30% of consulting backlog, more than 20% of consulting revenue, and over $4 billion in annualized revenue. Yet this has not translated into stronger reported growth.
The call needs to address whether consulting’s subdued revenue reflects ordinary backlog conversion timing, pricing pressure, reduced discretionary transformation spending, or productivity gains that lower billable labor demand.
Prior to the pre-announcement, IBM’s 2026 guide called for:
The preliminary 2Q release did not reiterate or revise this framework. Management instead said it would discuss full-year expectations on the July 22 call.
IBM generated $4.76 billion in free cash flow in the first half, essentially unchanged from 1H25. That is only about 30% of the roughly $15.7 billion implied by the prior full-year objective, although IBM’s cash flow is historically very back-end weighted.
Maintaining the FCF outlook is possible, but it would require clear confidence in second-half earnings conversion, working capital, and deal closures. Investors should focus less on a simple reaffirmation and more on the bridge: What specifically supports a substantial second-half FCF ramp after the revenue shortfall?
Investor implication: The July 14 selloff may have discounted a more severe or persistent slowdown than the facts justify.
Investor implication: The shares may stabilize, but a rapid re-rating would be difficult without tangible 3Q proof of recovery.
Investor implication: The debate shifts from one-quarter execution to a reset of IBM’s growth and cash-flow algorithm.
IBM’s 2Q26 report is fundamentally a credibility and guidance event, not a traditional earnings beat/miss event. The preliminary figures show a business that still produced modest EPS growth, margin expansion at the operating pre-tax line, and stable first-half cash flow—but whose revenue engine weakened abruptly in the most strategically important areas: mainframe-linked infrastructure and Transaction Processing software.
The stock’s decline has lowered the bar on reported 2Q figures, but it has raised the bar on management’s explanation. For the shares to recover sustainably, IBM must show that the June disruption was temporary, that its software growth engine remains healthy outside of mainframe-linked Transaction Processing, and that the company can still deliver its 2026 free-cash-flow commitment without relying on an implausibly sharp second-half rebound.