Built for supply chain and logistics teams

The AI operating layer for supply chain logistics.

LeedAB runs as a local agent system inside your office. It tracks allocation, screens export risk and chases suppliers across SAP, carrier portals, TMS dashboards, ERPs and inboxes. No API integrations. No cloud uploads.

Book a call → On-prem appliance · your hardware
/ 01 · The gap

The work between portals is where supply chains break.

From a 2026 study of 14 supply chain and operations teams. Numbers reflect medians across the cohort.

5days
Median time between PO issuance and legal sign-off on a single allocation commit.
Source · cohort study, n=14 teams
70%
Share of tier-2 and tier-3 supply base that procurement leaders report having no real-time visibility into.
Source · VP Sourcing survey, Q1 2025
1×/wk
Typical cadence at which carrier and supplier capacity states are reconciled by hand into a single spreadsheet.
Source · cohort interviews
/ 02 · Workflows
Five Artificial Beings ship out of the box.

ABs are agentic workflow units that run inside the brain. Each one owns a specific procurement loop, with memory, monitoring and a paper trail. Custom ABs ship in 1–2 weeks.

01 / 06
AB · 01CONTROL TOWER

Your control tower.

Sits in your control tower. Watches every supplier commit, carrier capacity update, and customer commitment for drift. Reconciles them into one live state. Flags the moment a commit slips. Owns the weekly allocation review you used to run in a spreadsheet.

WatchesSupplier portals, carrier TMS, inbound ETAs, PCNs
TriggersCommit slip, capacity shift, lead-time delta
OwnsFreight, packaging, and supplier pipelines
OutputsLive state, weekly digest, escalation memo
AB · 02POD RECON

Your POD reconciler.

Sits between your drivers, your carriers, and your client's POD systems. Flags shorted, refused, and undelivered loads the same day they happen. Drafts the customer email and the credit note before anyone has to ask. Live in production with our first paying customer.

WatchesCarrier portals, driver apps, client POD systems
TriggersShort delivery, refusal, missing POD, claim window
MemoryPer-driver and per-customer dispute history
OutputsReconciled sheet, customer email, credit note draft
AB · 03DEDUCTIONS

Your deductions desk.

Lives next to your client deduction sheets. The moment a monthly batch lands, it sorts each line into a category (lost shipments, traffic fines, vehicle damage, SIMs), produces numbered credit notes, and reconciles the summary by driver and category. PDFs in your folder before Monday.

WatchesClient deduction sheets, monthly invoices, driver records
TriggersNew deduction batch, dispute window, refund pending
OwnsCredit note numbering, category math, audit log
OutputsNumbered PDFs, summary spreadsheet, refund queue
AB · 04RISK MONITOR

Your supplier sentinel.

Walks your supplier map down to tier 2 and tier 3. Holds a memory of who-makes-what-where. Watches the world for natural-disaster, geopolitical, and single-source exposure. Drafts the exposure memo the morning of an incident, not the week after.

WatchesTier-2/3 supplier moves, fab geographies, NHC, USGS
MemoryPersistent supplier-to-product graph
TriggersNew single-source, region exposure, M&A event
OutputsExposure report, second-source recommendation
AB · 05COMPLIANCE

Your compliance officer.

Reads every part, customer, end-use, and shipment before it leaves the building. Screens against BIS Entity List, OFAC SDN, EAR ECCN classifications, the Foreign Direct Product rule, and customs filings. Pre-flights orders before a human ever touches them, with citations on every flag.

WatchesBIS Entity List, OFAC SDN, EAR, FDP, HTS/HS, ACE
TriggersNew order, customer add, ECCN change, customs flag
OwnsFirst-pass screen + audit log
OutputsPass/flag/escalate, memo with citations
AB · 06CUSTOM

A bespoke specialist.

Bring a procurement or operations loop you would rather not run by hand. We work with your team for 1 to 2 weeks to build a new one with its own watchers, triggers, memory, and audit trail. It onboards the same way the in-box five do.

ExamplesTariff reclassification, dual-source allocation, NPI risk
Timeline1–2 weeks to shipping
Owned byLeedAB solutions engineering
PricingIncluded with production tier
/ 03 · How it works
Live in days, not months.

Procurement transformations get measured in quarters. LeedAB is designed to be sitting in your office, watching live systems, inside the same fiscal sprint as the kick-off call.

01 Install

Plug in the brain.

An appliance ships to your office, or runs on hardware you already own on any spare Mac, Windows PC, or Linux box. Your IT team plugs it into the network it should sit on: your network of choice: corporate, air-gapped, anywhere. No cloud account to provision.

Day 0 · on your hardware

02 Connect

Sign in once, like a person.

A LeedAB engineer pairs with your team to log the agent into SAP, carrier portals, TMS dashboards, your inbox, and any supplier portals that matter. The same surfaces a buyer or dispatcher uses, with no API contracts and no IT integration tickets.

Day 1 to 3 · surfaces enrolled

03 Work

Five ABs wake up.

The control tower starts reconciling allocation, the screener starts pre-flighting orders, the follow-up agent starts chasing commits. You meet them where your team already lives. Slack, Teams, WhatsApp, or Telegram. As colleagues.

Day 4 to 14 · first reports shipped

/ 04 · Capabilities
Works where your team works.

ABs use a computer the way a buyer does, logging into the same portals, reading the same dashboards. They meet your team in the same channels you already live in.

Capability · 01

Computer use, not integrations.

