How to benchmark an OpenPass proposal.

A discount is only meaningful against a reference point. An OpenPass proposal that claims to cut your cost by a striking percentage tells you nothing until you know what it is cutting from. Benchmarking is the discipline of building those reference points yourself, so the headline figure is judged against your own numbers rather than the vendor's framing.

OpenPass is OpenText's enterprise licensing framework, built around a single contract, a defined term, and dual entitlements that support migration. When the vendor presents a proposal inside that framework, it almost always leads with a saving expressed against list price. That comparison is designed to look generous, because list price is the highest number in the room and noncompliance is priced against it. Under the EULA, an out of compliance licensee is deemed to have acquired licenses at the then current list price, with back maintenance and audit cost recovery added on top. A discount off that ceiling can be large and still leave the buyer paying far more than the estate is worth.

Benchmarking replaces the single vendor reference with several of your own. Done properly, it answers a sharper question than the proposal does. Not how much am I saving against list, but how does this proposal compare to what I actually own, what I would pay on a corrected position, and what I will be exposed to at renewal. A proposal that survives all three comparisons is worth signing. One that only survives the list price comparison is the vendor's anchor doing its job.

Benchmark one: your reconstructed position

The most important reference point is the one the vendor never supplies. Before any proposal can be judged, reconstruct the effective license position independently, product by product, against entitlements and the Additional License Authorizations that govern most Micro Focus products. That reconstruction tells you what you genuinely consume and what you are genuinely entitled to, which is the only honest baseline for comparison. The method for building it is set out in building an OpenPass target baseline before negotiation.

Once you hold a reconstructed target, the proposal can be laid against it line by line. Where the vendor's figure exceeds your defensible count, you have a question to raise, not a saving to celebrate. The gap between the proposal and the reconstruction is the real negotiating space, and it is invisible to any buyer who has not done the reconstruction first.

Benchmark two: list price, read correctly

List price is a legitimate reference, but only when read for what it is. It is the remedy the vendor would apply on noncompliance, not the price a prepared buyer pays. Comparing the proposal to list shows the ceiling you are being moved away from, which is useful context, but it must never be the only comparison. A discount of seventy percent off list can still sit well above your reconstructed position if the underlying count was inflated. The relationship between an OpenPass figure and a list price true up is examined in how much can OpenPass save versus a list price true up.

Benchmark three: total cost across the term

OpenPass is a term agreement, so the right unit of comparison is total cost across the full term, not the first year figure. A proposal with an attractive entry price can carry uplifts, renewal exposure, and maintenance terms that make its multi year cost far higher than a flatter alternative. The total cost view is what reveals whether the proposal is genuinely cheaper or simply front loaded to look that way. Modelling that view is the subject of reducing total cost with an OpenPass conversion.

Two protections shape the total cost more than any headline discount. The first is the price hold, which fixes the rate across the term and prevents uplift erosion, covered in OpenPass price hold and uplift protections. The second is the comparison to the licensing model you are leaving. Whether the proposal genuinely improves on a traditional arrangement is examined in OpenPass versus traditional perpetual licensing. Benchmarking against both keeps a clever entry price from disguising an expensive term.

Reading the proposal for what it omits

A proposal is as revealing in what it leaves out as in what it states. Watch for metrics that are described but not defined, growth allowances that are absent, renewal terms that are deferred to a later schedule, and a bundle that cannot be decomposed into product level figures. Each omission is a place where the benchmark cannot be applied, which is usually the point of the omission. A proposal that resists benchmarking is telling you something. Insist on the detail that lets each reference point be calculated, and treat reluctance to provide it as a negotiating signal rather than an administrative inconvenience.

An anonymised illustration

In a recent banking engagement, an ArcSight finding built on EPS and connector counts opened at $6.0M and settled at $1.8M, a 70 percent reduction, once burst rates were separated from sustained throughput and the connector population was rebuilt. A proposal that had benchmarked only against the $6.0M opening figure would have made any discount look impressive while still pricing the forward agreement off an inflated count. Benchmarked against the reconstructed position, the same proposal could be judged on its true merits. The reference point, not the percentage, decided whether the deal was good.

Common errors that defeat a benchmark

Even a buyer who intends to benchmark can undermine the work in predictable ways. The first error is comparing the proposal to the opening finding rather than to a reconstructed position, which simply confirms the vendor's own inflated reference. The second is treating the first year figure as the deal, ignoring the ramp that carries the real cost across the term. The third is accepting a discount off list as evidence of value when list is the highest possible number and the discount means little against a corrected count. Each of these errors flatters the proposal, which is why the vendor's framing leans on all three.

A fourth error is subtler and more common: benchmarking late. By the time a proposal is in front of you, the time to have built a reconstructed position has usually passed, and the pressure to respond can push the benchmark into a rushed afternoon. The reference points have to be ready before the proposal arrives, which means the reconstruction and the total cost model belong to the preparation phase, not the response. A benchmark assembled under deadline tends to accept the vendor's categories rather than test them, and an accepted category is a concession made without noticing.

Turning benchmarks into leverage

Benchmarking is not an academic exercise. Each reference point is a lever. The reconstructed position lets you contest any line above your defensible count. The list price reading lets you refuse the anchor without rejecting the framework. The total cost view lets you trade an attractive first year for protections that matter across the term. Used together, they convert a proposal you were asked to accept into one you can reshape. That work sits at the centre of our OpenPass enterprise agreement negotiation track, and it follows the same order set out in the complete OpenText audit defense playbook. If a proposal is in front of you now, open a case before you respond to the headline number.