Skip to content

One record of how your company runs.

Every order, shipment, invoice, declaration and promise your agents and your people touch is written to one record: what moved, where, when, for whom, at what cost and why. The next agent starts from what the last one wrote.

What is the operating record?
One memory of what moved, where, when, for whom and at what cost, written by your agents and your people. It is not a new ERP; it sits beside the one you have.
Fig 2.1The record, filling one row at a timeEach row comes in from the channel on the left and says what moved, where, when, for whom, at what cost and why. The orange column is the one no ERP keeps.
The record, filling one row at a time
WhatWhereWhenFor whomWhyWritten by
Order confirmedSohar branchSun 08:40A catererWeekly orderWritten by the orders agent, from a WhatsApp message. No approval needed: inside the thresholds.
Delivery movedMuscat warehouseSun 11:05A hotel groupSupplier lateWritten by the supplier follow-ups agent, from the supplier's email. No approval needed.
Invoice issuedHead officeMon 09:20A catererDelivered in fullWritten by the orders agent, from the delivery recorded in your ERP. No approval needed.
Discount givenDammam branchMon 14:10A contractorRepeat buyerWritten by the sales manager, from their note of the call. Approved by the sales manager, above the agent's limit.
Short deliverySohar branchTue 07:55A supermarketCarton short, signedWritten by the orders agent, from a photo of the signed delivery note. Approved by the warehouse lead.

Hover a row to see who wrote it.

A decision made on a call leaves no record. Every agent writes one, so the next can read it.

What is in it, and what may be done to it

In the record

  • Parties
  • Orders
  • Shipments
  • Invoices
  • Declarations
  • Promises
  • Thresholds
  • Approvals
  • Log entries

What an agent may do to it

  • Reads
  • Proposes
  • Writeswithin your thresholds
  • Asksabove them

The next agent starts where the last one ended

Nobody tells the collections agent an invoice went out. It reads the row the orders agent wrote, on the day your terms say, and the next agent after it reads both.

Fig 2.2Two agents, one recordThe orders agent writes three rows. Nobody tells the collections agent about the invoice: it reads that row, along the orange wire, and writes its own.

Orders agent writes: Order confirmed, Delivered, Invoice issued. Collections agent reads the invoice row and writes: Reminder sent, in Arabic. It read what the orders agent wrote. Supplier follow-ups: Reads the delivery.

Whose record it is

What an owner asks about the record before anything else: whose it is, where it lives, what it is not, and what each line of it keeps.

Today the record is a WhatsApp group

A delivery note is printed, signed on a tailgate and photographed. The photo goes to a WhatsApp group, and someone types it into a spreadsheet the next branch never sees. The record already exists; it is scattered across phones.

What owners ask about the record

Is this a new ERP?

No. It reads yours and writes back only what you allow; your ERP stays the place your accounts are kept.

Do we have to move our data into it?

No. Agents read where the data already is, and the record keeps what was done with it: what moved, for whom, and why.

Can the next company in the group use it?

What was learned carries to the next company, so it starts further on. Each company's data stays in that company's record.