Consolidating more than 5,000 vendors looks like a procurement exercise.
But it is a customer exercise first.
That distinction matters.
Every vendor plays a part in delivering a service. Some are easy to replace. Others carry knowledge, relationships or capabilities that are not immediately visible in a spreadsheet.
Remove the wrong one, or move too quickly, and the customer feels it long before the savings appear in the financial reports.
I led a vendor optimisation programme that consolidated more than 5,000 vendors into a leaner, more accountable structure and delivered measurable cost savings.
It reinforced a lesson I have carried through my transformation work.
Reducing the number of vendors is relatively straightforward on paper. Reducing costs while protecting service quality takes a different level of discipline.
Here is how I approach it.
Understand What You Are Changing
Before making decisions, understand the existing operation.
Not just how many vendors you have or how much you spend with them.
Understand what they actually do.
Which services do they support? How consistently do they deliver? Where are the dependencies? What happens to the customer if a particular vendor is removed?
These questions matter because vendor relationships are rarely equal.
One vendor may handle thousands of routine transactions. Another may support a smaller volume of work but provide a capability that is difficult to replace.
Looking only at spend or transaction volumes can lead to the wrong decision.
I would begin by establishing a clear baseline of costs, service performance, contractual obligations, operational dependencies and customer impact.
Without that baseline, it becomes difficult to prove whether the consolidation has genuinely improved the business.
Let Performance Decide
Cost is important.
But cost alone should never decide which vendors stay.
I would look first at quality, turnaround time, compliance and the ability to deliver consistently.
A cheaper vendor who regularly misses commitments is not necessarily a saving.
The additional cost may appear somewhere else. More rework. More escalations. More time spent resolving problems. And, eventually, dissatisfied customers.
A practical assessment should consider service quality, regulatory compliance, operational capacity, cost, customer experience and technology capability.
The importance of each factor will vary by business.
In regulated operations, for example, compliance cannot simply be traded for a lower price.
A vendor must first meet the requirements of the work it is expected to perform.
Only then does the commercial comparison become meaningful.
Know Which Relationships Carry the Greatest Risk
One of the mistakes in large consolidation programmes is assuming that every vendor can be assessed in the same way.
They cannot.
Some vendors provide standard services that can be transferred with relatively little disruption.
Others support specialist activities, difficult locations or customer requirements that need a more careful transition.
I would separate vendors according to their operational importance and the consequences of losing their service.
The question I always come back to is simple.
What happens if this vendor is no longer available tomorrow?
If the answer is a major customer disruption or a compliance issue, the business needs a proper alternative before making a change.
There is also a risk in concentrating too much work with too few partners.
A smaller vendor base can improve accountability. But it can also increase dependence on individual providers.
The objective is to remove unnecessary complexity, not create a new operational weakness.
Fewer Vendors Need Stronger Accountability
Consolidation should make the operation easier to manage.
That does not happen automatically.
When more work is placed with fewer vendors, expectations need to become clearer.
Service levels must be agreed. Performance must be reviewed. Escalation paths must work. And somebody must take ownership when delivery falls short.
I prefer simple governance that people can actually follow.
Who is responsible for the service? What is the expected turnaround? How do we identify a recurring problem? Who makes the decision when something needs to change?
These are basic questions.
But when they are not answered properly, even a well-designed consolidation can struggle.
Fewer relationships should mean better visibility and stronger accountability, not less attention to performance.
Compliance Cannot Be an Afterthought
This becomes particularly important when vendors operate across different regions or jurisdictions.
A vendor may have the capacity to take on additional work but may not meet every requirement associated with that work.
Data protection, confidentiality, contractual obligations and local regulatory requirements all need to be considered.
I would never assume that because a vendor is approved in one location, it is automatically suitable for another.
Those checks belong at the beginning of the decision process.
Not after the transition has started.
The same principle applies to business continuity.
If a vendor takes on a larger share of operations, the business needs to understand what happens if that vendor experiences a serious service failure.
Consolidation should strengthen control, not introduce risks that were previously spread across the network.
Move in Stages and Protect the Customer
The transition is where the real work begins.
A consolidation plan can look convincing in a presentation. The challenge is making it work while the business continues to serve its customers.
I would not move thousands of vendor relationships in one exercise.
Start with the baseline. Identify the right partners. Test the proposed arrangement with a manageable group of services or locations.
Then expand in stages.
Each stage should have clear ownership, agreed service measures and a way to respond if something goes wrong.
Most importantly, watch the customer metrics throughout.
SLA compliance, turnaround times, service failures and customer satisfaction should be visible before, during and after the transition.
In a separate regional consolidation, we reduced operating costs while improving SLA compliance and customer satisfaction.
That is the kind of result a transformation programme should aim for.
Not just lower cost.
Better service at a more sustainable cost.
Make Sure the Savings Are Real
There is a difference between savings identified in a business case and savings that actually reach the business.
I have seen how easy it is for a programme to report an attractive number before the full impact of the change becomes clear.
That is why I would agree on the financial baseline before consolidation begins.
Then measure the result against it.
Consider contract savings, changes in transaction costs, transition expenses and any additional cost required to manage the new vendor structure.
A lower contract price means little if the business spends the difference on rework, additional controls or service recovery.
I would also track the operational results alongside the financial ones.
Are service levels holding? Are customers satisfied? Have escalations reduced? Are the remaining vendors performing as expected?
A smaller vendor base is an output.
Realised savings, dependable service and clearer accountability are the outcomes.
The Lesson I Take From Large-Scale Transformation
Vendor consolidation is often presented as a cost reduction initiative.
I see it as an operating model decision.
It affects customers, people, processes, technology, governance and financial performance.
The challenge is not simply deciding which vendors to remove.
It is knowing which capabilities the business must protect, which relationships can be improved and how to make the change without disrupting the service customers depend on.
Across my transformation work, one lesson has remained consistent.
Cost programmes succeed when the financial objectives and customer outcomes move together.
Saving money matters.
But saving money while building a better operation is what makes the change worthwhile.
Leave a Reply