We build the interface between people and decisions.

Decision Interface P.S.A. is a product company rather than an agency or a design studio: we do not take on client implementations and we do not bill by the hour. We maintain our own products and stand behind them after release, so new versions also appear when nobody is paying separately for them. The company is registered in Poland, and all development happens here, from the first sketch of a screen to replying to messages from users. The name states what the work is about: we deal with the point of contact between people and the decisions they make at work.

Three levels of tooling share one assumption: we build the interface between a person and a decision rather than another place for loose notes. Fakturium covers invoicing for micro-businesses in Poland and works today, the operational layer for teams described above as ERP is still being built, and DI Cloud is a workspace for working with AI. A program should carry the work through to a resolution instead of ending it with a block of generated text: in Fakturium the resolution is a document issued and sent, and in DI Cloud it is an answer that shows its sources along with a confidence rating produced by the DI Core engine.

The software is built in small releases that we check on the running service right after deployment, because some faults only appear outside a developer's machine. The mobile applications connect to the same service and the same endpoints as the browser, so the account, the projects and the history of the work stay shared regardless of the device. The interface text is maintained in ten languages: Polish, English, German, French, Spanish, Portuguese, Russian, Chinese, Arabic and Hindi. Changing a single sentence in the product therefore means ten versions to agree on, which on its own enforces writing that is short and free of ornament.

We are equally careful about what we do not promise. An answer from a language model can be wrong, which is why DI Cloud shows the sources an answer rests on, and where matching material is missing it marks that case plainly and lowers the confidence rating instead of filling the gap with unsupported text. Access to projects, files and sources is limited by rules held on the database side, and the technical conditions of that protection are described separately on the security page. The last step belongs to the person: the tool prepares the material, points to where it came from and records the course of the work, but the resolution stays with whoever is using it.