What people actually build with it.

1. 01Search your own guidelinesAsk in plain language, get the passage from your own guideline and protocol documents, with the page it came from. No answer without a source.
2. 02Drafts for letters and reportsStructured notes in, a draft out, in your house wording. Facts stay in the source document; what is missing stays visibly missing instead of being filled in.
3. 03Intake of incoming documentsReferrals, findings and forms arrive as PDF or scan. Read out the fields you need, sort them by type and hand them to the system that stores them.
4. 04Translation and plain languageThe same information in German, French or Italian, and a version a patient can read, side by side with the original.

Where it stops. It does not diagnose and it does not decide on treatment. It reads documents, drafts text and points at the source. Everything that carries a signature stays with the person who signs it.

1. 01Read incoming documentsIdentity papers, statements, policies and contracts arrive in every format there is. Read out the fields, flag what is missing and hand the result to the system that checks it.
2. 02Search regulation and internal policyOne question against circulars, internal directives and manuals; the answer names the clause. Where two documents contradict each other, that is the answer.
3. 03Drafts for client correspondenceLetters and answers in your own wording, built from the file, not from memory. Numbers stay where they came from.
4. 04Sort and route what comes inMail, tickets and forms labelled by topic and urgency before anyone opens them. Your system does the routing; the model only reads and labels.

Where it stops. No investment advice and no trade. It reads, drafts and sorts; every decision that moves money stays with the people who are allowed to make it.

1. 01Answer enquiries from your own pagesA question in plain language, an answer from the pages and leaflets you have published, with a link to the page. Nothing invented in between.
2. 02Drafts for decisions and lettersStandard correspondence built from the file and the applicable provision. The person in charge reads, corrects and signs.
3. 03Search the recordMinutes, reports and old correspondence, searched by meaning rather than by exact word, with the document and the passage in the answer.
4. 04German, French, ItalianThe same text in the other national languages, and a plain-language version next to the formal one.

Where it stops. It makes no decision about a person. It prepares, reads and drafts; the decision, and the responsibility for it, stay with the office.

1. 01Read a contract against your own checklistNotice period, liability, jurisdiction, change of control: ask for what you always ask for, and get the clause, not a paraphrase.
2. 02Sort a data roomHundreds of documents grouped by type, party and date, with the ones that do not fit the pattern pulled out for a person to look at.
3. 03Standard draftsLetters, NDAs and internal notes from your own templates and the file. Your wording, your structure.
4. 04Search your own mattersWhat did we write last time on this question? Searched by meaning across past matters, with the document behind every hit.

Where it stops. It is not legal advice, and it does not decide anything. It finds, reads and drafts; the lawyer who signs carries the opinion, as before.

1. 01Ask the manualError code, model, year: the answer comes from your own service documentation, with the section it stands in. Also in the workshop, on a phone.
2. 02Read supplier documentsDelivery notes, spec sheets and invoices turned into the fields your system wants, with the unclear ones marked rather than guessed.
3. 03Sort service requestsWhat came in overnight, labelled by machine, topic and urgency, so the morning starts with a list instead of an inbox.
4. 04Reports and handoversShift notes and service reports drafted from what was written down, in the form your customer expects.

Where it stops. It does not control anything. It reads and writes text; it is not connected to a machine, a PLC or a safety system, and it should not be.

1. 01Help desk on your siteA question in the widget, an answer from your published pages, with the link. Where the pages do not say, it says so instead of inventing a policy.
2. 02Triage before the queueTopic, urgency and team on every new ticket, from one short call. Your help desk does the routing.
3. 03Reply draftsA draft in your tone, built from the ticket and the relevant page, for an agent to check and send.
4. 04Keep the knowledge base honestQuestions the pages could not answer, collected. That list is the best article backlog you will get.

Where it stops. It does not close tickets and it does not make promises about refunds, deadlines or exceptions. Those are decisions, and decisions stay with your people.

1. 01Invoices and receiptsSupplier, date, net, VAT, invoice number, line items - read out of the PDF and handed over as a row. What is unreadable comes back as unreadable.
2. 02Expenses against policyEach claim checked against your own rules, with the sentence from the policy next to the flag.
3. 03Month-end commentaryA first draft of the narrative from the figures you export anyway, in the structure your board is used to.
4. 04Supplier correspondenceDunning letters, queries and confirmations drafted from the ledger entry and the contract.

Where it stops. It does not book anything and it does not approve anything. It prepares rows and drafts; the posting stays in your system, under your controls.

1. 01Questions about the handbookHoliday, notice periods, expenses, home office: answered from your own regulations, with the section. Where the regulation is silent, so is the answer.
2. 02Job ads and role descriptionsA draft from the requirements you wrote down, in your own voice, without the usual adjectives.
3. 03Onboarding materialThe same content as a checklist for the first week, a page for the team and a short version for the manager.
4. 04Sort what comes inApplications and internal requests grouped by role and topic, so the reading order is a decision and not an accident.

Where it stops. No decision about a person: it does not rank candidates, does not reject anyone and does not assess performance. It reads and drafts; people decide about people.

1. 01Work in the repositoryFind the bug, propose the fix, run the tests. Every change is a diff you approve, on a machine you control.
2. 02Incidents and logsA readable summary of what happened, in the order it happened, from the logs and messages of the night.
3. 03Runbooks and internal documentationAsked in plain language, answered from your own pages, with the section. The wiki finally gets read.
4. 04Internal tools on the APIThe API speaks the OpenAI format, so an existing client usually needs a new base URL and a key, and nothing else.

Where it stops. It does not deploy and it does not touch production on its own. It proposes changes and writes text; the pipeline and the approvals stay yours.