Mid-market companies in DACH — typically 500 to 5,000 employees — operate in the structural gap that conventional vendor management thinking doesn't address well. They have vendor portfolios too complex for the informal management that works in smaller organizations (80–200 active vendors is typical), but the budget realities don't support a dedicated 5–8 FTE enterprise VMO. The pragmatic answer is a hybrid model: a small in-house function focused on strategic vendors, supplemented by external vendor-management-as-a-service capacity for breadth coverage and execution leverage.
The mid-market structural problem.
Vendor management thinking in IT has been shaped by two organizational poles. At one end, small organizations manage vendors informally — each business owner runs their relationships, finance reconciles invoices, and the model works because the portfolio is small enough that the cost of governance overhead would exceed its benefit. At the other end, large enterprises run dedicated vendor management offices with 10–30+ FTEs, integrated tooling, and embedded category leads.
Mid-market organizations sit in between, with structural characteristics from both worlds. Their vendor portfolios — typically 80–200 active suppliers, often spanning 10+ countries through subsidiary structures — are complex enough to require deliberate governance. But their cost structures don't support enterprise-scale internal functions, and the executive air-cover for building one is often missing.
The result, across most mid-market DACH organizations we engage, is the worst of both worlds: an informal model applied to a portfolio that's outgrown it.
The pattern that produces value.
The hybrid model: 1–3 in-house FTEs focused on strategic vendor governance and category strategy, supplemented by external vendor-management-as-a-service capacity for breadth coverage, structured benchmarks, and renewal-pipeline execution.
The economics work because of asymmetry. The strategic governance work — quarterly forums with tier-1 vendors, executive sponsorship, joint roadmap planning — requires deep internal context that an external partner cannot easily acquire. The breadth work — annual benchmark refresh on tier-2 vendors, contract repository maintenance, structured renewal review across the portfolio — is largely methodology and capacity, which an external partner can deliver more efficiently than an internal function building everything from scratch.
The hybrid model lets each side do what it does best. The internal team focuses on the work that requires institutional context. The external team provides the methodological depth, the comparable benchmark data across multiple engagements, and the execution capacity that internal headcount cannot economically provide.
Why mid-market is structurally different.
1. Vendor portfolio size and complexity.
Mid-market organizations typically run 80–200 active IT vendors. This is large enough to require structured management but small enough that none of the standard segmentation tools (which were built for enterprise portfolios of 500–2,000 vendors) apply cleanly. The Kraljic Matrix still works, but the long tail looks different — fewer vendors collectively account for a higher proportion of spend.
2. Internal capacity constraints.
Mid-market IT functions typically operate with 30–80 FTEs total. Carving out 5–8 of those for a dedicated VMO is not feasible without compromising operational delivery. The internal vendor management capability has to fit inside 1–3 FTEs or it doesn't get built.
3. Procurement maturity.
Mid-market procurement functions are typically less specialized than enterprise procurement. They run all categories — including IT services, which is itself a specialized category. The depth of IT-specific procurement methodology (Zero Vendor Deviation, structured benchmark analysis, AI contract review) usually sits outside what a generalist procurement function maintains.
4. Geographic complexity.
Mid-market DACH organizations frequently operate across Austria, Germany, Switzerland, and increasingly across the broader EU — adding regulatory complexity (GDPR, BaFin where applicable, sector-specific regimes) without the centralized legal capacity larger organizations have.
5. Decision-making structure.
Decisions move faster in mid-market organizations than in enterprises — fewer committees, shorter approval chains. This is an advantage when the decision-making framework exists. Without one, it's a vulnerability — fast decisions on insufficient information.
What the hybrid model actually looks like.
Internal (1–3 FTEs):
- Vendor management lead, often dual-hatted as senior IT manager or CIO direct report.
- Strategic vendor relationship owners for tier-1 vendors (typically 3–7 vendors).
- Standing membership in tier-3 strategic governance forums.
- Internal escalation point for vendor performance issues that need executive air-cover.
External VM-as-a-Service:
- Portfolio inventory and renewal-pipeline maintenance.
- Annual benchmark refresh across tier-2 vendors.
- Structured renegotiation execution on 2–4 contracts per year.
- AI contract analysis for renewal review and audit findings.
- Methodology and tooling — scorecard templates, governance materials, risk-register structure.
- Independent SLA verification on tier-1 vendors.
Shared:
- Tier-2 governance forums (monthly) — internal lead chairs, external function provides analytics and scorecard support.
- Quarterly strategic reviews with internal sponsor + external context on benchmark and market movement.
The economics.
For a mid-market organization with €30–80M annual IT vendor spend, the hybrid model typically costs 0.4–0.8% of vendor spend (combined internal and external capacity). The cost-leakage prevented — based on benchmark-driven renegotiation, renewal-pipeline value capture, and independent SLA verification — typically runs 10–18% of in-scope spend in year one, stabilizing at 15–22% recurring.
The ROI math is similar to the enterprise case but easier to build because the external capacity is variable cost — engaged when needed, scaled back when not — rather than fixed headcount that has to be defended budget cycle to budget cycle.
The Aventario perspective.
"In about 60% of our mid-market engagements, the client started by asking us to help them build a VMO. By month three, the more useful conversation was: how do we keep your 1–2 internal people focused on the strategic relationships where they actually add value, and use external capacity for the methodological breadth they cannot economically maintain in-house. The hybrid model is not a compromise — for the mid-market, it's the right answer."
— Margit Györfi, CPO, Aventario
FAQ.
How many vendor management FTEs does a mid-market company need?
1–3 internal FTEs focused on strategic vendors and category leadership, supplemented by external VM-as-a-Service capacity for portfolio breadth, methodology, and execution leverage. The full enterprise model (5–8+ FTEs) is rarely economically justified at mid-market scale.
What does VM-as-a-Service cost for a mid-market company?
Typically 0.2–0.5% of IT vendor spend annually for the methodological and execution components — much lower than the equivalent internal-only capability. The value capture is typically 10–18% of in-scope spend in year one.
What's the alternative for mid-market companies that don't want external partners?
Building a 4–6 FTE internal VMO with the right tooling — typically achievable but with 18-month build timeline and significant year-one fixed cost. Some mid-market organizations choose this route; most find the hybrid model produces better economics and faster value capture.
