We build the part that sits between the systems a company already has — where information gets re-typed from one place into another, documents are assembled by hand from several sources, and one person ends up being the consistency check for all of it.
What we do
Document work. Assembling documents that are put together by hand from several sources, and checking them against each other, field by field.
Order and lead handling. The step where information moves from one system into the next, and then has to be followed up.
How we work
Moving information into place is automated. Pressing the button is not. That isn't a technical limit — it's where we think the boundary belongs.
Failures are fail-closed. If the system can't identify what it is looking at, it stops and alerts a person. It never guesses.
Before a change ships, we re-run the old and the new version and compare every field, to prove the answers are identical. On the last one that meant all 463 cases.
What a first engagement looks like
A 20-minute call. We ask what the work looks like today; you decide whether it is worth going further.
If it is, we pick one narrow piece and agree in advance how it will be measured — what the before is, and what would count as better.
You keep the output either way, and there is nothing to migrate if you stop.
Who we are
KLADI is small, and we would rather say so than be found out. We came out of cross-border industrial trade — customs clearance, plant setup, long-term energy-performance contracts — rather than out of software.
Our own operation runs unattended: 33 consecutive days without a gap, and about 98% success across roughly 3,000 model calls.
Where the work touches your data, it can be installed and run inside your environment — nothing has to be copied out to us. That is how we shipped our last client system.