Vendor sprawl is the gradual, unintended accumulation of an excessive number of active suppliers in an organization. It compounds quietly over years as individual teams make reasonable local decisions without a global view of the vendor portfolio. Across DACH mid-cap IT organizations, the typical vendor portfolio carries between 80 and 220 active suppliers, with 15–25% of vendor management overhead consumed by the long tail of low-spend, low-strategic-value vendors.
How vendor sprawl happens.
It is not a procurement failure. It is the residue of many reasonable local decisions, made by competent people, in the absence of a portfolio view. A team needs a niche capability for a project; nobody at the time would have argued for routing the requirement through a strategic partner instead. Three years later, the project is gone but the vendor is still on the books, the contract auto-renewed, and nobody remembers who originally approved it.
Multiply by ten years and three reorganizations. The result is the average mid-cap IT vendor portfolio: somewhere between 80 and 220 active suppliers, with 60–70% of spend in the top ten and a long tail of 50–150 vendors collectively consuming 15–25% of spend and roughly the same proportion of vendor-management bandwidth.
Why it matters.
- Overhead tax. Each vendor carries an administrative footprint regardless of spend: contract maintenance, finance reconciliation, security review, governance touch-points. The marginal cost of a small vendor is non-trivial.
- Negotiation leverage erosion. Spend that could be concentrated with strategic partners is fragmented across the long tail. Volume discounts the organization should be earning, it isn't.
- Risk surface. Each vendor is a potential failure mode — security, financial, regulatory. A long tail of small vendors is an aggregate risk surface that nobody is actively managing.
- Knowledge fragmentation. Institutional knowledge gets scattered across many small relationships. When a vendor leaves, the relationship resets to zero.
- Governance capacity. Vendor management bandwidth is finite. Time spent on the long tail is time not spent on the strategic relationships where it would matter.
How to size your sprawl.
Three numbers tell the story:
- Total active vendors. Pull from finance: every supplier with spend >€1k in the last 12 months. Compare to the procurement record. Expect 15–30% more than the procurement record shows.
- Long-tail concentration. Sort by spend descending. What percentage of spend is in vendors below the top 20? In healthy portfolios, less than 15%. In sprawled portfolios, 25–40%.
- Vendors-per-FTE. Total active vendors divided by vendor-management headcount. Anything above 30:1 means the long tail is functionally unmanaged.
How to fix it.
Vendor consolidation is the structured response. Three principles:
- Segment first, cut second. Use the Kraljic Matrix or equivalent. Strategic, leverage, bottleneck, routine. Different quadrants need different treatment.
- Route through strategic partners. Routine-quadrant work should flow through existing strategic relationships wherever the strategic partner can deliver. Most can deliver more than they're currently being asked to.
- Sunset, don't just cancel. A vendor on the books for three years has integrations, knowledge, and ongoing commitments. Plan the exit deliberately; don't just stop renewing.
Why one-off rationalization rarely works.
A vendor consolidation program that cuts the portfolio from 180 to 60 will, without governance change, regrow to 140 within four years. The accretion mechanics that produced sprawl in the first place are still in place. Sustainable consolidation requires the underlying governance to change: a vendor-onboarding process that asks "could this be done by an existing strategic partner" before approving a new vendor, and a renewal-pipeline review that tests every renewal rather than letting it auto-roll.
FAQ.
What is vendor sprawl?
The gradual, unintended accumulation of an excessive number of active suppliers in an organization, typically driven by individual local decisions made without a global portfolio view.
How many IT vendors should an organization have?
The right number depends on size and complexity, but the structural target is to route 70–85% of in-scope IT services through five to seven strategic partners. The remaining long tail should be small and bounded.
Is vendor sprawl a procurement problem?
No, it's a governance problem. Procurement typically processes the request that creates a new vendor; the absence of a global onboarding gate is what allows sprawl to accumulate.
