KEY READ-THROUGHS FROM SAP’S Q3 2026 EARNINGS CALL

SAP’s results indicate a redistribution of enterprise technology spending toward cloud infrastructure, governed data, and business-process automation, rather than an indiscriminate expansion in IT budgets. Current cloud backlog grew 26% at constant currencies, approximately 90% of the 50 largest deals included AI and business data, and management described increasingly comprehensive cloud contracts. Simultaneously, services revenue declined 5%, SAP identified opportunities to reduce external contractors, and cloud gross margin contracted despite strong revenue growth. The most actionable implications are positive for established data-distribution and cloud-hosting partners, negative for labor-intensive service delivery, and competitively challenging for application vendors seeking to sell separate data and AI platforms into SAP-centered enterprises. The strongest conclusions concern identifiable revenue channels and competitive pressure, not automatic changes to other companies’ earnings forecasts.

ENTERPRISE DATA AND ANALYTICS

SNOWFLAKE GAINS A DISTRIBUTION CHANNEL, NOT JUST ANOTHER DATA CONNECTOR (READ-THROUGH 1)

Affected company: Snowflake (SNOW: United States). Directional impact: Positive. Magnitude: Moderate fundamental opportunity, potentially meaningful within SAP-intensive enterprise accounts; no defensible near-term revenue uplift can be quantified from this call.

The supporting evidence is SAP’s statement that AI, data, and platform products significantly contributed to cloud growth, together with approximately 90% attachment of AI and business data across its 50 largest transactions. Management also described RISE contracts becoming richer as customers purchase a harmonized data layer alongside ERP migration. This matters because Snowflake is an established participant in that architecture, not simply an external platform competing for access to SAP data.

Snowflake’s published partnership terms establish 2 commercial routes. Existing customers can connect their Snowflake environments to SAP Business Data Cloud through bidirectional, zero-copy integration. New customers can purchase SAP Snowflake, a full Snowflake offering certified, sold, and supported by SAP, with Snowflake participating in co-selling. The latter creates a direct distribution mechanism: SAP’s account relationships and ERP transformation budgets can introduce or expand Snowflake deployments without requiring Snowflake to originate every opportunity independently.

The transmission mechanism is broader access to governed financial, procurement, inventory, and customer data, followed by incremental analytical and AI workloads. Business context that previously required expensive extraction and reconciliation becomes more accessible for production use. That can increase Snowflake compute consumption and improve the commercial viability of projects previously constrained by data preparation. Zero-copy access does not itself generate billable usage, but it lowers an important obstacle to workloads that do.

The non-consensus implication is that stronger SAP Business Data Cloud adoption is not necessarily negative for Snowflake. SAP’s ownership of business semantics can coexist with Snowflake’s monetization of analytics and execution. Management’s acknowledgment that expanding resale arrangements and Business Data Cloud structures affect cloud margins is consistent with an ecosystem in which some revenue growth carries payments to external technology partners. The call does not disclose how much of that effect relates to Snowflake, so a specific revenue transfer cannot be inferred.

The near-term catalyst is confirmation of partner-sourced wins, deployment activity, and consumption in Snowflake’s subsequent reporting. The fundamental opportunity develops over approximately 2-8 quarters as integrations move into production. The principal limitation is that zero-copy sharing reduces the need for duplicated storage and some data movement; the positive thesis rests on incremental workloads and distribution, not an assumption that every additional SAP data set creates equivalent storage revenue.


SAP’S MASTER-DATA EXPANSION INCREASES COMPETITION FOR SALESFORCE’S INFORMATICA PLATFORM (READ-THROUGH 2)

Affected company: Salesforce (CRM: United States). Directional impact: Negative competitive read-through for Informatica and the broader enterprise data-platform opportunity. Magnitude: Moderate strategic pressure in overlapping accounts, but low immediate impact on consolidated Salesforce earnings.

SAP stated that its acquisitions of Dremio and Reltio extend its capabilities “far beyond SAP data” and provide “a unified context layer across the entire data landscape.” Management additionally discussed automated generation of non-SAP data products and AI-assisted matching of customer, supplier, and material records. These capabilities move SAP beyond supplying application data into managing the broader enterprise data foundation.

