Catalog Brain
An order arrives as a line of text, and the part it means has eight parameters. Matches by specification rather than part number — tolerances, materials, classes, cross-references.

We build the complex systems an operation runs on — on top of the ERP, the industry systems, and the spreadsheet half of it actually runs on.
What we build
We build the system around how your operations actually work, and keep it running after it goes live.
92%
Orders processed without a human touch
11min90sec
Per order, from email to ERP
+40%volume
Same headcount, over twelve months
How they behave
The industry changes, the data changes, the ERP changes. These four things hold in every one.

Today
Reading orders, checking documents, pricing deals, matching parts against a catalogue — done by software, with a person deciding where it matters.

Works with
Outlook
Gmail
Excel
SAP
Business CentralWe connect to the ERP and industry systems already in place. Replacing them is almost never the right project.

ApprovedWhy?
Every result carries what it was based on. When someone asks a year later why a decision went that way, there is an answer.

Repository access
Repository, documentation, configurations, prompts. Nothing is locked to us, and nothing to a model vendor.
Interface illustrations. Names and figures are examples.
How it works
Whatever the industry, whatever arrives — from the document that lands to the record it leaves behind.

Email, a PDF, a spreadsheet, an EDI message, an export from someone's portal. The system reads all of them, and a new sender is a configuration rather than a project.

NWNordwerk GmbH9/9 matched
| # | As written | Your SKU | Qty | Delivery | Status |
|---|---|---|---|---|---|
| 1 | bracket, galv. | 118902 | 180 | 14 Mar | Matched |
| 2 | seal kit, see att. | 204417 | 40 | 21 Mar | Matched |
| 3 | same as last time | 118840 | 250 | 14 Mar | Matched |
Line items, quantities, terms and parts resolved against your master data — not against a generic dictionary that has never seen your article numbers.

250 × SKU 118840Confirmed automatically
Based on
Each result arrives with the document and the rule behind it. A person checks it in seconds instead of redoing it.

Price 4% above contractNeeds approval
Routed to whoever can actually answer it, with the missing attribute named. Where the answer is about the data, it becomes a rule, and the same case doesn't come back.

Your ERPConnected
Sync activity
We connect to what you already run and write into it. Replacing it is almost never the right project.

Why was line 3 approved above contract?
What was decided, on what basis, under which version of the rules, and who could have overruled it.
Interface illustrations. Names and figures are examples.
Industries
In all four the operational data was never built to be read by a machine.
An order arrives as a line of text, and the part it means has eight parameters. Matches by specification rather than part number — tolerances, materials, classes, cross-references.
The economics of a deal lived in one trader's spreadsheet, and in his head. AgriCore prices a cargo across freight, transshipment, duties and FX in seconds, shows every line the number came from, and says so when the margin goes negative.

Closed testing on live deals at partner desks. Ten signed LOIs.
Calculation breakdown
Interface illustrations. Names and figures are examples.
The same certificate exists in four places and none of them is authoritative. Agents that reach a verdict and cite the passage it rests on — over the satellite link the ship already has.

Three vessels in installation.

The most valuable hour in the terminal is the one nobody controls. A passenger layer on the airport's own domain. No app, no login, no personal data at all.

Twelve-week terminal pilot scoped. First engagement at contract stage.


FAQ
The ones asked on every first call, answered before it.
Most of what people call automation, low-code already does — and if that is your case, buy one. A freelancer can build it too, once. What neither carries is the part afterwards: escalation rules for what the software must not decide alone, a record of what every result was based on, and a fixed set of known answers that runs against every change so drift shows up before a customer does. Two questions decide which you need: can the rule be drawn, and what does a wrong answer cost.
Yes. Forty-five minutes, and we keep to them. Send two or three of your real documents beforehand and we run them on screen during the call. You leave with a proposal, not a presentation; engineering time starts with the paid review.
No. We connect to it as it is configured today, and we write back into it. Replacing an ERP is almost never the right project, and a plan that quietly assumes you will is a plan that fails in month four.
It stops before it commits and asks. The item goes to a named person as a formed question, with the source attached and a clock on it — not to a folder. Once it is answered, the answer becomes a rule, and the same case does not come back.
You do. Repository, documentation, configurations, prompts and the set of known answers it is tested against. Nothing is locked to us and nothing to a model vendor. We keep running it because that is usually the cheaper arrangement, not because leaving is hard.
Bring two or three of your own documents to the first call and watch them run. Four systems in four industries are written up in full here, each with what it still needs in order to work. After that there is a paid review with a fixed length and a named list of what you get.
A first call is forty-five minutes. A paid review is a fixed number of weeks, agreed before it starts. A first system running on real work is months rather than weeks — and the part of it that starts earning arrives well before the last part is finished.
Every package is published with a number and a duration beside it, on one page. The entry point is a five-order teardown over 3 days; a paid review of one flow is a week. Both come off the price of the project. The packages are ways to start, not the whole menu. The price of a system is quoted once we have seen the full scope, and the published numbers are what that conversation starts from.
Get started
Forty-five minutes. Send two or three of your real documents and we'll run them while you watch. You leave with a proposal, not a presentation.
Or hello@logicllab.com
+36 20 223 2328
WhatsApp on the same number

Call with logicllab · 45 min
Your documents
After the call
Interface illustrations. Names and figures are examples.