13 quarries, one system,
twelve months measured.
RockProsUSA, an aggregates producer with 13 sites in the United States, moved dispatch, invoicing and daily reporting onto one system.
quarry sites on one system, one shared truck fleet.
dispatch cycle time, order raised to truck confirmed.
invoices matched and issued with zero manual touches.
operations hours returned in the first year.
All four numbers are from the first twelve months of one engagement.
What changed, operation by operation
| Operation | Before | After |
|---|---|---|
| Dispatch | Phone and WhatsApp between 13 site managers; whoever shouted loudest got the truck. | One queue across all sites; the Brain proposes the assignment with its reasoning, a dispatcher approves. |
| Invoicing | Weighbridge ticket, delivery note and purchase order reconciled by hand at month end. | Three-way match on delivery. Only genuine exceptions reach a person. |
| Reporting | Production numbers assembled Sunday night, stale by Monday standup. | Daily P&L-grade report written by 6:00 AM. |
| Rollout | The expected shape was a multi-quarter ERP programme. | Two partners and the Brain, at a fixed price agreed in the Sprint. |
Five apps, one dispatch engine.
We built the whole surface and the engine under it, so a truck movement, an invoice line and a production number describe the same event.
Customer ordering app
The first record of a haul is created once, by the person who wants the material.
Trucker app
The hauler's surface: what was offered, accepted and confirmed.
Driver app
Built native, because a driver at the pit with a weak signal is the hardest user on the system.
Admin console
13 sites on one board: who has trucks, who has orders, which cycles broke pattern.
The dispatch backend
Order to invoice in one path, so the three-way match reads the records the assignment was made from.
30 repositories, 2020 to 2026: a six-year relationship, not a launch.
Representative views of the running system
Three mechanisms
The assignment carries its reasoning
Reasoning makes approval fast; the 38% lives in the minutes between an order existing and a truck confirmed.
The match happens on delivery, not at month end
Ticket, note and order reconcile as the haul completes, so 2,140 invoices went out with zero manual touches.
The report is a by-product, not a task
The report is assembled from records already written, by 6:00 AM; those hours are a large share of the 11,200 returned.
What runs here, we build elsewhere.
The dispatch engine, the reporting and the invoice matching each have their own page.
Quarry dispatch automation · Plant production reporting · Freight reconciliation · all six systems
Updated 15 September 2026 · WE_AINA
Book a Diagnostic Sprint
These numbers started as a two-week Sprint; yours would start the same way.