
IBM has already disclosed its key Q2 figures in advance. That means the value of the formal July 22 earnings release is not in confirming $17.2 billion in revenue or $2.93 in adjusted EPS again. The real question is whether the revenue shortfall can be recovered, whether Red Hat growth is reliable, and whether the free cash flow target needs to be revised. If you follow IBM stock, enterprise software, hybrid cloud, or post-earnings trading opportunities, you should put segment quality and full-year guidance ahead of the single-quarter headline numbers.

IBM has already disclosed revenue, major segment growth rates, margins, EPS, and first-half cash flow, but these are still selected preliminary figures. The July 22 formal earnings release will be most important for the full segment details, currency impact, deferred revenue, accounts receivable, acquisition-related adjustments, and full-year outlook. In other words, the market already knows Q2 missed expectations. What it does not yet know is whether the shortfall was a quarterly timing issue, a sales execution problem, or a more durable shift in enterprise IT spending.
The IBM Q2 earnings event schedule shows that the company will hold its earnings call at 5:00 p.m. Eastern Time on July 22. Formal materials are usually released before the call. The first round of after-hours pricing tends to reflect the financial statements, while management’s Q&A may trigger a second round of volatility.
According to IBM’s preliminary financial information filed with the SEC, Q2 revenue was approximately $17.2 billion, up 1% year over year. Software revenue grew 5%, consulting revenue was flat, and infrastructure revenue declined 7%. GAAP diluted EPS was $2.27, down 2% year over year; operating non-GAAP EPS was $2.93, up 5%. These numbers show that IBM still delivered earnings growth, but its revenue mix and deal timing fell short of pre-earnings expectations.
The market disappointment mainly came from revenue, not from whether IBM was profitable. FactSet’s pre-earnings consensus was around $17.86 billion in revenue and $3.01 in adjusted EPS. Compared with IBM’s preliminary figures, revenue was short by roughly $660 million and adjusted EPS was short by around $0.08. The revenue gap was about 3.7% of consensus expectations, but because it was concentrated in software and mainframe-related businesses that investors had valued more highly, the valuation impact was much larger than the percentage alone suggests.
| Metric | Q2 Preliminary Data | Market Expectation | What Still Needs Confirmation |
|---|---|---|---|
| Total revenue | $17.2 billion | About $17.86 billion | Currency, product mix, and acquisition contribution |
| Adjusted EPS | $2.93 | About $3.01–$3.02 | Tax rate and adjustment items |
| Software revenue | Up 5% | Faster growth had been expected | Sub-segment breakdown |
| Consulting revenue | Flat | Close to expectations | Signings conversion and margin |
| Infrastructure revenue | Down 7% | Decline larger than expected | z17 versus distributed infrastructure |
| First-half free cash flow | $4.76 billion | Full-year target pending | Second-half collection pressure |
IBM stated on July 14 that its financial close process was still ongoing, and the preliminary disclosure did not include a full balance sheet, software sub-segment growth, or Q3 pacing. CEO Arvind Krishna also acknowledged that the company did not adapt quickly enough to customers’ budget reprioritization and that several large deals did not close on schedule. As a result, the formal earnings call must explain where those delayed deals stand, whether they were reduced or canceled, and how IBM plans to repair its sales execution process.
Summary: July 22 will not create a completely unknown revenue result. The true incremental information will come from the full financial statements and management’s second-half roadmap. You should treat the preliminary data as facts already reflected in the stock, then check whether the formal release proves that the revenue shortfall mainly came from deal timing rather than customers permanently cutting IBM software and mainframe spending. If order status, segment margins, and full-year guidance are explained with quantifiable detail, formal earnings can still repair some investor confidence. If the company cannot provide a verifiable conversion path, simply confirming $17.2 billion in revenue will not be enough to change the market’s view.

