A European telco converted its legacy CA contract and saved forty seven percent.

The operator runs an extensive monitoring estate across its national network and its IT environment. The CA AIOps, APM and IT operations products had been in place for more than a decade under a contract that pre dated the Broadcom acquisition and had been renewed twice since the acquisition without a structural conversion. The contract was a layered document with three classes of entitlement. Perpetual licenses with maintenance. Subscription licenses added after the acquisition. And a hybrid set of legacy enterprise license agreements that nobody on the buyer side could fully reconcile against current deployment. The renewal trajectory pointed to twenty one million euros across the next term, calculated on the maintained perpetual base plus the subscription base plus a proposed conversion of the legacy enterprise agreements onto modern subscription terms.

The engagement ran eight months. The signed contract closed at eleven million one hundred thousand euros across three years, with the legacy enterprise agreement footprint reset, the maintained perpetual base scoped to actual deployment, and the subscription base rebalanced on the products the operator actually used. The forty seven percent reduction against the trajectory was the visible outcome. The structural outcome was that the contract, for the first time in six years, was a document the buyer side could read end to end and reconcile against the operations engineering team's own deployment inventory.

The Quote

The trajectory quote was not a single document. It was a conversation across three Broadcom representatives over six weeks. The numbers moved across the conversation because the underlying entitlement positions had not been agreed. A maintained perpetual base at one number. A subscription conversion at another number. A treatment of the legacy enterprise agreements as a third number. The composite reached twenty one million euros only after the third conversation, by which point the operator's procurement lead had asked us to come in. The first task was to convert the open ended conversation into a structured document.

The structured document we produced for the operator was a six page entitlement reconciliation that listed every product, every entitlement class, every contract reference, and the operator's actual deployment of that product. The document was not given to Broadcom. It was used internally to build the buyer side position before any further conversation with the account team.

The Find

The reconciliation produced three findings. The first was on the maintained perpetual base. The maintenance was being paid on a license count that included approximately fourteen percent of licenses that had not been deployed in more than four years. The deployment data was clean enough that the operator could prove the non deployment with operations logs. The maintenance on the non deployed licenses had been paid forward, and could not be recovered, but the renewal could be scoped to remove them prospectively.

The second finding was on the subscription base. The subscription licenses added after the acquisition were sold against a deployment forecast that had not materialised. The operator had subscribed to capacity that the deployment never reached. The subscription contract had no use it or lose it language, but it had a true down provision the operator had not invoked. The true down was available on renewal. It had not been offered.

"The legacy enterprise agreements were not a liability. They were a document we had inherited a position from. Once we read them carefully, the position they gave us was strong. Broadcom expected us not to have read them."Director of vendor management

The third finding was on the legacy enterprise agreements. These were the documents the buyer side had been most apprehensive about, because nobody on the team had been at the operator when they were signed. Reading them carefully showed that they carried entitlement language that defined the deployment scope by site rather than by capacity. The operator's actual deployment was within that scope. The account team's proposed conversion of the legacy agreements onto modern subscription terms was being calculated against capacity, not against site scope. The legacy paper supported the operator's reading. The operator had not asserted that reading.

The Restructure

The restructure proposal had four parts. First, the maintained perpetual base was scoped to active deployment, removing the fourteen percent non deployed footprint. Second, the subscription base was true downed against the realised deployment, using the existing contract's true down provision. Third, the legacy enterprise agreements were converted onto a modern subscription, with the conversion calculated against site scope rather than against asserted capacity, on the language the legacy paper actually contained. Fourth, the three converted streams were merged into a single contract with a single anniversary and a single price ramp.

The account team responded to each part separately. The perpetual scope reduction was the easiest concession and closed inside four weeks. The subscription true down was contested across two rounds and was conceded after the operator produced the contractual reference. The legacy enterprise agreement conversion was the longest conversation and took three months. Two senior reviewers on the Broadcom side had to be brought into the discussion before the site scope reading was accepted. The merge of the three streams into a single contract was the final concession and was agreed in the closing round on the basis that the operator's procurement function needed a single document to administer.

The Outcome

The signed contract delivered eleven million one hundred thousand euros across three years, forty seven percent below the trajectory. The operator gained a single document covering the previously fragmented entitlement position, with a defined ramp, a defined anniversary, and a defined growth allowance. The operations engineering team was given the document and reconciled it against the deployment inventory inside two weeks. The reconciliation matched. That match, the alignment between the contract and the deployment, was the durable outcome of the engagement.

The lesson on CA renewals, and on the broader pattern of legacy Broadcom contracts converted from pre acquisition paper, is that the legacy documents are usually stronger on the buyer side than the buyer side asserts. The work is to read them carefully, to surface the entitlement language they actually contain, and to use that language in the conversion. Account teams sometimes do not know what is in the legacy paper. Buyer sides almost always do not. The reconciliation work is unglamorous, takes six to eight weeks, and is usually the single largest source of value in the engagement.

The takeaway

• Legacy CA paper carried forward from before the acquisition is usually stronger on the buyer side than the buyer side asserts. Reading it carefully is the highest value first work on any conversion.
• Subscription contracts often contain true down provisions the buyer has never invoked. Renewal is the moment to invoke them. The provisions disappear from the next contract if they are not exercised.
• Conversion to a modern subscription should produce a single document with a single anniversary. Fragmented entitlement positions across maintained, subscribed and legacy paper hide value that consolidation surfaces.