# Case study: What if six contracts became one?

Source: https://ollie.coach/case-studies/what-if-six-contracts-became-one
Author: Oliver Fernandez, MBA
Published: 2026-08-21
IT Infrastructure · Global manufacturer (anonymized) · 3-year enterprise agreement

A fragmented ~$1.067M three-year projection became a ~$600K global enterprise agreement — same technology, one customer.

## In short

A global organization ran the same network platform across North America, Europe and several affiliated businesses — but bought it through separate contracts, dashboards and renewal dates. Assembling the estate into a single visible requirement turned a projected three-year spend of roughly $1.067M into a ~$600K enterprise agreement, while creating a commercial framework that could absorb future acquisitions.

## Results

- Fragmented baseline: ~$1.067M (Projected 3-year value of separate agreements)
- Enterprise agreement: ~$600K (3-year global structure)
- Three-year difference: ~$467K
- TCO improvement: 43.8%

## The network wasn't the problem

For the IT infrastructure team, the incumbent network platform was familiar territory.

The technology was already deployed across multiple parts of the organization. Wireless access points, security appliances and switching infrastructure supported offices and users across regions and business units. In Europe, a related cloud-security service added another layer of security licensing.

The problem was not that the technology had failed.

The problem was that the company was buying it in pieces.

North America had its requirements. Europe had its own. Acquired and affiliated businesses had separate quantities, dashboards, renewal dates and commercial arrangements.

Each agreement could be explained on its own. Together, they raised a more interesting question.

> **THE UNCOMFORTABLE QUESTION**
>
> If we use the same technology around the world, why are we still buying it as if we are several different customers?

## Fragmentation can feel normal

There was no single moment when someone decided to create a fragmented commercial model. It accumulated.

Regions bought what they needed. Acquisitions brought inherited contracts. Renewal dates drifted apart. Different dashboards and organizations were created over time. A reseller handled much of the purchasing.

This is common in growing companies, because technology becomes standardized long before the contracts do.

From an IT perspective, that is easy to tolerate. The equipment works. Licenses renew. Local teams know their environments.

But commercially, the company may be giving away one of its strongest advantages: scale.

## The first challenge was simply seeing the whole estate

Before anyone could ask the technology provider for a global structure, IT needed to know what "global" actually meant.

The team pulled together device and license information across the estate: access points, security appliances, switches and other network products, plus dashboard IDs, invoices, renewal dates and regional requirements.

The resulting inventory included roughly 1,300 wireless licenses plus hundreds of other network license requirements across product families. The proposed global structure ultimately brought together North America, Europe and several affiliated businesses, while also incorporating the European cloud-security requirement.

That work was not glamorous. But it changed the conversation.

> **THE DISCOVERY**
>
> The company did not have six unrelated technology needs. It had one global technology footprint being purchased through several commercial relationships.

## The numbers began to look different

Once the requirements were brought together, the company could compare the fragmented future state with a single enterprise structure.



Those numbers changed the nature of the decision. This was no longer a question of negotiating each renewal a little harder. IT had to decide whether it was willing to change the way the company bought the technology.

## But consolidation creates new risks

A global agreement can produce better economics. It also creates commitment.

The organization was acquisitive. New businesses and devices could arrive during the term. IT needed to understand how growth, true-ups and mergers would be handled.

There were also practical timing issues. Regional licenses were expiring on different schedules, and the consequences of getting renewal timing wrong were not theoretical: at one point, service continuity became an operational concern.

So the lowest global price was not enough. The structure had to work as the company changed.

## What would you do?

Imagine you are the CIO or infrastructure leader.

Your teams already rely on the same technology across the company, but the contracts are fragmented. A global agreement appears capable of materially reducing three-year cost — while concentrating more of the estate into one commercial commitment.

| Option | Choice |
| --- | --- |
| A | Keep the regional agreements. Local flexibility is worth more than the potential savings. |
| B | Negotiate each region harder but preserve separate contracts and renewal cycles. |
| C | Consolidate everything immediately into one global agreement and maximize the discount. |
| D | Build a global agreement — but only after validating the inventory, future growth, credits, renewal timing and the parts of the estate that genuinely belong together. |

Which option creates the better technology decision — not merely the lowest price?

## What happened

The company chose something closest to **D**.

The team did not start with a global discount target. It started by making the fragmented estate visible.

Once the quantities were assembled, the organization could approach the technology provider as something it had not fully behaved like before: one enterprise customer.

