Third-Party Support for IBM Software: A CIO's Playbook

Why IBM Software Support Costs Spiral — and What You Can Do About It

IBM's support and subscription model is one of the most effective cost escalation mechanisms in enterprise software. The base rate — approximately 20 percent of the original licence value per year — appears modest at first glance. But compounded at 5 to 7 percent per year over a five-year period, and applied against a growing software estate, the cumulative support cost often exceeds the original licence investment. For organisations with $5 million or more in IBM software licences, this trajectory produces millions of dollars in annual support spend, much of it for products that are stable, mature, and not meaningfully improved by IBM's ongoing development investment.

IBM's support renewal model is structured to maximise renewal rates. Subscription and Support agreements auto-renew by default unless the customer sends a written non-renewal notice within the contractual cancellation window, which is typically 90 days before the renewal date. Organisations that miss this window are automatically committed to another full support term at the escalated rate. IBM's account teams will rarely remind clients of the approaching cancellation deadline — their compensation depends on renewals, not on making it easier for clients to exit. The result is a support cost that grows reliably and is difficult to interrupt without deliberate, proactive management.

Third-party IBM software support (TPSS) changes this dynamic fundamentally. Third-party providers — most notably Origina (formerly known as IBM-exclusive TPSS) and Rimini Street — offer support for the same IBM products at 50 percent or less of IBM's S&S fees, with multi-year price locks that eliminate the annual escalation dynamic. They maintain the software on the version you are running, without requiring upgrades that IBM uses to justify support renewals, and they provide dedicated engineering support rather than the tiered, script-driven support model IBM's standard S&S delivers.

The Legal Foundation: Is Third-Party IBM Support Legal?

Third-party support for IBM software is entirely legal. The software licence agreement grants the organisation the right to use the software it has licensed in perpetuity — for perpetual licence products. Third-party support does not require IBM's consent, does not modify the original software, and does not transfer the licence. The organisation retains its IBM licence, continues using IBM software under the original terms, and simply changes who provides the support and maintenance services from IBM to a third-party provider.

IBM's response to the TPSS market has been to tighten its contractual language around security patches, updates, and interoperability — specifically to make the argument that switching to TPSS creates security or compliance risk by eliminating access to IBM's security updates. This argument requires careful evaluation. For stable, mature IBM products running defined workloads in controlled environments, the security update requirement is often less urgent than IBM implies. For products with active vulnerability profiles or those integrated with externally-facing systems, the security update consideration is more material. Third-party support providers address this through independent security patch analysis and, in some cases, their own security advisory services for supported products.

For IBM subscription-based products — those sold as annual subscriptions rather than perpetual licences — the TPSS model does not apply in the same way. Subscription licences terminate when the subscription expires, and third-party support of subscription-based IBM products requires that the client maintain at minimum an IBM licence entitlement. For cloud-based IBM services, TPSS is generally not relevant. The TPSS opportunity is primarily focused on perpetual IBM software licences — our IBM advisory team can help you identify which elements of your IBM estate qualify.

Eligible IBM Products: Where Third-Party Support Works Best

The most suitable IBM products for third-party support share a common profile: perpetual licence basis, mature and stable codebase, low dependency on IBM's ongoing development roadmap, and no active migration or modernisation commitment from the organisation. Across these criteria, the following IBM product categories are consistently the strongest TPSS candidates.

IBM WebSphere Application Server. Traditional WAS deployments running legacy Java applications on established infrastructure are ideal TPSS candidates. Organisations that have no planned migration to WAS Liberty or alternative application servers, and whose WAS version is functioning reliably, have no inherent need for IBM's support renewal beyond the security update question addressed above.

IBM DB2. Mature DB2 deployments on established versions — particularly DB2 LUW on Linux or AIX — are strong TPSS candidates. For organisations with no plans to upgrade DB2 or migrate to alternative database platforms in the near term, IBM's support renewal is primarily paying for the right to receive fixes for problems they are not experiencing in production.

