Part 1 of 2 in a series on vendor management, drawn from Optimizing Corporate Efficiencies
In my previous article I introduced the foundational concepts of budget optimization — the difference between cost cutting, efficiency, cost savings, and cost avoidance, and why institutional inertia is the primary obstacle to recovering them. In the articles that follow I will work through the specific levers that generate real savings in large organizations.
This article is the first of two on vendor management. Vendor management is, in my experience, one of the least painful areas of cost optimization because the savings come out of the pockets of third parties rather than your own organization. There is no morale impact, no reorganization, no difficult conversations with employees. There is simply a more disciplined approach to how you buy and what you pay.
The two articles in this series cover: (1) identifying duplication and consolidating your vendor landscape; and (2) using competitive RFPs and negotiation to optimize pricing. Each area has generated material savings in every organization I have led. Taken together, they can represent tens of millions of dollars per year in recoverable spend.
Why Vendor Sprawl Is Almost Universal
If your organization has more than 1,000 employees, I will guarantee you have needless vendor duplication. The mantra at most companies seems to be "Why use one product when you can have five at eight times the cost?" This is not hyperbole — it is the predictable result of decentralized top-down budgeting combined with weak governance.
The exercise begins with a simple inventory. Pull the full vendor list from your procurement and legal departments, with the approximate spend over one, two, and three years. Use this list to prioritize which vendor relationships warrant scrutiny. Then reach out to the managers responsible for each relationship and understand exactly what each product does for their organization. What you will find, consistently, is a collection of overlapping solutions: duplicate reporting platforms, redundant CRM systems, multiple event management tools, parallel middleware. Some of these are true duplicates that can be consolidated immediately. Others are legacy solutions that exist because older applications depend on them. Those need to be scheduled for renovation with a clear ROI attached.
A note of caution: not every apparent duplicate is one. For example, most IT organizations legitimately need multiple storage solutions — one for rapid retrieval, one for low-cost archival. Some functions genuinely require more than one tool to achieve the required breadth of capability. The goal is not to minimize vendor count for its own sake, but to scrutinize every case where more than one solution serves a similar function and eliminate the ones that cannot justify their existence.
Vendor Consolidation: The Carrot You Are Not Using
Once genuine duplication has been eliminated, a second pass looks for consolidation opportunities. Many vendors offer substantial discounts when you expand your footprint with them. Are you already on O365 for email and productivity? Moving your CRM to Microsoft Dynamics rather than a standalone competitor may generate meaningful savings. Using Oracle as your standard database? Migrating your financial software to Oracle Financials could yield additional discounts across both products.
Every example is different. In some cases the consolidation saves money. In others the transition cost or functional trade-off makes it uneconomical. The analysis itself is a lightweight exercise and almost always surfaces interesting possibilities worth evaluating.
Pricing: Where 50 to 70 Percent of Vendor Savings Live
Eliminating duplication and pursuing consolidation are valuable. But the most lucrative exercise — the one that has generated 50 to 70 percent of my vendor savings across multiple organizations — is ensuring you are paying the right price for what you are already buying.
Start by checking utilization. There are frequent cases where an organization purchased a certain number of licenses in the past, usage has since declined substantially, and no one has reviewed the contract to adjust the fee accordingly. This alone can represent meaningful savings with minimal effort.
Next, benchmark your pricing against the market. There are third-party firms that specialize in providing this intelligence, and peer groups often share this data informally. The gaps you find can be striking. In one particularly egregious case I encountered seven separate contracts between a single vendor and a single client where the unit cost for the identical item ranged from $3.25 to $7.50. I had negotiated $1.50 for the same item at a previous organization, at less than 20% of this company's volume. The result of renegotiating was a three-year saving of $6.2 million. Both the IT team and the procurement department should have caught this. Neither had.
Negotiation: Carrots, Sticks, and Reputation
Expanding a vendor relationship is a powerful lever for negotiating better overall pricing. If you are adding a new capability, explore whether an existing vendor can provide it — and use the expansion as leverage to improve pricing across your entire relationship.
The stick is more powerful than the carrot, but it must be used carefully. Threatening to end a vendor relationship is a strong motivator — only if the vendor believes you will follow through. I have always taken the position that an organization must be known as a tough negotiator willing to change vendors, regardless of the transition pain. Vendors talk to each other. Your reputation as someone who will walk away from a bad deal spreads through the industry and shapes every negotiation that follows.
The way to build that reputation without taking on unnecessary risk is to use low-priority acquisitions as your proving ground. At the World Bank, I was evaluating a new monitoring solution to replace an aging home-grown system. The vendor quoted $1.75 million per year. I told the team the solution was worth $750,000 to us. After three weeks of back-and-forth the vendor reached $950,000 and my team was ready to accept. I held firm. The monitoring infrastructure had been substandard for five years. If it remained so for another year, the situation was manageable. A week later the vendor accepted $750,000.
The moral is simple: use the deals that are not pressing to build your reputation, so you do not need to play hardball with the deals that are pressing.