Whose roadmap is your software estate running on?

You can choose to defer software upgrades based on business needs instead of vendor schedules.

Origina, an independent software maintenance and support provider, asserts that enterprise IT budgets are disproportionately allocated to maintaining existing systems, with up to 90% of IT budgets spent on "keeping the lights on" and only 10% left for new initiatives. The company projects a 40% increase in enterprise software costs by 2027, largely driven by vendor-imposed changes rather than customer needs. Origina advocates for businesses to control their software estate's evolution based on their own strategic timelines, such as mergers or capability upgrades, rather than succumbing to vendor-driven support deadlines or licensing model shifts. They highlight this approach with examples like extending VMware license support and planning SAP modernization on business-driven schedules, while also addressing security vulnerabilities proactively. Origina's OPTAS service is presented as a tool for managing these risks.

The current model forces IT departments into a reactive stance, dictated by vendor roadmaps and end-of-support dates, consuming the majority of their budget and diverting resources from innovation. This sponsored post from Origina challenges this status quo, proposing an alternative where businesses maintain control over their software lifecycles, ensuring stability, compliance, and security without succumbing to vendor-imposed upgrade pressures. The argument centers on aligning IT changes with genuine business requirements, such as mergers or strategic capability enhancements, rather than arbitrary support expiration dates.

This perspective suggests a market opportunity for third-party maintenance and support providers who can offer businesses more flexibility and cost control over their software estates. By decoupling IT updates from vendor-driven timelines, companies can potentially reallocate significant portions of their budget, currently tied up in reactive maintenance, towards strategic projects and genuine innovation. The emphasis on proactive vulnerability management, rather than reactive patching driven by disclosed vulnerabilities, also points to a shift in how security is approached within enterprise IT.