Red Hat was one of the few core businesses that clearly improved in Q2, but it cannot single-handedly offset the broader slowdown in IBM software. Preliminary data shows that Red Hat revenue growth improved sequentially to 11%, while total software revenue grew only 5%. That suggests Transaction Processing, related mainframe deals, and some large contracts dragged down the overall portfolio. You need to look at Red Hat’s growth quality, the recovery pace of traditional software, and acquisition-driven revenue together. A single bright spot is not enough to conclude that IBM’s software engine has fully recovered.
For comparison, IBM’s Q1 2026 results showed software revenue growth of 11%, or 8% at constant currency. Red Hat grew 13% as reported and 10% at constant currency. Q2’s stated acceleration to 11% for Red Hat likely uses a comparable management view, but investors still need the formal earnings release to confirm the exact basis and avoid mistaking currency improvement for demand acceleration.
Red Hat’s value does not come only from current-quarter revenue. It comes from subscription renewals, OpenShift workloads, RHEL deployments, and visibility from long-term contracts. If the growth came from stable renewals, new subscriptions, and enterprises migrating critical applications to hybrid cloud, 11% growth can support IBM’s medium-term software valuation. If it mainly came from pricing, currency, or short-term recognition timing, the sustainability is weaker. If the formal materials disclose ARR, bookings, or OpenShift trends, those should be read alongside revenue growth.
Transaction Processing is closely tied to core workloads, capacity expansion, and long-term software licensing among mainframe customers. Beyond revenue size, it also has meaningful profit contribution. The Q2 problem was not that all software demand weakened at the same time. Rather, z17 deal shortfalls and the related software stack came in below company expectations. The formal earnings report should clarify whether Transaction Processing declined year over year, grew at a low-single-digit rate, or merely missed internal plans, and whether the full-year outlook needs to change.
IBM said HashiCorp and Confluent performed strongly in Q2, but acquisition contribution needs to be separated from organic growth. The Confluent acquisition, completed in March, will add revenue, but it will also bring intangible asset amortization, integration expenses, and financing costs. Looking only at total software growth is not enough to determine whether IBM’s legacy business momentum is improving.
| Area to Watch | Positive Signal | Risk Signal |
|---|---|---|
| Red Hat | Solid renewals and OpenShift momentum | Growth driven mainly by currency or pricing |
| Transaction Processing | Delayed orders are signed later | Contracts are reduced or canceled |
| Automation and Data | Multiple product lines grow | Red Hat is the only strong performer |
| Acquired businesses | Cross-selling increases | Acquisitions mask organic slowdown |
| Software margin | Mix offsets amortization | Mainframe software becomes a drag |
Summary: Red Hat’s 11% growth is an important positive signal for the software segment, but it is not sufficient on its own. The combination that would truly support IBM’s software story should include subscription and workload growth at Red Hat, delayed Transaction Processing deals closing later, continued expansion in Automation and Data, and acquisition contribution from HashiCorp and Confluent that does not mask organic slowdown. If the formal earnings release quantifies these items, the market will have a better basis for judging whether Q2 was a contract-timing issue. If total software growth is still mainly supported by acquisitions and currency, Red Hat’s improvement alone will not fully repair the valuation.

