Selective adoption pricing.

PeopleSoft Selective Adoption is Oracle's continuous delivery model, replacing the old approach of major version upgrades with a stream of incremental update images that customers apply selectively. It is a genuine improvement in how the product is maintained, but it also reshapes the economics of support. The annual support fee buys access to this continuous stream, and the buyer should understand what that access is worth, whether the organisation is actually consuming it, and what alternatives exist if the value no longer justifies the cost.

1. What Selective Adoption is.

Under Selective Adoption, Oracle delivers PeopleSoft updates as cumulative images on a regular cadence, and customers choose which updates to apply rather than waiting for and absorbing a single large version upgrade. This lets organisations stay current incrementally, apply only the changes they need, and avoid the disruptive multi year upgrade projects that characterised the old model.

The licensing implication is that the value of the support fee is now tied to consuming this update stream. A customer that actively applies images, takes new features, and stays current is getting strong value. A customer that has frozen its environment and applies nothing is paying the same fee for far less. Understanding which one you are is the starting point. The product context is on our PeopleSoft product page.

2. The value of the support fee.

PeopleSoft support, like all Oracle support, is charged as a percentage of the licence base and rises annually. Under Selective Adoption that fee buys access to the continuous update stream, security fixes, and Oracle support services. For an organisation actively maintaining its environment, this is reasonable value. For a frozen environment, the proportion of the fee that delivers value shrinks.

The buyer should assess honestly how much of the support entitlement it actually uses. This is the same discipline we apply to shelfware in our HCM pricing note, applied to the support line rather than the licence line. The question is not whether support has value in the abstract, but whether this organisation is realising it.

3. The frozen environment question.

Many PeopleSoft customers run stable, heavily customised environments that they have deliberately frozen, applying minimal updates to avoid disrupting business critical processes. For these organisations the continuous delivery value of Selective Adoption is largely unrealised, yet the full support fee continues. This is the situation in which the support value gap is widest.

A buyer in this position should consider its options carefully. Continuing full support may still be justified by security needs and the option to resume updates, but it should be a deliberate decision, not a default. The buyer that examines the trade off, rather than renewing on autopilot, often finds room to act. See the related thinking in our replacement versus optimization note.

4. Third party support as leverage.

For PeopleSoft environments that are stable and require limited new development, third party support providers offer an alternative at substantially lower annual cost. Whether or not a buyer ultimately moves, the existence of this credible alternative is leverage in any conversation with Oracle about support cost. A buyer that has genuinely evaluated third party support negotiates from a stronger position.

The decision to move to third party support is significant and has trade offs, including the loss of access to new Oracle updates and the complexity of returning later. But even the credible option to move changes the negotiation. This is the same walk away dynamic we describe in our walk away point note, applied to the support relationship.

5. The cloud migration overlay.

As with all PeopleSoft discussions, Oracle's strategic preference is a move to Fusion Cloud. The Selective Adoption support question therefore sits within a larger picture, and a buyer evaluating its support value should also be clear eyed about its long term application strategy. The two decisions are connected and are best considered together.

A buyer that intends to stay on PeopleSoft for years has different support priorities from one planning a cloud move in the near term. Aligning the support decision with the application roadmap avoids paying for a model that does not fit the plan. The migration principles are the same as in our EBS to Fusion migration note, and the structural options are on the apps unlimited deal page.

6. Negotiating the support line.

Oracle resists reducing the support base, but the support line is not entirely fixed. At renewal, and especially in the context of a larger transaction such as a cloud move or a new purchase, support terms become negotiable. A buyer that brings a clear view of its support value, a credible alternative, and a larger deal to the table has the leverage to improve the terms.

The buyer that simply renews support each year at the uplifted rate, without examining value or alternatives, captures none of this. Our renewal negotiation service and contract review service assess support value and build the negotiating position, and the full method is in the Oracle Negotiation Playbook.

7. What disciplined buyers do.

• Assess what you consume. Measure how much of the update stream you actually apply.
• Identify frozen environments. Recognise where continuous delivery value is unrealised.
• Evaluate third party support. Build the alternative even if you do not move, for leverage.
• Align with the roadmap. Match the support decision to your long term application strategy.
• Negotiate support in context. Use renewals and larger deals as the moment to improve terms.

For the broader framework see our PeopleSoft and JDE pillar, the HCM pricing note, the renewal negotiation service, the apps unlimited deal page, and the Oracle Negotiation Playbook.