The Managed Services Paradox: AI Is Resolving More Tickets — So Why Are Your Costs Still Rising?

If you have a managed services contract for your SAP environment, your provider has almost certainly told you about their AI capabilities. Automated ticket resolution. Intelligent monitoring. Predictive issue detection. The pitch is compelling — and in many cases, the technology is real.

So here is the question executives should be asking: if AI is resolving an increasing percentage of support tickets automatically, why does the cost of your managed services contract keep going up?

It is a question most providers would prefer you did not ask. At Astraeus, we think it is one of the most important questions in enterprise IT right now.

The managed services industry has undergone a quiet but significant transformation over the past several years. AI-driven automation — including large language models, intelligent runbook execution, and predictive monitoring — has materially reduced the human labor required to resolve a substantial portion of routine support tickets.

Industry estimates vary, but leading managed services providers are now resolving anywhere from 30% to 60% of Level 1 and Level 2 tickets through automated means, with no human intervention required. For SAP environments specifically, common automation targets include system monitoring alerts, batch job failure recovery, user access requests, and routine configuration queries.

The economics of this shift are straightforward: the provider's cost to deliver a unit of service has decreased. The question is whether those savings are being passed to the client — or retained as margin expansion.

In the majority of contracts we have reviewed, the answer is the latter.

Managed services providers offer several explanations for continued cost increases, some more legitimate than others.

Scope expansion. As SAP landscapes grow more complex — adding BTP integrations, cloud infrastructure, new modules, and AI capabilities — the scope of what needs to be managed genuinely expands. This is a real factor, and it is worth evaluating honestly.

Talent and inflation. Senior SAP expertise remains expensive, and providers cite rising labor costs as justification for price increases. This argument has merit for complex, judgment-intensive work — but it does not hold for ticket categories that are now handled entirely by automation.

Investment recovery. Providers argue that the AI capabilities driving automation required significant investment to build, and that clients benefit from those capabilities. This is partially true — but it conflates the cost of building automation with the ongoing cost of delivering service.

Contract structure. Most managed services contracts are structured around fixed monthly fees or tiered pricing based on system complexity — not on actual labor consumed. This structure insulates providers from passing through the efficiency gains that automation delivers.

The net result is a pricing model that was designed for a labor-intensive service delivery model, applied to an increasingly automated one — with the productivity gains flowing to the provider.

This is not an argument against managed services, or against AI-enabled service delivery. Both can deliver genuine value. It is an argument for renegotiating the commercial terms to reflect the current reality of how services are actually being delivered.

Demand transparency on automation rates. Ask your provider directly: what percentage of tickets in each category are resolved through automated means? What is the trend over the past 12 to 24 months? Providers who are genuinely delivering AI-driven efficiency should be able to answer this question with data.

Restructure pricing around outcomes, not inputs. Fixed-fee contracts based on system size or user count were designed for a world where service delivery cost was proportional to those inputs. In an automated environment, they are not. Push for pricing models that include efficiency sharing — where automation-driven cost reductions are reflected in contract pricing.

Benchmark against the market. The managed services market has become more competitive, and pricing benchmarks have shifted. If your contract was last renegotiated more than two years ago, there is a meaningful probability that you are paying above-market rates for a service that has become less expensive to deliver.

Audit the actual ticket mix. Before your next renewal, conduct a detailed analysis of your ticket volume by category, resolution method, and time-to-resolve. This data is the foundation of any credible renegotiation. Providers who resist providing it are telling you something important.

Separate commodity support from strategic advisory. Routine ticket resolution and system monitoring are increasingly commodity services. Strategic SAP advisory — architecture decisions, upgrade planning, integration design — is not. Consider whether your current contract structure appropriately distinguishes between the two, and whether you are paying strategic rates for commodity work.

The managed services paradox is a specific instance of a broader dynamic that executives should be alert to across their technology vendor relationships: the gap between how a service was priced when the contract was signed and how it is actually being delivered today.

AI is compressing the cost of delivering a wide range of technology services. The organizations that benefit from that compression will be the ones that actively renegotiate their commercial relationships to reflect it — not the ones that allow legacy pricing structures to persist by default.

Your managed services provider is not going to initiate that conversation. That is your job — or the job of an advisor who is working for you, not for them.

If you are approaching a managed services renewal and want an independent assessment of your contract terms and market positioning, contact a partner directly. No salespeople. No intake queues.