IBM MQ. Established IBM MQ deployments running message broker workloads in stable environments qualify, though the ILMT requirement for sub-capacity licensing remains even under TPSS — IBM's compliance obligations for software usage are independent of who provides support. The IBM MQ licensing guide covers the licence compliance dimension in detail.

IBM Cognos Analytics. On-premises Cognos BI and reporting environments with satisfied user communities and no pending platform upgrade are excellent TPSS candidates. Cognos is mature, stable, and IBM's Cognos development investment is modest relative to its cloud-native analytics competitors.

IBM Notes and Domino. For organisations that have not completed or are not actively pursuing Notes/Domino migration, TPSS from providers like Origina delivers specialist Domino engineering support that IBM's standard S&S increasingly cannot match as IBM has deprioritised Domino investment.

IBM Tivoli products. IBM's Tivoli portfolio — Tivoli Monitoring, Tivoli Storage Manager (now Spectrum Protect), Tivoli Identity Manager — includes many mature products where third-party support is a viable cost reduction lever. IBM has restructured and rebranded much of the Tivoli portfolio, and organisations running older Tivoli versions that IBM no longer actively develops are particularly well positioned for TPSS.

IBM Maximo. On-premises Maximo CMMS installations are among the best third-party support use cases in the IBM portfolio. Maximo is mission-critical, deeply embedded, and often running on versions that IBM has de-prioritised in favour of Maximo Application Suite. Specialist Maximo TPSS providers deliver deep product expertise and faster resolution times than IBM's standard support for older Maximo versions. Note that ILMT compliance obligations for Maximo remain regardless of the support provider.

The Third-Party Support Providers: Who Are They?

Origina is the most IBM-specialised TPSS provider, founded specifically around IBM software support. Origina maintains a team of former IBM software engineers and certified IBM product specialists who provide Level 3 support, security advisory, interoperability guidance, and custom fixes for IBM software. Origina's model locks pricing for the contract term — typically three years — eliminating the annual IBM S&S escalation and delivering savings of 50 percent or more versus IBM's current S&S rate. Origina does not support IBM SaaS, IBM cloud services, or IBM z/OS (mainframe OS) software but covers a comprehensive range of IBM application software, middleware, and database products.

Rimini Street covers over 600 software products across IBM, Oracle, SAP, Salesforce, Microsoft, and other megavendors. Rimini Street's IBM practice supports DB2, WebSphere, IBM Informix, and a broad range of IBM application software. Rimini Street has been involved in significant litigation with Oracle over intellectual property issues, though their IBM support practice operates under a separate contractual and legal framework. For organisations that want a single TPSS provider covering multiple vendor estates, Rimini Street's breadth is an advantage over a specialist IBM-only provider.

Selecting between providers requires evaluation of specific IBM product coverage, support response commitments, patch management approach, security advisory methodology, and reference client validation in your specific IBM product environment. A direct comparison should also include the IBM S&S counter-proposal that IBM will invariably make once TPSS is introduced as a negotiation lever — IBM commonly offers 30 to 40 percent pricing concessions to retain support revenue that it perceives as at risk.

Using Third-Party Support as IBM Negotiation Leverage

Even organisations that ultimately choose to remain on IBM S&S can use a TPSS evaluation process to achieve materially better IBM support pricing and contract terms. IBM's account teams know the TPSS market and understand that a serious TPSS evaluation by a client represents genuine revenue risk. When presented with formal TPSS proposals showing 50 percent or greater savings, IBM's negotiating posture shifts — from defending the standard renewal terms to finding ways to retain the relationship.

The most effective approach is to obtain formal TPSS quotes from one or two providers, present them to IBM in writing as part of the support renewal negotiation, and give IBM 30 days to respond with a competitive counter-proposal. In our experience, IBM's response typically includes one or more of: a 25 to 40 percent reduction in the annual S&S rate, a multi-year price lock eliminating annual escalation, bundled support for additional IBM products, or enhanced SLA commitments. This approach consistently produces better IBM support economics than renewing without a demonstrated alternative.

