Building an OpenPass target baseline before negotiation

A negotiation without a target baseline is a negotiation conducted on the vendor's number. Building an OpenPass target baseline before negotiation means reconstructing the effective license position independently, so that when the vendor's proposal arrives you already know what defensible usage looks like and what you intend to sign. The baseline is the buyer's anchor, and the buyer who walks in without one is negotiating against a figure they cannot challenge.

The Reconstruct step of the method exists to build exactly this. Before any vendor measurement script runs, the buyer assembles an independent view of what the estate actually deploys, mapped against entitlements and the Additional License Authorizations. That view becomes the target baseline: the position the buyer believes is correct and is prepared to defend. Everything in the negotiation that follows is measured against it.

Why the baseline comes first

Negotiation dynamics favour whoever defines the starting number. If the vendor's finding or proposal is the only number on the table, every discussion becomes a debate about how much to come down from it, and the vendor controls the frame. If the buyer arrives with an independently reconstructed baseline, there are two numbers in the room, and the conversation becomes a comparison rather than a concession. The baseline does not just inform the buyer. It changes the shape of the negotiation by giving the buyer a defensible anchor of their own.

The baseline also protects against the most common conversion mistake, which is signing an OpenPass agreement on top of an uncorrected finding. The detail of why that matters is in converting an audit finding into a clean OpenPass deal. A target baseline built before the negotiation ensures the agreement reflects defensible usage rather than the vendor's opening position.

What goes into the baseline

A target baseline is built from the estate, not from assumptions. It starts with an inventory of what is actually deployed across each product line, then maps that deployment against the entitlements the buyer holds and the metric definitions in the governing agreements. For OpenText's own ECM line, that means reading the end user license agreement. For the Micro Focus products, it means reading the Additional License Authorizations, where the key traps live. The reading of those authorizations is covered in the cluster note on legacy entitlements, and the broader ALA interpretation in our ALA and entitlement review track.

The reconstruction has to disqualify the things the vendor counts but should not. Service and dormant accounts are not consumers. Decommissioned systems are not deployments. A momentary peak is not a sustained requirement. Building the baseline correctly means removing each of these from the count before the number is set. The same disqualifications that bring a finding down also define the baseline up front.

Setting the target, not just the floor

A baseline is more than the minimum defensible position. It should express a target: the number the buyer wants to land on, the metrics the buyer wants defined, the protections the buyer intends to secure. Negotiation is easier when the buyer knows not just the floor they will not go below but the outcome they are aiming for. That target should reflect realistic growth as well as current usage, because an OpenPass term that does not account for planned expansion forces a true up later. Building room for growth is covered in the cluster note on capacity and growth allowances.

The target should also be benchmarked. A baseline that reflects internal usage but ignores what comparable estates pay leaves money on the table. Benchmarking the proposal against market reality is the subject of how to benchmark an OpenPass proposal, and the two exercises reinforce each other: the baseline says what you use, the benchmark says what it should cost.

Documenting the estate that supports the baseline

A baseline is only as strong as the evidence behind it. Every count in the reconstruction should be traceable to a source the buyer controls: deployment records, access logs, system inventories. When the negotiation reaches a disputed line, the buyer who can show the evidence behind their number holds the line, and the buyer who cannot concedes it. The discipline of assembling that evidence is covered in documenting your estate for an OpenPass negotiation. Documentation is not bureaucracy. It is the difference between a baseline you can defend and one you merely assert.

How the baseline performs in practice

In a recent engagement, an estate facing an OpenPass proposal built a target baseline before responding to the vendor at all. The reconstruction disqualified accounts and systems the vendor had counted, mapped real deployment against the authorizations, and set a target that included documented growth. When the negotiation opened, the buyer was not arguing down from the vendor's figure. The buyer was presenting an evidenced position and asking the vendor to reconcile to it. The corrected baseline, not the proposal, became the centre of gravity. That is the pattern across the engagements collected in our engagements, and the full method is set out in the complete OpenText audit defense playbook.

Keeping the baseline current

A baseline built once and then left to age is a baseline that misleads. Estates change continuously: users are added and removed, environments are spun up and decommissioned, data grows and is archived. A target baseline that reflects the estate as it was six months ago will understate or overstate the position by the time the negotiation opens, and either error costs the buyer. The discipline is to treat the baseline as a living view, refreshed as the estate moves, so that the number the buyer brings to the table reflects the estate the vendor will actually measure. That continuous practice is the subject of OpenPass governance and license position tracking, and it is what separates a baseline the buyer can defend from one that has quietly gone stale.

The same currency matters for the metrics, not just the counts. A baseline expressed in metrics that no longer match how the estate is deployed invites the vendor to recount under its own reading. Keeping the baseline tied to current deployment, and to current metric definitions, ensures the buyer is never surprised by a number that has moved while no one was watching. The connection between an accurate baseline and tight metric definitions is set out in how to challenge OpenPass metric definitions.

The anchor you bring to the table

A target baseline is the most valuable thing a buyer can carry into an OpenPass negotiation. It defines the starting number, it protects against signing on an inflated position, and it gives every disputed line an evidenced answer. The work to build it, reconstructing the effective license position independently before the vendor's script runs, is the same work that brings a finding down, and it pays for itself the moment the negotiation opens. The baseline is the foundation of our OpenPass enterprise agreement negotiation work. If an OpenPass proposal is coming, open a case and build the baseline before you respond.