Siebel Support Cost Reduction: 6 Proven Strategies for 2026

Why Siebel Support Costs Are Under Scrutiny in 2026

Oracle's support model for mature platforms like Siebel is structured to maximise vendor revenue rather than reflect the actual support services consumed. The 22 percent annual support rate is calculated on the original net licence fee — a number that was set years or even decades ago and has been inflating through periodic uplifts ever since. Organisations that paid £3 million for Siebel licences in 2008 are now paying £660,000 or more per year just to maintain their entitlement to patches and technical support for a platform many of them haven't substantially changed in years.

The irony is that Oracle's confirmation of Siebel support through at least 2036 — intended to provide long-term stability — has inadvertently made the cost reduction conversation more urgent, not less. Organisations that previously tolerated high support costs because they expected to migrate within three to five years now face the reality that Siebel may be in their IT estate for another decade or more. At that time horizon, every percentage point of support cost reduction compounds into very significant savings.

The good news is that there are credible, commercially tested strategies for reducing Siebel support costs without compromising platform stability, abandoning Oracle's support entitlements permanently, or creating material compliance risk. The six strategies below represent the most effective approaches we have implemented across client engagements.

Strategy 1: Third-Party Maintenance

Third-party maintenance (TPM) is the most impactful single strategy for organisations with stable Siebel deployments that are not planning functional upgrades. Providers including Rimini Street, Spinnaker Support, and Support Revolution offer support services for Oracle Siebel at typically 30 percent of Oracle's annual support rate — representing an immediate 70 percent cost reduction compared to Oracle list pricing.

