SAP AMS: what it covers and what it costs
SAP application management services (AMS) are priced in five main ways: dedicated staff, time and materials, per ticket, a fixed pool of monthly hours, or outcome-based agreements. Which model suits you, and what you pay, depends on how many tickets you raise, how much custom code and integration you run, and how predictable you need the bill to be. AMS is separate from, and in addition to, the annual support fee you pay SAP.
AMS is not the same as SAP support
Many buyers assume their SAP support fee already covers day-to-day help. It does not.
| SAP support fee | SAP AMS | |
|---|---|---|
| Who provides it | SAP | Your own team or an AMS partner |
| What it covers | Bug fixes, security patches, legal updates and new releases for SAP's standard software | Your configuration, custom code, interfaces, user incidents and small changes |
| Typical cost | Typically around 22% of net licence value a year | Depends on the pricing model and volume of work |
Under RISE with SAP the picture is similar. SAP runs the infrastructure, but interfaces, custom jobs and incident handling stay with you or your AMS partner unless you buy SAP's packaged services for an extra fee.
What SAP AMS usually covers
- Incident management. Fixing errors and failures users report, within agreed response times.
- Small changes and enhancements. Configuration changes, new reports and minor developments.
- Monitoring. Watching jobs, interfaces and system health so problems are caught early.
- Basis and technical support. Transports, user access, patching and performance, if included in scope.
- Problem management. Finding and fixing the root cause of repeat incidents.
Always check which components the provider owns, such as Basis, ABAP development or interfaces, and which stay with your team. Anything outside the written scope usually becomes a change request.
The five common pricing models
| Model | How you pay | Best for | Watch out for |
|---|---|---|---|
| Dedicated team (FTE) | A fixed monthly cost per named person | Large, steady workloads | Paying for idle capacity in quiet months |
| Time and materials | Hours actually worked | Small or unpredictable workloads | Monthly cost moves, and every reprioritisation is billable |
| Per ticket | A fixed price per incident or request, often by severity | High volumes of similar tickets | Incentive to close tickets rather than fix root causes |
| Capacity pool | A fixed monthly fee for a set number of hours or days | Predictable budgets with mixed work | Unused hours may expire; overruns cost extra |
| Outcome-based | Fees tied to service levels or business results | Mature estates with good data | Needs clear, measurable targets agreed upfront |
Fixed-scope arrangements make annual planning easier, but price certainty only holds if you keep an accurate inventory of your applications and treat new integrations as contract changes.
What drives the cost
- Ticket volume and severity. More tickets, and more urgent ones, need more capacity.
- Custom code and interfaces. Heavily customised systems take longer to support.
- Coverage hours. 24/7 support costs far more than UK business hours.
- Hand-offs between teams. A 2026 HappySignals and ISG benchmark of 889,164 incidents found that a ticket passed between five teams costs about 8.5 more working hours than one fixed on first contact.
- Onshore or offshore delivery. Offshore rates are lower, but time zones and hand-offs can add effort.
A rough way to sense-check a quote
A capacity-pool AMS contract is essentially a number of consultant days each month. The median UK contract SAP consultant day rate is £550 (IT Jobs Watch, six months to 1 November 2026). As an illustration only, a pool of 10 days a month at that rate would be about £5,500 a month. Consultancy rates and the mix of skills will move the real figure, but this gives you a starting point for comparing quotes.
How to keep AMS costs down
- Fix repeat incidents at the root instead of paying to close the same ticket every month.
- Clean up unused custom code, especially before an S/4HANA migration.
- Agree a clear service catalogue so routine requests are priced in advance.
- Review ticket data every quarter and adjust the pool size to match real demand.
- Ask for metrics such as ticket ageing, repeat incidents and change failure rate, not just response times.
Frequently asked questions
Is AMS included in my SAP support fee?
No. SAP's support fee covers SAP's standard software. Support for your configuration, custom code, interfaces and users is AMS, provided by your own team or a partner.
What is the most common SAP AMS pricing model?
Common models are dedicated staff, time and materials, per ticket, a fixed pool of hours, and outcome-based agreements. A capacity pool is often a practical middle ground because it balances flexibility with a predictable monthly bill.
Does RISE with SAP include AMS?
Not by default. SAP runs the infrastructure, but application-level work such as interfaces and incident handling stays with you or your AMS partner unless you buy SAP's packaged services.
How can I reduce SAP support costs?
Fix repeat incidents at the root, remove unused custom code, define a clear service catalogue and size your support capacity to real ticket data.
SAP managed services from Liditech
Liditech provides SAP managed services and AMS for UK organisations, with a focus on reducing repeat incidents rather than just closing tickets. See our SAP managed services and SAP consultancy UK pages, read what SAP consultancy costs in the UK, or contact us.