What we build

Systems that read, connect, answer and act.

Four kinds of system, each built on the ontology and run on the Foundry. They live inside the processes your business already has: orders, stock, purchasing, invoices, service.

01 · Read

Document intelligence

Half of what a business knows is in documents. We read them into records you can check.

Every detail tied to its place
A date, an amount or a clause is stored with the page and the line it came from, so a reader can open the source.
Matched to what you already hold
An invoice is matched to its purchase order and its goods receipt; a contract to the customer and the prices it governs.
Differences stated, not smoothed
When the invoice and the order disagree, the system says where, and leaves the judgement to the person who owns it.
No inference past the evidence
A payment is not marked paid because an invoice exists. What a document does not show is recorded as unknown.
  • Contracts
  • Supplier invoices
  • Purchase orders
  • Delivery notes
  • Email threads
  • Certificates and licences

02 · Connect

Connected knowledge

One model of the business, across the ERP and everything beside it.

One customer, one supplier, one item
The same party appears once, whatever each system and each spelling calls it.
Relationships that carry meaning
An order waits on a delivery; a delivery belongs to a purchase order; a price rests on a contract.
Read from the systems you run
The ERP stays the system of record. The ontology reads from it and from the systems around it; it is not a second copy of the truth.
Each fact with its source
Every node can say which record it came from and when that record was last read.

03 · Answer

Answers you can check.

A question follows its own path through your records. The answer names what it rests on, and says what it could not establish.

1 · A question

2 · The records it reads

  • SO-1042 · ERP · sales order

    40 valve kits VK-7 for Halden Marine, promised for Friday.

  • STK-EAST · ERP · stock, read 09:10 today

    22 on hand at the east warehouse, 6 already reserved.

  • PO-881 · ERP · purchase order

    30 valve kits due Thursday; the supplier confirmed the date.

  • ACC-HM · ERP · customer account

    No credit hold.

3 · An answer you can check

Not from stock alone: 16 kits are free today against 40 ordered. With the 30 arriving on Thursday the order can ship on Friday.

Rests on SO-1042, STK-EAST, PO-881.

4 · The next step

Reserve the 16 free kits now and link the Thursday delivery to this order.

Waits for approval by the operations manager.

Illustrative example on sample records. The companies and figures are made up for this page.

04 · Act

Agent workflows

An answer should lead to the next step. An agent workflow has four parts.

  1. 01

    Information

    The agent gathers what the step needs from the ontology: the order, the stock, the supplier, the rule that applies.
  2. 02

    Actions

    It proposes the action the rule allows: reserve the stock, draft the query, raise the transfer, update the promise date.
  3. 03

    Approvals

    Where the action has consequences, it waits for the person the rule names, with the evidence in front of them.
  4. 04

    Monitoring

    Every run is recorded: what was read, what was proposed, who approved, what happened next.

Where teams start

One process first.

Examples of first processes on an ERP. Each engagement starts with one, agreed with you, and widens when it has proved itself.

Sales and fulfilment

Order exceptions

Which open orders are at risk, why, and what can be done today: stock, supplier dates and credit read together.

Finance

Invoice matching

Invoices read and matched to orders and receipts, with every difference stated for the person who settles it.

Purchasing

Supplier follow-up

Late confirmations and changed dates found in email and in the ERP, and the orders they put at risk.

Inventory

Stock questions

What is on hand, what is reserved, what is arriving, and which figure to trust when two records disagree.

Credit and approvals

Decisions with their evidence

A request arrives at the approver with the records it rests on and the rule that applies.

Service

Answers from the record

A customer question answered from the order, the delivery and the contract, not from memory.

Bring us one process.

Tell us what you want to change, the systems involved and how you would judge the result.