Application management services are usually bought around availability, response times, and cost. And they deliver what the contract asks for. Applications stay available, tickets are closed within the agreed time, and reports remain green. Yet, when renewal comes around, it can be difficult to point to anything that has improved. That is often the result of a contract that was designed to maintain the status quo.
The problem is that organizations often treat application management services spend as part of their technology strategy, even when the underlying contract has no clear mechanism for improvement. Availability is essential, but it is only the baseline. When it becomes the main objective, a major recurring technology expense has little reason to make the application estate better over time.
Why Availability-Only Application Management Services Cannot Produce Improvement
Service levels typically focus on incidents resolved, requests completed, and systems kept available. A provider working against those measures will naturally prioritize restoring service and closing tickets. There is little incentive to spend time removing the underlying causes of those incidents, especially when doing so could reduce the volume of work being measured.
The result is an estate that remains stable but does not necessarily become easier to manage or change. Requests take about the same amount of time. Releases carry similar risks. The same difficult integrations remain untouched because nobody is specifically responsible for fixing the structural problems behind them.
Where the Effort Actually Goes
MuleSoft’s 2026 Connectivity Benchmark Report, based on 1,050 IT leaders, found that the average organization runs 957 applications, with only 27% integrated. Its accompanying analysis also found that IT teams spend an average of 36% of their time designing, building, and testing custom integrations.
That represents a significant amount of IT capacity going into recurring work rather than creating new capability. Application management solutions could help reduce that structural burden, but most contracts do not create a reason to do so. The provider is paid to keep existing integrations working, not to reduce the number of bespoke integrations the organization depends on.
The Structural Change Application Management Solutions Need
A better approach is to reserve a defined share of the contracted capacity for improvement work and report it separately. A fifth can be a practical starting point, but the exact allocation matters less than making it explicit, protecting it, and measuring what it produces.
This changes the purpose of the contract. Part of the budget continues to protect day-to-day operations, while another part is used to make the estate better.
- Reserve the improvement allocation in the contract. State the percentage clearly and include a reporting requirement.
- Choose improvement work based on evidence. Look at repeat incidents, integration failures, and recurring requests that point to an unresolved underlying problem.
- Assign an owner to every improvement item. Each item should have someone responsible for delivering it and a clear expectation of what will change.
- Put improvement results at the top of the report. They should be visible alongside, or even ahead of, availability measures.
- Review the allocation quarterly. Senior stakeholders should be able to redirect capacity when the work is not addressing the right problems.
Track the measures that show whether the estate is improving. These can include standard request fulfilment time, release frequency, repeat incidents, and the number of bespoke integrations.
The sixth point is what makes the model measurable. If these measures remain unchanged over time, the improvement allocation may simply be maintenance under a different name. Application management service providers that are unwilling to report on this allocation also give you useful information about how they expect to use their capacity.
Why This Matters More with AI in the Delivery Chain
AI is increasing the pace at which software teams can make changes, but faster delivery does not automatically mean better delivery. DORA’s 2025 research found that higher AI adoption was associated with both increased delivery throughput and increased delivery instability. Its research describes AI as an amplifier. It can work well when platforms, APIs, and testing are strong, but it can also increase technical debt when the underlying tools and infrastructure are fragmented or fragile.
Managed application estates often contain exactly these weaknesses. Introducing AI-assisted development without improving test coverage and deployment safety can, therefore, increase the amount of change without improving the quality of that change.
The better division of responsibility is straightforward. AI can handle repetitive work, while engineers remain responsible for architecture, judgment, and review. When assessing a provider, ask what it has changed in testing, deployment, and rollback processes to support faster delivery. Simply asking whether the provider uses AI tools tells you much less.
The Cost Argument for Doing This
The cost of maintaining an application estate can accumulate without being obvious. Organizations continue paying for duplicate integrations, unused environments, and applications that remain active because nobody has been given the time or budget to retire them.
Seen this way, an improvement allocation is not necessarily additional spending. It is a way to use part of the existing application management services budget to reduce future costs. That makes the conversation easier to have with business and technology leaders.
What Should Stay in the Availability Half
This does not mean availability should become secondary. Incident response, request fulfilment, monitoring, patching, and access management still belong in the arrangement, and each needs clear service levels.
A system that is not reliably available leaves little room for improvement work. Likewise, a provider that focuses too heavily on change while allowing day-to-day service quality to decline simply creates a different problem.
The point is not to choose between availability and improvement. It is to give both a defined place in the contract and report on them separately.
Frequently Asked Questions
What Share of Capacity Should Go to Improvement?
A fifth is a reasonable starting point, but the exact percentage is less important than making the allocation explicit, protected, and measurable. Without a defined share, improvement work has to compete with business requests that already have visible sponsors and immediate deadlines. It usually loses that competition.
How Do We Measure Whether Application Management Solutions Are Adding Value?
Look beyond service levels. Track measures such as standard request fulfilment time, release frequency, repeat incident rates, and the number of bespoke integrations.
These measures show whether the application estate is actually becoming easier and safer to operate. If they remain unchanged, the service may be maintaining the estate without improving it.
Is It Cheaper to Bring Application Managed Services In-House?
Moving application managed services in-house can remove an external margin, but it also introduces coverage and skills risks, particularly when the application estate spans multiple technologies.
A hybrid model can work well for many organizations. Internal teams can retain ownership of priorities and business knowledge, while external teams provide additional capacity and specialist skills. Whatever model is chosen, the more important question is whether improvement is funded within it.
Will a Provider Agree to This Model?
Serious application management service providers should be able to work with a defined and reported improvement allocation. Some may resist because the model makes their use of capacity more visible.
That can be useful when selecting a provider. A company that is confident in its ability to improve the estate should have little reason to avoid measuring the work it performs.
What Should Application Management Consulting Services Assess First?
Application management consulting services should begin by examining where the team is currently spending its capacity. Review the last two quarters and group the work by category.
Many organizations have never looked at this breakdown in detail. It can reveal how much capacity is being consumed by recurring work that could potentially be eliminated through targeted improvements. That evidence can then support a change to the contract.
Availability is the foundation of any application management service. Improvement is what turns that service from ongoing preservation into something that creates additional value. For that to happen, the contract needs to reserve capacity for improvement and make the results visible.
Sign in to leave a comment.