01

Automations

Connecting one system to another is a solved problem, and the tools that solve it are cheap. That is not what I sell.

The reason automation projects fail is almost never the integration. It is that nothing defines what the system does when it is not sure — so it either proceeds silently, which is dangerous, or it stalls on a person who was never told they had become the review step. I build the boundary explicitly: what the machine may do alone, what it must ask about, and what it has to show you when it asks.

In this category

04

Teyit — document intake with an explicit confidence boundary

Supplier invoices and receipts arrive as PDFs, scans and phone photographs in Turkish, Arabic or English, and come out as validated structured records. The extraction is the commodity half.

The product is the confidence boundary. Every field carries a confidence and a reference back to the region it was read from, deterministic arithmetic runs over the model's output, and each document ends up committed, held, or rejected — never silently guessed at, and never quietly parked on a person who was not told they had become the review step.

In development
Document AITurkish · Arabic · EnglishHuman-in-the-loopSelf-hosted

The model proposes; arithmetic disposes. That is what makes a non-deterministic extractor safe to trust.

Other categories