An agent asks
Reconcile March supplier invoices
Agent teams are part of your company’s agent layer, and people are in the team. The owner sets the goals, people review and decide, and agents do the work under the same rules. One agent is a demo; a team is a workforce: a lead that plans, specialists that own an area, reviewers that check work they did not write, and workers brought in for one task. How the team works is a harness strategy you install and version like code. No agent grades its own homework, and every step is in the audit log. Use the strategies we ship, shape them, or build your own.
A team is
Your first process connects the systems it needs and sets its rules. Every process after it starts from there: the same sign-in and roles, the same approvals and audit, the same agents and connections. Each team builds only what is new.
Reuse never widens access. Each team, person and agent reaches a shared connection only within its own permissions.
One platform, many teams
What each new process starts with
Supplier management
Built with the first process
Identity, approvals, audit and agent execution come with the platform, and the connections your organisation has already made are reused. Your team builds the supplier rules and the screens. Your team builds the business; Xema is the foundation.
An authorised coding agent can build on the same foundation: it creates and extends applications inside the permissions you set. People and agents work on the same platform — delegating, coordinating and approving work under the same rules.
A new application
Supplier management
A customer asks to move a delivery date and correct the invoice. The CRM knows the order, the ERP knows the stock, Finance owns the invoice. Each system stays the system of record: your ERP stays your ERP.
Xema coordinates the work and the rules across them, including agents and automations from different vendors.
A customer asks
Move delivery to 14 March and correct the invoice
passed: Done — each system kept its own record
A support agent finds a duplicate charge and asks to refund it. Xema checks what the agent may do and what the person it acts for may do. Refunds above €10,000 need Finance, so the work waits for the controller, and runs once she approves.
The AI can start the work. It cannot go around your rules.
An agent asks
Refund invoice INV-2291 · €18,400
A model, an MCP server or another vendor’s agent sits behind a capability you defined, so you can switch it without touching processes, permissions or connections.
Start with external services, move to your own models on your own servers, or run with no network at all. The architecture is the same at every stage.
Agents ask for a lane, never a model. Planner, coder, review, light: your organisation maps each lane to a model in one place. Swap a model for every agent with one config change, and bring your own provider keys.
You change the AI
Processes, permissions and connections stay
The agentic layer under all your agents: permissions, approvals and audit that stay the same whichever runtime and model do the work. The eight questions every team asks before agents reach production, answered in one place, with room to bring or build your own runtime.
What it covers
Your teams work on the business. The rest is already done.
Each is something a team builds and runs on Xema, connected to the systems the work already lives in, with a person answering where the decision matters.
Finance
Bank, suppliers and ledger reconciled, anomalies sent to the controller, and nothing posted without sign-off.
Read moreCustomer support
A duplicate charge is confirmed, refunded in billing after approval, and the customer is told.
Read moreContracts & legal
Every clause checked against your standards; counsel approves only the deviations.
Read morePeople & IT
Access granted by role on day one, sensitive systems approved by a manager, everything revoked on the last day.
Read moreEngineering
A ticket is planned, coded in a sandbox and reviewed against your secure-coding skill. The tech lead approves before release.
Read moreOperations
An agent recommends a maintenance window from live data. A supervisor approves the crew booking, the team hears in Teams or Slack, and every refusal is audited.
Read morePutting AI to work at the core of your business is part product, part programme. Xema is yours to run, and our team works alongside yours until the first process is live and your people own it.
Platform
The foundation your solutions run on, yours to operate.
Partnership
We scope the first process with you, build it with you, and hand it over.
We work with a small number of teams each quarter. We take one real process, connect the systems it touches, and put it live under your own approvals. The next process reuses what the first one built, and anything you build on top, an app, an agent or a whole team, starts from the same foundation. One agentic platform for the whole company, and a foundation to build anything on, your own way.
How it goes
Same platform the whole way.
Get a demoAlready have access? Sign in