The final structure combined global network licensing with the European cloud-security requirement under a three-year enterprise agreement worth approximately $600,000, allocated across North America, Europe and several affiliated businesses.

| Included component | Approx. value |
| --- | --- |
| North America network | $153,990 |
| EMEA network | $190,241 |
| EMEA cloud-security | $177,055 |
| Affiliated Business A | $11,541 |
| Affiliated Business B | $29,337 |
| Affiliated Business C | $21,572 |
| Affiliated Business D | $16,264 |
| Total | ~$600,000 |

## The price wasn't the only thing that changed

The enterprise structure did several things at once.

It pooled buying power that had previously been scattered across entities. It forced the organization to normalize its inventory. It created a common commercial framework for growth. It aligned more of the renewal cycle. And it made future acquisitions part of the commercial conversation rather than an afterthought.

That last point mattered. The company was actively acquiring businesses, so a contract designed only for today's device count could become tomorrow's problem.

> **THE SHIFT**
>
> The organization stopped asking, "What discount can this region get?" and started asking, "What should this technology cost us as one enterprise?"

## The Parsimoney lesson

Companies often look for savings by negotiating harder with the suppliers they already have.

Sometimes the bigger opportunity is to change the shape of the demand before negotiating at all.

A supplier sees ten contracts differently from one enterprise commitment. It sees scattered quantities differently from an aggregated requirement. And it prices uncertainty differently from a clear, normalized estate.

In many organizations, the cost problem is not weak negotiation. It is never presenting buying power coherently.

> **AGGREGATION PRINCIPLE**
>
> Scale only creates leverage when the supplier can see it — and when the organization is prepared to act like one customer.

## Why this case matters

This is not really a story about one technology provider.

The same pattern appears in software, telecom, cloud services, professional services, marketing platforms and almost any category that has grown region by region or acquisition by acquisition.

A company can be globally standardized operationally and still be commercially fragmented.

When that happens, the opportunity may not be hidden in a better negotiation. It may be hidden in the organizational structure of the spend itself.

## Three questions to take back to your business

| # | Question |
| --- | --- |
| 1 | Where are different teams or regions buying essentially the same thing separately? |
| 2 | If you combined those requirements, what new leverage — or new risk — would become visible? |
| 3 | Are your contracts reflecting the company you are today, or the way the company happened to grow? |

> **IF YOU REMEMBER ONE THING**
>
> You cannot use enterprise scale that you have never made visible.

## Before and after

| Measure | Before | After |
| --- | --- | --- |
| Three-year commercial value | ~$1.067M | ~$600K |
| Commercial relationships | Several, by region and entity | One enterprise agreement |
| Renewal dates | Drifted apart | Largely aligned |
| Future acquisitions | Handled after the fact | Built into the agreement |

## Principles applied

- Principle 01: Why Cost Resilience Beats One-Off Negotiation Wins (https://ollie.coach/blog/why-cost-resilience-beats-negotiation-wins) — The saving came from restructuring how the company buys, not from a single hard renewal conversation — the structure keeps working after the deal is signed.
- Principle 02: Competition Discovers the Market (https://ollie.coach/blog/competition-discovers-the-market) — Aggregating the requirement was what made the market respond; the supplier priced one enterprise very differently from six scattered buyers.
- Principle 08: A Renewal Date Is Not a Decision Date (https://ollie.coach/blog/renewal-date-is-not-a-decision-date) — Regional licenses expired on different schedules, so the renewal calendar had to be actively managed rather than followed.
- Principle 10: The Contract Is Not the Commercial Reality (https://ollie.coach/blog/contract-is-not-commercial-reality) — Six defensible contracts described a commercial reality nobody had ever looked at as a whole.

## FAQ

### Wasn't this just a volume discount?

Volume was already there — the company simply had never presented it. The work was assembling roughly 1,300 wireless licenses plus hundreds of other network requirements into a single visible estate so the supplier could price one customer instead of several.

### Doesn't consolidation reduce flexibility?

It concentrates commitment, which is a real risk for an acquisitive company. That is why growth, true-ups and merger handling were negotiated into the structure rather than left to the next renewal.

### Does this only apply to network hardware?

No. The same pattern appears in software, telecom, cloud, professional services and marketing platforms — any category that grew region by region or acquisition by acquisition.

You cannot use enterprise scale that you have never made visible.

Next step: take the Cost Resilience Health Check at https://ollie.coach/health-check
Vocabulary: https://ollie.coach/glossary