The competitive exposure belongs to Salesforce because its acquisition of Informatica was completed in November 2025. Informatica’s capabilities include master data management, data integration, quality, governance, and metadata management. These functions overlap directly with the problems SAP intends to address through Reltio, Dremio, and Business Data Cloud. This is therefore more specific than a generic assertion that SAP and Salesforce compete in enterprise AI.

The transmission mechanism is budget consolidation during ERP transformation. A customer already purchasing SAP cloud migration and AI may obtain identity resolution, data harmonization, governance, and business context within the same commercial program. That increases the burden on a separate Informatica-led proposal to demonstrate incremental functionality or superior economics. Even where displacement does not occur, a more credible alternative can constrain pricing, reduce expansion scope, or lengthen competitive evaluations.

The pressure is strongest in SAP-centered operating environments where customer, supplier, material, and financial records are central to the proposed AI use case. It is less direct in Salesforce-centered customer-engagement environments or heterogeneous estates where Informatica’s existing coverage and integration relationships remain valuable. Salesforce also has substantial application context and distribution of its own; SAP’s progress does not establish universal architectural superiority.

The near-term catalyst is product evidence at SAP TechEd and delivery of the non-SAP data capabilities discussed for Q1. The fundamental effect is more likely to appear over 12-36 months through new-project selection, expansion decisions, and renewals. No customer displacement from Informatica was identified on the call. The high-conviction conclusion is increased competitive overlap and pricing pressure within a defined opportunity, not an immediate Salesforce revenue shortfall.

IT SERVICES AND DIGITAL TRANSFORMATION

AUTOMATION IS REDUCING THE REVENUE INTENSITY OF SAP IMPLEMENTATION AND MANAGED SERVICES (READ-THROUGH 3)

Affected companies: Accenture (ACN: Ireland), Capgemini (CAP: France), Infosys (INFY: India), and Tata Consultancy Services (TCS: India). Directional impact: Negative for labor-based delivery revenue and conventional application-management economics. Magnitude: High structural importance for exposed service lines; moderate and contract-dependent impact at the consolidated company level.

The clearest evidence is SAP’s 5% services revenue decline and management’s warning of further “downward pressure on billable hours and services revenue also next year.” SAP also described AI-driven migration tools, approximately 70% more internal code contributions, and automation across deployment, monitoring, incident management, and application operations. Management specifically identified an opportunity to “cut some of our third party contractors we deploy in our cloud delivery.”

The transmission mechanism is fewer paid human interventions per implementation or operating workload. Automated data migration, code conversion, testing, incident resolution, and application administration reduce the labor required to deliver a given customer outcome. Providers paid by time and materials can experience revenue compression even when customer project activity remains healthy. In managed services, automation can lower delivery costs initially, but customers can reclaim part of the benefit through productivity commitments and contract repricing.

This creates a crucial distinction between revenue and margin. A fixed-price provider that automates faster than its contractual pricing resets can initially improve margins. A time-and-materials provider may surrender revenue more quickly. Over time, competitive bidding tends to transfer some productivity gains to customers. Consequently, the call is more clearly negative for the historical relationship between project activity and billable headcount than it is for every provider’s immediate operating margin.

The non-consensus risk is that strong SAP cloud bookings and weak services revenue can coexist without inconsistency. Enterprise modernization can accelerate while the services revenue earned per migration declines. A bullish interpretation based solely on the size of the SAP installed-base transition would therefore overstate the benefit to labor-intensive delivery models.

The near-term catalyst is commentary on productivity commitments, contract repricing, utilization, and application-management demand in upcoming services earnings. SAP’s stated intention to adjust third-party arrangements over the next 12 months makes this more than a distant technology scenario. However, the call did not identify the contractors affected. Accenture, Capgemini, Infosys, and TCS should be treated as exposed ecosystem participants, not as confirmed recipients of SAP contract reductions.

