Back-office work, wired into what already runs.

Who it is for

An industrial operator, manufacturer, EPC, or plant with a back-office or production loop that still moves on paper, inbox, or re-keying — in the UAE, and elsewhere in the Gulf when the decision is named.

Buyer in the room: COO, head of operations, plant or quality lead. Not an innovation theatre. One constraint, then a written decision.

If the work is official Arabic correspondence in a ministry, that is Correspondence, not this page.

The workflow shape

One named loop per engagement. Typical shape, not a menu of products:

A work order. A quality exception. A dispatch note. An invoice pack.

The item comes in. It is classed. It is routed to the owner. The next action is drafted. A human approves where the action commits. The result is written back. The trail starts at action one.

That is the shape. The SOW names the loop. The next loop is a new decision.

In scope

• One named production or back-office workflow the institution already runs.
• Agents inside that workflow, with a human in the chain where a decision is a decision.
• An audit trail from the first action: who, what, which policy, which model.
• Write-back to the system of record. The ERP, MES, or CMMS stays the system of record — as classes. Instance names belong in the SOW.
• In-country run, on the same substrate as every 54east build.
• Train so the team that owns the process owns the agent.

Out of scope

• Replacing the ERP, MES, or CMMS.
• A chatbot overlay, or a new operations suite.
• Autonomous spend, ship, or sign without a named owner.
• Six workflows in one engagement.
• A general “AI operations platform.”
• Unsupervised action on the line.

Not a chatbot

A chatbot answers. This writes into a workflow that already has owners, policies, and a system of record.

If the demo is a conversation window, it is the wrong object. If the trail cannot show who did what under which policy, it is the wrong object. If the plant has to leave its system of record to use it, it is the wrong object.

The trail

From action one. Who initiated. What was proposed. Which policy applied. Which model. Who approved. What was written back.

The trail is the reason a COO can live with an agent on a work order. Without it, this is a toy.

The system of record stays the system of record

We do not ask the plant to migrate in order to close a quality exception. Agents sit with the system that already holds the order, the batch, or the invoice. ERP / MES / CMMS are classes, not a vendor list. A contracts officer names the instance in the SOW.

Train is the exit

The team that owns the process owns the agent. Executive for the people who signed. Technical for the people who will run it on Monday. Train-the-trainer so the next shift does not need us.

A forever operator on the plant floor is the failure mode. See Train.

What a contracts officer can start with

• One named workflow (work order, quality exception, dispatch, invoice pack — or a defined equivalent already running).
• Acceptance: an item can be followed from intake to write-back, with a human at commit, and a trail from action one.
• Classes of connection: ERP / MES / CMMS / the current operations system. Instances named in the SOW.
• In-country residency, keys, and trail, as a floor.
• Train as a contracted exit.
• A written decision to build. Board briefing or decision audit. Nothing is built before that exists in writing.

Who sits in the first conversation: the people who would architect the build. The CEO is the face of the client.

Industrial is the wrapper. It points here. How we work is the five rungs.