# Agents and packaged applications

Most processes run inside packaged software you cannot rewrite. Two tests decide whether to wait for the vendor's agent, buy it, or build a thin one.

Author: Murali Sid (https://linkedin.com/in/muralisid)
Source: https://www.agenticarchitectureskills.com/use-cases/packaged-applications
Published: 2026-10-14
Updated: 2026-10-15
Licence: CC BY-SA 4.0, https://creativecommons.org/licenses/by-sa/4.0/
Cite as: Murali Sid. Agents and packaged applications. Agentic Architecture Skills. https://www.agenticarchitectureskills.com/use-cases/packaged-applications

---


Most of the processes an enterprise wants to automate run inside packaged software it cannot rewrite. Billing, finance, asset and field systems are bought, not written. So the question is not only whether to build an agent. It is also whether the vendor will ship one for your edition, and when. Two tests answer it. Is the process inside one package or across several? Is a vendor agent generally available on your edition, or dated within two quarters? Inside one package, with a vendor agent available or dated, wait or buy. Across packages, or on an excluded edition, build a thin agent of your own.

## The two tests [#the-two-tests]

Two questions come first. Does the work need an agent at all, or will ordinary code do? Can its result be judged? [Choose where to start](/use-cases/choose-where-to-start) covers both.

<TeachingIllustration src="/figures/use-cases/packaged-applications-tests.svg" mobileSrc="/figures/use-cases/packaged-applications-tests-mobile.svg" title="Two tests: wait, buy or build thin" alt="A decision flow. Does it need an agent? If not, use ordinary code. Can it be evaluated? If not, prepare first. Then come the two tests. Is the process inside one package? Is a vendor agent generally available on your edition, or dated within two quarters? If yes, wait or buy. With vendor agents in several packages, use and govern them. Otherwise build thin. Every agent then gets an impact score on the risk profile and a portfolio score." caption="Wait for a vendor only when a dated agent exists for your edition. Build thin where the work crosses packages." />

1. **Is the process inside one package or across several?** Inside one package, the vendor holds the data and the permissions, and is likely to ship an agent. Across several packages, no vendor agent covers the whole job.
2. **Is a vendor agent generally available on your edition, or dated within two quarters?** Generally available means any customer can buy it and run it in production. Count only agents marked that way in release notes. Treat an announced agent as unavailable. Check the price after any free period ends.

## Wait, buy or build thin [#wait-buy-or-build-thin]

| Outcome        | When it applies                                                                   | What you do                                                                                                      |
| -------------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Wait or buy    | One package, a supported edition, an agent available or dated within two quarters | Use the vendor's agent. Register it. Check the date each quarter.                                                |
| Build thin     | Across packages, an excluded edition, or nothing dated                            | Build a small agent that works through governed <Term k="api">APIs</Term>. Leave each package's rules inside it. |
| Use and govern | You use vendor agents in several packages                                         | Use them. Own the interface inventory, the business definitions, the registry and the policy.                    |
| Not an agent   | The work does not need an agent                                                   | Use ordinary code, a fixed workflow or plain search.                                                             |
| Prepare first  | The result cannot be judged, or the data or interfaces are not ready              | Fund the definition of success, the data and the interfaces first.                                               |

Thin means small and easy to retire. The agent keeps no business rules of its own. When a vendor agent later covers the job, you switch yours off. The interfaces and definitions stay.

Then treat every agent the same, bought or built. Answer [the four questions](/architecture/agent-types) for it. Score its <Term k="impact">impact</Term>, meaning what it can damage, on [the risk profile](/architecture/risk-profile). Check which [deterministic zones](/architecture/deterministic-zones) it touches. A bill change is a money action, whoever built the agent. Then score it for [the use-case portfolio](/library/frameworks/use-case-portfolio).

## Where vendor agents are today [#where-vendor-agents-are-today]

As of 14 October 2026, every large package vendor sells agents. Most need the vendor's cloud edition. Oracle's agents are not coming to E-Business Suite, JD Edwards, PeopleSoft or Hyperion. Prices are still moving. Dates slip. An SAP billing agent for utilities moved from Q2 to Q3 2026 between two articles \[vendor]. No vendor publishes how many of its agents run in production.

## A worked example: a utility's packaged systems [#a-worked-example-a-utilitys-packaged-systems]

Take a typical electricity or water utility. [The utilities page](/use-cases/utilities) shows its full estate, layer by layer, as do [healthcare](/use-cases/healthcare) and [energy](/use-cases/energy). The table below picks out its packaged systems.

<TeachingIllustration src="/figures/use-cases/packaged-applications-estate.svg" mobileSrc="/figures/use-cases/packaged-applications-estate-mobile.svg" title="Where agents land in a packaged-application estate" alt="Seven packaged systems in a utility estate, badged with what vendors ship as of 14 October 2026. Generally available vendor agents exist for BI, portals, integration, grid systems and SAP billing self-service. SAP billing exceptions, SAP's MCP Gateway and Microsoft scheduling are planned but not confirmed. Nothing was found for GIS, asset registers or Oracle billing. A band marks the join across billing, outage, GIS and field. A strip at the base lists what you own: the interface inventory, business definitions, agent registry and gateway policy." caption="Vendors cover most single systems. The join across systems is the place to build." />

| System, and its layer                                                                                                                  | What vendors ship, dated                                                                                                                               | What to do                                                                                                          |
| -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| Billing (SAP IS-U or S/4HANA Utilities, Oracle Customer Care and Billing), in [systems of record (R04)](/layers/r04-systems-of-record) | SAP self-service agent live since Q4 2025 \[vendor]. Billing-exception agents planned for Q2 to Q3 2026, not confirmed. No Oracle billing agent found. | Cloud editions: wait. Older IS-U: build thin over the exception worklists. A named person approves any bill change. |
| SCADA and ADMS, the grid control systems, in [line of business and OT (R05)](/layers/r05-lob-and-ot)                                   | Schneider Electric Grid AI Assistant, 4 June 2026: operational actions stay subject to user review \[vendor].                                          | Use the vendor's assistant. Build only on the read-only information path.                                           |
| GIS maps and asset registers, in systems of record (R04)                                                                               | None found.                                                                                                                                            | Build. Matching asset, GIS and field records crosses packages.                                                      |
| Mobile workforce, in line of business and OT (R05)                                                                                     | Microsoft scheduling agent slated for April to September 2026 \[vendor].                                                                               | Use the vendor's scheduling. Build search across procedures and asset history.                                      |
| Integration and APIs, in [integration fabric (R03)](/layers/r03-integration-fabric)                                                    | MuleSoft Agent Fabric, September 2025 \[vendor]. Sources conflict on whether SAP's MCP Gateway is generally available.                                 | No new bus. Govern the interfaces agents may use. SAP PI/PO mainstream support ends in 2027.                        |
| Portals, in [experience and channels (R09)](/layers/r09-experience-and-channels)                                                       | Kraken agents live at one unnamed utility on about 1.3 million accounts, June 2026 \[vendor].                                                          | Vendor agent inside one system. Build for journeys across billing, outage and field.                                |
| BI (reporting), in [data platform (R02)](/layers/r02-data-platform)                                                                    | Databricks Genie generally available 12 June 2025 \[vendor].                                                                                           | Use the vendor's agent. Invest in business definitions and read-only database roles.                                |

No measured result exists yet for an agent inside either billing system, or for a portal agent an enterprise built. The one measured result on the [line of business and OT](/layers/r05-lob-and-ot) page is for the asset-data work. No utility found lets an AI agent operate protection or switching.

Take an outage. Billing knows who is affected, the outage system what failed, GIS where, and the field system who is coming. A customer message and a work order need all four. No single vendor's agent sees all four today. That join is the strongest place to build. Gartner expects agent networks across applications only in 2028 (as reported 27 August 2025).

## What to own whatever you buy [#what-to-own-whatever-you-buy]

Four things stay yours whichever agents you run. They also make each vendor agent easier to replace.

* **Interface inventory.** List every interface between systems, with its owner and purpose. Retire dead flows. Decide which ones become agent tools.
* **Business definitions.** Keep one set of business definitions under every reporting agent, often called a <Term k="semantic layer">semantic layer</Term>.
* **Agent registry.** Keep one <Term k="registry">registry</Term> of <Term k="vendor-embedded agent">your own agents and vendor-embedded agents</Term>. Agents you build run through your gateway. Vendor-embedded agents run on the vendor's platform, and you govern them through its settings. Several vendors offer to hold this list \[vendor]. It must hold other vendors' agents too. [The agent lifecycle](/architecture/agent-lifecycle) lists the record's fields.
* **Policy at the gateway.** Put access and approval rules at your own <Term k="gateway">tool gateway</Term> and <Term k="policy decision point">policy decision point</Term>, not inside each vendor's agent. Then a change of vendor does not change the rules.

## Evidence and limits [#evidence-and-limits]

The evidence does not settle wait versus build. The case against building on middleware, portals and reporting rests on documented problems. Poor data limits any agent, as SAP's chief executive said in May 2026 \[vendor]. Old systems lack modern APIs and secure identity (Deloitte, 10 December 2025). Vendors are building into the same places (SAPinsider, 13 August 2026). The case against waiting rests on dated facts about editions, prices and slipping dates. Lock-in is analyst opinion (Futurum, 12 June 2026).

The sources stop short in several places. No named custom agent was found that a vendor feature later replaced. No measured outcome exists for a portal, middleware or reporting agent an enterprise built. No published framework found asks either test. Microsoft's Cloud Adoption Framework comes closest (updated 2 June 2026) \[vendor]. The two tests and the two-quarter window are a proposal, not yet tested against results.

## Next step [#next-step]

Put a value and a full cost on the agent on [measure value and full cost](/use-cases/value-and-investment).

<details>
  <summary>
    Explore this topic
  </summary>

  **Vendor status as of 14 October 2026.**

  * **SAP.** Over 30 agents and 2,500 Joule skills (14 April 2026) \[vendor]. AI tied to cloud editions or a committed migration. Joule Studio free only through 2026. No general availability date for the "Autonomous Suite" (12 May 2026) \[vendor].
  * **Oracle.** 1,000-plus prebuilt agents (Forrester, 8 May 2026) \[vendor]. They need the Fusion cloud applications. Renewal pricing unresolved.
  * **Salesforce.** Agentforce annual recurring revenue of USD 1.2 billion, quarter to 30 April 2026 \[vendor]. Pricing moved from USD 2 per conversation to per-action credits.
  * **Microsoft.** Dynamics 365 agents slated for April to September 2026 (18 March 2026) \[vendor].
  * **Registries.** SAP, ServiceNow, Workday, Microsoft and MuleSoft each offer to list other vendors' agents \[vendor]. Workday's registry is not confirmed as generally available.

  **Gaps.** Gartner's notes were seen only as abstracts. No source was found for Oracle's utilities agents, or for a per-agent list of what shipped at Sapphire 2026.

  **Sources.**

  * [SAP News, AI release highlights Q1 2026](https://news.sap.com/2026/04/sap-business-ai-release-highlights-q1-2026/), 14 April 2026 \[vendor]
  * [CIO.com, SAP at Sapphire 2026](https://cio.com/article/4170465/saps-biggest-ai-bet-yet-agents-that-execute-not-just-assist.html), 12 May 2026
  * [ERP Today, Sapphire 2026 keynote](https://erp.today/will-sap-be-a-software-company-in-the-future-sapphire-2026-keynote-maps-saps-new-erp-stack/), May 2026
  * [SAPinsider, after Sapphire 2026](https://sapinsider.org/articles/sapphire-2026-your-sap-erp-just-got-an-ai-brain-now-what-seven-questions-every-leader-must-answer/), 15 May 2026
  * [SAPinsider, Integration Suite](https://sapinsider.org/articles/inside-the-enhanced-edition-what-saps-integration-suite-shift-means-for-the-autonomous-enterprise/), 13 August 2026
  * [SAP Architecture Center, MCP Gateway](https://architecture.learning.sap.com/docs/ref-arch/d2e34e), read October 2026 \[vendor]
  * [ASUG, Joule for utilities](https://www.asug.com/insights/sap-positions-joule-as-a-process-native-copilot-for-the-utilities-value-chain), 21 January 2026 \[vendor]
  * [ASUG, SAP agents for meter-to-cash](https://www.asug.com/insights/sap-bets-on-ai-agents-to-tame-utilities-most-complex-workflow), 27 May 2026 \[vendor]
  * [Futurum, SAP Joule in support](https://futurumgroup.com/insights/saps-joule-bets-on-agentic-ai-to-redefine-enterprise-support-will-customers-buy-in/), 12 June 2026
  * [Forrester, Oracle analyst summit](https://www.forrester.com/blogs/oracle-applications-analyst-summit-fusion-agents-are-shifting-from-assist-to-decide/), 8 May 2026
  * [Salesforce, Q1 fiscal 2027 results](https://salesforce.com/news/press-releases/2026/05/27/fy27-q1-earnings), 27 May 2026 \[vendor]
  * [Constellation Research, Agentforce launch pricing](https://www.constellationr.com/insights/news/salesforce-push-ai-agents-agentic-ai-overload-looms), 15 September 2024
  * [Redress Compliance, Agentforce pricing](https://www.redresscompliance.com/salesforce-agentforce-pricing-evolution-2026.html), 2026, a firm that sells licence advice
  * [Microsoft, Dynamics 365 release wave 1](https://www.microsoft.com/en-us/dynamics-365/blog/?p=201384), 18 March 2026 \[vendor]
  * [diginomica, ServiceNow Knowledge 2026](https://diginomica.com/servicenow-knowledge-2026-ai-control-tower-expands-autonomous-workforce-reaches-every-function-and), 5 May 2026
  * [Workday, agent system of record](https://blog.workday.com/en-us/managing-ai-powered-future-of-work.html), undated \[vendor]
  * [CIO.com, MuleSoft Agent Fabric](https://www.cio.com/article/4063090/mulesoft-launches-agent-fabric-to-tackle-agent-sprawl-and-unify-enterprise-ai-workflows.html), September 2025
  * [Microsoft Cloud Adoption Framework, AI agents](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ai-agents/business-strategy-plan), updated 2 June 2026 \[vendor]
  * [Deloitte, Tech Trends 2026](https://www.deloitte.com/us/en/insights/topics/technology-management/tech-trends/2026/agentic-ai-strategy.html), 10 December 2025
  * [Gartner, build versus buy](https://www.gartner.com/en/documents/8252458) and [a second note](https://www.gartner.com/en/documents/8145229), July and August 2026, abstracts only
  * [IT Brief Australia, Gartner forecast](https://itbrief.com.au/story/ai-agents-to-power-40-of-enterprise-apps-by-2026-says-gartner), 27 August 2025
  * [Databricks, Genie generally available](https://www.databricks.com/en/blog/aibi-genie-now-generally-available), 12 June 2025 \[vendor]
  * [Pulse2, Kraken agents with Sierra](https://pulse2.com/kraken-launches-autonomous-agents-with-sierra-to-transform-utility-customer-service/), 12 June 2026 \[vendor]
  * [Eurelectric, Schneider Electric Grid AI Assistant](https://www.eurelectric.org/stories/schneider-electric-grid-ai-assistant-for-advanced-distribution-management-system-adms-operations/), 4 June 2026 \[vendor]
</details>