Across DACH, UK and Polish enterprises, IT supplier lists are being cut aggressively in the name of savings. The logic looks clean on a slide and frequently breaks in delivery. Supplier count is a poor proxy for portfolio quality. Lower administrative costs often coincide with higher operational and technical exposure because dependencies accumulate under fewer suppliers. A consolidation program dashboard must track spend concentration alongside supplier count, savings, and operational incidents. The healthiest supplier ecosystems keep at least two capable players in the game for one tower. For most categories, a primary supplier should receive 70 to 80 percent of the volume. One or two secondary suppliers maintain a real relationship and preserve optionality.
Fewer vendors can create a larger failure domain
The better objective: optimize dependencies, not vendor count
Procurement teams celebrate visible benefits like simpler governance and aggregated purchasing. They often miss the invisible costs of lock-in, switching, and business continuity. IT sourcing is better treated as portfolio risk engineering. The goal is preserving credible alternatives rather than minimizing the roster. Consolidation that leaves a company unable to switch suppliers at renewal is a long-dated price increase with a celebratory kickoff meeting, dressed up as a savings program. For critical inputs that are technically complex or difficult to substitute, dependency risks frequently outweigh the benefits of consolidation. A smaller roster increases risk when one failure can simultaneously remove operational capacity, technical expertise, negotiating leverage, and access to undocumented knowledge.
The hidden trade: visible savings for invisible concentration
Spend and contract volume hide dependency depth. Dashboards miss exit costs, knowledge ownership, and correlated failure modes. Finding and certifying a replacement supplier for critical components can take six months to two years. This leaves the organization effectively captive.
The case against indiscriminate consolidation
Where procurement dashboards fail
[concentration-risk-map]
Assess each critical capability by system, supplier, platform, scarce skill, knowledge owner, delivery region, subcontractor, contractual right, and credible substitute. For DACH, the UK, and Poland, identify whether apparently distributed teams rely on the same talent pool, cloud platform, or sub-tier provider. Record data and environment access, documentation quality, termination assistance, portability rights, and the time required to activate an alternative. Warning signs can appear quickly. One supplier controls design and operations. Internal knowledge decays. Alternatives cannot access documentation or environments. Exit rights have not been exercised. Nominally separate services share the same underlying provider. A renewal window is shorter than the realistic switching period.
Calculate total value, not the contract discount
| Decision Ledger Component | Category | Ledger Element | Calculation & Risk Adjustment |
|---|---|---|---|
| Potential Savings | Financial & Commercial | Volume discounts & admin savings | Discounted across transition years |
| Potential Savings | Operational | Governance & integration gains | Discounted across transition years |
| Concentration Risks | Operational Transition | Transition and exit costs | Impact multiplied by probability |
| Concentration Risks | Business Continuity | Disruption & supplier failure | Impact multiplied by probability |
| Concentration Risks | Commercial Leverage | Lock-in & sharp repricing | Impact multiplied by probability |
| Concentration Risks | Market Readiness | Alternative-supplier carrying costs | Impact multiplied by probability |
| Concentration Risks | Innovation & Capabilities | Lost options & skill withdrawal | Impact multiplied by probability |
Administrative savings often vanish when compared with lock-in, transition effort, duplicated tooling, business interruption, reduced negotiating leverage, delayed access to scarce skills, and constrained innovation. Industry research on consolidation programmes reports roadmaps running about 18 months longer than planned. Consolidating more spend with a supplier who is already 25 percent above market price increases exposure rather than improving the position. A viable renewal alternative must be available within the contract’s switching window and exercised recently enough to be real. If not, the supplier will price to what the buyer can absorb. Compare baseline administrative savings, volume discounts, governance gains, and integration benefits against transition and exit costs, continuity exposure, lock-in, alternative-supplier carrying costs, and lost innovation options. Then adjust the ledger for supplier failure, sharp repricing, skill withdrawal, acquisition, geopolitical disruption, and technology discontinuation. Weigh the two columns the way a risk register does rather than as a flat subtraction: put every cost item in as an expected annual value – estimated financial impact multiplied by the probability of that scenario over the contract term – and discount the savings side across the transition years in which they are not yet realised. Show ranges and unknowns rather than disguising weak evidence as a precise financial result. A consolidation case that survives only when the risk column is set to zero is not a business case.
Test concentration before it becomes a crisis
[supplier-stress-test-loop]
Build a scorecard covering business criticality, dependency depth, replaceability, recovery time, exit cost, knowledge control, geographic correlation, contractual leverage, supplier financial health, and innovation alternatives. Track the share of critical services, spend, proprietary knowledge, and recovery paths concentrated in each supplier, platform, geography, and subcontractor. Run stress tests for sudden outage, degraded service, sharp repricing, key-person loss, acquisition by a competitor, sanctions or cross-border restrictions, and failure during an active transformation. Measure service impact, recovery time, switching time, data portability, and whether the alternative has sufficient access, skills, and capacity. Set thresholds from the organization’s risk appetite and recovery obligations. Executive review should trigger when critical exposure breaches those limits, no substitute fits the switching window, exit readiness is untested, or a shared platform or geography defeats nominal diversification. For significant consolidations, pilot the consolidated relationship for 90 days at elevated volume before formally ending fallback options.
The strongest argument for fewer suppliers
Consolidation can remove real friction
Fewer suppliers reduce coordination overhead, incompatible tools, and weak purchasing leverage. Consolidated environments are reported to deliver 4x ROI compared with fragmented ones, while integration timelines improve by 25 to 50 percent. Currently, only 29 percent of systems are fully integrated across enterprises. Consolidation reallocates a retired supplier’s capability to an existing partner with broader scope, typically with better commercial terms. For lower-risk, easily substitutable categories, consolidation remains a sound strategy. It works best when services are noncritical, modular, documented, portable, and supported by tested exit options.
Redundancy is justified only when it buys recoverability
Deliberate redundancy is justified for critical operations, scarce skills, region-specific delivery, foundational technologies, and transformation programs where one failure could halt material business activity. Reject redundancy when providers depend on the same cloud, subcontractor, talent pool, or proprietary platform. Assess whether the additional supplier materially improves switching speed, recovery, negotiating leverage, knowledge retention, or innovation access. If not, it is just waste. Redundancy should act as resilience capacity, not administrative bloat.
What a resilient target portfolio looks like
Segment suppliers by role and failure consequence
Segment supplier categories by supply risk and business impact. Categories high on both dimensions warrant a multi-source strategy. Treat high-spend, lower-strategic-importance suppliers as the highest-value consolidation targets. Avoid disrupting low-spend, high-strategic-importance niche suppliers that cannot be easily replaced. Use strategic partners for differentiating capabilities, specialist providers for deep expertise, scalable delivery providers for variable capacity, and contingency suppliers for recovery. Apply intensive dependency oversight to critical domains and lighter controls to commodity services. Preserve internal knowledge, modular architecture, data portability, access rights, and contractual exit mechanisms. For major IT categories, maintain at least two tier-1 suppliers. One supplier can hold 70 percent of the infrastructure business while another holds 30 percent to preserve competitive pressure. Structure service bundles with optional components so suppliers compete on the core service and selected add-ons.
Unwind dependency without destabilizing delivery
Map dependencies, stabilize documentation and access, rebuild internal ownership, modularize interfaces, qualify alternatives, transfer limited scope, rehearse exit, and only then rebalance volume. Use parallel transition windows and bounded pilots to protect live services and transformation milestones. In a benchmark methodology covering 168 enterprise consolidation programs, a representative program allocates months 12 to 18 to migration planning, months 18 to 30 to migration execution, and months 30 to 36 to realization. Prioritize dependencies with the greatest business consequence and weakest recoverability.
Put the portfolio under executive control
Ask for a dependency map, not a supplier count
Challenge the executive team to review critical capabilities by supplier, platform, region, knowledge owner, substitute, recovery path, and tested exit status. On average, organizations are trying to manage more than 10 supplier relationships for a single initiative. Before approving consolidation, executives should assess how many remaining suppliers could credibly be replaced within a reasonable switching window. Relying purely on the number of suppliers being removed is a mistake. Require every proposal to show both administrative value and the optionality it removes.
Make resilience a condition of approval
Establish an executive review cadence for concentration metrics, threshold breaches, scenario results, remediation ownership, and exit-plan readiness. Periodically review supplier financial health, capacity utilization, geographic concentration, and sub-tier dependencies. For categories with both high supply risk and high business impact, approval should require a multi-source strategy, even when it carries a pricing premium. Identify one efficient supplier relationship that would be hardest to replace. Commission a stress test before the next renewal or scope expansion. Peoplemore sits on the alternative side of this problem. As a nearshore delivery partner for Telco, Finance and Healthcare organisations across DACH, the UK and Poland, it is usually the supplier that keeps a second credible option alive in a critical domain rather than the one absorbing every tower. Executives running the dependency review described above are welcome to use that outside view as a second opinion before the next renewal.
Marcin Dąbrowski
