Whose roadmap is your software estate running on?

Origina says up to 90% of IT budgets go to keeping systems running, leaving 10% for new initiatives, and forecasts enterprise software costs rising 40% by 2027, driven mostly by vendors. It promotes independent support for VMware and SAP to let companies defer upgrades until they make business sense, and says more than 48,000 vulnerabilities were published in 2025 but only around 1% were used in attacks. Sponsored content; no company financial results or market reaction are reported.

Analysis

The investable question is whether independent maintenance becomes a material substitute for vendor support—or remains a procurement tactic used by a narrow set of customers. If adoption broadens, SAP could face longer-lived legacy installations, delayed migrations and pressure on support-related revenue; the offset is that deferred upgrades may eventually create larger, more complex modernization projects. That trade-off matters more to SAP’s migration cadence and cloud-conversion narrative than to near-term group fundamentals absent evidence of meaningful customer uptake.

Treat the article’s budget and vulnerability statistics as vendor-sponsored claims, not verified market data. Independent support can improve customer flexibility, but it does not remove compatibility, security, or migration risks. A further constraint is that enterprises may lack the internal expertise to assess whether third-party support is adequate for their specific systems.

Over 1–3 months, watch for customer adoption evidence, SAP commentary on legacy-system transitions, and any change in cloud backlog or current-cloud growth. Over 6–18 months, broader use could extend legacy lifecycles and defer conversions; that would be a risk to the timing of SAP’s transition, not by itself proof of a durable deterioration in earnings. The thesis weakens if customers continue migrating on schedule or SAP’s cloud metrics remain resilient. Given the sponsored source and no disclosed adoption or financial-impact data, there is no standalone trading signal.

Key Decisions for Investors

• No trade on this article alone. Do not infer material revenue exposure for SAP without evidence that customers are switching support providers at scale.
• Add a watch item for SAP earnings and disclosures: legacy-to-cloud conversion pace, current-cloud growth, and any commentary on third-party maintenance or extended legacy usage.
• If independent-support adoption is later substantiated alongside slower conversions or weaker cloud metrics, reassess SAP exposure; falsify that concern if migration cadence and cloud indicators remain resilient.
• For VMware-related implications, track customer uptake of independent maintenance separately from SAP: the article does not establish adoption, and VMware is not a listed company identity in the supplied mapping.