You run operations, and the orders live in inboxes

For operations directors whose orders and suppliers live in inboxes.

You have an ERP, and the order desk, purchasing and the suppliers still run on email: orders that arrive as PDFs, confirmations nobody chases until the customer rings, deliveries that don’t match what was ordered, subcontractors who invoice what they shipped rather than what you asked for. We match, chase and settle that work for you, alongside the ERP you run, and your people approve anything that goes back to it or out to a customer.

Start with one process, live in four weeks on your own orders, priced per document or per exception. Your ERP stays exactly where it is.

02The pilot

Live in four weeks, on your own orders.

We run a pilot on your own orders and supplier documents, on your ERP as it stands. The measure is simple: what proportion goes through without a person touching it, and what happens to the rest. The gap is usually order formats and supplier discipline rather than software, and we will show you which customers and suppliers it is.

Week 1

Connect

Your ERP, the order and purchasing inboxes, supplier and carrier portals, read-only to begin with.

Week 2

Rules record

Order validation and purchase-order-to-confirmation matching on your real documents. You see what agrees first time, and what doesn’t.

Week 3

AI resolves

The agent works the slips, short shipments and substitutions, contacts the supplier, recommends. You approve.

Week 4

Measure

Orders through without a person, confirmations outstanding, days from delivery to invoice, and which customers, suppliers or formats are the gap.

No long-term contract. If the honest answer is “fix the order formats first”, we’ll say so.

03Which systems

The ERPs you run, and the systems around the order desk.

Read and written through the API where one exists, and through the user interface where it doesn’t.

  • SAP Business One Deepest
  • Sage Deepest
  • Exchequer Deepest
  • NetSuite Production
  • Business Central Production

Also integratedSAP S/4HANA · Oracle · Intact · QuickBooks · Xero · MS Dynamics GP · custom-built ERPs · UI-driven agents where no API exists

  • WMS and goods receipts.
  • Supplier and carrier portals.
  • EDI.
  • UI-driven agents where no API exists.
04What it’s worth

Measured on your orders, not quoted from someone else’s.

  • Customer dates kept.
  • Days from delivery to invoice, which is cash.
  • Hours returned to the order desk and purchasing.
  • No admin hires as volume grows.
05Pricing model

Priced against what a clerk costs, not against hours.

  • Per document or per exception. The outcome component is priced per order and confirmation handled or per exception resolved, set against what a clerk costs to do the same work.
  • A run fee. A monthly fee covers the platform and the people who run it: tuning, new suppliers, changed processes.
  • A scoped build. At a transparent cost, agreed before we start, for the first process and each one after it.
06Questions operations directors ask

Straight answers.

Our ERP has a purchasing module. Why isn’t that enough?

The module records a purchase order. It doesn’t read the supplier’s email, notice the date slipped, ask for a part-shipment or tell the customer. That work sits between the module and the inbox, and it is what we run.

We subcontract manufacturing. Does that change anything?

It’s the shape we built the suppliers-and-subcontractors process for: purchase orders from your orders by your product rules, confirmations and deliveries checked against them. We don’t run production.

Does anything reach a supplier or a customer without approval?

Only routine requests, to wording you sign off: chasing a missing confirmation, asking for a delivery note or a credit note. Anything that changes what was agreed, such as a new date, a part-shipment, a substitution or a price, is approved by a named person before it goes out.

Which confirmations is nobody chasing?

Thirty minutes, your process, no slides.