
IBM, Oracle, and ServiceNow are all benefiting from enterprise AI investment, but the quality of their revenue is not the same. ServiceNow is closer to a high-renewal, high-visibility subscription software model. Oracle’s OCI and RPO show the strongest AI cloud growth elasticity, but capital expenditures and free cash flow pressure are greater. IBM’s AI revenue is more dispersed: Red Hat and software have resilience, while consulting and mainframe-related revenue are more affected by project cycles. You need to distinguish AI orders, AI revenue, and AI profit instead of looking only at growth rates.

The core question in AI revenue quality is not “whether the revenue is related to AI,” but whether that revenue can be recognized continuously, renewed, generate high margins, avoid massive capital expenditures, and reduce dependence on one-off projects. Subscription revenue is usually more stable. Cloud infrastructure revenue grows faster but is more capital-intensive. Consulting revenue has value as a customer entry point, but it is more exposed to budget approvals and delivery cycles.
Enterprise AI spending is still growing rapidly. Gartner’s forecast for global AI spending in 2026 reaches $2.59 trillion, up 47% year over year. IDC’s forecast for AI infrastructure spending in 2026 reaches $487 billion, up about 53% year over year. This shows that overall AI demand remains strong, but enterprise budgets will prioritize compute, data centers, networking, security, and software modules with measurable returns instead of being distributed evenly across all IT vendors.
The advantage of subscription revenue is that it is predictable, renewable, and expandable. When you evaluate ServiceNow, you should not look only at current-quarter revenue. You should also look at subscription revenue, cRPO, renewal rates, net new ACV, and whether AI add-on modules enter long-term contracts. If AI functionality is only deployed once, revenue quality is limited. If it can be embedded into ITSM, ITOM, customer service, security, and employee workflows, and continue billing as customers scale, its revenue quality becomes meaningfully higher.
The advantage of cloud infrastructure revenue is strong growth elasticity, especially when demand for AI training, inference, and database cloud services rises quickly. But IaaS revenue does not automatically equal high-quality revenue. You still need to examine data center utilization, GPU depreciation, customer concentration, pricing stability, capital expenditures, and free cash flow. Oracle’s OCI is a typical case: growth is very fast, but the return cycle still needs time to be proven.
Consulting revenue is not low-quality revenue, but it is not the same as subscription revenue. IBM’s AI consulting, hybrid cloud migration, data governance, and systems integration help customers implement AI projects and can also drive software sales. But consulting projects are more easily affected by budget approvals, delivery labor, customer internal timelines, and project delays. Therefore, consulting revenue is better viewed as an AI entry point rather than directly equivalent to renewable, high-margin software revenue.
| Revenue Type | Representative Company | Advantages | Risks | Key Metrics |
|---|---|---|---|---|
| Subscription revenue | ServiceNow | Stable, renewable, strong cash flow | Valuation is sensitive to growth | Subscription revenue, cRPO, renewal rate |
| Cloud infrastructure | Oracle | Fast growth, strong AI demand | High capex, long payback cycle | OCI, RPO, capex, FCF |
| Software and hybrid cloud | IBM | Strong customer stickiness, higher margins | Growth divergence, mainframe cycle | Red Hat, software revenue |
| Consulting revenue | IBM | Deep customer entry point, broad project coverage | Deferrable, margin volatility | Consulting revenue, signings |
Summary: AI revenue quality should be judged from five angles: sustainability, recognizability, gross margin, cash flow, and customer dependency. ServiceNow is closer to high-quality subscription revenue. Oracle is closer to high-growth but heavy-asset AI cloud revenue. IBM is a mix of software, consulting, and infrastructure. You should not assume revenue quality is higher just because a company mentions AI, nor should you ignore the capital investment, delivery cycle, and customer concentration behind fast-growing revenue. Truly high-quality AI revenue should be continuously recognizable, reasonably profitable, and convertible into free cash flow.