What third-party support delivers: tax and regulatory update support, break-fix assistance for platform issues, custom code support (which Oracle's standard support explicitly excludes), and dedicated service levels often significantly better than Oracle's standard response times. What it does not deliver: access to new Oracle patches, upgrades to future Siebel versions, or Oracle's proprietary diagnostic tools (My Oracle Support). For organisations with stable deployments that are not planning upgrades, these exclusions are typically immaterial.

The documented financial impact is compelling. A global manufacturing company we advised transitioned from Oracle to Rimini Street support at approximately £860,000 per year — 30 percent of their Oracle support cost — achieving an immediate recurring saving of approximately £2 million per year. Over a three-year period, the total saving exceeded £6 million. The transition took four months and required no changes to the Siebel deployment itself.

The primary risk of TPM is Oracle's matching service levels policy, which requires all products within a product set to be maintained at the same level. If you drop Oracle support for Siebel but maintain Oracle Database at Premier Support, Oracle may challenge your entitlement to apply certain patches across the combined estate. This requires careful legal and commercial review before transitioning — something we facilitate as part of our TPM advisory work.

Strategy 2: Licence Rationalisation and Named User Reduction

Oracle Siebel support is calculated on net licence value, which in turn reflects the number of named users and the edition and modules licensed. Organisations with user populations that have shrunk since original licence purchase — through attrition, automation, business unit divestiture, or migration of some users to other CRM platforms — may be paying support on licences they no longer need.

Oracle does not automatically reduce your support liability when your user count decreases. You must proactively negotiate a licence reduction, which Oracle will typically resist but cannot refuse if you can demonstrate that licences are genuinely unused and your contract permits termination of individual user entitlements. The negotiation is not straightforward, and Oracle will often propose a ULA (Unlimited Licence Agreement) or other instrument to prevent the support reduction. Independent advisory support through this process is strongly recommended.

In our experience, organisations that have not reviewed their Siebel named user count in more than three years frequently find 20 to 35 percent of licensed users are inactive — former employees, users who migrated to alternative tools, or over-provisioning at the time of original purchase. Rationalising to active users, where contractually permitted, produces a proportional reduction in support costs without any change to the Siebel deployment.

Strategy 3: Negotiated Support Cap Agreement

For organisations committed to maintaining Oracle Premier Support — either because they plan future upgrades or because their risk posture requires Oracle's patch entitlement — a negotiated annual support cap is the most effective cost containment strategy within the Oracle relationship. Under a cap agreement, Oracle agrees to limit annual support increases to a fixed percentage (typically two to five percent) for the duration of the contract term, in exchange for a multi-year renewal commitment.

Oracle list pricing includes standard uplift provisions that apply at renewal. At list terms, annual support costs can increase by three to five percent per year, compounding significantly over a five or ten-year horizon. A cap at two percent over five years produces a cumulative saving of approximately 15 percent compared to Oracle's standard renewal trajectory — not the 70 percent available through TPM, but material for organisations with £500,000 to £1 million Siebel support lines.

The negotiation leverage for a support cap comes from the credible alternative of TPM or licence reduction. Oracle's support revenue for mature platforms like Siebel represents high-margin annuity revenue — they do not want to lose it. Demonstrating that you have evaluated and are commercially ready to execute a TPM transition consistently produces better renewal terms than approaching the negotiation without that preparation.

Strategy 4: Consolidation onto Oracle ULA or PULA

For organisations with a broad Oracle estate — Database, Middleware, E-Business Suite, or other products alongside Siebel — an Oracle Unlimited Licence Agreement (ULA) or Perpetual ULA can sometimes provide a path to resolving Siebel support costs as part of a broader enterprise agreement restructure. Under a ULA, Oracle agrees unlimited deployment rights for specified products in exchange for a fixed three-year fee, after which the organisation certifies its deployment and receives perpetual licences accordingly.

Including Siebel in a ULA is only appropriate where your Siebel deployment is growing or where you have material unlicensed compliance risk that the ULA would resolve. For stable or declining Siebel estates, a ULA typically locks you into higher overall Oracle spend rather than reducing it. The decision requires careful modelling of both the ULA economics and the alternative strategies available.

Strategy 5: Module Rationalisation

Many Siebel deployments were licensed with modules that were implemented during the original project but are no longer actively used. Siebel Analytics reporting modules, vertical industry modules that were deployed for a business unit subsequently divested, or integration components that have been superseded by middleware investments — all represent support cost that is potentially recoverable if the licences can be formally terminated.

Oracle will not volunteer to remove modules from your support schedule. Identifying unused modules requires a structured review of your Siebel deployment against your licence inventory — what is licensed versus what is deployed and actively used. Where modules are genuinely unused and deployable under a different licence structure, negotiating their removal from the support schedule reduces the net licence value basis for annual support calculations.

Strategy 6: Hybrid Support Model

A hybrid support model combines Oracle Premier Support for specific high-risk components — typically Oracle Database if Siebel runs on Oracle DB — with third-party maintenance for the Siebel application layer itself. This approach preserves Oracle patch entitlement for the database infrastructure while capturing TPM savings on the application licence cost, which typically represents the larger share of total Siebel support spend.

The hybrid model requires careful structuring to manage Oracle's matching service levels policy, but it is commercially achievable for organisations with technically distinct Oracle products that can be treated as separate product sets. Legal advice from an Oracle contract specialist is essential before implementing a hybrid structure to ensure compliance with your specific contract terms.

Implementation Considerations and Risk Management

Every support cost reduction strategy carries implementation risk that must be managed carefully. For TPM, the key risks are contractual (Oracle's matching service levels policy) and operational (ensuring the TPM provider can genuinely support your specific Siebel customisations and release level). For licence rationalisation, the risk is triggering an Oracle licence review that surfaces compliance gaps created by historical module deployments — which is why a licence position review should always precede any formal negotiation with Oracle.

Timing matters significantly. Oracle's strongest negotiating window is at or near contract renewal, when they face the risk of losing your business entirely. Approaching cost reduction negotiations six to twelve months before renewal — with a clear alternative strategy prepared and a credible signal that you are prepared to execute it — is consistently more effective than negotiating at the point of renewal pressure when your leverage is lower.

The optimal approach for most organisations with significant Siebel support costs is a combination of strategies: a near-term licence rationalisation to remove provably unused entitlements, a medium-term TPM evaluation to quantify the alternative, and a renewal negotiation that uses both to secure the best available outcome within or outside the Oracle relationship. We have executed this sequence for dozens of Siebel clients and consistently achieved cost reductions of 40 to 65 percent over a three-year programme.