LeedAB
R01
Contract administration
Abstracts contracts and addenda, maintains the obligation calendar.
Platform
Operations delegated. Judgement retained.
Not a trading terminal. A working operations layer for a physical desk.
Architecture
Three Layers, One File Per Trade
Layer 01
Context
The contract and its addenda, counterparty data, trade rules, and your policy on tolerances. Read once, reused everywhere.
Layer 02
Execution
Roles that own a function of the lifecycle. They read, calculate, chase, and draft continuously, not when a screen is opened.
Layer 03
Control
Authority per role, approval routing, and a complete audit trail. Anything that binds the company waits for a named human.
Chasing is delegated. Committing is not.
Claim noticesNomination acceptancesPresentationsPayment release
Roles
What the Desk Hands Over
Start with one. Add the rest as the desk gets comfortable.
R02
Logistics coordination
Follows the vessel across agents and ports, keeps laytime current.
R03
Documentation control
Assembles the shipping set and checks it against the credit.
R04
Quality and claims
Reads certificates on arrival, computes allowances, protects notice periods.
R05
Inventory control
Reconciles elevator, warehouse, and afloat against third party reporting.
R06
Settlement and cost
Builds the cost stack and invoices from executed reality.
Questions
What Desks Ask First
Do we have to replace our trading system?
No. LeedAB can work alongside your CTRM or ERP, or give the operation its own custom system by turning the spreadsheets your team already runs on into a live operational workspace. It keeps the records current and covers the work that never had a proper home.
How does it handle scans and low quality documents?
Scans, faxes, and photographs of stamped originals are the normal case in physical trade, and the document handling is built for them. Where a field cannot be read with confidence it is flagged, not guessed.
Can it message external parties and compliance teams?
Only within the authority you set. Routine status requests and internal compliance follow-up can be delegated. Anything sent to banks, authorities, or other regulated parties is drafted and held until a named person releases it.
What happens when it gets something wrong?
Every conclusion links to its source document and clause, so a disagreement is checkable in seconds. Automated steps are inspectable and reversible.
Does our contract data leave our environment?
LeedAB can run in our enterprise cloud on AWS or GCP, in your own cloud tenancy, or fully on-premise. In every deployment, your contracts are never used to train LLM models.
Which commodities does it cover?
Physical commodities on both sides of the house: grains, oilseeds and meals, vegetable oils, sugar and softs, and base metals, concentrates, and ores. The contract forms, specifications, and claim mechanics differ by complex, so we configure them against the paper you actually trade.
Start Where Operations Slow You Down
See how LeedAB’s AI agents move the work forward, not just record what happened.