ABs log into supplier portals, carrier TMS, SAP, and your inbox the same way your team does. Allocation and capacity states reconcile in real time across surfaces that have no API.

Capability · 02

Meets your team in channels.

ABs answer in Slack, Teams, WhatsApp, or Telegram, with citations and an audit link. Procurement engineers stay in the chat surface they live in, and the agent stays one @mention away.

/ 05 · The stack
Sits across your existing systems.

No procurement team rips and replaces. LeedAB sits behind the systems you already pay for and operates them on your behalf, the same way a senior buyer would, only continuously.

ERP
SAP / SAP Ariba
S/4HANA · ECC
ERP
Oracle SCM
Cloud · Fusion
ERP
NetSuite
SuiteCommerce
Source-to-pay
Coupa
Procure · Pay
Planning
Kinaxis · o9
RapidResponse · IBP
Supplier
Supplier portals
Direct logins · web · email
Freight
Carrier TMS
Project44 · FourKites · direct
Compliance
BIS · OFAC · EAR
Entity List · SDN · ECCN
Compliance
Customs · trade
HTS · HS · CBP · ACE
Market data
Bloomberg · S&P
Terminal · Capital IQ
Mail
Outlook · Gmail
EWS · Google Workspace
Chat
Slack · Teams · WhatsApp · Telegram
Channels · DMs · groups
12 surfaces shipping · custom surfaces on request NO APIs REQUIRED
/ 06 · Security
A vault inside your building.

The brain runs on hardware that physically lives inside your office, behind your firewall. Your allocation data, your supplier contracts, your export memos. They do not leave the room.

SEC · 01
Encrypted at rest.

FileVault-class disk encryption with hardware-backed keys; every credential the brain holds is sealed against a key that never leaves the appliance's secure element.

AES-256 · Secure Enclave
SEC · 02
Full audit trail.

Every action an AB takes, every login, every memo drafted, every flag raised, is logged with cryptographic chain-of-custody and exportable to your SIEM.

SIEM · WORM log
SEC · 03
Role-based access.

Buyers, planners, legal, security each see only the surfaces and ABs they're cleared for. Approvals are scoped, time-bounded and revocable from your SSO.

SAML · SCIM · MFA
SEC · 04
Air-gappable.

For export-controlled customers, the brain runs without internet egress. Models, weights and tooling are pre-baked into the appliance and updated by signed image.

Zero egress · signed updates
/ 07 · FAQ
Eight questions we get on every call.

If your question isn't here, your account engineer will answer it on the kickoff call. We don't gate technical detail.

/ 01 What is the product, exactly? +

LeedAB is a brain (an appliance that runs in your office, on hardware you choose: a spare Mac, Windows PC, or Linux box) running a small set of Artificial Beings. ABs are agentic workflow units that operate the same procurement surfaces your team does. The brain is the runtime; the ABs are the work.

Five ABs ship out of the box: an advanced-packaging control tower, a BOM risk monitor, an export-compliance screener, an LTB/EOL command center, and a supplier follow-up agent. Custom ABs ship in 1–2 weeks.

/ 02 Who is it built for? +

VPs and senior directors of supply chain, operations, strategic sourcing, and procurement at manufacturers, freight forwarders, last-mile operators, distributors, fabless designers, IDMs, and CHIPS-Act fabs.

/ 03 Where does our data live? +

Inside the appliance that sits in your office, behind your firewall, on the network you choose. Nothing is shipped to a LeedAB cloud. There isn't one. For air-gapped deployments, internet egress is physically blocked at the appliance.

/ 04 Which AI models do the ABs use? +

A mixture of on-device models (for reasoning, classification and screen understanding) and, where you allow it, large frontier models accessed under your contract. Model choice is a deployment-time decision, including all-local for export-controlled customers.

/ 05 Can we use it on export-controlled data? +

Yes. The export-compliance screener was built first for exactly this reason. In air-gap mode, models, weights and tooling are pre-baked into the appliance and the brain does not call out. Every classification, citation and memo is produced on-device.

/ 06 Why hardware at all? What runs the brain? +

Because the buyer we serve will not accept a cloud-hosted agent reading SAP and BIS. The hardware boundary is the security model. The brain runs on whatever fits your room and your model needs: a quiet Mac Mini for most teams, a GPU workstation when local inference is heavier. Minimum spec is 8 GB of RAM on macOS, Windows, or Linux.

/ 07 How long does deployment take? +

Pilots are live in 14 days. Day 0 is the appliance arriving at your office. Days 1–3 are surface enrollment (logging into SAP, carrier portals, TMS dashboards, supplier portals, inbox). By day 14, the first reports have shipped and the first commit has been chased.

/ 08 How do you compare to Kinaxis, o9, Coupa or SAP Ariba? +

We don't replace them. Kinaxis, o9, Coupa and Ariba are systems of record and planning. LeedAB is the operator sitting behind them. It's the layer that actually does the work between portals that today gets done by a senior buyer pasting into a spreadsheet.

/ Book a call

See the brain run on your allocation data.

A 30-minute call. Bring one workflow you'd rather not run by hand. We'll walk you through how the matching AB would handle it inside your office.

Book a call → Request a brief
Engagement Open
Call30 min · Zoom or in-personstep 1
BriefWorkflow scoping memostep 2
Pilot14-day on-prem deploymentstep 3
Time to live
14 days
Form factor
Appliance · your hardware
Deployment
Inside your network
Support
Dedicated solutions engineer