Skip to content

What we build

Built around the ERP you already run

Our engineers build the software your ERP does not cover, around it, and leave it running. Your ERP stays the system of record, and what gets built is yours.

01 Three layers

Three layers, and you already have one

Read it from the bottom up. Your ERP holds the transactions. The operations layer is the only layer that talks to it, and the agents reach the ERP only through the operations layer.

  1. Agent layer

    AI agents that work the queues in the operations layer, under the autonomy ladder.

  2. Operations layer

    Software built for you around your workflows: screens, queues, rules and integrations. This is where your people handle exceptions.

  3. System of record

    Your ERP and other core systems. It stays the source of truth. We read from it and write to it only through interfaces it supports.

Fig. 1 The three layers. The lowest one is the ERP you already have.

What lives in each layer, from the bottom up

What lives in each layer, from the bottom up
Layer What lives there Who works in it
System of record Customers, items, price lists, sales orders, purchase orders, inventory balances, invoices and the ledger. Your people, as they do today.
Operations layer The screens, queues, rules and integrations built for your workflows, and the working data they produce: source documents, drafts, approvals, exceptions and the audit trail. The people who do the work: the order desk, your buyers, accounts payable, customer service.
Agent layer AI agents, each tied to one workflow, with its limits and its level on the autonomy ladder. Agents. Your people supervise them from the operations layer.

02 The operations layer

What our engineers build for a desk

The operations layer has four kinds of parts. Each one is there because an engineer watched someone do that work at your site.

  • 01

    Screens

    Where your people do the work and check it. An order screen shows the customer's purchase order next to the order being entered.

  • 02

    Queues

    Lists of work waiting for someone: purchase orders to enter, invoices to match, exceptions to resolve. People and agents take work from the same queues.

  • 03

    Rules

    Your policies, written as checks the software runs. The price must match the price list. The order must fit the credit limit.

  • 04

    Integrations

    The connections that read from your ERP and write finished transactions back to it.

What that looks like, by industry

Your people keep using the ERP itself for everything the operations layer does not cover.

03 What attaching means

Your ERP stays the system of record

Attaching means the software reads from your ERP and writes finished transactions back to it, through interfaces the ERP supports. The operations layer must never turn into a second ERP that disagrees with the first.

Four rules that keep it that way

  1. A transaction is real when it is in the ERP. The operations layer holds work in progress: the email, the draft, the approval, the exception.
  2. Master data is maintained in the ERP. Customers, items and price lists are read from it, and the ERP's version always wins.
  3. Only interfaces the ERP supports. We never write to its database tables directly.
  4. The operations layer keeps only what the ERP has no place for. The original purchase order PDF. The corrections the order desk made to a draft.

A simple test

If the operations layer were switched off tomorrow, the ERP would still hold every finished transaction, and your people could go back to keying into it directly.

The work would be slower, and work in progress would have to be picked up by hand. No finished transaction would be missing.

Illustrative example

Sales order entry at Level 2 (Prepared). A typical case, not a specific client.

Fig. 2 One order through the three layers.
  1. The purchase order arrives

    A customer emails a purchase order. The operations layer puts it in the order queue with the original attachment.

  2. An agent builds the order

    It takes the purchase order from the queue and builds the complete sales order from the customer, items and prices read from the ERP.

  3. The rules check it

    Against the price list and the credit limit, and for an open order with the same purchase order number.

  4. A person approves

    Someone on the order desk opens it, sees the purchase order next to the order and approves it.

  5. The order is written to the ERP

    The operations layer writes it through an interface the ERP supports, and the ERP applies its own checks.

  6. The record is kept

    The operations layer stores the ERP's order number. The audit trail records what the agent did, who approved the order and when.

04 Ways of attaching

Four ways to attach, in order of preference

