IBM's preliminary Q2 results: what changed before the full report
IBM's selected preliminary second-quarter results showed revenue up 1%, with Software growth slowing to 5% and Infrastructure falling 7%. IBM said customers shifted late-June budgets toward supply-constrained servers, storage and memory.
IBM released the figures on 14 July, eight days before its scheduled full earnings call, while it was still closing the quarter. The early disclosure showed where performance weakened, but it could not determine whether delayed deals, product-cycle timing or a more durable change in client spending did most of the damage.
Update, 23 July 2026. IBM has now released the completed quarter and reduced its annual revenue outlook. This article preserves the evidence available before that release. Read our final Q2 analysis and preliminary-versus-final comparison.
What IBM disclosed early
IBM's 14 July Form 8-K contained selected, unaudited preliminary results for the quarter ended 30 June 2026. IBM said the financial close was incomplete and that final results could differ slightly.
The preliminary release put quarterly revenue at US$17.2 billion, up 1% year on year. Software grew 5%, Consulting was flat in reported currency and grew 1% at constant currency, while Infrastructure declined 7%. Diluted GAAP earnings per share was US$2.27 and operating non-GAAP earnings per share was US$2.93.
IBM's first-quarter release had reported total revenue growth of 9%, Software growth of 11%, Consulting growth of 4% and Infrastructure growth of 15%. Each percentage compares with its own prior-year quarter, but together they showed that momentum weakened across all three operating segments in Q2.
Software
Reported YoY growth- Q1 2026 reported YoY
- +11%
- Q2 2026 preliminary YoY
- +5%
- Q2 status
- Segment dollars not disclosed
Consulting
Reported YoY growth- Q1 2026 reported YoY
- +4%
- Q2 2026 preliminary YoY
- 0%
- Q2 status
- +1% at constant currency
Infrastructure
Reported YoY growth- Q1 2026 reported YoY
- +15%
- Q2 2026 preliminary YoY
- -7%
- Q2 status
- Segment dollars not disclosed
The table compares year-on-year reported growth unless stated otherwise. Q1 was final when published; Q2 remained preliminary on 14 July. It shows the change in momentum, not a sequential revenue comparison or forecast.
Why IBM said the quarter changed late
IBM said clients shifted late-June capital spending toward supply-constrained servers, storage and memory before expected price increases. Industry-wide cybersecurity concerns also distracted customers during the quarter, according to the investor letter.
The company also acknowledged an execution problem. Numerous large deals did not close on the expected timetable, driving most of the shortfall. A delayed deal can still become revenue later, while a cancelled or reduced deal changes the demand picture. The early release did not quantify either group.
IBM Z and the associated Transaction Processing software also fell short of the company's plan as the z17 launch cycle matured. That connection meant the hardware shortfall could reach the higher-margin Software segment rather than remain isolated inside Infrastructure.
The business was not uniformly weak
Red Hat revenue growth accelerated to 11%. Distributed Infrastructure grew 37% and ended the quarter with approximately US$500 million of backlog. IBM also said the z17 programme remained at nearly 130% of the comparable z16 programme.
Those indicators used different measurement bases. Backlog and programme comparisons are not recognised revenue, while segment growth is. Their value was in identifying the parts of IBM that still had momentum and the later evidence needed to confirm whether that momentum converted into sales.
Consulting signings continued to grow, led by generative artificial intelligence, while Consulting revenue was flat. That gap made conversion more important than the size of the pipeline alone.
What the full report needed to resolve
The preliminary letter did not provide segment revenue dollars, detailed Software category growth beyond Red Hat, a complete income statement, an updated balance sheet or the normal segment-profit schedules. It also did not formally update IBM's April expectation for more than 5% constant-currency revenue growth.
The key tests were whether delayed Software deals closed, whether organic Software growth held up, how IBM Z compared with Distributed Infrastructure, whether Consulting signings became revenue, and whether IBM could still deliver its revenue, margin and free-cash-flow framework.
IBM's completed results have now answered part of that list. The final quarterly figures stayed close to the early release, several delayed deals closed in early Q3 and the detailed segment mix became visible. The larger change was a reduction in expected full-year constant-currency revenue growth to 4–5%. Read the full final-results analysis for the exact comparison, revised annual path and remaining uncertainties.
Sources
7 references- IBM 14 July 2026 Form 8-Ksec.gov
- IBM preliminary investor letter, Exhibit 99.1sec.gov
- IBM non-GAAP measures, Exhibit 99.2sec.gov
- IBM first-quarter 2026 resultsnewsroom.ibm.com
- IBM second-quarter 2026 earnings eventibm.com
- IBM final Q2 analysis on Helmbeam/blog/ibm-q2-2026-earnings-outlook
- Open IBM in Helmbeamhelmbeam.com
Frequently asked questions
Were IBM's 14 July Q2 2026 figures final?
No. They were selected, unaudited preliminary results released while IBM was still closing the quarter. IBM published the completed results on 22 July; Helmbeam's final-results article compares the two disclosures.
Why did IBM say second-quarter growth slowed?
IBM cited the maturing z17 cycle, a late-June shift in customer spending toward supply-constrained infrastructure, cybersecurity distractions and numerous large deals that missed their expected closing dates.
What did the preliminary IBM article tell readers to monitor?
It highlighted segment revenue and margins, Software category growth, IBM Z versus Distributed Infrastructure, backlog conversion, Consulting signings versus revenue, free cash flow and any change to full-year expectations. The final report later reduced expected constant-currency revenue growth to 4–5%.
Helmbeam is a research and analysis tool operated by Scydex Ltd. Scydex Ltd is not authorised or regulated by the Financial Conduct Authority. Helmbeam does not provide investment advice, recommendations, or solicitations to buy or sell securities. All data is for informational purposes only. Past performance of any signal, cohort, or classification does not guarantee future results. All investing involves risk, including loss of principal. Always conduct your own research and consult a qualified financial adviser before making investment decisions.
Where Helmbeam fits in the research process
Helmbeam helps readers monitor whether changes in revenue, margins, cash generation and valuation develop into a structural setup. For IBM, the preliminary release established the questions; the completed quarter supplied the next evidence.
As at 14 July 2026, Helmbeam displayed IBM as IGNORE, meaning no setup was active or forming for the ticker at that time. The state is a dated observation and can change as new evidence arrives.
Helmbeam's last recorded IBM window began on 17 October 2008 with an adjusted structural gate of US$45.19. From that window-entry reference to the 14 July 2026 adjusted close, IBM's price change was +380.34%. It is a price-only historical comparison before trading costs, not an executed or annualised return, and it does not override the dated state.
Every stock is a research opportunity, but not every stock has an active setup. Open IBM in Helmbeam to check the live state, then place it beside our completed Q2 analysis and IBM's primary disclosures.
Helmbeam is available as a free download on iOS and Android.