IBM's year-end deadline — December 31st — creates a natural window for this leverage strategy. Initiating TPSS due diligence in September, obtaining formal proposals in October, and presenting them to IBM in November gives IBM time to respond meaningfully before year-end. IBM's fiscal year-end pressure, combined with the credible TPSS alternative, produces the optimal conditions for IBM support negotiation. Our IBM contract negotiation service provides the full end-to-end support for this process.

Risk Management: What to Consider Before Switching

Third-party IBM support is not the right decision for every product or every organisation. The risks require honest assessment against the cost savings opportunity.

Security updates are the most commonly cited concern. IBM delivers security patches through S&S — when the S&S is cancelled, the organisation loses access to IBM's patch stream for that product. For products with a history of material security vulnerabilities, or those exposed to external network traffic, the security patch question requires careful analysis. Third-party providers offer security advisory services that analyse IBM security bulletins and advise on compensating controls, but they do not deliver IBM's actual code fixes for products where S&S is not in force.

Regulatory compliance is a related consideration. Some regulatory frameworks — particularly in financial services and healthcare — require documented evidence of vendor support for critical software. The interpretation varies significantly by regulator, jurisdiction, and specific framework, but organisations in regulated sectors should obtain a legal opinion on the compliance implications of TPSS for specific products before proceeding.

Integration with IBM's ELA or Passport Advantage agreement may create complications. Some IBM enterprise agreements include provisions that tie specific pricing or entitlements to maintaining S&S above certain thresholds. Review the current IBM agreement before cancelling S&S on any product to ensure it does not trigger adverse contractual consequences elsewhere in the IBM relationship. The IBM IULA guide covers the key licence agreement provisions relevant to this analysis.

IBM's Typical Responses to Third-Party Support Evaluations

IBM's account teams have a structured playbook for responding to TPSS evaluations, and understanding it in advance gives CIOs a significant tactical advantage. When IBM learns that a client is evaluating TPSS, the typical response sequence unfolds in three phases.

In the first phase, IBM's account team will typically raise concerns about security, compliance, and support quality. The messaging is: "Third-party support cannot access IBM's proprietary code, so they cannot resolve complex defects." "IBM security patches are critical to your security posture and you'll lose access if you switch." "Your auditors and regulators require IBM vendor support." Each of these claims requires analysis rather than acceptance. IBM's own security update release frequency for mature products is measurable — for products with few critical CVEs in recent years, the security update argument is weak. The compliance and regulatory argument varies by organisation and must be verified independently, not taken at face value from IBM's account team.

In the second phase, if the client signals continued interest in TPSS, IBM will typically escalate internally and return with a price concession. The concession pattern is predictable: IBM offers to freeze the current S&S rate (eliminating future escalation) or reduce it by 15 to 25 percent, sometimes adding incremental services or product bundles to increase the apparent value. IBM's goal at this stage is to make the TPSS economics look less attractive without fully matching the 50 percent savings on offer.

In the third phase — if the client proceeds with a credible TPSS selection process and gives IBM a deadline to match the terms — IBM's concessions can reach 35 to 45 percent, with multi-year price locks and enhanced SLA commitments. This level of IBM concession is only achievable when IBM believes the client will actually switch if IBM does not match the offer. TPSS quotes that are not followed by a credible procurement process signal to IBM that the evaluation was not serious, reducing IBM's willingness to make genuine concessions in future cycles.

The implication for CIOs is straightforward: treat TPSS evaluation as a genuine procurement process, even when the primary goal is to create negotiation leverage with IBM. Obtain formal proposals, establish a realistic timeline for a decision, and communicate that timeline to IBM clearly. The more credibly the client signals its willingness to switch, the more generously IBM will respond to preserve the relationship.

Third-Party Support and IBM Compliance: What Stays the Same

Moving to third-party IBM support changes who provides support services — it does not change any of the IBM licence compliance obligations that the organisation carries. This point is frequently misunderstood and worth stating explicitly for every product category.

