The Application Management (AMS) contract you’ve been renewing for fifteen years is losing its rationale, and the cause is cost. Artificial intelligence has changed the price of building software and rendered obsolete the assumption that underpinned traditional AMS. In its place, another discipline is gaining ground: business process consulting. Renewing classic AMS in 2027 means paying for a service identical to that of 2020 while the market already operates on a different cost logic.
What business process consulting is
Business process consulting analyzes each of a company’s processes and decides, case by case, what the best way to handle it is among the available technology options. It looks at the actual process, not the legacy system, and applies three criteria at once: technical, economic and business-experience. Its output is a well-founded decision, with vendor neutrality.
The work starts with an end-to-end mapping of the process and ends in a recommendation backed by numbers. In between: mapping the current flow, diagnosing where the standard covers things well and where it falls short, modeling the cost of each alternative, and choosing the route. The decision may send a process to SAP, move it out to a custom application, replace it with an external service, or orchestrate it with AI agents.
The market has already priced in this shift
In January 2026, SAP’s stock fell about 15% in a single session — its largest daily drop since October 2020 — after its cloud revenue guidance for the year came in below market expectations (Reuters). Relative to its high over the prior twelve months, the stock had accumulated a decline of roughly 40%.
ServiceNow lost around 17% in April following its first-quarter results — its worst day on record — and from its all-time high it fell close to 55% by February. Salesforce dropped about a third in six months.
These declines aren’t cyclical noise. The market is testing a concrete hypothesis: when an AI agent executes on its own the tasks that used to require per-user licenses, the per-seat pricing model comes under pressure. Betting your entire operation today on a single vendor is a position Wall Street has begun to question by moving capital.
Building software is no longer expensive
The price of building software has collapsed. What used to take a SAP developer a week is now resolved in one or two days. Code generation, technical documentation, integration mapping: everything has accelerated by a factor of ten to a hundred. Pure technical skill, on its own, has ceased to be an advantage.
The consequence has two sides. When SAP’s standard covers a process well, building something on top of it loses its justification. When it falls short, there’s no longer any reason to tolerate it: today it’s viable, in time and cost, to stand up a cloud application that extends S/4HANA with the experience the business needs, without touching the core. Two years ago, those timelines and costs weren’t realistic.
From two options to six
Three years ago, the question “how do I solve this process?” had two realistic answers: solve it within SAP, through standard configuration or Z development, or buy specialized software. The rest existed only on paper. Building custom was expensive and slow, modernizing a legacy system was a multi-year project, integrating meant proprietary code, and AI agents weren’t there yet.
- Solve it within SAP. Standard configuration or Z development. Still the best answer when the process is generic and the standard covers it — though it’s no longer the automatic option.
- Specialized software. Best-in-class by category in CRM, HR, planning, logistics or pricing, with growing maturity.
- Custom cloud application. Viable today with AI and modern architectures, for the processes where the business truly competes and no standard does it justice.
- Modernize the legacy system. When what’s been built slows the operation but the business logic is still correct.
- Intelligent integration. Integration platforms (iPaaS), APIs and modern orchestration. The glue between systems is no longer proprietary code.
- AI agents as a cross-cutting layer. They enhance the other five and automate tasks that used to depend on per-user licenses.
The most common mistake comes before choosing: it’s sticking with the same old option without evaluating the other five.
How to choose: three criteria at once
The question is no longer “how do I configure SAP for this?” Now it’s “which of the six options fits this process?” And it’s answered using three dimensions of analysis at the same time.
Technical criterion. How well each option solves the problem, what technical debt it leaves, how it integrates with the rest of the systems, and how maintainable it remains five years out.
Economic criterion. What it costs to build, operate and evolve each option over three to five years. The real total cost of ownership, with licenses, infrastructure, talent and debt included. What frees up capital and what leaves it tied down.
Business experience. Which option gives the end user the experience the process demands, which one speeds up the cycle, and which one enables a competitive edge the others block.
No single dimension decides on its own. A cheaper option that generates technical debt ends up costing more. A technically elegant option that users don’t adopt solves nothing. The decision lives at the intersection of the three.
Why traditional AMS is no longer enough
An AMS set up as incident management resolves symptoms. Each closed ticket, however, is information about how the business operates: what the standard covers well, where it falls short, which critical processes are held together with temporary patches. That information exists in every AMS. In most, it’s discarded.
The AMS that makes sense today handles each incident twice. The first time resolves the user’s case within the service level agreement (SLA). The second asks whether the problem will recur and what prevents it from coming back. The first response is support. The second is continuous consulting. Without that second layer, tickets reproduce endlessly and the company pays twice: for the license and for the symptom.
What profile does this work
This service calls for a profile different from the classic SAP consultant. Someone who understands the process end to end, knows the six options in real depth, can model the economics of each, and answers to no vendor’s sales quota. Someone who can say “this stays in SAP,” “this moves out to a cloud application,” “this gets replaced by an external service,” “this gets orchestrated with agents” — and defend each decision with all three criteria at once.
That’s business process consulting. It works on the process, not the system. It’s technology-neutral. And it uses AI as part of the method, at every stage, from discovery to cost modeling.
What’s at stake over the next two years
Over the next two years, companies’ technology decisions are going to diverge far more than they did in the past decade. Those who evaluate case by case, with a process mindset and no vendor reflex, will operate with lighter systems that are easier to change and cheaper. Those who keep buying traditional AMS on the assumption that SAP solves everything will keep paying licenses for capabilities they no longer use and accumulating technical debt on processes that should have left the core years ago.
The first step isn’t to contract anything. It’s to take your five most expensive processes to operate and ask, for each one, which of the six options it corresponds to. That single conversation usually reveals where you’re overpaying.
Related notes:
