ZANUS BACK OFFICE — ASK YOUR COMPANY ANYTHING
Every company runs on questions: what did we agree with this client, which version of the procedure applies, where is the drawing, how do we handle this case. Here your people ask the AI — and it answers from your documents and records, with the passage shown. Not a public chatbot with your data pasted in: a private chat that knows the company.
Hosted, private or on a unit you own · your rules, your approved sources · live in days, not months

A private chat: the question, the grounded answer, the sources, and the assistant mode chosen for this kind of work.
Contracts, procedures, records, past emails: the chat searches what you approved and quotes it. It also reads the file you drop in and reasons on it.
A purchasing assistant, a compliance assistant, a project assistant: each with its own skills, presets and libraries — and its own memory of how you like things done.
Several language models built in, chosen per assistant or per conversation. On a unit you own, models run locally; the rule is the same either way.
Click a tab. Every picture is the working Back Office — the left menu is the whole product.

A consultant asks for every commitment made to a client across three years of correspondence and gets a dated list with the emails cited. A production manager drops a supplier’s spec sheet and asks whether it meets the drawing’s tolerances. A warehouse lead asks which orders are waiting on the same missing item. Same chat, same verifier, different libraries.

What the chat knows is what you put in the libraries — and what each user is allowed to see.

Every conversation and every piece of AI work is searchable later — the company stops losing what it already figured out.
An assistant is a chat with a job description: which libraries it reads, which skills it uses, how it writes, what it checks each time. It keeps a memory of your corrections, so the third report sounds like your company and not like a first draft. Presets make the common requests one click: “summarise this file for the board”, “compare these two offers”, “draft the reply in our tone”.
Chat lives at the third stop of the loop: the AI reasons on your sources and the file in front of it, then answers with the passages shown.
In one working day new colleagues ask the questions they would have asked a senior; seniors ask the ones that used to take an afternoon of searching. Every answer names its source, so a wrong assumption is caught on the spot — and the conversation is there tomorrow.
The functions, named. Every one of them is on the demo.
Included from AI WORKEach assistant sees only the libraries its users are allowed to see.Plans →
No. Your libraries and conversations are yours; they feed the answers of your tenant and nothing else. On a unit you own, the models run inside your building.
An assistant answers from the libraries its users may read. Permissions per domain and per library decide that, and the audit log records every question.
Several, and the list evolves; you choose per assistant. The verifier and the citation rule apply regardless of the model.
← Previous: Answers with the source · Sharing with a colleague? 📄 Get the PDF · ✉️ Email this page ·