① Journal · Renewal Playbook
Endevor is a Broadcom (CA) source code management product, typically priced on MIPS or MSU capacity, not on developer count. It sits at the center of software delivery, which makes it sticky and makes the vendor strong. The footprint, the MCL model choice, fiscal year timing, and the ISPW alternative are the levers. Here is what actually moves the number.
Endevor is priced on capacity, not on developers. So shrinking the team does not shrink the bill.
Endevor is a Broadcom (CA) source code management product, and like most of the Broadcom mainframe portfolio it is typically licensed on capacity, measured in MIPS or MSU, rather than on the number of developers who use it. That single fact catches many buyers out. Cutting developer headcount does nothing to the Endevor bill, because the number tracks the capacity of the environments Endevor runs in, not the size of the team that touches it. What does move the number is the licensed footprint itself: consolidating environments, retiring unused LPARs from scope, and controlling the capacity Endevor is entitled across. The first job of an Endevor renewal is therefore to know exactly what capacity the product is priced on and to make sure none of it is dead weight.
The harder truth is that Endevor is sticky. It holds source, controls promotion, and enforces change management, which puts it at the center of the delivery process and gives the vendor a strong hand. A deeply embedded SCM is exactly the kind of product that absorbs uplift quietly inside a Broadcom portfolio renewal. The way to counter that is to treat the stickiness as a known fact and work the levers that remain: the choice between traditional MIPS pricing and Broadcom Mainframe Consumption Licensing, the timing of the renewal against Broadcom's fiscal calendar, and above all a credible alternative so embeddedness does not become unconditional captivity. This builds on our Endevor licensing page and our Endevor estates journal.
Lever · what it moves · how to pull it
| Lever | What it moves | How to pull it |
|---|---|---|
| Capacity footprint | The MIPS or MSU Endevor is licensed across drives the price | Consolidate environments and remove dead capacity from scope |
| MCL vs traditional MIPS | The model sets how all Broadcom capacity is charged | Model both; choose deliberately rather than defaulting to the renewal as offered |
| Fiscal year timing | Quota pressure near Broadcom's year end softens the number | Align the close to Broadcom's autumn fiscal year end where possible |
| ISPW and Git modernization | A credible alternative reframes captive into contestable | Hold a costed displacement or modernization path, even a partial one |
| Term and uplift caps | Caps prevent the embedded product from compounding silently | Negotiate multi year caps so stickiness does not become open ended uplift |
Endevor's price is capacity times model times leverage. Control the footprint, choose the model, and hold an alternative.
Endevor's strength is the belief that you cannot leave. A credible alternative is how you disprove it.
The reason Endevor renewals are difficult is structural. As the system of record for source and the enforcer of change control, it is woven into the way the organization ships software, and unwinding that is genuine work. Broadcom understands this, and the negotiating consequence is that Endevor can absorb uplift more quietly than a peripheral tool ever could. A buyer who walks into the renewal treating the stickiness as a surprise has already lost the argument. The productive stance is to name it: yes, Endevor is embedded, and that is precisely why the renewal needs the discipline of footprint control, a deliberate model choice, and timing, rather than a hope that the price will be reasonable on its own.
The lever that actually shifts the vendor's posture is a credible alternative. ISPW, now part of the BMC AMI DevX portfolio, is a direct SCM alternative, and Git based modernization paths increasingly let teams manage mainframe source in distributed tooling alongside the rest of the enterprise codebase. Neither needs to be fully adopted to matter. A costed, believable plan to move a portion of the estate, or to modernize the source management layer over a defined horizon, reframes a captive renewal into a contestable one and gives the buyer something the vendor must respond to. Paired with control of the MIPS or MSU footprint, a clear eyed choice between MIPS and MCL, timing against Broadcom's autumn fiscal year end, and negotiated uplift caps, the alternative is what converts Endevor from a price you accept into a number you move. Our Broadcom (CA) contract review works the structure, and our license negotiation service turns the alternative into a position.
Endevor is priced on MIPS or MSU, not developers. Map exactly what capacity it is licensed across, consolidate environments, and remove dead capacity from scope before the renewal, because that footprint is the number.
You pay for the capacity, not the people; license the capacity you use.
Broadcom Mainframe Consumption Licensing changes the math across the portfolio. Model both traditional MIPS and MCL for your estate and choose on the numbers, rather than accepting whichever the renewal is offered under.
Default to neither model; decide on the math.
Quota pressure near Broadcom's autumn fiscal year end can soften the number. Where the term allows, align the close to that window so the vendor is negotiating against its own clock as well as yours.
The quarter you close in is part of the price.
ISPW and Git based modernization are real SCM alternatives. A costed, partial displacement or modernization plan reframes a captive renewal into a contestable one and gives the vendor something it must answer.
A believable exit reprices the product that stays.
⑤ The discipline that pays
Endevor is sticky, priced on capacity, and embedded on purpose. Footprint, model, timing, and a credible alternative are what move the number.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Endevor is a Broadcom (CA) SCM product, typically licensed on capacity in MIPS or MSU rather than on developer count. The number tracks the capacity of the environments it runs in, so cutting team size does not cut the bill, but consolidating the licensed footprint can. Many estates also have the option of Broadcom Mainframe Consumption Licensing, which changes the math again.
Because it is sticky. It holds source, controls promotion, and enforces change management, which makes switching costs high and the vendor's position strong. A deeply embedded SCM absorbs uplift quietly inside a portfolio renewal. The counter is to name the stickiness and work the levers: footprint, model choice, timing, and a credible alternative.
A credible alternative, even a partial one. ISPW, now part of BMC AMI DevX, is a direct SCM alternative, and Git based modernization lets teams manage mainframe source in distributed tooling. A costed, believable plan to move part of the estate reframes a captive renewal into a contestable one, especially paired with footprint control and fiscal timing.
Audit the capacity footprint and remove dead scope, model MIPS against MCL and choose deliberately, time the close to Broadcom's autumn fiscal year end, hold a credible ISPW or Git modernization alternative, and negotiate multi year uplift caps. See our Endevor licensing page.
Related: Endevor licensing · Endevor vs ISPW · Endevor estates · Broadcom (CA) contract review · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →