From Buying AI Capabilities to Continuing Operational Improvement
Image source: Infor
Infor’s Velocity conference splashed the new motto “Industry Forward” and shifted Infor’s pitch from “buy our AI capabilities” toward “subscribe to continuing operational improvement.” My esteemed colleague Shashi Bellamkonda already provided an overview of the conference news – please, see Infor Turns Industry Process Knowledge Into an AI Advantage. This article provides critical review of the news identifying the most differentiating capabilities, how they may change (if at all) Infor’s position on the market, and what deserves buyers’ and existing customers’ attention.
Most Differentiating News and Offerings
Continuing delivery within the subscription. The inclusion of Forward Deployed Engineer pods is the most meaningful commercial development. Infor combines software, a prebuilt use-case catalog, and engineering capacity to adapt capabilities to customer requirements. Industry templates provide a starting point; customer policies, configurations, and exceptions still require implementation work. Embedded engineers could help close the gap between available AI capabilities and production results.
Business context connected to executable processes. Infor IQ combines product-level “micro-ontologies” and ecosystem-level “macro-ontologies” with process catalogs, a knowledge graph, a semantic layer, and APIs exposed through Model Context Protocol (MCP). The potential value lies in carrying business meaning and constraints through to the execution.
For example, resolving an inventory shortage requires more than knowing quantities on hand. An agent must consider delivery commitments, existing allocations, customer priorities, and alternative routes before reallocating goods. Connecting those considerations to executable business operations could reduce orchestration complexity and improve decision quality.
More explicit interoperability and governance. Infor describes external assistants and orchestrators as entry points into its operational capabilities. Its governance approach includes agent registration, named human owners, time-bound and task-specific access, and audit records. These mechanisms make the proposition more concrete, although their availability and effectiveness require validation in each customer’s environment.
Together, these developments strengthen Infor’s case for combining industry context, governed execution, and continuing implementation support. The differentiation depends on how consistently it delivers that combination.
Comparison with competition
Industry semantics, embedded agents, and governance are becoming common features across ERP platforms. Infor’s strongest competitive argument is therefore the implementation effort and operating cost required to achieve comparable outcomes.
| Competitor | How Infor’s proposition compares | What determines the advantage |
| SAP | SAP also combines business semantics, knowledge graphs, process intelligence, and agents. Its use of forward-deployed engineering teams weakens claims that customer co-innovation is unique to Infor. | Infor must demonstrate easier adoption, stronger fit for selected industries, and more predictable delivery economics. |
| Oracle | Oracle includes embedded AI and AI Agent Studio with Fusion subscriptions, making bundled AI tooling a limited differentiator. Infor adds a more explicit continuing engineering proposition. | Compare the full cost of implementing and maintaining equivalent workflows, including custom agents and external integrations. |
| Microsoft | Dynamics 365 agents and Copilot Studio offer extensive building and integration capabilities. Infor presents a more prescribed industry solution with continuing delivery support. | Infor is attractive where buyers prioritize industry fit and vendor accountability; Microsoft is attractive where broader platform flexibility matters most. |
| Epicor | Epicor also targets industry-specific, governed agents operating within ERP. Infor adds a shared-context architecture and an explicit continuing delivery model. | Buyers should compare supported workflows, exception handling, implementation effort, and measurable results in their industry. |
Infor’s flat-fee positioning may improve cost predictability, but it does not establish lower total cost. Competitors combine included capabilities, consumption charges, and separately priced customization in different ways. A meaningful comparison requires equivalent workflow scope and service commitments.
Interoperability also creates room for coexistence. An external assistant such as Copilot could provide the interface while Infor supplies business context and transaction execution. Customers should test how well permissions, definitions, and accountability survive that arrangement.
What CIOs should be watching out for
Contractual meaning of “unlimited.” Define fair-business-use limits, engineering allocation, supported environments, external integrations, maintenance responsibilities, and renewal terms. A predictable subscription fee does not automatically make implementation costs predictable.
Availability in the relevant CloudSuite. Separate demonstrated capabilities, generally available functionality, and roadmap commitments. Require written confirmation for the applications and regions in scope. Rapid deployment of a selected AI workflow should not be interpreted as an ERP migration timeline.
Engineering capacity and ownership. Clarify how pods are assigned, how competing requests are prioritized, and who maintains customer-specific agents. Establish ownership of configurations and intellectual property, along with what happens if the subscription or engineering engagement ends.
Cross-system semantics and data readiness. An ecosystem ontology does not by itself reconcile conflicting customer, product, or location definitions. Test mappings to external applications and existing semantic layers. Poor master data, undocumented processes, and extensive customization will constrain results.
Controls through transaction execution. Require visibility into the sources, rules, calculations, and permissions behind agent actions. Test segregation of duties across cooperating agents, approval thresholds, exception handling, and recovery from incorrect transactions. Auditability supports accountability; decision accuracy needs separate validation.
Timelines. The under-four-week deployment likely applies only to selected AI use cases. The nine-to-twelve-month target for full CloudSuite implementation (possibly shorter) looks like an evolving ambition. Don’t confuse rapid delivery of one AI workflow with an ERP migration timeline.
Evidence of sustained value. Treat headline “up to” improvements as scenarios to investigate. Seek comparable customer references and measure results against an operational baseline, including cycle time, errors, working capital, and the effort needed to review or correct outputs.
Our Take
Infor’s announcement is a coherent consolidation of its AI story rather than a technical breakthrough. Its four pillars (industry-specific agents, open architecture, adaptive UX, built-in governance) mirror where the ERP market is heading, and SAP, Oracle, Microsoft, and Epicor have all introduced agent studios, embedded agents, and governance layers. Architecture alone does not separate vendors.
What is distinctive is the pairing of deep industry focus with a single-subscription model and embedded engineering support. Infor’s most meaningful move is folding continuing delivery into the subscription. This addresses a real barrier: organizations often stall between AI experimentation and measurable value, and Infor’s own survey points to a gap between investment and efficiency gains. If the model delivers, it lowers procurement friction and shortens time to value in Infor’s focus industries. However, for this to happen, Infor must ensure it can scale their engineering support in case too many of their customers take them up on this offer.
We expect the strongest near-term impact among existing CloudSuite customers, where Infor can build on established applications and process knowledge. It also strengthens the cloud-migration argument, although AI benefits alone rarely justify replacing an ERP.