Q2 infrastructure revenue fell 7%, but that does not mean enterprise hardware demand broadly collapsed. The more precise reading is that z17 and related software deals came in below expectations, while distributed infrastructure, which includes servers, Power, and Storage, grew 37% and ended the quarter with about $500 million in backlog. Consulting revenue was roughly flat, but signings continued to grow. What you need to identify is budget reallocation across IBM’s own product lines, rather than using one segment growth rate to summarize all enterprise IT spending.
Some customers prioritized purchases of servers, storage, and memory in the final weeks of June to lock in equipment ahead of constrained supply and expected price increases. Cybersecurity issues also diverted management attention. Budget shifts are an industry factor, but the fact that several deals did not close on schedule also reflects IBM’s own execution shortfall. The formal earnings call needs to quantify these two types of impact separately.
Q1’s high base is the starting point for assessing z17. In that quarter, IBM’s infrastructure revenue grew 15%, with IBM Z revenue up 51%, or 48% at constant currency. By Q2, the product-launch comparison base had become more difficult, so some cooling was not surprising. The problem is that the actual decline was worse than IBM had expected in April and also affected related Transaction Processing software.
At the same time, the overall z17 program was still at about 130% of the comparable z16 period, and customers representing 85% of installed MIPS had maintained or increased capacity. A strong overall product cycle and a Q2 deal gap can both be true. The formal earnings report needs to use backlog, installed capacity, and July deal activity to prove whether the second half can recover.
In the short term, customers prioritizing servers, storage, and memory can pressure traditional software, mainframe expansion, and consulting projects that can be delayed. That creates revenue-recognition pressure for IBM. Over the medium term, however, more AI infrastructure also creates demand for data governance, hybrid cloud orchestration, automation, and security, which are exactly the markets IBM’s software and consulting businesses want to serve. The key question is not whether AI spending is increasing, but whether IBM can convert hardware procurement into later software and services revenue.
Consulting revenue was flat in Q2, or up about 1% at constant currency, but signings continued to grow and were supported by generative AI. Signings are a leading indicator of demand, while revenue still depends on project kickoff, staffing, and client acceptance. Large projects may take months to convert into revenue and should not be simply added to next-quarter forecasts.
IBM’s Q1 prepared remarks focused on consulting backlog, generative AI, and margins. If Q2 revenue was weak but signings, backlog, and margins improved, demand is more likely delayed than lost. If all three weaken at the same time, the risk extends beyond revenue timing.
| Business | Q2 Signal | What Needs Verification | What It Helps Determine |
|---|---|---|---|
| IBM Z | Below expectations | Orders, capacity, July signings | Cycle issue or demand issue |
| Distributed infrastructure | Up 37% | $500 million backlog | Whether delivery can continue |
| Infrastructure support | Not fully broken out | Renewal rate and margin | Stability of installed-base value |
| Consulting | Revenue flat, signings up | Backlog and margin | Whether signings can convert to revenue |
| GenAI | Contributed to signings | Software and consulting conversion | Quality of demand |
Summary: IBM’s Q2 exposed a combination of enterprise budget reprioritization and internal execution weakness, not a simultaneous collapse in hardware and services demand. z17 underperformed in the quarter but still had a stronger cumulative program than the previous generation. Distributed infrastructure grew sharply because of server, Power, and Storage purchases. Consulting signings improved, but revenue conversion has not yet been proven. If the formal earnings report shows delayed mainframe orders beginning to close, a clear delivery schedule for the $500 million backlog, and stable consulting backlog, Q2 looks more like a pacing issue. Otherwise, the risk will extend into the second half.
IBM missed revenue expectations in Q2, but adjusted pre-tax margin still expanded by 30 basis points year over year, and first-half free cash flow reached $4.76 billion. That means the company has not yet shown a simultaneous deterioration in profitability. The key financial question in the formal report is whether the revenue shortfall will pressure second-half margins, and whether IBM can still achieve its original 2026 goals of constant-currency revenue growth above 5% and free cash flow increasing by about $1 billion year over year.
Q2 GAAP gross margin was 57.7%, down 100 basis points year over year. Non-GAAP gross margin was 59.4%, down 70 basis points. At the same time, GAAP pre-tax margin was 14.4%, down 90 basis points, while non-GAAP pre-tax margin was 19.2%, up 30 basis points. This shows that gross margin was affected by revenue mix and acquisition amortization, but productivity measures and expense control still supported adjusted pre-tax profit.
Non-GAAP metrics should not replace GAAP results. IBM’s definition of adjusted metrics excludes acquisition-related intangible asset amortization, certain transaction and integration expenses, and retirement-related costs. Acquisitions such as Confluent increase these adjustments. That means you should use non-GAAP margins to assess ongoing operating efficiency, but also use GAAP profit and cash flow to test whether acquisition costs are genuinely eroding shareholder value.
IBM’s first-half operating cash flow was $7.766 billion. After excluding changes in IBM Financing receivables, it was $5.503 billion; after subtracting $743 million of net capital expenditures, free cash flow was $4.760 billion. Q1 free cash flow was $2.22 billion, which implies Q2 contributed roughly $2.54 billion. Year-over-year and seasonal cash flow details still require the formal statements, but the absolute amount suggests the target has not become impossible after one quarter.
IBM’s 2025 annual report showed 2025 free cash flow of $14.7 billion. Q1 guidance expected 2026 free cash flow to increase by about $1 billion year over year, so roughly $15.7 billion can be used as a reference point for the original target scale. If that target remains unchanged, IBM would need to generate about $10.9 billion of free cash flow in the second half. Seasonal collections can help, but delayed orders raise execution requirements.
Cash flow quality matters more than the total number. You should watch accounts receivable, deferred revenue, capital expenditure, and acquisition-related cash integration costs. IBM’s Q1 2026 10-Q showed that debt increased after the Confluent transaction, and the Q2 balance sheet will help investors assess deleveraging, dividend capacity, and room for investment.
Revenue and free cash flow do not always move in the same direction. IBM may lower revenue guidance due to delayed orders while maintaining cash flow through margins and collections. It may also maintain revenue guidance but push deal-execution pressure into the fourth quarter. Therefore, “maintained guidance” is not automatically positive; the assumptions and buffers behind it matter more.
| Scenario | Revenue Guidance | Free Cash Flow | Meaning |
|---|---|---|---|
| More positive | Maintains growth above 5% | Increases by about $1 billion | Orders can be recovered |
| Neutral | Slightly reduced | Maintained | Margins and collections offset pressure |
| More cautious | Depends on Q4 deal execution | Maintained or narrowed | Execution risk rises |
| More negative | Meaningfully reduced | Also reduced | More than a quarterly timing issue |
Summary: IBM’s defensive profile is still supported mainly by margins and free cash flow, not by Q2 revenue growth. Adjusted pre-tax margin expansion and $4.76 billion in first-half free cash flow show that the operating base remains intact. However, a full-year cash flow target near the $15.7 billion scale means the second half must carry a heavier collections burden. The most convincing outcome would not be simply maintaining guidance. It would be maintaining guidance while showing order recovery, controlled accounts receivable, sustainable margins, and enough capital-allocation flexibility. If IBM maintains the target without those supporting details, the market may continue to discount the guidance.
IBM stock will not stabilize after earnings simply because final revenue differs from the $17.2 billion preliminary figure by a few million dollars. The stock’s direction will depend on whether management can prove that delayed orders are recoverable, that Red Hat growth is sustainable, and that full-year revenue and free cash flow paths are credible. You should observe the earnings reaction in this order: guidance changes, order evidence, segment quality, cash flow delivery, and market confirmation. Avoid treating one after-hours rebound as proof that fundamentals have already recovered.
IBM’s July 8 earnings announcement confirmed that the earnings call will be held at 5:00 p.m. Eastern Time, which corresponds to 5:00 a.m. Beijing time on July 23. The first round of after-hours pricing will reflect the financial statements and guidance, while analyst Q&A may lead to repricing afterward.
You can use the following questions to judge whether management is providing verifiable information:
High-quality answers should include amounts, percentages, or time windows. If management only says that customer interest is strong or the pipeline is healthy without explaining July progress, the information value is limited. Even if IBM slightly reduces revenue guidance, the market may still view the risk as better reflected if the company quantifies order recovery and gives a conservative baseline.
| Signal | More Positive | Neutral | More Negative |
|---|---|---|---|
| Full-year revenue | Orders start to recover | Slightly reduced | Meaningfully reduced or target withdrawn |
| Red Hat | Growth keeps improving | Maintains low double-digit growth | Falls to single digits |
| Transaction Processing | Delayed contracts are signed | Still under negotiation | Reduced or canceled |
| Consulting | Backlog and margins improve | Signings stable | Signings weaken too |
| Free cash flow | Target maintained and collections normal | Depends on Q4 | Guidance reduced |
| Stock and volume | Stabilizes on strong volume for several days | High volatility | Rebounds, then makes a new low |
After-hours quotes can be moved by a relatively small number of orders. A more reliable confirmation window is the several trading days after the earnings call, combined with volume, analyst forecast revisions, and performance versus software peers. If IBM continues to outperform peers after improved guidance, the recovery signal becomes more credible.
Earnings trading also involves spreads, slippage, platform fees, external agency fees, and currency conversion costs. FINRA’s explanation of extended-hours trading risks notes that pre-market and after-hours trading usually has lower liquidity, higher volatility, and inconsistent quotes. Market orders may execute away from expected prices, while limit orders may not be fully filled.
If you use the U.S. stock search tool to track IBM, you can first record price, volume, and bid-ask spread before and after the earnings materials are released. Biya charges $0 commission for U.S. stock trading, with a platform fee of $0.005 per share, a minimum of $0.99 per order, and a maximum of 1% of trade value. External agency fees and trading activity fees are $0.00396 per share. Fractional-share orders are charged a platform fee equal to 1% of the total trade value, capped at $1. The actual amount should be based on the order page and account statement.
International investors also need to consider currency conversion. You can use real-time exchange rates to estimate the difference between local currency and the U.S. dollar, but actual settlement may differ. Service availability depends on location, identity verification, platform rules, and applicable laws and regulations. Public earnings analysis does not constitute investment advice.
Summary: To judge IBM’s direction after earnings, first check whether full-year guidance changes, then verify whether delayed orders, Red Hat, Transaction Processing, and free cash flow provide quantifiable evidence. Finally, wait for regular-session price and volume confirmation. An after-hours rise only shows that the first orders entering the market leaned toward buying; it does not independently prove that fundamentals have recovered. If the company provides a verifiable order-recovery path, maintains cash flow, and improves software quality, the stock is more likely to be re-evaluated. If answers are vague, guidance is cut, and collections are under pressure, a lower share price alone is not a sufficient reason to buy.
If you follow U.S. stocks such as IBM that are driven by earnings and guidance, you can use Biya Web Trading to monitor pre-market and after-hours quotes, regular-session trading, and order costs, then make decisions based on your own risk tolerance. Biya is a global multi-asset trading wallet that supports U.S. stocks, Hong Kong stocks, crypto, and other markets. Users who meet local service requirements can also use the global multi-asset trading wallet to learn more about account and funding arrangements. U.S. stock trading commission is $0, while platform fees, external agency fees, and other charges are subject to the Fee Center and order page. Earnings releases can cause price gaps and lower liquidity, so trading should comply with local regulatory requirements and leave room for volatility.
IBM will hold its Q2 earnings call at 5:00 p.m. Eastern Time on July 22, 2026, which corresponds to 5:00 a.m. Beijing time on July 23. Full financial materials are usually released before the call begins. International investors should pay attention to daylight-saving time conversion and refer to IBM’s investor-relations schedule for the latest timing.
Preliminary results include selected figures before the full financial close is completed, while formal Q2 earnings provide the complete income statement, balance sheet, cash flow statement, segment details, accounting adjustments, and full-year outlook. Final numbers may change slightly, but the more important difference is that formal materials can explain revenue quality and second-half assumptions.
Investors should look at both GAAP and non-GAAP EPS. GAAP EPS includes acquisition amortization, integration costs, and retirement-related costs, making it closer to the full accounting result for shareholders. Non-GAAP EPS helps compare ongoing operating efficiency. You should also check whether excluded items are recurring and whether their size is increasing, rather than relying only on the higher adjusted figure.
One quarter of weaker-than-expected revenue does not automatically mean IBM will cut its dividend. Dividend safety depends more on full-year free cash flow, dividend payout needs, debt interest, and capital investment. You should watch cash flow coverage and management’s capital-allocation commentary in the formal earnings release, rather than using one quarter’s revenue or stock-price decline to infer future dividends.
The main risks of after-hours trading are lower liquidity, wider spreads, higher volatility, and incomplete order execution. Actual costs may also include platform fees, external agency fees, and currency conversion. Different platforms support different trading sessions and order types, so investors should check platform rules, the order page, account statements, and local regulatory requirements before trading.
*This article is provided for general information purposes and does not constitute legal, tax or other professional advice from BiyaPay or its subsidiaries and its affiliates, and it is not intended as a substitute for obtaining advice from a financial advisor or any other professional.
We make no representations, warranties or warranties, express or implied, as to the accuracy, completeness or timeliness of the contents of this publication.



