SAP AMS pricing models explained: ticket-based, fixed capacity and outcome-based
What you are actually buying
SAP AMS covers incident resolution, small changes, enhancements, statutory updates, monitoring and, increasingly, continuous improvement. How it is priced shapes how your partner behaves, so the model matters as much as the rate.
Ticket-based pricing
You pay per incident or service request, often by priority. It is simple and transparent when volumes are low and predictable.
- Works well for: stable systems with few changes.
- Watch out for: no incentive to remove the root cause of recurring tickets.
Fixed monthly capacity
You buy a block of consultant hours or a team each month, with service levels on response and resolution. Unused hours can often be redirected to enhancements.
- Works well for: mid-size companies with a mix of support and improvement work.
- Watch out for: make sure monthly reports show where every hour went.
Outcome-based pricing
Fees are linked to agreed results, such as availability, backlog reduction or business KPIs.
- Works well for: mature landscapes with good baselines.
- Watch out for: outcomes need clear, measurable definitions both sides accept.
Questions to ask any AMS partner
- Which SAP versions and modules do you cover, including SAP Cloud ERP, Private and SAP Cloud ERP?
- How do you reduce ticket volumes over time?
- How is AI used in triage and resolution?
- What happens to unused capacity?
- How long does transition take, and what do you need from us?
Our approach
Most of our clients choose a fixed monthly capacity sized after a short review of their tickets, then move part of it to improvements once the backlog is under control. See SAP AMS.
