OpenPass bundling and the entitlement trap.

A bundle looks like a discount. Inside an OpenPass proposal it is more often a way to obscure what you actually own, blur the line between products you use and products you do not, and lock an inflated baseline into a contract you will live with for years. The entitlement trap is not the headline price. It is what the bundle hides underneath it.

OpenPass is OpenText's enterprise licensing framework, built around a single contract, a defined term, and dual entitlements that support migration. That single contract structure is genuinely useful when the underlying counts are correct. The problem is that bundling lets the vendor present a mixed estate as one rolled up figure, so the buyer never sees how the total was assembled. When several product families are folded into a single line, the metric that drove each one disappears, and with it the ability to challenge any single number. A buyer who signs the bundle accepts every assumption inside it at once.

This matters because a bundle written off the back of an audit carries the audit's inflation forward. If the finding overstated seats, overcounted environments, or treated dormant accounts as live consumers, those errors do not vanish when the products are bundled. They are baked into the baseline and priced for the full term. The bundle does not correct the finding. It freezes it.

What bundling actually obscures

The core trick of a bundle is aggregation. Once products are combined, the per product entitlement, the metric definition, and the deployed quantity are no longer visible on the page you are asked to sign. You see a total and a term. You do not see that the Documentum seats were counted by named user while the security products were counted by capacity, or that one line assumes production and non production are the same environment. Aggregation is convenient for the vendor precisely because it suppresses the questions a buyer would otherwise ask line by line.

The same pattern appears in the authorizations that govern most Micro Focus products. Additional License Authorizations, or ALAs, define the metric and the rights for each product, and bundles tend to flatten those distinctions into a single commercial wrapper. The way bundles conceal genuine entitlement is examined in detail in how ALA bundles obscure true entitlement, and it is the same mechanism that operates inside an OpenPass proposal.

Why a bundle is hard to rebut

A line item can be challenged. A bundle resists it. When every product is priced separately against a defined metric, you can disqualify a population, separate non production from production, or remove a decommissioned system and watch the number fall. When the same products are rolled into one figure, there is no line to attack. The vendor can decline to decompose the bundle, claim the discount only holds at the aggregate level, and present the total as indivisible. That is not a technical limitation. It is a negotiating posture, and it works only on a buyer who has not insisted on a decomposed view.

Insisting on decomposition is the first defensive move. The buyer is entitled to understand how each product was counted and priced before agreeing to a combined figure, and a vendor confident in its numbers has no reason to refuse. The metric definitions inside the agreement are themselves negotiable, and pinning them down is covered in how to challenge OpenPass metric definitions. Without defined metrics, the bundle can be reinterpreted later, which is how a forward agreement quietly produces the next finding.

Reconstruct before you accept the bundle

The defensive sequence does not change because the vendor presents a bundle. Reconstruct the effective license position independently, product by product, against entitlements and the ALAs, before any vendor measurement informs the proposal. That reconstruction gives you a per product target you can hold against the bundle, so you are no longer comparing the vendor's total to nothing. Building that target is the subject of building an OpenPass target baseline before negotiation, and it is the single most important preparation before any bundle is discussed.

With a reconstructed position in hand, the bundle stops being an opaque total and becomes a set of claims you can test. Each product line can be matched to your own count, each metric can be checked against the ALA, and each gap can be questioned. The bundle is only powerful when the buyer has nothing to compare it to. Once you arrive with an independent baseline, the aggregate figure loses its protective shell.

The structure question: one contract or product schedules

Bundling also raises a structural choice. A single rolled up contract is simpler to administer but harder to govern, because the terms for very different products are merged. Product schedules under a single master keep each product's metric and quantity visible while still giving you the single contract convenience OpenPass is built around. The trade off between these two shapes is set out in OpenPass single contract versus product schedules. For most estates with mixed metrics, schedules preserve the transparency that a flat bundle removes.

Defined metrics belong in whichever structure you choose. A metric that is written into the contract cannot be reinterpreted at the next review, which is the protection a bundle most often lacks. The case for embedding them is made in defined metrics in an OpenPass enterprise agreement. A bundle without defined metrics is an invitation for the vendor to recount on its own terms once the ink is dry.

An anonymised illustration

In a recent insurance engagement, a Documentum seat count finding opened at $7.2M and settled at $1.6M, a 78 percent reduction, once dormant and service accounts were disqualified and the population was rebuilt from actual use. Had that finding been folded into a bundle before the reduction, the forward agreement would have been priced off the $7.2M figure, and the 78 percent never recovered. The lesson is order. The reduction has to precede the bundle, never follow it. A bundle assembled on top of a corrected position is a clean baseline. A bundle assembled on top of an opening finding is the trap.

How to defend against the bundle

The defense is straightforward to state and demanding to execute. Insist on decomposition so every product shows its metric and quantity. Reconstruct your position independently so you hold a per product target. Reduce the underlying finding before any bundle is priced. Write defined metrics into the agreement so the counts cannot drift. And choose a structure, schedules under a master where the estate is mixed, that keeps each product visible. None of this requires the vendor's cooperation. It requires the buyer to refuse the aggregate and work the parts. That discipline is the core of our OpenPass enterprise agreement negotiation track, and the wider sequence that precedes it is set out in the complete OpenText audit defense playbook. If a bundled proposal is already on the table, open a case before you sign the total.