For operating partners managing a portfolio of investments, the IT vendor spend across that portfolio is rarely treated as a strategic lever. It should be.
A typical portfolio company at $40M–$400M in revenue accumulates technology vendor relationships organically over five to ten years. Software licenses are added, upgraded, renewed, and never canceled. Managed service provider contracts are signed early, auto-renew annually, and never benchmarked. Tooling sprawls into departmental subscriptions that finance never consolidates. By the time the company reaches the PE portfolio, technology vendor spend is typically between 15% and 40% above what the same scope would cost under fresh procurement.
Across a five-company portfolio, this is not noise. It is a meaningful, recoverable line item that no one is owning.
Why MSP and Vendor Spend Compounds Quietly
The structural problem is that no one inside the portfolio company is positioned to challenge vendor spend.
The IT director is operationally dependent on the MSP and on most software vendors. Challenging the relationship creates friction with people the IT director works with daily. The CFO sees the contracts but rarely has the technical depth to assess whether scope is appropriate or pricing is competitive. The CEO has bigger fires. The operating partner sees the line item in financials but has no mechanism to test whether it is appropriately priced.
Meanwhile, the MSP’s commercial model is built on retention. The MSP is incentivized to maintain the existing scope, avoid measurement, and let the contract auto-renew. The MSP knows what the market rate is, because they bid against it for new business. The portfolio company doesn’t.
The result is predictable. Pricing drifts higher than market over time. Scope drifts wider than necessary. Performance is reported by the MSP itself and never independently verified. And the contract auto-renews on a 60- or 90-day cancellation window that nobody tracks.
This is not a hostile actor problem. It is a structural problem. The portfolio company cannot solve it from inside, because no one inside has the standing, the leverage, or the time.
What a Structured Audit Surfaces
A disciplined vendor and MSP audit run in the first 45 days of ownership — or the first 45 days of a new technology leadership engagement — typically surfaces findings in five categories.
Software licensing rationalization: 15–30% reduction. Companies accumulate licenses for users who left, tools that overlap, premium tiers no one uses, and seat counts that never got reconciled. A clean license audit against actual usage reduces total software spend in this range as a baseline. Companies that have been through M&A almost always have higher recoverable spend because licenses come over from acquired entities and never get consolidated.
MSP repricing: 20–40% reduction for the same scope. This is the largest single line item in most audits. An MSP priced competitively when the contract was signed three or four years ago is now priced materially above market. The market has moved — compute, monitoring tools, and labor arbitrage have all changed the cost structure for MSPs. Companies that take the audit findings to their incumbent and request a market-rate adjustment usually receive one rather than lose the contract. Companies that go to market with a clear scope often beat that adjustment.
Auto-renewal exposure: variable. Most enterprise software contracts and MSP agreements carry auto-renewal clauses with 60- or 90-day cancellation windows. A contract calendar built in the first 30 days of an audit identifies which windows are about to close — and locks in optionality before the renewal takes effect. Missing one of these windows is not a small error. It is another full year at the incumbent rate, which on a meaningful contract can be six figures.
Duplicate and redundant tooling: variable. Departments buy tools without cross-checking against existing licenses. The marketing team has a project management tool the engineering team also has. The sales team has a contract platform the legal team duplicated. The operations team is paying for a monitoring service the MSP’s tooling already provides. A consolidated tooling audit usually identifies between three and eight redundancies in a portfolio company of this size.
Scope inflation in MSP agreements: 10–25% scope reduction. MSPs are often paid for scope the company doesn’t actually use — managed backup for systems that no longer exist, managed endpoints for users who left, monitoring on retired services, premium support tiers the company never invokes. A scope audit aligned to current operational reality reduces the contracted scope without changing what the company actually receives.
The five categories together typically recover enough vendor spend in the first year to fund the cost of structured technology leadership for that year — and the savings compound through the remainder of the hold period.
The Compounding Effect Across a Portfolio
The recovery on a single portfolio company is meaningful. The recovery across a five- or ten-company portfolio is consequential.
If a typical portfolio company at $40M–$400M in revenue carries an annual IT vendor spend between $1.5M and $6M, and a structured audit recovers between 15% and 30% of that spend on a sustained basis, the per-company annual recovery is between $225,000 and $1.8M. Across a five-company portfolio, this is $1.1M to $9M of annual recovered EBITDA, recurring through the hold period.
This recovery is also defensible at exit. Buyers do not give credit for lazy IT spend that the operating partner allowed to persist for the duration of ownership. They do give credit for a documented, benchmarked, performing technology vendor environment that the buyer can take over without immediate restructuring.
The audit is also one of the few EBITDA levers in technology that does not require operational disruption. Cost actions in headcount, real estate, or operations introduce execution risk and management distraction. A vendor and MSP audit produces savings without disrupting the commercial operation of the business. It is run alongside operations, not through them.
Why This Doesn’t Get Run Without External Discipline
Three reasons the audit doesn’t get run from inside the portfolio company.
First, the IT director cannot run it. The IT director is the daily relationship owner with the MSP and with most software vendors. Asking the IT director to negotiate aggressive repricing creates an immediate working-relationship problem. Even if the IT director has the inclination, they typically do not have the benchmarking data — they know what the company is paying, not what the market is paying.
Second, the CFO cannot run it alone. The CFO has the financial visibility but rarely has the technical depth to assess scope appropriateness or identify duplicate tooling. The CFO can renegotiate contract terms once the technical analysis is complete, but cannot generate the analysis from finance alone.
Third, the MSP will not surface its own pricing exposure. The MSP’s account management team is measured on retention and contract value. They will not proactively identify that the company is overpaying. If asked, they will defend the existing pricing.
The audit requires a function with technical depth, vendor management experience, market benchmarking data, and no relationship dependency on the incumbents. That function does not typically exist inside a $40M–$400M company.
What the 45-Day Audit Actually Produces
A structured vendor and MSP audit in the first 45 days produces specific outputs:
- A complete inventory of technology vendor relationships, contract terms, renewal dates, and cancellation windows
- A benchmarked assessment of MSP pricing against current market rates for equivalent scope
- An identified list of license, tooling, and scope rationalization opportunities with quantified savings
- A renegotiation plan with prioritization, timing, and target outcomes
- A vendor management calendar that prevents auto-renewal exposure going forward
The audit is not a one-time exercise. The output is a sustained vendor management discipline that prevents the same drift from accumulating again over the remainder of the hold period.
Where This Fits at Vertex
This is the work Vertex was built to do. We run the audit operating partners don’t have the bandwidth to run — vendor by vendor, contract by contract, MSP relationship by MSP relationship — and deliver the findings as a quantified, defensible plan with named owners and named deadlines. Pre-acquisition diligence, post-close 100-day window, or mid-hold cleanup — the analysis is the same. The recoverable EBITDA is usually already on the page; the discipline to actually capture it is what’s missing.
If you’re looking at portfolio IT spend and wondering where it should be, the first conversation is free →