Available today
The web app
The workspace on any device: library, conversations with sources, data tables, memory, automations, tenders.
The MCP server
Your own tools, an AI client or a script use the workspace through one endpoint and an API key: search, documents, memory, data tables, calculations, reports, tenders.
Google Drive and Sheets
Connected from the settings, in your own Google account: documents come in from Drive, reports and tables go out to the sheets your team already uses.
e-Factura (SPV)
After a one-time ANAF authorisation, incoming e-invoices are retrieved automatically several times a day and become answers, totals, due dates and table rows.
Any system with an API
A scheduled automation can call a system that exposes an API, bring the data back and check it against your documents. No extra software is needed, just a description of what to fetch and when.
On request, based on an offer
The web assistant
A chatbot on your own website that answers visitors only from the documents you provide, citing document and page.
WhatsApp Business
Ask the assistant from your phone, send a photographed document, receive the morning digest where the team already talks.
Slack and Messenger
The same conversation from a team channel or from a customer chat, with the same confirmation before anything leaves.
A public API
Send messages and documents from your own applications through a simple HTTP endpoint and receive the answers with their sources.
ERP, CRM and accounting connectors
Named connectors for the software you use every day, so that invoices, orders and contacts flow in both directions without an export. We build them for the customers who ask, each with its own offer.
How “on request” works: you name the system and the job, we send you a written offer with the scope, the schedule and the price, and once you accept it, we build the integration with you, run it in shadow mode first, then hand it over. What you use every day comes first.
How a connector works
- 1
Reads
It takes in the document, message or record that arrived, whatever the format: PDF, scan, photo, email or table.
- 2
Matches
It compares what arrived with what the workspace already knows. It recognises a supplier seen before, even when the name is spelled differently, finds the purchase order that is still open and applies the rules you set once.
- 3
Proposes
It drafts the record line by line, with the source next to every value, and marks anything that does not add up.
- 4
Waits for you
A person sees the proposal and the evidence, corrects what needs correcting and approves. Nothing leaves before that.
- 5
Writes back
It saves the approved record in the other system and keeps an audit trail: who approved what, when and on what evidence.
What all channels and connectors respect
- Sending, deleting, changing a record or submitting to a third party always waits for a person’s confirmation, on every channel.
- Each channel and each connector is switched on by you and can be switched off at any time.
- Credentials are limited to the job: an API key that reads invoices cannot send email; keys are stored only as hashes and can be revoked.
- Writes are idempotent: a synchronisation run twice creates nothing twice.
- Data stays in the EU; the only transfer outside it happens if you connect Google Drive or Sheets, in your own account.
How we start
- 1.You list the systems your company uses and where information is carried by hand between them.
- 2.We pick the first connection together: the one with the most hours and the cheapest mistakes.
- 3.Once you accept our written offer, we run it in shadow mode, compare, then hand it over with the figures on the table.