Every operation we work with has the same shape: a catalogue, a rulebook, physical stock in many places, and decisions that today depend on someone's memory. The nouns change from one industry to the next. The build does not.
We sit with the people who do the work and follow real cases end to end: an order that went wrong, a substitution that was argued over, an item that expired on the shelf. Out of it comes a map of jobs to be done, the rules behind each decision, the documents and systems involved, and the failure points. Ranked by return, readiness and effort.
Fixed scope. Two or three jobs from the top of the list go live inside your environment, integrated with your systems of record, with controls and audit built in. Forward-deployed engineers work in your tenant, on your data, with your process owners. Not a prototype.
We operate the system, improve it as your rules and suppliers change, and bring the next jobs onto the same foundation. You subscribe to a running system. The build is what gets it live; the subscription is what keeps it right.
We configure these to your catalogue, rules and process. Nothing starts from a blank repository.
Exact item, then equivalent, then acceptable alternative, against your approved list and specifications. The decision that today takes hours of catalogue work, in seconds, with the reasoning shown.
Every line tested against the rulebook: specifications, certifications, licences, controlled items, shelf-life minimums. Deterministic where the rule is deterministic.
What each site should hold, minus what it has, over a configurable window, corrected for expiry and declared usage. A proposal the site can accept in one step.
What may go where, under which licence, with which paperwork. The part of the job that most software ignores because it never had to cross a border.
Exceptions routed to named people with the case laid out. Every decision, override and approval logged and attributable. Audit-ready by construction.
You own your data, your rules and your integrations, in your environment. We own the reusable modules we bring. You subscribe to the running system. Leave, and you keep everything that is yours.
Four nouns. Everything else in the build is identical.
| Operation | The site | The thing | The rulebook |
|---|---|---|---|
| Manufacturing | Plant | Spare parts | OEM equivalence, criticality, maintenance windows |
| Energy and mining | Camp, platform | Consumables, PPE, spares | HSE, customs, permits |
| Maritime | Vessel | Chests, spares | Flag state, certification, port rules |
| Field services | Remote site | Kits, consumables | Import licences, expiry, controlled items |
| Humanitarian | Field mission | Kits | Donor compliance, cold chain |
Our qualification rule is simple. If we can fill in your row in one conversation, we can build it. If we cannot, it is not our job, and we will say so.
A chatbot waits for a person to ask. Our systems react to events: a stock-out, an expiry, a broken item, a changed rule.
Making a bad process slightly faster is an electric motor on a horse carriage. We rebuild the decision, not the typing around it.
A pilot is a way to postpone a decision. A Foundational Build is a decision with a six-week clock on it.
