Teams as the workplace
Dictation, question, photo from the site visit in the Teams chat, the answer comes back there.
What you have in mind
An assistant that works with you. Not software you have to learn first.
Agents are the big promise right now, and part of it is true. What decides, though, is not the agent but the system around it.
-
You think
The AI should work inside our systems, not beside them.
Our experience
Exactly. Outlook, Teams, SharePoint, your specialist program. Our own interface is an offer, not a condition.
-
You think
It should do tasks, not just answer questions.
Our experience
Yes, and the right ones. Note, appointment, file, draft. The assessment stays with you. That is not a gap, that is the point.
-
You think
If it is secure, ChatGPT will do.
Our experience
We would be careful there. A public tool sees your clients in plain text. You are bound to confidentiality, in the crafts by § 91 HwO. Better if the assistant never receives the names at all.
-
You think
We will build a few agents and orchestrate them.
Our experience
That is the part that tips over. A single agent runs quickly. Several calling each other lose the thread: who saw which data, who decided, what is in the log. We orchestrate too, but the rules for it live in the system, not in the prompt.
Where it works
Your systems stay.
Nothing is replaced. The assistant gets tools for the programs you use today.
Microsoft 365: Outlook, calendar, SharePoint
Mailbox and calendar in both directions. The file stays in SharePoint, searchable.
Your appraisal software
Gutachten Manager, SV Works, Bauexpert, autoiXpert: stays. We attach to export or API.
Calculation
DAT, Audatex, GT Motive: the figures come from there, the assistant reads the export.
Invoice and accounting
The invoice grows out of the case and goes as PDF and export to accounting or tax advisor, whether DATEV or Lexware.
Open interfaces
Calendar subscription, CSV, REST and MCP, through which a Copilot uses the same tools.
Law firm, engineering office, planning office? The path is the same.
The limit
A court cut the fee to zero. Because of AI.
Darmstadt regional court, 10 November 2025, 19 O 527/16: an expert had produced the report with AI and had not disclosed it. The court cut the fee from 2,374.50 euros to 0.00 euros (§ 407a para. 3 ZPO, § 8a para. 2 JVEG).
The assistant may do the legwork. Findings, assessment and signature stay with you, and you can prove it. The DGuSV described in 2026 where the line runs.
„Even if a software error is present, you are liable for the report you deliver.“
Permitted, according to DGuSV
Stays with you
What it takes over
Four things it does from week one.
The clips run in our own installation, with invented data. At your office the same runs deeply integrated in and with your programs, in the Teams chat or in Outlook.
-
The site visit note sits in the case. · Clip, no sound 1 / 4
Dictate the site visit
Speak your findings into the phone. The note sits in the case.
-
The knowledge search names passage and document. · Clip, no sound 2 / 4
Ask the file
Which moisture readings were in the first protocol? The answer names passage and document.
-
A draft letter to the insurer. 3 / 4
Prepare correspondence
The draft grows out of the case. You review and send.
-
The calendar shows site visit and submission deadline. 4 / 4
Deadlines in view
Site visits and submission deadlines in the calendar you already have.
How the system is built
Guardrails that hold. Even when things have to move fast.
An agent that may do everything is built in an afternoon. We chose the more thorough way: a system between your programs and the language model. It knows the rights, replaces personal data before the model sees it, and audits every step. Its broad tool base gives the assistant a strong and secure foundation.
Where you work
Teams · Outlook · Phone, dictation · Microsoft Copilot
SCHILLER control layer
- › Rights per person
- › Personal data protection
- › Log
- › Tools
- › Deadlines and appointments
- › Approvals
Your systems
Appraisal software · SharePoint, OneDrive · Outlook calendar · DAT, Audatex, GT Motive · Accounting, tax advisor · Email · Language model, replaced names only
The middle is what we build and run. It decides who sees what, what the model receives and what goes into the log. Left and right, everything stays as it is.
Visible in the conversation
One click shows whether protection is active.
The log
How many personal data items were replaced. No plain text, only checksums.
Underneath: a modular system
The assistant is one module. Not the whole house.
We work with this system and its modules ourselves every day, and we build the same modules into systems like yours. You take the assistant alone or more of it, at your pace.
Cases
Status, parties, documents, notes.
Contacts
Synced with Outlook.
Appointments and deadlines
On the case, in the calendar.
Tasks
With owner and reminder.
Time and trips
The basis of the invoice.
Quotes and invoices
From the case, as PDF for your accounting.
Documents and knowledge
Searchable, with source.
Team and rights
Microsoft account or passkey.
How we work
One thing, four weeks.
No transformation. After four weeks the assistant does one thing, and you know whether to continue.
-
1
Where you stand
Where time is lost, from order to invoice.
-
2
One pilot
One thing, the team, four weeks. Then measure.
-
3
Grow or stop
If it holds, the next module follows. If not, we say so.
Who we are
We do not work alone.
What is outside our field we bring in from our network. Who is part of the first conversation.
We do this ourselves
Development
We build and run the system ourselves and bring in partners where it fits.
Organisational development
So the new way of working stays with the team.
Design and usability
Built with the team, not for the team.
Operations and hosting
With us or on your server, with EU partners for data centre and language models.
We bring this in
IT law and data protection
Contracts and records are checked by lawyers.
IT security
Your own server? Access and backups are checked from outside.
