SAP’s Sean Kask: software firms must become AI companies or perish

SAP chief AI strategy officer Sean Kask said established software companies need to rebuild products around AI rather than add it as another feature. He made the remarks at Wave by Vento in Turin on Thursday; the article provides no financial figures or company-specific outlook.

Analysis

The strategic distinction is economically important but not yet an earnings signal. For SAP, rebuilding workflows around AI could strengthen the value of its ERP data and system-of-record position if customers keep AI actions inside governed business processes. The counter-risk is that AI interfaces make applications more interchangeable, shifting value toward model and cloud platforms and weakening pricing power for traditional software vendors. Microsoft, Oracle and Salesforce are relevant competitive reference points, but the article provides no evidence of customer switching or relative product performance.

Near term (days), this is commentary, not a basis for repricing SAP on its own. Over 1–3 months, look for product releases and customer evidence that AI is embedded in paid workflows—not merely demonstrated—and for any change in cloud backlog, adoption or margin guidance. Over 6–18 months, the key question is whether AI increases retention and monetization enough to offset inference costs, development spending and potentially heavier implementation work.

Contrarian angle: the market may overvalue visible AI features and undervalue the harder-to-replicate data, permissions and process context held in enterprise systems. But that advantage is conditional: if customers can access equivalent workflows through competing platforms, SAP’s installed base may not translate into incremental pricing power. The thesis weakens if AI uptake remains pilot-heavy, monetization is unclear, or management signals material cost without corresponding growth.

Key Decisions for Investors

• No immediate trade from this statement alone; treat it as a strategic framing, not evidence of incremental revenue or a changed competitive position.
• Watch SAP’s upcoming disclosures for paid AI adoption, workflow usage, cloud backlog and margin commentary. Verify whether reported adoption reflects production deployment rather than pilots.
• If evidence emerges that AI is driving paid workflow expansion and retention, consider SAP exposure relative to diversified software peers; size only after assessing valuation and the cost of delivery.
• Falsify the constructive view if adoption remains non-monetized, cloud or backlog indicators weaken, or AI-related spending pressures margins without a corresponding outlook improvement.