Choosing an SAP AMS partner — questions that discriminate
Most AMS proposals look identical. Nine questions that separate a support service that improves your landscape from one that just closes tickets.
Written by APx Technology
Application managed services proposals converge on the same shape: tiered support, SLA table, monthly reporting, continuous improvement. Comparing them on price is tempting because the content looks interchangeable.
These questions produce answers that differ.
1. What proportion of your incidents are repeats?
The single most revealing metric, and most providers do not track it.
A service optimising for closure speed will resolve the same recurring incident promptly every month and report excellent SLA attainment while the business loses the same two days each cycle.
Ask for the repeat rate across their existing accounts, and ask whether it is trending down. An evasive answer here is informative.
2. Who will actually be on our account, and for how long?
SAP support only becomes good when the consultant already knows why your intercompany process is configured that way and which interface is fragile at quarter-end. That takes months and evaporates when people rotate.
Ask for named people, their experience, and what the provider’s retention actually looks like. “A pool of certified consultants” means nobody will learn your system.
3. What happens in the first ninety days?
A good transition has a stabilisation phase: backlog clearance, recurring incident analysis, documentation gap closure. A provider planning to go straight to steady-state has not thought about transition.
4. How do you handle change versus incident?
Many organisations find their AMS contract covers incidents well and enhancements badly, so every small improvement becomes a separate commercial conversation. Ask exactly where the line sits and what happens to work on the other side of it.
5. What does your monthly report contain?
Volume and SLA attainment are table stakes and tell you little. The useful report includes recurring themes, root causes eliminated, the improvement backlog, and system health trending.
Ask for an anonymised example. If it is three charts, that is the service.
6. What are your coverage hours, really?
Not the headline. What happens at 11pm during month-end close? Who answers during a cutover weekend? What is the escalation path at 3am and who holds the phone?
7. How do we exit?
A provider confident in their service will have a clean, documented exit with a knowledge transfer period and full runbook handover. Reluctance here tells you they expect to retain you through switching cost rather than quality.
8. Will you work alongside our internal team?
Most organisations keep some capability in-house. The split has to be explicit — who holds first line, who owns the business relationship, where the boundary sits on a shared incident — or every ambiguous ticket becomes a dispute.
9. What would you want to fix first?
Ask this at the end, after they have seen your landscape.
A provider who has paid attention will name something specific and probably slightly uncomfortable. A provider who answers in generalities has been reading from a deck.
What good looks like
Named people who stay. Repeat incidents tracked and falling. A transition plan with a stabilisation phase. Reporting that drives decisions. A clean exit nobody expects to use.
None of it is exotic. It is just rarer than the proposals suggest.