① Mainframe contract review
Mainframe agreements are won or lost in the language: uplift caps, audit clauses, capacity definitions, exit rights. We review every line from the buyer side before you sign, so the next renewal starts from a contract that protects you.
The vendor wrote the paper. Every default clause favors the party that drafted it.
Publisher agreements arrive as standard paper, and standard paper is engineered: escalators that compound quietly, audit clauses that hand the vendor scope control, capacity definitions that count machines you did not know were in scope, and renewal terms that convert a year one discount into a year three uplift. Broadcom (CA) renewals, for example, commonly carry annual escalators in the 5 to 7% range when buyers do not negotiate caps, and uplifts of 30 to 80% are commonly reported where capacity grew without protection.
Procurement teams see a mainframe contract once every three to five years. The vendor's deal desk sees one every week. A buyer side review closes that asymmetry before signature, which is when the language is still negotiable. After signature, the same clauses become next cycle's leverage problem, the kind we work through in license negotiation and audit defense engagements.
Every agreement, amendment, and order form in scope, indexed into one structure. Mainframe estates commonly run on layered paper accumulated through acquisitions: CA terms inside Broadcom agreements, Compuware terms inside BMC paper, Micro Focus terms now renewing under Rocket Software.
Each clause is scored for financial exposure: uplift and escalator mechanics, audit scope and notice terms, capacity and sub-capacity definitions, true up mechanics, transfer and outsourcing restrictions, and termination rights. The output ranks what will actually cost money, not what merely reads badly.
Your terms get compared against the patterns we see across 500+ engagements: which caps this publisher typically concedes, which audit limitations comparable buyers have negotiated, and where your language sits against market.
You receive proposed replacement language for every priority clause and a negotiation brief that explains the rationale in vendor facing terms. Your legal team keeps ownership; we supply the licensing specific substance.
We stay in the loop through execution, pressure testing vendor counterlanguage until the agreement is signed. Where the review uncovers negotiating leverage beyond the language itself, the engagement extends naturally into renewal advisory.
| Clause area | The trap we commonly find | The buyer position |
|---|---|---|
| Renewal pricing | Uncapped uplifts or compounding annual escalators that reset the baseline every term. | Hard caps on renewal increase, escalators tied to an index with a ceiling. |
| Audit clause | Vendor controlled scope, short response windows, vendor selected auditors, no confidentiality limits. | Defined scope, 30+ day notice, data limited to contract relevance, agreed methodology. |
| Capacity definitions | Licensed capacity counting coupled systems, DR machines, or full machine capacity where sub-capacity was intended. | Definitions matched to SCRT reality, DR and dev test carve outs in writing. |
| True up mechanics | Penalty rates on overage, true ups that ratchet the baseline upward but never down. | Pre agreed overage rates, downward adjustment rights, rollover of unused capacity. |
| Exit and transfer | Restrictions that block outsourcing, divestiture transfers, or migration during the term. | Transfer rights for corporate events, defined data egress and transition assistance. |
Mainframe spend negotiated across the seven major publishers
Engagements delivered since 2019
Typical renewal reduction, protected by the contract language we close on
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Before signature, ideally while you still have negotiating leverage. The most expensive clauses we see were accepted at signing and only discovered at renewal or audit, years later. A review late in a renewal cycle is still worth running: even small language changes to caps, audit terms, and capacity definitions change the economics of the next five years.
IBM, Broadcom (CA), BMC, Rocket Software, Software AG, Compuware (BMC), and Syncsort (Precisely). Each publisher has its own contract vehicles and recurring clause patterns, and we review against the behavior we commonly observe from that specific vendor at renewal and audit. Publisher specific reviews, like Broadcom (CA) contract review and IBM contract review, go deeper on that vendor's paper.
A clause by clause risk map of the agreement, redline language for the terms that matter, and a negotiation brief that ranks each issue by financial exposure. You decide what to push; we provide the language and the rationale. For the recurring patterns, see Mainframe Contract Clauses That Cost Millions.
Yes. A post signature review maps your current exposure: audit clause mechanics, uplift and escalator terms, capacity definitions, and exit rights. It typically becomes the foundation for renewal preparation, which we recommend starting 18 months before expiry.