Operations that don't depend on two people.
Written rules, approvals with context and a record of everything.
What costs operations teams today
What makes a process depend on emails, spreadsheets and two people. Pick yours above and Xophia shows how it would be solved in your operation.
Approvals live in email
A purchase, a discount or a supplier change gets approved in an email thread. Nobody knows where it stands, and months later it's hard to reconstruct who approved what and why.
Everything depends on spreadsheets
The process rules live in spreadsheets with macros that two people understand. If one of them leaves or someone changes a column, the process stops.
We can't see what's pending
What's pending is scattered across emails, spreadsheets and systems. Knowing what's late means asking every owner.
Month-end close waits for stock to reconcile
ERP inventory doesn't match what's on the shelf or what was received, and the close waits until someone finds the difference.
From a purchase over email to an approval on record
This is how an approvals module built to measure would work: it gathers the context, sends the request to the right person according to your rules and records the decision.
Illustrative example with fictional data. Operations has no reference module: this one is built to measure, on the same foundation as the others.
01 · Gather
The request arrives with its context
The module takes the purchase request and puts it together with the cost center's available budget and previous purchases from the same supplier.
- Request
- Spare parts · CLP 4,800,000
- Available budget
- CLP 6,200,000
02 · Route
It goes to whoever has to approve it
Your rule says the head of operations approves anything over CLP 3,000,000. The agent prepares the summary and sends it to that person, not to the whole team.
- Rule
- Over CLP 3,000,000 → head
- Owner
- Head of operations
03 · Record
The decision is kept with a name and a time
The head of operations approves, rejects or asks for more information. The decision is tied to the rule, the person and the moment, and the order reaches the ERP only once approved.
- Status
- Approved
- Record
- Head of operations · 11:20
Where your team would start
In operations, the module is almost always built to measure, on the same foundation of connections, definitions and controls the others use.
- Approvals: out of email, with context and a recordRequests that arrive with their backup, are routed by your rules and are recorded with a person and a moment.
- KPI copilotWhat's pending, what's late and what's coming, in one question. It answers on shared definitions and shows where each figure comes from.
- Purchasing and inventory: what was received, matched to what was orderedPurchase orders, receipts and ERP stock matched by your rules, so the close doesn't wait for inventory to reconcile.
Control, from your side
Every decision in the process can be explained later, without digging through email.
Approvals on record, not over email
Each approval is tied to a rule, a person and a moment.
Rules written once
The process rules live in the platform, not in two people's heads or in spreadsheet macros.
Nothing is written without approval
Agents prepare and propose; writes to your systems and high-impact actions wait for approval from a person with the right role.
Reading before you redesign a process
See the whole blog- The company that depended on one personIf the process lives in someone's head, the company doesn't own its operations. That person does.
- Excel isn't the villain. It's the witness.The spreadsheet that carried the company through its early years now exposes a risk: critical rules without controls and operations that depend on them.
- Having an ERP isn't a transformationMany companies celebrated their ERP go-live. Months later, they still operate as if it didn't exist.
Questions from operations teams
Is there a ready-made module for operations?
There is no reference module for operations yet. Approvals, purchasing or inventory modules are built to measure, on the same foundation of connections, definitions and controls the other modules use.
Do we have to drop the ERP or the spreadsheets?
Not all at once. What works gets connected and stays the system of record. What creates friction, like a spreadsheet only two people understand, can be replaced by a module, one at a time, with its data migrated and validated. You make that call.
Who defines the approval rules?
Your team. Amounts, owners and exceptions are written with you and live in the platform: each rule is defined once and, if it changes, it changes in one place.
Which systems does it connect to?
To your ERP, for example Odoo, SAP or NetSuite, and to the systems your team already uses through MCP, REST, GraphQL, SQL, events or webhooks. Read and write scope is confirmed for each implementation.
Which process depends on an email or a spreadsheet today?
In a 20-minute diagnostic we review your processes, who approves what and where things get stuck, and propose a concrete first module.