The longer-duration effect is a change in competitive advantage over approximately 1-3 years. Reusable intellectual property, industry-specific implementation assets, and outcome-based pricing become more important than the ability to supply large teams. Geographic exposure follows the global delivery model: this is relevant to Indian providers serving European and North American clients, not merely to European consulting firms.


DATA REMEDIATION AND PROCESS REDESIGN REMAIN REAL SERVICES BOTTLENECKS (READ-THROUGH 4)

Affected companies: Accenture (ACN: Ireland), Capgemini (CAP: France), and Infosys (INFY: India). Directional impact: Positive for complex transformation, data engineering, and industry-specific deployment work. Magnitude: Moderate demand support, with greater relevance to project mix and bookings than to an immediate broad-based earnings upgrade.

The supporting evidence is the combination of 26% current cloud backlog growth, a strong Q4 pipeline, broader RISE contract scope, and management’s acknowledgment that customer data problems still constrain deployment. Klein stated that “not everything works out of the box” and emphasized that customers “need still a clean core.” The call also identified completed migrations at major enterprises, demonstrating that the opportunity extends beyond software demonstrations and pilot announcements.

The transmission mechanism is the work required to make enterprise AI operational. Customers must reconcile master data, redesign approval processes, map authorization rules, remove unnecessary customization, integrate non-SAP systems, and manage organizational adoption. These activities depend on business-specific judgment and accountability. Faster code generation does not eliminate disagreement over which customer record is authoritative, which employee may approve a transaction, or how a redesigned process should operate.

Accenture has a particularly direct channel through its established forward-deployed engineering program with SAP. The program covers discovery, process redesign, data integration, AI implementation, and production activation. That positioning matches the bottlenecks described in the call more closely than a generic claim that all consulting benefits from AI spending. Capgemini and Infosys also have established SAP transformation capabilities, although the call did not allocate any particular customer project to them.

The positive conclusion is deliberately narrower than a general IT-services recovery. More complex, higher-value work can offset some erosion in routine delivery hours, but it does not guarantee that total services revenue per customer will rise. Providers must capture the architecture and adoption budget rather than merely retain the coding and support work that automation is reducing.

The near-term catalysts are Q4 SAP bookings and subsequent implementation awards. Because approximately 50% of SAP’s annual bookings occur in Q4, the largest potential replenishment of transformation activity remains ahead. Software bookings are not equivalent to service-provider bookings, however, and implementation revenue can lag contract signing by several quarters.

Over approximately 6-24 months, the strongest relative positioning belongs to firms demonstrating paid production deployments, reusable industry solutions, and improved delivery economics. The cross-portfolio implication is that labor commoditization and transformation demand are simultaneous exposures. A services portfolio should not assume that the positive migration cycle automatically neutralizes the negative pricing and productivity cycle.

ENTERPRISE APPLICATIONS AND HUMAN CAPITAL MANAGEMENT

SAP’S SUITE-LEVEL AI OFFERING INCREASES THE COMPETITIVE BURDEN ON WORKDAY (READ-THROUGH 5)

Affected company: Workday (WDAY: United States). Directional impact: Negative incremental competitive pressure, particularly in SAP-centered enterprises. Magnitude: Moderate strategic significance; low immediate earnings impact without evidence of changed win rates or renewals.

SAP management cited IDC estimates indicating that SAP was growing more than 1.7x faster than the overall HCM market. The call identified SuccessFactors activity, a SmartRecruiters deployment, and the intended acquisition of TechWolf to extend workforce and skills intelligence. These disclosures support a more specific competitive conclusion than the general observation that SAP is adding AI features.

The transmission mechanism is the integration of workforce information with finance, procurement, operational planning, and enterprise permissions. An organization evaluating HR software may increasingly assess whether workforce decisions can be executed within a broader governed process. SAP’s proposition is that the customer can obtain this context across its suite without assembling every connection independently. That can strengthen SAP’s position in HCM expansion and replacement decisions, particularly where SAP already controls the financial and operational backbone.

The potential effect on Workday is higher sales friction, increased investment required to demonstrate cross-system value, and pressure on the economics of competitive deals. It is not necessarily the loss of an existing subscription. Large HCM deployments are difficult to replace, and the more immediate competition may concern adjacent modules, recruiting, skills intelligence, or new AI budgets rather than the core system.

