Will AI agents replace packaged business software?

Which applications agents can replace, what still needs to remain, and how CIOs and CFOs can assess a credible business case.

Ersetzen KI-Agenten Standardsoftware?

English edition — originally published in German as Ersetzen KI-Agenten Standardsoftware?.

The next software decision may start with a task rather than a product demo: “Prepare this service contract for renewal, check outstanding work and show me what I need to decide.” An agent could gather information, compare terms and prepare the next steps. Employees would need to open several applications themselves less often.

Does that mean the agent replaces packaged business software? Partly, yes. It can take over interaction, coordination and individual applications. The underlying functions still need to work reliably. For CIOs and CFOs, the decisive question becomes: which capabilities do we keep buying, which do we connect differently, and what can we actually switch off?

:::takeaways{title="For the management decision"}

:::

Three layers, three different decisions

A business application combines several functions. It displays information, guides a process and handles authoritative business records. Agents can combine these layers differently. Separating them in an investment decision helps identify where replacement makes sense.

| Layer | What agents can change | |---|---| | Interaction | Employees state a goal and review results instead of navigating every dialogue themselves. | | Coordination | An agent connects information and permitted steps across several systems. | | Authoritative business functions | Data storage, calculations, transactions and permissions still require an implementation with an accountable owner. |

The system of record may remain packaged software. It may also be deliberately replaced. In that case, its required capabilities must be migrated, tested and operated. An agent that uses a system has not replaced its functions. The agent and its integrations are also software that needs maintenance.

The technical basis for these connections exists. The MCP tools specification describes how applications expose functions with defined inputs to models. That does not guarantee that every existing product makes the required functions accessible.

Where an application can actually disappear

A plausible candidate is a small add-on whose main purpose is gathering, comparing and preparing existing information. If a shared work layer takes over that process completely, the separate tool may become unnecessary. Its less visible capabilities must also be covered: saved templates, history, approvals, exports and exception handling.

Consider contract renewal as an illustrative example. Today, service data is exported, checked against open cases and assembled into a decision brief in another application. An agent could take over this preparation. The authoritative contract record and subsequent billing initially remain in their existing systems.

In this case, replacement concerns the additional preparation tool. The business systems gain a new way of being used. Both changes can be valuable, but they have different cost implications. An inventory must establish whether a contract can actually be cancelled or whether fewer people simply use an interface directly.

Agent, automation or an existing feature?

Not every task with several steps needs an agent. A clear process with stable rules may be easier to operate as conventional automation. An agent is particularly worth evaluating when the steps vary with the situation and unstructured information matters.

A technical discussion of agentic systems distinguishes predefined workflows from model-directed tool use. It also highlights additional cost and latency from greater complexity. The choice should therefore be measured against the specific outcome.

First check whether the existing business software already supports the process or can reasonably be extended. An embedded agent feature may simplify data access and interaction. An independent work layer becomes more interesting when the value comes specifically from connecting several systems. Building a complete replacement is another option, but requires a justified decision to take ownership of its functions and operations.

The AI cockpit changes the role of applications

Our article on the workplace of the future describes a shared work surface. In the related prototype work, we bring context, responsibility and the next action together. Demo data allows us to explore this design; it does not establish production integrations or measured savings.

The strategic perspective extends further. People could increasingly use software through its capabilities, rather than navigating the structure of individual applications. “Review contract” becomes the visible task. The systems supplying information and recording changes move into the background.

The interface must still show where information comes from and where an action takes effect. An accessible business process remains necessary when uncertainty arises. A shared work surface should reduce application switching while preserving the distinction between a draft, an approval and a binding business transaction.

A business case that separates licences and time

An attractive interface does not, by itself, justify replacement. Include the initial transition, ongoing operations, remaining licences and human rework. Check the terms for automated access as well: fewer direct users do not automatically permit a corresponding reduction in the contract.

:::callout{type="info"} Hypothetical annual example, not project results: A replaceable add-on costs CHF 18,000. The new agent solution requires CHF 30,000 annually for operations and support, plus a one-off CHF 40,000 implementation. It also frees 300 hours valued at an assumed CHF 80 each: CHF 24,000 of capacity. Under these assumptions, annual cash outflow increases by CHF 12,000; in the first year, including implementation, it increases by CHF 52,000. Available capacity is not an automatic cost reduction. :::

The initiative could still make sense if that capacity relieves a demonstrated bottleneck or enables additional output. The business team must identify exactly how it will be used. A proposal promising only licence savings would not be convincing under these assumptions. Cost per resolved AI case adds quality and ongoing effort to the assessment.

Start with a replacement you can verify

Choose a bounded process and document the baseline, handling time, rework and every function it uses. Then compare two realistic options: improving the existing system and introducing the proposed agent solution. Use the same representative cases, including exceptions.

Before cancelling a service, resolve data migration, history, exports, permissions and the fallback process. Define who will operate the new approach and what constitutes acceptance. If no application can ultimately be switched off, the project may still improve productivity. The investment proposal should describe that benefit accurately.

Which of your applications provides distinct business value, and which mainly organises handovers? We can assess a specific replacement candidate and the conditions for a sound business case with you.

Sources and interpretation

Reviewed: 29 October 2026. The linked primary sources establish technical capabilities and architectural distinctions. The layer model, replacement criteria and financial example are our editorial analysis. They do not predict the disappearance of a software category or establish savings across the board.