The choice is made from the Systems and Data Audit, and your IT manager or ERP administrator agrees to it before anything is built. One ERP can use more than one.

  1. A supported API. The first choice. The ERP applies its own validation, numbering and posting to every call. The Systems and Data Audit records which screen-level checks the interface does not run.
  2. Database views or a read replica. For reading only: history and bulk data, without slowing the live system.
  3. File and EDI exchange. The ERP's own import and export jobs, in batches on a schedule.
  4. Screen automation. A last resort, for one named transaction at a time, when nothing else is available.

That holds for the ERP you already run, such as SAP Business One, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Epicor, Infor, Sage, Acumatica, SYSPRO, QuickBooks Enterprise, or whatever you run. We are not a partner or reseller of any ERP vendor, and we do not bring a ready-made connector. Our engineers build the attachment for your ERP as it is set up today: your version, your customizations, your data.

Reading first, writing later

The Discovery Sprint runs on read access alone. Write access is requested one workflow at a time, when that workflow is ready to write back, and it goes through your change control.

Each write-back is a named transaction, such as creating a sales order. After a write, the operations layer reads the transaction back from the ERP and compares it with what was sent.

05 No usable ERP

When there is no ERP worth attaching to

Our default is to attach. If the ERP is missing, at end of life or cannot be extended, our engineers build an ERP-like core as part of the operations layer, and you own it.

What the core covers

Orders
Customers, sales orders and shipments
Inventory
Items, stock locations, quantities on hand and every movement
Purchasing
Suppliers, purchase orders and receipts
Invoicing
Customer invoices and credits

In each area, only what your company uses. If you ship from one warehouse, the core has one warehouse. If you do not track lots, it has no lot tracking.

What it is not

The core is not a general-purpose ERP and not a packaged product. It has no general ledger: your accounting system stays the system of record for the books.

Disliked is not unusable

An ERP that is disliked, slow to change or poorly set up is still usable, and we attach to it. The call is made on the evidence in the Systems and Data Audit, and whether to build a core is your decision.

Moving onto it, in principle

  1. Mirror the old data

    The core first holds a read-only copy of the old system and the spreadsheets that matter. The work still happens in the old place, and the data problems show up early.

  2. Run in parallel

    One workflow at a time, the work is done in the new screens and in the old system side by side, and the results are compared.

  3. Cut over workflow by workflow

    When the workflow owner signs off, the core becomes the source of truth for that workflow. The next one follows when it is ready.

There is no single weekend where everything changes at once, and that has a cost. During a parallel run some work is done twice. No vendor ships upgrades for a core built for one company, so someone has to run it: us, your own people or another vendor you choose.

06 Ownership and handover

You own it and can take it over

You own the custom code and the data built for you. We keep our reusable tooling, and you keep the right to run and change the copy inside your software.

What you own

  • The software in the operations layer: the screens, queues, rules and integrations built around your workflows
  • What was built for each agent: its instructions, its limits and the thresholds set with its workflow owner
  • The data that software holds: the records, the corrections, the exceptions and the audit trail
  • The four Discovery Sprint deliverables
  • The ERP-like core, if we built one

What a handover includes

  • Source code, with its change history, in a repository you control.
  • System documentation. How the three layers fit together at your site, and what each connection to the ERP reads and writes.
  • Runbooks. Release a change, roll one back, use the stop switch, move a workflow down a level.
  • Workflow records. Each workflow's owner, level, limits and thresholds, and the record of every promotion review.
  • An access inventory. Every account the software and the agents use.

Common parts of what we build come from our reusable tooling: the work queue, the approval screens, the audit trail and the stop switch. It stays ours and holds none of your data, your rules or your documents. Your contract gives you the right to keep running and changing the copy inside your software after we leave, with no license fee.

You can ask for an export at any point, in formats you can read without our tooling. Where the software and its data are hosted is agreed in your contract.

Next step

Start with a call with an engineer.

Tell us which ERP you run and the three workflows that hurt most. That is the whole first conversation.