An AI agent for training and documentation writes your company’s procedures from what the people who know the job tell it, keeps them current when something changes and answers colleagues from them. For a new hire it prepares the learning path, step by step. Every procedure is approved by a person in your company before it reaches the team.


In many small businesses, the way work gets done isn’t written down anywhere. One colleague knows how to close the register at night. Another knows how to handle a return to a supplier. As long as both are in the office, everything runs. When one goes on leave or resigns, the others improvise, and the new hire learns on the go, from whoever has time.
Procedures don’t get written because nobody has the time. The person who knows the process is exactly the busiest person. And the document written two years ago no longer looks like what’s done today, so nobody opens it anymore.
The training and documentation agent takes over this work. It writes, keeps things current and explains. Your people keep the part only they can do: saying how the work is done correctly and confirming that the text is true.
Tell us what slows you down. We talk, then decide together whether and how we work.

The capability has three connected parts: written procedures, answers for the team and training for new people. The agent carries all three.
It writes work procedures from raw sources: a recording of a colleague talking through the process, notes, screenshots, old messages with instructions.
It brings every procedure to the same shape: who does it, when, with which tools, what the steps are and what to do when something goes wrong.
It keeps documents current. When a step, a form or a program changes, it proposes the new text and shows what differs from the old version.
It answers the team’s questions from approved procedures and shows which document the answer came from.
It builds the learning path for a new hire: what they read on day one, what they practice next and which check questions they get.
It keeps a list of the questions it couldn’t answer. That list shows you which procedure is missing.
The result isn’t a thick binder nobody reads. It’s a set of short pages, written in your team’s own language, that a new person can follow without asking someone at every step.

The flow is the same for every procedure, whether it covers receiving goods, opening a customer account or closing the month.
It receives the raw material. A colleague records a spoken explanation or sends the notes they have.
It writes the first draft of the procedure and marks the places where information is missing or contradicts itself.
It puts the clarifying questions to the person who knows the process, on the channel they already use.
It sends the draft to the process owner for approval.
It publishes the approved procedure where the team keeps its documents and announces what changed.
It answers colleagues’ questions and notes the ones left without an answer.
It revisits old documents periodically and asks the owner whether they still hold.
The agent doesn’t write procedures from imagination. If nobody has told it how something is done, the page stays marked as incomplete, with the question open for the person who knows.
For each role, the agent links the procedures into a path. The new hire gets the materials in sequence, not all of them on the first morning. After each chapter they answer a few check questions. Their manager sees where they did well and where a face-to-face conversation is still needed.

Documentation lives where the team already works. We don’t ask you to move everything into a new program.
Google Workspace, meaning Google Docs and Google Drive, for procedures and course materials.
Microsoft 365, with Word, SharePoint and OneDrive, if the company works in the Microsoft ecosystem.
Notion or Confluence, when you want an internal handbook organized by section.
Slack, Microsoft Teams or email, for the team’s questions and for change announcements.
Loom or Google Meet recordings, as the source for procedures explained out loud.
Google Forms, for the check questions at the end of a chapter.
If your procedures currently sit in Word files on one office computer, we start from there. First we bring them into a shared place, then we put them in order. And if you use a program that isn’t on the list, we check whether it has a way to connect before promising anything.

The limits matter as much as the task list. Here is what stays outside its work.
It doesn’t invent rules. If the company hasn’t decided how to proceed in a situation, the agent flags the gap.
It doesn’t replace the occupational health and safety training required by Law 319/2006. That is delivered and signed with the designated worker or the external prevention and protection service.
It doesn’t evaluate people or decide who passed the probation period. It shows the results on the check questions, and the conclusion belongs to the direct manager.
It doesn’t draft employment contracts and doesn’t work in REGES. That part stays with your HR person or your accountant.
It doesn’t publish or change a procedure without the owner’s approval.
It doesn’t give legal advice on labor law.

We don’t begin with the handbook for the whole company. Together we pick one process that hurts right now: one that only a single person knows, or one where new people often make mistakes.
The colleague who knows the process explains it once, out loud or in writing. The agent writes the procedure, the owner corrects and approves it, and the team starts using it. After the first procedure you see how close the text is to the way you really work. Only then do we move on to the next ones, in the order you set.
Once you have enough procedures for a role, we link them into the training path for the next hire. We tell you the cost of the tools involved at the start, before you agree to anything.
A wrong procedure is more dangerous than a missing one, because people follow it. That’s why no page reaches the team without approval from a person in your company.
Every procedure has a named owner, usually the person who runs that process. They read the agent’s draft, correct it and approve it. With every change they see exactly what was modified, without rereading the whole document. If two sources contradict each other, the agent doesn’t choose on its own. It puts both versions in front of the owner and waits.
When the team asks questions, the agent answers only from what has been approved. When a question touches a personal case, for example pay, a disciplinary matter or a medical situation, it sends the colleague to the person in the company who handles that. And a person on our side follows how the agent works and checks the documents before they go for approval.
The most important link on the page. From here you go up to the agent we sell.
Sideways, on the same level, so you can move easily between pages.
It writes your company’s work procedures starting from the explanations of the people who know the processes, brings them to the same shape and updates them when something changes. It answers the team from approved documents and prepares the training path for new hires. No procedure reaches the team without approval from its owner in your company.
Every procedure has an owner in your company, who reads and approves it before publication. The agent writes and proposes, but it doesn’t publish on its own. If someone spots a mistake after publication, they flag it, the owner corrects the text, and from then on the agent answers from the new version.
No. The agent reads the existing documents, brings them to the same structure and marks the passages that look outdated or that contradict each other. Then it asks the person who knows the process what still holds. You start from what you have, not from a blank page.
No. Occupational health and safety training is a legal obligation of the employer under Law 319/2006, and it is delivered with the designated worker or an external service. The agent can keep the internal materials in one place and remind you who is due for training, but it doesn’t replace that training and doesn’t sign anything.
In your own space, meaning Google Drive, SharePoint or Notion, where the team keeps them today. The agent works with the access rights you give it and doesn’t move documents anywhere else. If you end the collaboration, the written procedures stay with you, in their approved form.
Tell us what slows you down. We talk, then decide together whether and how we work.