Terms, plainly.

The Polish national e-invoicing system. A structured invoice has a number and can be moved to the ledger without retyping fields. With us it is one entry point into the flow — not a separate service. source →

Reading text and fields from an image or a scanned invoice. We separate a confident reading from an uncertain field; the latter goes to a person. source →

The path of an invoice or order from arrival to the system: where it comes from, who handles the fields, who approves, where the record goes. source →

A field whose reading is not certain (a disputed amount, a missing order, an exception). It stays with a human; the rest never goes back to manual retyping. source →

The first step of an engagement: a map of one flow and a quote. It takes 1–2 weeks. source →

An inquiry that meets agreed criteria. The basis for billing marketing — next to a low fixed base, instead of a commission on sales. source →

A set of a company’s content (many platforms and languages + the company’s experience). Every fragment has a named source; people find their way easily, bots very hard. source →

A recorded way of working that AI performs on a company’s knowledge base — with its context, vocabulary and rules. No name and no avatar. source →

Connecting systems (ERP, CRM, store, API) so data moves between them without retyping. source →

A task after client silence: who should pick up the thread and when. Not another mass mailing. source →