A federal judge rules IBM must pay $1.6B to BMC for swapping in its own software while servicing a mutual client, AT&T, violating an IBM and BMC deal from 2015
Context & Ripple Effects
This ruling opens what becomes a three-year legal arc between IBM and BMC over a 2015 licensing agreement covering AT&T, a client both companies service. A federal judge finds IBM breached that deal by substituting its own software while working on the mutual account, and puts a $1.6B price tag on it — one of the largest software-contract verdicts on record.
The verdict does not survive intact: in 2024 IBM wins a US court decision overturning the $1.6B damages award, and in 2025 the Supreme Court declines to hear BMC's bid to revive the award, leaving the overturned judgment standing. The case sits in a familiar IBM litigation pattern — the company had earlier extracted an $83M patent verdict from Groupon in 2018.
First-order effects
- BMC holds a $1.6B judgment against IBM for breaching the 2015 agreement, while IBM faces immediate liability — and an appeal bill — for swapping in its own software on the shared AT&T account.
- AT&T, the mutual client at the center of the dispute, now has its servicing arrangements governed by a contract whose enforcement both vendors must litigate around.
Second-order effects
- IBM's successful 2024 overturn shows the verdict's real cost is appellate exposure: BMC must fund years of litigation to keep a judgment that the courts ultimately vacate.
- The dispute forces every vendor operating under co-existing licensing agreements with a shared enterprise client — IBM and BMC's exact structure — to re-examine how their contracts allocate the right to touch that account.
Third-order effects
- If the pattern holds, mega-verdicts in enterprise software servicing disputes become opening positions in multi-year appellate fights rather than final outcomes, raising the bar for licensors like BMC to convert breach findings into collected damages.
- The case hardens the principle that a vendor servicing a mutual client cannot use that access to substitute its own products — a boundary line that shapes how co-existence clauses in enterprise licensing deals are drafted and enforced.
The trend: Enterprise software disputes over who controls a shared client relationship are escalating into billion-dollar verdicts that get decided as much on appeal as at trial.