"Your IT Runs" Is the New Outcome-Based Contract

The future of IT managed services is outcome-based contracting, and the simplest outcome specification is the most powerful: "your IT runs." The customer pays for the outcome — operating IT infrastructure, available and secure, with defined service levels — rather than for the hours of labor that historically produced that outcome. This shift is made possible by AI operating layers that execute the underlying work at materially lower cost than the labor model could support. For MSPs and internal IT functions alike, outcome-based contracts are the commercial framing that converts operating-layer capability into durable pricing power.

The Problem With Labor-Hours Economics

Managed services has historically billed on per-seat, per-endpoint, or per-hour structures. All three are labor-proxy metrics — they assume a relationship between the count of things managed and the labor required to manage them. That relationship held when the underlying work was human-performed and roughly linear with volume.

The relationship breaks when the underlying work is operating-layer-performed. A single operating layer can manage 1,000 endpoints or 10,000 endpoints at approximately the same marginal cost. Per-seat pricing no longer reflects the actual cost structure; it reflects a pricing inertia from the labor era. Customers eventually notice, and pricing pressure begins.

The solution is not to defend the per-seat model. It is to reprice the category around outcomes — which is both what the customer actually wants and what operating-layer economics can support profitably.

What "Your IT Runs" Actually Means

"Your IT runs" is shorthand for a defined set of outcomes the provider commits to delivering, measured against specific SLAs and incident metrics. The typical contract specifies uptime for core systems, mean time to resolution for defined incident categories, patching and update currency, security-posture metrics, and user-experience metrics like help-desk response time.

The provider commits to delivering these outcomes for a monthly fee. How the provider delivers them — with labor, with operating-layer automation, with hybrid approaches — becomes a provider-side operating decision rather than a customer-specified input. Customer gets the outcome; provider captures the margin from executing efficiently.

This is a meaningful commercial shift. Under labor-hours economics, efficiency gains flow mostly to the customer through reduced billable hours. Under outcome-based economics, efficiency gains flow to the provider as margin expansion, which aligns provider incentives with operating-layer adoption.

The Operating Layer as the Enabler

Outcome-based contracting requires the provider to have high confidence in outcome delivery at a cost structure that supports margin. Without an operating layer, outcome-based pricing is risky because human-delivered services have variable performance and unpredictable cost escalation (cat events, surge demand, incident clusters). With an operating layer, outcome delivery becomes more predictable because the execution runs on software rather than labor capacity that can be exhausted.

The operating layer handles the deterministic work — monitoring, alerting, patching, provisioning, routine ticket resolution, security-posture maintenance. Human engineers handle the judgement-intensive work — architecture decisions, major incident response, strategic planning, customer relationship management. This division makes outcome-based pricing economically sustainable because the deterministic work runs at software margin and the judgement-intensive work is capped in scope per customer.

The pattern matches the broader shift from labor-based to operating-layer-based delivery that is reshaping services categories across the economy, covered at a higher level in two autopilots in one policy: the unbundling of insurance operations and analogous pieces.

The Customer-Side Advantages

Outcome-based contracts are not just a provider-side advantage. Customers prefer them because the pricing matches the value they actually want from the provider. Customers never wanted to buy hours; they wanted to buy "IT that works." Outcome-based pricing explicitly delivers that — and the alignment of incentives means the provider is economically motivated to prevent incidents, not just respond to them.

Customer executives also prefer the operating-expense predictability of fixed outcome-based fees. CFOs plan better against stable monthly costs than against variable hours-driven billing. Outcome-based contracts remove the billing surprise that mid-market companies often experience when incident volume spikes and hours billing balloons.

Implications for MSP Platforms

For PE-backed MSP platforms, the shift to outcome-based contracting is both an opportunity and a requirement. The opportunity is margin expansion on existing customer relationships; the requirement is that customers increasingly expect outcome-based pricing and will migrate to competitors offering it if the platform holds onto labor-hours economics.

MSP platforms should be repricing new customer contracts on outcome-based terms immediately, with operating-layer-supported delivery models that make the pricing sustainable. Existing customer contracts get migrated on renewal, with explicit communication about the shift from hours-billed to outcome-delivered. The platform's overall economic profile improves both on new business and on renewals within 12-18 months.

The deployment sequence — operating layer first, then outcome-based commercial model — matches the dynamic covered in the $100B MSP market is about to get disintermediated. The commercial shift is downstream of the operating-layer deployment; attempting it without the operating layer produces unsustainable economics.

Implications for Internal IT Functions

Outcome-based contracting is not limited to third-party providers. Internal IT functions inside mid-market companies should also be framing their relationship with the business in outcome terms. The framing shifts the conversation with the CFO and the operating leaders away from "IT is expensive" toward "IT delivers these outcomes at this cost," which is a fundamentally better conversation for the function.

Internal IT leaders deploying operating layers gain the same economic advantage as MSP providers: they can commit to specific outcomes at defined cost, demonstrate delivery against those outcomes, and redirect the resulting capacity toward strategic initiatives. This is the internal-function version of the same shift covered across services categories in why your GC should be firing outside counsel for standard work.

The Risk Transfer

Outcome-based contracts transfer execution risk from the customer to the provider. Under labor-hours economics, the customer absorbs the risk that a specific incident takes more hours to resolve than expected. Under outcome-based economics, the provider absorbs that risk in exchange for the consistent margin from routine operations.

Providers without operating-layer capability cannot take that risk transfer profitably. Their cost structures are too variable and their margin headroom is too thin. Providers with operating-layer capability can price the outcome-based contract against a predictable cost base because the operating layer absorbs volume elastically. This risk-transfer dynamic is another reason the operating layer is a prerequisite, not a companion, to outcome-based pricing.

SLA Design in an Operating-Layer Model

Outcome-based contracts depend on SLA design that is both meaningful to customers and measurable by providers. The operating layer supports materially better SLA measurement than labor-based delivery because every action it takes is logged, timestamped, and attributable. Uptime metrics, time-to-resolution metrics, patching-currency metrics, and security-posture metrics all become automatically reportable.

Providers should use this measurement capability to design SLAs that reflect outcomes customers actually care about — not just infrastructure uptime but end-user productivity, incident impact on business operations, and security-posture maturity. Sophisticated customers reward providers whose SLAs reflect genuine value, and the operating layer makes that sophistication commercially viable.

What the Category Looks Like in Three Years

In three years, the managed services category will be dominated by operating-layer-enabled providers running outcome-based contracts. Legacy MSPs running labor-hours economics will be compressing in revenue, margin, or both. Internal IT functions in mid-market companies will be operating against outcome-framed agreements with the business, supported by operating-layer capability.

The operators running PE-backed MSPs or advising on MSP acquisitions should be evaluating targets and portcos explicitly on their trajectory toward this end state. Platforms that are actively deploying operating layers and migrating to outcome-based pricing will trade at premium multiples. Platforms that are not will trade at compressing multiples as the category repricing happens around them.

The Commercial Transformation Is the Value Capture

The operating-layer deployment is the operational transformation. The outcome-based commercial model is the value capture. Providers who do the first without the second give the benefits to customers through reduced per-hour billing. Providers who do both capture the benefits as margin expansion.

"Your IT runs" is the commercial framing that converts operating-layer capability into provider economics. Every MSP should be moving in that direction — and the ones that move fastest own the next cycle of the category.