ILMT deployment and reporting obligations continue regardless of support provider. If an organisation is licensing IBM software at sub-capacity — running IBM WebSphere or DB2 on virtualised infrastructure with ILMT deployed to capture only the virtual machine consumption rather than the full physical host — that ILMT obligation persists indefinitely. IBM retains the right to audit software usage under the original licence agreement terms, and those audit rights exist regardless of whether the organisation is paying IBM for support. Cancelling IBM S&S does not cancel IBM's right to audit the software licence.

For Cloud Pak deployments, IBM License Service remains mandatory for sub-capacity VPC licensing validity even when an organisation moves middleware components to TPSS. If the organisation is running IBM MQ within a Cloud Pak for Integration deployment, IBM License Service must continue to operate in the relevant namespace. The switch to third-party MQ support does not affect the VPC licensing or IBM License Service obligations for that deployment.

IBM licence transferability rules also remain unchanged. Moving to TPSS does not create new licence portability rights, alter the scope of authorised users, or modify the deployment restrictions in the original IBM programme licence agreement (IPLA). Organisations should review their IBM licence terms before making significant infrastructure changes — such as migrating IBM software to new virtualised or cloud environments — to ensure the planned deployment is within the existing licence's scope, regardless of who is providing support.

The practical governance implication is that organisations implementing TPSS need to maintain two separate workstreams: the IBM support relationship (now managed through the TPSS provider) and IBM licence compliance (which continues under the original IBM licence terms and must be managed through ILMT, IBM License Service, and documented compliance processes). Merging these under the TPSS provider's umbrella would be an error — TPSS providers deliver support services, not IBM licence compliance management. For comprehensive IBM licence compliance management under a TPSS model, organisations should consider engaging independent IBM licensing advisory support to maintain governance across both dimensions.

Six CIO Action Priorities for IBM Third-Party Support

1. Audit your IBM perpetual licence estate. Identify every IBM product running on a perpetual licence where S&S is currently active. This is the universe of TPSS opportunity. Exclude cloud services, SaaS products, and subscription licences.

2. Segment by maturity and ILMT obligation. For each perpetual product, assess stability, version currency, and whether ILMT or IBM License Service obligations apply independently of support. Products that are stable, mature, and fully ILMT-compliant are your best TPSS candidates. Remember that switching to TPSS does not alter ILMT compliance obligations — IBM licence usage monitoring continues regardless of who provides support.

3. Obtain formal TPSS quotes from Origina and Rimini Street. Formal proposals create the documented evidence of savings opportunity that IBM's account team needs to escalate internally for a counter-proposal. Informal conversations with TPSS providers produce informal responses — formal RFP responses to formal IBM renewal requests.

4. Present TPSS alternatives to IBM 60 to 90 days before the support renewal date. IBM's S&S cancellation window is typically 90 days before the renewal date — and IBM's fiscal year ends on December 31st, which concentrates many IBM renewal windows into Q4. Initiating the TPSS process in September, obtaining formal quotes in October, and presenting alternatives to IBM in early November creates the maximum leverage window before IBM's year-end urgency peaks. To maintain the option of actually switching, you must present alternatives within this window and allow IBM time to respond while keeping the TPSS option open.

5. Evaluate IBM's counter-proposal independently. IBM's counter-proposal will often include pricing and contractual concessions that appear attractive in isolation but may not represent the best achievable outcome. Have the counter-proposal reviewed against market benchmarks and against what TPSS providers have confirmed they can deliver.

6. Implement TPSS with a structured transition plan. If you proceed with TPSS, plan the transition carefully: document the current IBM support position, establish the hand-off protocol with the TPSS provider, confirm retention of IBM ILMT obligations, and communicate the change to relevant internal teams including security, compliance, and operations. The IBM licence compliance workstream — ILMT reporting, VPC governance, audit preparation — must continue in parallel with the transition to TPSS, as these obligations persist independently of the support relationship. Our IBM advisory services provide full transition support including both the commercial negotiation and the ongoing compliance governance.