Wiki, document storage and templates in one place, searchable through the assistant. What has been written down once does not have to be explained a second time.
The year-end accrual procedure lives in a Word file on a drive, the exception to it in an email from 2024, and the actual reasoning is known by the person retiring this summer. While she is here everything works, because you can ask. Afterwards the same procedure is reinvented, usually slightly worse, and the exception is missed the first time round. That is not a documentation problem. It is a findability problem.
Filing something is quick. Making it findable is the work. These five points take it on.
Work it out with your own numbers. The running part is the time that goes daily into questions whose answer already exists in the building, in many firms ten to twenty minutes per person per day. The other part is rare but expensive: the departure or retirement of a key person. If a procedure has ever had to be rebuilt after someone left, you know the order of magnitude, and you also know the damage is not in the hours, it is in the mistakes of the first months afterwards.
This is built for Swiss companies with roughly ten to a hundred employees whose procedures have to exist in writing: fiduciary and consulting firms, technical services, planning and construction, manufacturing with quality assurance, organisations in care and education. Typically there are directives on a shared drive, templates in several versions, and a handful of people who get asked whenever something is unclear.
It carries most where the same work is done by changing people: part-time roles, stand-ins, apprentices, seasonal peaks. The more hands a procedure passes through, the more often it gets explained, and the more it pays off when the explanation stands once and can be quoted next time with its source.
You upload what already exists: Word files from the drive, PDF directives, Excel lists, presentations. On upload the text is read out so the document becomes searchable; the file itself stays in its original format and opens as before. The wiki does not then fill up in one sitting, it fills up along the questions of everyday work: whoever has answered a question turns the answer into an entry. Templates for contracts, quotes and reports you approve once.
After that the work shifts from explaining to adding. What you do not have to bring along is the folder structure that grew over the years, the naming convention from the last decade and the standing argument over whether a document belongs to the customer or to the project: it hangs off the record it belongs to, and you look for it through the question rather than through the path.
Talk, report, inform — without anyone keeping three programs open.
Inbox, appointments, documents, notes: the working day, not the toolbox.
From the first contact to the signed contract, in one unbroken chain.
What carries the business: orders, stock, assets, projects, tickets.
What the company knows stays findable — even when someone leaves.
Eighteen modules, one surface, one login. Not a patchwork of tools that know nothing about each other.
We show you a wiki entry, a document produced from an approved template, and a question to the assistant answered from both, with a reference to the source. No contract, no preparation.