Follow the Margin: Mapping the Middlemen Between Your Enterprise and Its Infrastructure
Ask a CIO how many vendors touch their production infrastructure and you'll usually get a confident number. Ask how many intermediaries sit between the organization and the systems it actually runs, and the room goes quiet. For most mid-to-large US enterprises, that number is larger than anyone wants to admit — often exceeding the intermediary count in the physical supply chain that procurement teams scrutinize line by line.
The pattern is predictable. A global hyperscaler sells through a distributor. The distributor sells through a value-added reseller. The VAR wraps the deal in a managed services agreement. A separate professional services firm handles implementation, and a staffing agency supplies half the engineers who touch the environment. By the time a workload reaches production, four or five entities have added margin — and only one or two have added meaningful capability.
The Anatomy of the Stack
Not all intermediaries are created equal, and a blanket consolidation strategy can do more harm than good. The useful exercise is to classify each layer by what it genuinely contributes.
Value-adding layers typically include integrators with deep engineering benches, managed service providers who take real operational accountability under SLAs, and specialist firms whose domain expertise — say, regulated healthcare workloads or low-latency trading infrastructure — cannot be replicated in-house economically. These parties earn their margin by transferring risk or capability that the enterprise lacks.
Margin-only layers are harder to defend. These include pass-through resellers whose primary contribution is a contract vehicle, distributors who add logistics but no engineering, and referral brokers who exist largely to introduce parties that could have found each other directly. In many enterprise agreements, these layers collectively add 15 to 30 percent to cost while adding zero points of accountability.
The uncomfortable truth is that margin-only layers persist because they are invisible. They hide inside blended rates, bundled SLAs, and multi-year agreements signed by predecessors. The first step toward fixing the problem is simply drawing the map.
Drawing the Map: A Three-Question Audit
For every intermediary in your infrastructure stack, procurement and engineering leadership should be able to answer three questions jointly:
- What failure does this party absorb that we cannot? If the answer is nothing, the layer is a cost, not a control.
- If this party disappeared tomorrow, what would break, and how quickly could we replace them? Genuine partners have documented runbooks and knowledge transfer; pass-throughs have termination clauses.
- Who do our engineers actually call at 2 a.m.? Accountability lives where the pager lives. If escalation paths route through layers that never answer, the SLA is theater.
Enterprises that run this audit frequently discover that the partner they trust most is two layers removed from the vendor on the contract — a structural fragility that surfaces at the worst possible moment, usually mid-outage or mid-renewal.
Consolidating Without Losing Accountability
The instinct after such an audit is to cut everyone out and buy direct. That instinct is often wrong. Direct relationships with hyperscalers and hardware OEMs transfer enormous operational burden onto internal teams — burden that, per our previous analysis of the quiet tax aging infrastructure places on senior engineers, your best people cannot afford to carry.
The goal is not zero intermediaries. It is one accountable throat to choke per domain, with all other layers either eliminated or made transparent. A well-structured consolidation does three things: it reduces the number of entities with access to production systems, it converts opaque blended pricing into line-item visibility, and it aligns contractual accountability with the party actually performing the work.
An RFP Scoring Rubric for Direct vs. Multi-Tier Arrangements
When evaluating proposals, score each bidder on five weighted dimensions:
- Escalation proximity (25%): How many organizational hops between the on-call engineer and the signatory on the contract? Fewer is better.
- Pricing transparency (20%): Can the bidder decompose its rate into labor, licensing, and pass-through margin? Refusal to do so is disqualifying.
- Named engineering continuity (20%): Will you get the same team across the engagement, or a rotating cast? Rotation hides margin.
- Outcome-based SLAs (20%): Are penalties tied to service levels you experience, or activity metrics the vendor controls?
- Exit portability (15%): Does the contract guarantee documented handover, infrastructure-as-code artifacts, and data egress without penalty?
Score direct partners and multi-tier bidders on the same rubric. Frequently, a well-structured two-tier arrangement with a genuinely accountable lead partner will outscore both a pure direct relationship and a tangled five-layer chain. The structure matters less than the accountability.
The Bottom Line
Your supply chain gets quarterly reviews, dual-sourcing analysis, and executive attention because its margins are visible on a spreadsheet. Your infrastructure intermediaries deserve the same scrutiny — arguably more, because their margins compound silently across every renewal. Map the chain, classify each link by what it earns, and consolidate around accountability rather than around the illusion of simplicity. The savings are rarely dramatic in any single quarter; they are relentless across every one that follows.
