HomeCase Studies › Finance firm cuts a BMC Helix contract by 33 percent
Case Study · CS-02 · Finance

Finance firm cuts a BMC Helix contract by 33 percent

A financial services group ran an overlapping BMC Helix estate where the CI count, not the user count, drove most of the bill. We consolidated duplicate modules and capped the CI based pricing at renewal. The contract closed at $5.2M from $7.8M, a 33 percent reduction.

Sector FinancePlatform BMC HelixReduction 33%
$7.8M
Annual cost before
$5.2M
Annual cost after
33%
Total reduction
$2.6M
Saved per year

The situation

The client had grown its BMC Helix footprint through acquisition, which left overlapping modules doing similar jobs and a configuration item count that climbed every time the discovery scope widened. BMC Helix prices a large part of the estate on CI volume, so an expanding CMDB quietly expanded the bill, regardless of whether the extra items carried any commercial value.

The renewal quote treated the accumulated sprawl as the new baseline and uplifted it. Nobody had asked whether two modules needed to coexist, or whether the CI count reflected managed reality or just discovery reach. The number was large because the estate had never been rationalized, not because the platform was being used more.

The levers we pulled

Before and after

The contract moved from $7.8M a year to $5.2M, a 33 percent reduction worth $2.6M annually. Module consolidation removed the duplication; the CI cap stopped the largest variable line from compounding. The two together reset the baseline rather than buying a one off discount.

Because the CI pricing was capped rather than simply discounted, the saving is protected against the natural growth of the CMDB over the term.

The outcome

The group closed on a consolidated, rationalized estate with a capped CI line and tightened renewal terms. The finance team gained a forecastable number, and the platform team kept the capability it relied on without the duplication it had been paying for twice.

BMC Helix deals reward this kind of rationalization more than most, because so much of the price hangs off CI volume and module count. See the BMC Helix negotiation page and the BMC Helix Buyer Guide for the full lever set.

Another result
A related outcome.

Is your BMC Helix bill driven by CI count?

500+ engagements. $420M+ negotiated. We consolidate modules and cap CI based pricing so the estate stops inflating the bill. Fixed fee or gainshare.

Book a BMC Helix review →
Questions
Common questions.

Why was the BMC Helix bill so high?

Most of it was driven by configuration item volume and overlapping modules accumulated through acquisition, not by added user value. BMC Helix prices heavily on CI count, so an expanding CMDB inflated the bill even where the extra items carried no commercial benefit.

What does capping CI based pricing achieve?

It stops the largest variable line from compounding. By capping the CI pricing at renewal rather than only discounting it, the saving is protected against the natural growth of the configuration management database over the contract term.

The ITSM Negotiation Brief

Vendor moves, benchmark data, and renewal alerts for ITSM buyers.

ITSM Negotiations

Independent, buyer side ITSM contract negotiation. Fixed fee or gainshare. Not affiliated with any ITSM vendor.

Services
Contract NegotiationRenewal AdvisoryLicense OptimizationCompetitive Leverage
Platforms
ServiceNowBMC HelixJiraCherwell Migration
Company
AboutPricingCase StudiesWhite Papers
Independent. Not affiliated with ServiceNow, BMC, Atlassian, or any ITSM vendor.Buyer Side · Est. 2019