IBM’s AI revenue quality cannot be judged only by the “AI” label. It needs to be broken down into Red Hat, software, consulting, and infrastructure. Red Hat and hybrid cloud have relatively high continuity. Consulting can help IBM enter customer AI transformation processes. But mainframes and Transaction Processing still have clear cyclical characteristics. IBM’s preliminary second-quarter 2026 data showed revenue up 1%, software up 5%, consulting flat, and infrastructure down 7%, indicating that the AI transition still needs further validation.
The most important part of IBM to break down is Red Hat and hybrid cloud. Starting in 2025, IBM adjusted its software revenue categories, placing Hybrid Cloud, Automation, Data, and Transaction Processing into software segments. This makes it easier to determine which revenue is closer to platform software and which is still tied to the mainframe cycle. Red Hat’s value lies in OpenShift, RHEL, Ansible, and AI platform capabilities entering enterprise hybrid cloud architecture, rather than only selling one-time software licenses.
IBM is also connecting Red Hat with AI inference and virtualization services. Red Hat AI Inference and OpenShift Virtualization Service on IBM Cloud show that IBM wants to manage AI workloads in hybrid cloud environments. Red Hat OpenShift AI also emphasizes enterprise-grade hybrid AI and MLOps platform capabilities. If this type of revenue can continue renewing and expanding, its quality is higher than one-time hardware or short-term projects.
IBM’s consulting business has value because many large enterprises need strategic planning, systems integration, data migration, model governance, application modernization, and process redesign when deploying AI. The problem is that consulting revenue usually advances project by project, making it more vulnerable to delays when customers tighten budgets. Compared with ServiceNow’s subscription revenue, IBM consulting revenue is less predictable and less automatically scalable. Compared with Oracle’s OCI, consulting also does not directly benefit from higher compute consumption.
IBM’s Transaction Processing and mainframe ecosystem have high stickiness, but they are also more prone to quarterly volatility. Customers will not easily migrate core systems in banking, aviation, government, and large enterprises. But when budgets shift toward servers, storage, memory, and cybersecurity, mainframe upgrades, related software renewals, and system modernization projects may be delayed. IBM’s first-quarter 2026 results showed software revenue up 11% and Red Hat up 13%, indicating that the core base remains intact. But the preliminary second-quarter data reminds you that IBM’s AI revenue quality must be evaluated in layers.
| IBM Revenue Module | AI Relevance | Revenue Quality Assessment | Main Risk |
|---|---|---|---|
| Red Hat / Hybrid Cloud | High | Renewable, platform-like, high strategic value | A slowdown would weaken the transformation narrative |
| Automation / Data | Medium to high | Can combine with AI governance and data management | Needs to prove incremental demand |
| Transaction Processing | Medium | Strong mission-critical system stickiness | Mainframe cycle and project deferrals |
| Consulting | Medium to high | Deep customer entry point | Project-based, cyclical, labor-intensive delivery |
| Infrastructure | Medium | Can be related to AI-ready systems | Hardware cycle and budget reshuffling |
Summary: IBM’s AI revenue quality is a combination of “high-stickiness software + project-based consulting + cyclical infrastructure.” Red Hat and hybrid cloud are the parts most worth emphasizing because they are closer to platform-like, renewable revenue. Consulting helps IBM enter customer AI transformation processes, but it is more project-driven and less stable than subscription software. Mainframes and Transaction Processing have customer stickiness, but they can also amplify quarterly volatility. IBM’s AI revenue quality is not weak, but the structure is complex. Red Hat, software, consulting, and infrastructure must be evaluated separately.

