The Six-to-One Rule: Why Services Spend Dwarfs Software in Every Portco

Every PE operating partner should internalize a specific ratio: the services spend inside a typical mid-market portco runs approximately six times the software spend. This ratio — call it the six-to-one rule — has significant implications for where AI operating-layer deployment should focus. Software deployment projects capture disproportionate operating-partner attention because software is new, visible, and vendor-driven. Services spend — outsourced finance, outsourced IT, outsourced billing, outsourced tax, outsourced legal, agency relationships, consulting engagements — consumes far more capital and contains far more addressable margin.

The Math Behind the Six-to-One Rule

For a mid-market portco with $80M in revenue, typical annual software spend runs $1.5M-$3M across ERP, CRM, HRIS, collaboration tools, productivity software, and specialized business applications. The exact figure varies by industry, but the mid-market range is reasonably tight.

Services spend at the same portco runs significantly higher. Outsourced or contracted labor across finance, IT, legal, procurement, marketing, RCM (for healthcare), billing, tax, HR, and specialty advisory typically totals $10M-$25M depending on industry and operating model. For healthcare-services portcos, the ratio can exceed ten-to-one because outsourced billing and clinical-support services absorb particularly large budgets.

The six-to-one rule is a mid-point estimate; many mid-market portcos run higher ratios. The critical point is that services spend is materially larger than software spend across essentially all mid-market portco types.

Why This Ratio Is Under-Appreciated

The ratio is under-appreciated because services spend fragments across the P&L. Software spend is typically consolidated into IT or technology budgets and reviewed as a category. Services spend scatters across departmental budgets — finance's outsourced close, HR's benefits-administration vendor, legal's outside-counsel spend, operations' contract-labor arrangements, marketing's agency relationships. No single category owner sees the full aggregate.

Operating partners reviewing portco financials see specific line items (outside-counsel fees, outsourced-billing costs, consulting expenses) but typically do not aggregate them mentally into a "services spend" category. Software spend, by contrast, is visible as a line item and attracts scrutiny as a category.

Running the aggregation produces a specific, often surprising, view: the software budget is the smaller cost category, and the services spend is where the real labor-replacement opportunity sits.

The Operating-Layer Implication

The six-to-one rule has direct implications for AI operating-layer deployment prioritization. Deployments targeted at displacing services spend produce materially larger absolute savings than deployments targeted at improving software utilization. Operating partners focused on EBITDA impact should weight their deployment portfolio heavily toward services displacement.

This is why the blog series covers workflow-specific services displacement so extensively. The outsourced close swap, the outsourced tax swap, the outside-counsel rationalization, the MSP-replacement deployment, the consulting disaggregation — each of these is a services-displacement deployment targeting a specific line in the six-to-one category.

The Six-to-One Ratio in PE Portfolio Terms

At fund level, the six-to-one ratio produces enormous absolute spend against which operating-layer deployment can capture savings. A ten-portco portfolio with aggregate software spend of $20-30M typically carries aggregate services spend of $120-180M.

Capturing 25-40% of that services spend through operating-layer deployment — which is a realistic and achievable target over a multi-year hold cycle — produces $30-70M in annualized savings across the portfolio. At typical exit multiples, that translates into hundreds of millions of dollars of enterprise-value impact across the portfolio over the hold period.

No other cross-portfolio cost category offers similar absolute-dollar impact. Procurement, working capital, and revenue optimization are all valuable but smaller at the aggregate portfolio level. Services-spend displacement through AI operating layers is the largest single lever available to PE operating partners managing mid-market portfolios.

The Vendor-Landscape Nuance

Operating partners reading the six-to-one rule sometimes conclude that the right move is to simply buy more software from traditional SaaS vendors. This is not what the analysis suggests. Traditional SaaS vendors sell tools that accelerate labor; they do not replace the services layer. Moving from manual processes on top of tools to AI-delivered tools on top of tools is a copilot-category deployment, not an autopilot-category deployment.

The services displacement requires operating-layer capability that executes the workflow end-to-end — which is structurally different from traditional SaaS tooling. Operating partners who blur this distinction end up paying more for software while still carrying the full services spend. The successful deployment replaces services spend with operating-layer infrastructure, not with additional SaaS tools. This is the exact distinction covered in copilot vs autopilot: the framework every PE operating partner needs for 2026.

The Reporting Implication for Operating Partners

Fund-level operating reviews should include explicit tracking of the services-spend displacement metric across portcos. For each portco, what is current services spend, what is the addressable portion that operating-layer deployment can target, how much has been captured to date, and what is the trajectory for the remainder of the hold period?

This reporting cadence ensures that operating partners stay focused on the category where the largest value sits. Portcos that are under-indexed on services-spend displacement attract targeted attention; portcos that are executing well become case studies that travel across portfolio.

The same cross-portfolio reporting discipline covered in AI copilots for PE operating partners applies here — visibility into services-spend progression at fund level is essential for driving portfolio-wide coordination.

The Exit-Readiness Implication

Buyers diligencing mid-market portcos increasingly scrutinize services spend. A portco with services-heavy cost structure (high outsourced spend, fragmented vendor relationships, large agency reliance) signals operational immaturity and underwritten-for-improvement upside to the buyer. A portco with services-light cost structure (low outsourced spend, consolidated vendor relationships, operating-layer-supported delivery) signals operational maturity and limits the buyer's improvement thesis.

Sellers want to look like the second. Buyers want to find the first to underwrite post-close margin capture. The diligence conversation about services spend is becoming more sophisticated every year, and PE operators preparing for exit should be documenting their services-spend reduction explicitly in the exit narrative.

This is a component of the broader exit-multiple dynamic covered in how AI increases exit multiples for PE-backed services firms. Services-spend discipline is a specific diligence dimension where operating-layer-enabled portcos show up materially better than peers.

Why Operating Partners Miss This

If services spend is six times software spend and the operating-layer opportunity is correspondingly larger, why do operating partners frequently under-weight it?

Three reasons dominate.

The software industry has been aggressive about articulating its value proposition to PE operating partners. CIOs, CTOs, and software vendors all push for technology-deployment budgets. The services category has no equivalent advocacy — outsourced providers do not want to see their spend displaced, and internal services-consuming functions are often under-resourced to articulate the displacement opportunity.

Services-spend displacement is operationally harder than software deployment. It involves change management, vendor transitions, and role redesign. Software deployment, even when it underperforms expectations, is comparatively lower-friction. Operating partners naturally gravitate toward the lower-friction work, which means the bigger opportunity gets under-prioritized.

The operating-layer category that actually replaces services is newer and less well-understood than the software category. It takes operating-partner education to recognize the category, evaluate vendors, and structure deployments. That education investment has not yet happened across every fund.

The Operator's Response

The correct response for a PE operating partner is to treat services-spend displacement as a portfolio-level priority with dedicated attention, explicit metrics, and cross-portfolio coordination. The opportunity is too large to under-manage, and the competitive window for capturing it is relatively short as operating-layer capability becomes more widespread.

Services spend is six times software spend. The AI operating-layer opportunity scales with the size of the addressable category. Operating partners who internalize this ratio and act on it capture portfolio-wide value that those focused purely on software deployment will miss.