Support pricing quietly shapes how your HR team behaves. Here's what to look for in any SuccessFactors AMS contract — and why we priced the meter out of ours.
Here is a question worth asking before you sign any SuccessFactors support contract: what behaviour does this pricing model create in my HR team?
It sounds abstract. It is anything but. The commercial structure of an AMS agreement determines, more than any SLA table, whether your team treats support as a resource or as a cost to be rationed. And rationing is where platforms quietly go wrong.
How the standard model works
Most AMS agreements are sold as a bucket of hours. You buy, say, 800 hours for the year. Every ticket — an incident, a configuration correction, even a “how do I run this report?” question — is logged, estimated, and drawn down against the bucket. When the bucket runs low, you either stop asking or buy more.
The logic seems fair on paper: you pay for what you use. But watch what happens in practice.
An HR executive notices a workflow routing approvals to a manager who left last month. Fixing it is a fifteen-minute ticket. But it’s November, the bucket is at 12%, and year-end compensation planning is coming. So she works around it — forwards the emails manually, keeps a note to raise it “when hours reset.” The workaround becomes habit. Six months later, an audit asks why approvals were bypassing the system of record.
Or a payroll officer isn’t sure how a new leave type interacts with the payroll integration. The safe move is to ask. But asking costs hours, so he makes his best guess. The guess is nearly right. Nearly.
None of this shows up in the AMS provider’s reporting. Ticket volumes look healthy. Response times are met. The bucket lasts the year. Meanwhile, the platform is accumulating small compromises — unfixed configuration, undocumented workarounds, questions that were never asked — and every one of them compounds.
Metered support doesn’t just charge for questions. It discourages them. And an HR team that stops asking questions is an HR team slowly losing command of its own system.
The second problem: who answers
There’s a staffing pattern that usually accompanies the hour-bucket model: the support queue is where the newest people learn the product. It makes sense for the provider — support tickets are lower-stakes training ground than implementations. It makes less sense for you, because diagnosis is where experience pays. A consultant who has configured the module fifty times reads a symptom and knows the cause. A consultant who hasn’t opens an investigation. Both bill the same hour; only one of those hours was worth it.
So when you evaluate an AMS provider, the two questions that matter most are commercial and human: what happens when I use the service a lot, and who exactly picks up the ticket.
What we did about it
When we designed Avyan’s AMS, we started from the behaviour we wanted to create: an HR team that asks everything, immediately, without a meter running in their heads.
That led us to a structure with two distinct parts. Business-as-usual support is unlimited, for a flat annual fee. Incidents, configuration corrections, permission changes, release management, and every “how do I” question your team can generate — none of it is metered, because we want you to ask. A question asked early is a fifteen-minute answer. The same question suppressed for six months is an incident.
Genuine new build sits in a defined enhancement pool — a set number of hours for new workflows, new modules, and structural changes, with unused hours rolling forward quarterly. This keeps the boundary honest in both directions: you’re never charged extra for using support as intended, and we’re never asked to smuggle a new implementation through the support queue.
And every ticket is answered by an experienced consultant — someone who has run implementations, not someone learning the product on your incident. That’s not generosity; it’s economics. Experienced diagnosis is faster, which is precisely what makes unlimited support sustainable for us to offer. The flat fee and the experienced staffing aren’t two separate promises. Each one is what makes the other possible.
A checklist for any AMS contract
Whoever you’re evaluating — including us — put these to them:
What happens when I exceed my hours? If there’s a bucket, understand exactly what your team will do in month eleven.
Is “how do I” support included, or only break-fix? Adoption questions are where platform value is won or lost.
Who answers the ticket, and what’s their experience level? Ask for it specifically, not for the firm’s average.
What proactive work is included? SAP ships releases twice a year. Someone should be assessing the impact on your configuration before it lands, not after. Health checks and release reviews should be in the base service, not billable extras.
Where does escalation actually end? A named person, reachable, in the contract.
Your SuccessFactors platform will be with you for a decade. The right AMS model is the one that keeps your team curious, confident, and in command of it for all ten years — not the one that teaches them to stop asking.
Avyan’s AMS is a flat annual fee with unlimited BAU support, a rolling enhancement pool, and experienced consultants on every ticket. If you’d like to see the full SLA grid, ask us — we publish it in every proposal.