Announcing o11's backing from Y Combinator.

AI for SAP

AI that operates the launchpad.

  • Cut friction in repetitive launchpad tasks.
  • Move from request to action inside the system.

My Home

Run the launchpad

Add a new "Approve POs" tile to my home and pin it to the top.

Reasoning

I'll add the Approve POs tile under My Home with the open count from the workflow inb

o11 for SAP Fiori: an AI execution layer for ERP workflows

o11 acts inside the SAP Fiori launchpad. The agent navigates SAP, completes the same workflows your team runs through tiles and apps every day, and stays inside the security model your IT team has already approved. That makes the launchpad something a procurement, finance, or sales operator can drive with intent instead of clicks.

If you have searched for AI for SAP, an SAP AI agent, or a layer beyond Joule for the screens your team actually uses, the missing piece is execution depth. Joule answers questions about your data. o11 also runs the workflow.

What teams use o11 for in SAP

  • Procurement. Open and close purchase orders, manage supplier evaluations, and clear blocked invoices through Fiori without retraining the team.
  • Finance. Process journal entries, reconcile accounts, and clear open items inside the existing transaction codes.
  • Sales operations. Update sales orders, manage credit holds, and follow up on shipment exceptions without bouncing across screens.
  • Reporting. Pull KPI tile data and turn it into the slide or the email that the executive actually sees.

Why this matters for ERP buyers

ERP rollouts are heavy. The cost is rarely the software; it is the change management, the training, and the friction of the daily workflow. o11 lowers that friction by making the existing Fiori apps feel like something a person can operate with intent. The team does not have to learn another tool — they keep using SAP, and they get a workflow agent on top of it.

Cross-system fit

SAP is the system of record for the business, but the work product usually ships outside it: a board deck, a procurement memo, a finance close package, an audit response. o11 sits across SAP, Office, Workspace, and the rest of the operational stack so that data inside SAP becomes the deliverable outside SAP without a manual export step.

Where SAP teams typically start with o11

  • Procurement and supply chain with PO management and supplier reviews.
  • Finance and controllership with month-end close and reconciliations.
  • Sales operations with order management and credit holds.
  • Internal audit with controls testing and exception reporting.

How o11 respects SAP authorizations

The agent runs through the user’s own session. SAP authorization objects, role assignments, and segregation-of-duties controls apply exactly as they do in the UI. The agent cannot do what the user cannot do. That is what makes o11 deployable in SAP environments where compliance and audit readiness drive every decision.

FAQ

Why does SAP matter here?

Broadens retrieval handles and the agent-layer story.

Only for SAP customers?

No. Shows o11 works in operational systems too.