Oracle’s AI revenue quality shows a pattern of “strong growth visibility, long cash-flow validation period.” OCI and AI cloud contracts allow Oracle to directly benefit from compute demand, while RPO provides strong order visibility. But negative free cash flow shows that cloud infrastructure expansion requires massive capital expenditures. The question is not whether Oracle has AI demand, but whether these AI cloud orders can turn into long-term revenue with high utilization and high returns.
In Oracle’s fiscal 2026 fourth-quarter results, total cloud revenue grew 47%, while OCI infrastructure revenue grew 93%. This shows that Oracle is already positioned at the center of demand for AI training, inference, and enterprise cloud migration. For enterprise customers, OCI is not just compute resources. It also forms a combination with databases, dedicated cloud, multicloud deployment, and enterprise applications, so its revenue elasticity is stronger than traditional software licenses.
Another layer of Oracle’s advantage comes from databases. For AI applications to truly enter enterprise workflows, they need access to finance, supply chain, customer, transaction, and operating data. Oracle databases have long controlled core enterprise data entry points. Oracle AI Database also emphasizes support for AI applications through vector search, LLM integration, and enterprise data governance. This improves the customer stickiness of Oracle’s cloud revenue.
Oracle’s most striking metric is RPO. Oracle’s investor-disclosed RPO reached $638 billion, up 363% year over year. This indicates strong future contract demand, but RPO is not current revenue or current cash profit. It represents future performance obligations that still require data center construction, customer usage, capacity delivery, and revenue recognition.
This is where Oracle’s revenue quality can be most easily misread. The larger the RPO, the stronger the revenue visibility. But if the conversion cycle is long, customer concentration is high, or delivery costs rise, revenue quality must be discounted. Oracle’s AI revenue is more like an “orders first, capital investment first, profit verified later” model.
Oracle is not a pure IaaS company. Cloud Applications SaaS, Fusion, NetSuite, database cloud, and multicloud database services can all improve revenue stability. Ideally, OCI drives growth, while database and SaaS provide customer stickiness and margin stability. But if AI cloud revenue growth mainly depends on large-scale data center investment, short-term free cash flow will remain under pressure.
| Oracle Revenue Module | Growth Elasticity | Revenue Quality Advantage | Quality Discount Factor |
|---|---|---|---|
| OCI / IaaS | Very high | Direct AI demand, strong orders | High capex, FCF pressure |
| Cloud Applications SaaS | Medium | More stable subscription attributes | Slower growth than OCI |
| Database / Multicloud | Medium to high | Deep data entry point, strong customer stickiness | Requires continued cloud migration |
| RPO | Very high | Strong future revenue visibility | Conversion cycle and fulfillment risk |
| AI data centers | High | Captures the supply window | Power, hardware, depreciation risk |
Summary: Oracle’s AI revenue quality has the strongest two-sided nature. From the demand side, OCI and RPO show that customers are willing to sign long-term contracts for AI cloud resources. From the cash-flow side, negative free cash flow shows that growth requires continued investment. Oracle increasingly looks like a cloud infrastructure operator rather than a traditional asset-light software company. If contracts convert smoothly, data center utilization remains high, and customer concentration risk is controlled, revenue quality will gradually improve. If capital expenditures continue to run ahead of revenue realization, AI growth will also bring higher financial volatility.
ServiceNow’s AI revenue quality is closer to a typical high-quality SaaS model: subscription share is high, cRPO provides visibility into revenue over the next 12 months, and Now Assist can be sold as an AI add-on to existing customers. It does not face Oracle’s heavy capital expenditure burden and is more stable than IBM’s consulting and mainframe cycles. The main question is whether AI functionality can expand contract value rather than compress traditional seat-based revenue.
ServiceNow’s first-quarter 2026 results showed subscription revenue of $3.671 billion, up 22% year over year, while total revenue also grew 22%. This type of revenue is high quality because customers are not buying software once; they continue using the platform across IT services, asset management, security, customer service, HR, and business workflows.
ServiceNow’s platform value comes from workflow embedment. Once enterprises place approvals, tickets, knowledge bases, security responses, and asset data into the same platform, switching costs increase. If AI functionality can improve efficiency inside these workflows, it is more likely to become an upsell rather than an isolated new tool.
ServiceNow’s cRPO was $12.64 billion, up 22.5% year over year. cRPO refers to contract revenue expected to be recognized over the next 12 months, making it more relevant to short-term revenue quality. Compared with Oracle’s massive RPO, ServiceNow’s cRPO is much smaller, but it is more suitable for observing one-year revenue visibility.
This is the key difference between ServiceNow and Oracle: Oracle is about large cloud contracts and future capacity realization, while ServiceNow is about subscription contracts and shorter-cycle revenue recognition. For readers focused on revenue quality, cRPO matters because it verifies whether customers have already locked in future spending through contracts.
ServiceNow’s AI revenue quality also depends on Now Assist. Now Assist customers with more than $1 million in ACV grew by more than 130% year over year, showing that some customers are already willing to pay higher contract values for AI functionality. Now Assist AI agents emphasize embedding AI agents into data, workflows, and integrations, while AI Control Tower strengthens enterprise governance over AI systems, agents, and workflows.
| ServiceNow Metric | Meaning for Revenue Quality | Risk to Watch |
|---|---|---|
| Subscription Revenue | High renewal, predictable | Slower growth can affect valuation |
| cRPO | Visibility into the next 12 months | Large customer contract timing volatility |
| Now Assist ACV | Signal of AI upsell | Continued customer willingness to pay must be validated |
| Workflow Platform | High switching costs | Partial replacement by AI-native tools |
| Free Cash Flow Margin | Advantage of the software business model | Acquisition integration may pressure short-term profit |
Summary: Among the three companies, ServiceNow’s AI revenue quality is closest to “high-visibility subscription revenue.” It does not gain AI growth by selling compute capacity; it embeds AI into existing workflows and monetizes through renewals, expansion, and AI add-ons. Its risks are not capital expenditures, but valuation expectations, AI pricing models, and whether customers will continue paying for Now Assist. As long as subscription revenue, cRPO, and AI ACV grow together, ServiceNow’s revenue quality is easier for the market to recognize.
If ranked by revenue quality, ServiceNow is more stable, Oracle has the strongest growth, and IBM requires the most detailed breakdown. ServiceNow wins on subscription revenue and cRPO. Oracle wins on OCI and RPO, but is weakened by capital expenditures. IBM wins on mission-critical systems and Red Hat, but consulting and mainframe cycles make revenue quality more complex. Different investors should judge them separately by stability, growth, cash flow, and valuation risk.
In terms of revenue sustainability, ServiceNow is the clearest. Subscription revenue and cRPO provide a good view of the next year’s revenue cadence, and the workflow platform has switching costs. IBM’s software business has relatively good sustainability, especially Red Hat and hybrid cloud, but consulting and infrastructure bring volatility. Oracle’s RPO is strong, but revenue recognition and capital returns still need time to be verified.
In terms of AI monetization intensity, Oracle is the most direct. AI infrastructure demand is driving OCI growth, while databases and multicloud deployments can also capture enterprise data demand. ServiceNow’s AI monetization path is more application-layer and process-layer oriented; the core question is whether Now Assist, AI agents, and AI Control Tower can increase customer contract value. IBM’s AI monetization is more dispersed, covering hybrid cloud, consulting, data governance, automation, and system modernization.
In terms of cash-flow quality, ServiceNow has the advantage, IBM still has a mature cash-flow base, and Oracle is in a heavy investment phase. Gartner’s forecast for global IT spending in 2026 reaches $6.31 trillion, showing that the overall enterprise IT pool is still expanding. But capital flows will continue to diverge, and revenue quality depends on who can turn AI demand into sustainable profit and cash flow.
| Dimension | IBM | Oracle | ServiceNow |
|---|---|---|---|
| Subscription / recurring revenue | Medium to high | Medium | High |
| AI growth elasticity | Medium | High | Medium to high |
| Short-term revenue visibility | Medium | Medium to high | High |
| Free cash flow quality | Medium to high | Low to medium | High |
| Capital expenditure pressure | Medium | High | Low |
| Consulting / project dependence | High | Low to medium | Low |
| Overall revenue quality | Medium | Medium to high, but more volatile | High |
If you view these companies from a trading perspective, you also need to consider both fundamentals and actual costs. U.S. stock trading costs usually include more than commissions; they may also include platform fees, external institutional fees, trading activity fees, FX costs, and order execution differences. 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 order page. Service availability depends on the user’s location, identity verification result, platform rules, and applicable laws and regulations. Public financial data can help you judge company quality, but it should not replace a pre-trade review of fee structures, order types, and risk tolerance.
Summary: The three companies do not represent the same AI revenue model. ServiceNow’s revenue quality resembles stable SaaS and is more suitable for readers focused on renewals, visibility, and cash flow. Oracle’s revenue quality resembles AI infrastructure expansion and is more suitable for readers focused on high growth but able to tolerate volatility. IBM’s revenue quality resembles a mature IT company in transition, with both high-stickiness software and consulting/mainframe cyclicality. The final judgment should not depend only on the size of AI revenue, but on whether that revenue is sustainable, profitable, and convertible into free cash flow.
When tracking the AI revenue quality of these three companies, you should not look only at AI language in earnings headlines. Build a metric checklist: for IBM, track Red Hat, software categories, consulting signings, and Transaction Processing; for Oracle, track OCI, RPO, capex, free cash flow, and customer concentration; for ServiceNow, track subscription revenue, cRPO, Now Assist ACV, and renewal quality. This helps you avoid being misled by a single AI narrative.
During earnings season, prioritize the following indicators:
| Tracking Question | IBM | Oracle | ServiceNow |
|---|---|---|---|
| Has AI become real revenue? | Look at software and consulting breakdowns | Look at OCI and RPO conversion | Look at Now Assist ACV |
| Is revenue sustainable? | Look at Red Hat and Transaction Processing | Look at cloud contract renewals and usage | Look at subscriptions and cRPO |
| Does growth consume cash? | Look at FCF and acquisitions | Look at capex and FCF | Look at FCF margin |
| Is valuation under pressure? | Watch growth recovery | Watch capital returns | Watch cRPO slowdown risk |
You should also watch for several signs of deteriorating revenue quality:
Placed in the same framework, the three companies have different validation priorities. IBM needs to prove that Red Hat and software growth can cover volatility in consulting and mainframes. Oracle needs to prove that RPO can become high-utilization, high-return cloud revenue. ServiceNow needs to prove that AI functionality can expand platform contract value rather than weaken legacy seat-based pricing.
Summary: Retail investors can break AI revenue quality into three layers. The first layer is whether revenue is truly growing. The second is whether it can be renewed and recognized. The third is whether it can become free cash flow. For IBM, the focus is separating software, consulting, and mainframe cycles. For Oracle, the focus is separating RPO, OCI revenue, and capital expenditures. For ServiceNow, the focus is subscription revenue, cRPO, and AI upsell. Only by placing these indicators together can you avoid being misled by a single AI narrative.
When continuously tracking U.S. technology companies such as IBM, Oracle, and ServiceNow, you can include earnings metrics, valuation changes, and actual trading costs in the same observation framework. You can use U.S. stock information lookup to view related stock information, and review U.S. stock trading fees to understand order cost structures in advance. As a global multi-asset trading wallet, Biya supports U.S. stocks, Hong Kong stocks, and cryptocurrency trading, and covers local-currency payment scenarios across multiple markets. If services are available in your region, you can also download the app to manage watchlists and trading arrangements. The information above only introduces public market information, trading rules, and fee structures, and does not constitute investment advice.
IBM’s AI revenue should not be judged only by consulting because Red Hat, automation, data, Transaction Processing, and infrastructure all affect AI commercialization quality. Consulting can help customers implement AI, but project cycles and margin volatility are greater, so it cannot represent IBM’s overall AI revenue quality on its own.
Oracle’s RPO growth shows strong future contract demand, but it does not mean current revenue or free cash flow has already improved. To judge revenue quality, you also need to look at RPO conversion speed, OCI utilization, capital expenditures, customer concentration, and margin changes.
ServiceNow’s cRPO is useful for observing AI revenue quality because it represents contract revenue expected to be recognized over the next 12 months. If cRPO and Now Assist ACV grow together, AI upsells are more likely to convert into stable subscription revenue.
AI subscription revenue is usually more stable, while AI cloud revenue has stronger growth elasticity but higher capital expenditure requirements. Revenue quality depends on renewal rates, gross margin, customer usage, infrastructure investment, and free cash flow—not simply on the revenue category.
Retail investors should distinguish AI orders, AI revenue, and AI profit. Orders represent future demand, revenue reflects recognition progress, and profit plus free cash flow reflect business quality. For trading decisions, investors should also consider valuation, fee structure, and their own risk tolerance.
*本文仅供参考,不构成 BiyaPay 或其子公司及其关联公司的法律,税务或其他专业建议,也不能替代财务顾问或任何其他专业人士的建议。
我们不以任何明示或暗示的形式陈述,保证或担保该出版物中内容的准确性,完整性或时效性。


