SUSI · AI for teamwork
AI for teamworkOne project, one team, separate chats — and everything still in one place.
With AI the work goes faster: the folder is drafted, the data sheet translated, the manual written, the brief boiled down to a single page. In a project you do all of that together.
Request a demoHand out tasks, ask for status, nothing gets lost along the way.
01 — WHAT THIS IS ABOUT
A project is the place where you work with the AI.
Not a task manager. The place where several people work on the same thing — with the AI that moves the work forward.
- Drafting a folder.
- Launching a product.
- Putting together training material.
- Reworking a website.
In every one of those the AI is what makes the work faster. And when two, three, five people use it on the same thing, they do it in a project.
Everyone sits in their own chat, at their own pace, with their own questions. And everything is still in one place.
You create the project, give it a name and share it with the people working on it. There is nothing else to set up.
02 — AN EXAMPLE
The product launch
A new product is coming out. It needs manuals, a brochure, and somebody to review both before they go out.
Gerald is the project lead, Hans writes the technical documentation, Erna does the marketing, Mr Teufel reviews. Four people, four own chats, one undertaking.
GGeraldProject leadown chat
Hans does the manuals, Erna the brochure, Mr Teufel reviews. Hand out the tasks — and tell them to report back when something is done.
Got it. I’ll pass it on.
Say it once. Everyone knows.
EErnaMarketingown chat
Hi, Erna here — what’s on my list?
Hi Erna! The brochure. The brief is in the library, I’ll summarise it for you.
There are three main products in the brochure. Shall I list the specifications?
Yes please, go ahead. Then we have the text done by the end of the day.
Here you go, I’ll start.
V-200 · control valve
Operating pressure up to 16 bar, medium temperature up to 120 °C, connection G ½ inch, gunmetal body.
Data sheet V-200, page 2
V-300 · control valve, large version
Operating pressure up to 25 bar, medium temperature up to 150 °C, connection G 1 inch, stainless steel body.
Data sheet V-300, page 2
Adapter A-12
…
This is where the work happens, not just the reporting. The brochure takes shape in the chat where Erna asks.
Erna puts her name into the question, and there is a reason for that: the login name does not have to be Erna, it can be CompanyXY01. Whoever introduces themselves at the start of a new chat is correctly assigned within that chat.
HHansTechnical documentationown chat
The manual for the valve is done. I put it in the library.
Good. When Mr Teufel comes in, I’ll let him know so he can review it.
TMr TeufelReviewown chat
Valve manual reviewed. Two places do not fit: the operating pressure on page 3 and the connection size. The measurements are attached — write me the review report.
Here you go.
Review report — valve manual V-200
Basis: manual dated 2 September, measurement series from the attachment.
1 · Operating pressure, page 3
Stated 16 bar. Measured 14.8 bar under continuous load over two hours. Adjust the figure.
2 · Connection size
…
HHansTechnical documentationown chat
How are things looking on the valve?
Mr Teufel has reported in: two places do not fit, the operating pressure on page 3 and the connection size — and here is the summary of the review report that Mr Teufel worked out with me.
Nobody sent Hans anything. He asked.
GGeraldProject leadown chat
Give me the status.
Brochure: draft is in, Erna reported back. Valve manual: back from Mr Teufel, two places with Hans. Remaining manuals: nothing reported yet.
And a week later:
EErnaMarketingown chat
I was away for a week. What happened in the project?
Mr Teufel reviewed the valve manual, two places go back to Hans. Your brochure is unchanged, still a draft. Nothing else.
- Hand out tasks
- Erna picks up
- Hans reports
- Teufel reviews
- Ask for status
03 — HOW IT WORKS
How does that work?
Nothing is pushed to anyone. It is asked for.
Every conversation in the project goes into the project library. In full — the question, the answer, what was reported. Anyone who wants to know how things stand asks in their own chat, and the answer comes out of the project library.
That is why Gerald knows what Hans reported, although the two were never in the same chat. That is why Hans learns of Mr Teufel’s remarks without anyone writing him an email. And that is why the status is still there next week, long after today’s conversation has been closed.
What you put in yourselves counts just as much: the brief, the data sheet, the old brochure. Every answer names the passage it comes from.
04 — SHARING
Who sees what
A project belongs to the people it is shared with. Whoever is in it sees every chat in it and may ask where the others stand. Questions only work inside the shared project and only within your own team — what is in another project stays there.
Hierarchy exists where you set it up. Say nothing and the AI refuses information to nobody: whoever is in the project gets an answer.
How the project is run is decided by the project lead. Gerald says it once, and it applies to every chat in it.
“And no, I do not tell tales. I only say what is in the project — you wrote it in there yourselves.”
05 — THE INTERFACE
This is what a project looks like
Projects on the left, the conversation in the middle. Erna comes back and asks — the answer comes out of the project library, with a note on what it is based on.
I was away for a week. What happened in the project?
Mr Teufel reviewed the valve manual, two places go back to Hans. Your brochure is unchanged, still a draft.Source: project Product launch — reports from 2 and 3 September
And the brief for the brochure?
It is in the project library. Shall I summarise it for you on one page?
Real teamwork with AI.
Tell us what you have in mind, then we will take a look at it.
Request a demoPrices’n’Packages