Workday is not a passive competitor. Its October product announcements included agents across hiring, payroll, accounting, and deployment, with orchestration and controls linked to customer policies and permissions. Those capabilities directly address the same requirements SAP emphasized. The high-conviction implication is therefore a more demanding competitive market and a higher cost of differentiation, not a conclusion that Workday lacks a viable response.

The near-term trading catalyst is the comparison between SAP’s HCM commentary and Workday’s subsequent subscription outlook, competitive commentary, and evidence of paid AI adoption. The longer-duration effect unfolds over 12-36 months through enterprise selection cycles. SAP’s reported HCM outgrowth is a warning against assuming that AI demand lifts all HCM vendors equally; market expansion and market-share redistribution must be evaluated separately.

CLOUD INFRASTRUCTURE AND AI PLATFORMS

ERP MIGRATION SUPPORTS HYPERSCALER WORKLOADS, WITHOUT PROVING A PROPORTIONATE GPU SPENDING CYCLE (READ-THROUGH 6)

Affected companies: Amazon (AMZN: United States), Microsoft (MSFT: United States), and Alphabet (GOOGL: United States). Directional impact: Positive for cloud infrastructure and related data services. Magnitude: Moderate within SAP-related workloads, but modest at the diversified parent-company level.

The supporting evidence is SAP’s 25% constant-currency cloud revenue growth, 26% current cloud backlog growth, named customer go-lives, and management’s statement that AI was a principal driver of cloud migration. These are more relevant to infrastructure demand than the number of AI agents announced: they indicate movement of production business systems and associated data into cloud environments.

The supplier relationships are established. AWS hosts RISE with SAP workloads, Azure supports SAP cloud deployments and Business Data Cloud, and Google Cloud provides SAP hosting and data-platform integrations. The transmission mechanism is recurring consumption of compute, memory, storage, networking, backup, and resilience services as customer environments are deployed and operated. Additional analytics and AI use can create further consumption around the core ERP workload.

The important non-consensus distinction is between SAP’s software revenue and the infrastructure revenue earned underneath it. Higher application pricing or broader software bundles do not create a proportionate increase in hyperscaler consumption. Conversely, actual customer go-lives can be more economically relevant to infrastructure providers than a software contract signed well before deployment. The call supports the direction of infrastructure demand, not an equivalent 25% growth forecast for any supplier’s SAP business.

Model choice reinforces the value of broad cloud platforms while limiting conclusions about any particular model vendor. SAP offers access to more than 70 models, is increasing its use of open-weight models, and stated that it is “not committing to a preferred model.” Customers may consume infrastructure and model-management services even as the identity of the underlying model changes. The more durable exposure is to hosting and orchestration across models, rather than an assumption that SAP adoption creates exclusive demand for a particular proprietary model.

The geographic signal is also constructive but specific. Stronger cloud growth in EMEA and APJ was attributed partly to lower existing cloud penetration, while North America was described as advanced in AI adoption. This points to a broader geographic migration opportunity, including regional hosting and compliance capabilities. Slower Americas growth should not automatically be interpreted as weaker US AI demand.

The near-term catalyst is corroboration in hyperscaler commentary on enterprise migrations and production consumption over the next 1-2 reporting periods. The fundamental benefit develops over approximately 1-3 years as contracted environments go live and expand. Competition for hosting share, customer optimization, and SAP’s own delivery efficiencies limit the amount of revenue each provider ultimately captures.

The semiconductor implication is intentionally narrower. The call does not disclose GPU orders, accelerator utilization, model-training capacity, or a supplier allocation. ERP hosting, model inference, and frontier-model training have different infrastructure requirements. SAP’s results therefore support enterprise cloud demand more directly than a new earnings revision for AI semiconductor suppliers. Across portfolios, exposure to Snowflake, hyperscalers, and SAP implementation providers should also be recognized as partially linked to the same customer deployment cycle, rather than treated as independent AI growth opportunities.