Projects in the neuland.ai HUB

Project status belongs to the team.

Not to someone's inbox.

A project brings together the documents, group chats, and knowledge bases of an initiative for every department involved. Newcomers ask for the current status instead of reading through old emails.

Talk to us

Projektwissen steckt in Postfächern und Köpfen. Wechselt eine Person, geht es mit ihr.

Decisions are in minutes, the reasoning in emails, the current status in the project lead's head. When someone joins or leaves, exactly the knowledge that people ask for later goes missing.

Example · Project timeline

Project status grows with every set of minutes.

No reasoning gets lost, not even after months.

Project status grows with every set of minutes.

No reasoning gets lost, not even after months.

An example: the ERP replacement at Muster Armaturenwerk AG: IT, procurement, logistics, and finance, eleven months, one project. Minutes, assessments, and decisions go into the project status as soon as they are created.

Month 1

The project is set up on day one

The project lead sets up the ERP replacement 2027 and invites IT, procurement, logistics, and finance. From then on, the requirements specification, requirements, and schedule are in one place, not in four mailing lists.

Month 2

The policies apply too

The procurement policy and IT security policy knowledge bases are linked to the project. Procurement and information security keep maintaining them; the project always uses the current version.

Month 4

Every workshop record lands in the project

After each requirements workshop, the project lead brings in the Meeting Recap Generator; it summarizes decisions and open items and files them in the project. The related tickets are in Jira, and the chat in the project reads them too.

Month 5

Three proposals, one comparison

In the group chat, the team compares the proposals of three vendors against the 212 requirements in the specification. Every assessment cites page and chapter, and all departments see the same list. The steering committee adopts decision E-07.

Month 11

The steering committee gets its briefing paper

In the group chat, the project lead calls the Projektstatus Reporter with “/”. It writes the briefing paper from the project's decisions, minutes, and Jira tickets; the project lead adds to it and presents it.

Month 1

The project is set up on day one

Month 2

The policies apply too

The procurement policy and IT security policy knowledge bases are linked to the project. Procurement and information security keep maintaining them; the project always uses the current version.

Month 4

Every workshop record lands in the project

Month 5

Three proposals, one comparison

Month 11

The steering committee gets its briefing paper

Month 1

The project is set up on day one

Month 2

The policies apply too

The procurement policy and IT security policy knowledge bases are linked to the project. Procurement and information security keep maintaining them; the project always uses the current version.

Month 4

Every workshop record lands in the project

Month 5

Three proposals, one comparison

Month 11

The steering committee gets its briefing paper

Example · Group chat

In the group chat, the team asks for the project status.

Every answer cites the documents.

In the group chat, the team asks for the project status.

Every answer cites the documents.

An example: the new logistics subproject lead asks in the group chat why vendor C was eliminated. The neuland.ai HUB answers from the proposal, the workshop minutes, and the steering committee records, with page, agenda item, and decision number.

Muster Armaturenwerk AG

EU operation

Muster
Armaturenwerk AG

ChatsProjectsAgentsAutomationsAppsKnowledge

Warehouse workshopData migrationWarehouse interfaceSteering committee September

ProjectsGroup chat · Vendor selectionactive

Why was vendor C eliminated from the selection?

Vendor C tracks batches only via an add‑on module that is not available until release 2028 ^[1]. In the warehouse requirements workshop on February 12, 2026, logistics confirmed this traceability as a mandatory requirement ^[2]. That is why the steering committee excluded vendor C on March 14, 2026, decision E‑07 ^[3].

Ask the project a question

SharePointJiraConfluenceOutlook+ Context+3

Step 1 of 3

Built in Germany · EU operation

Searching 3 documents

Source [1]

Proposal_vendor_C_2026.pdf

p. 23 · ch. 6.4 Warehouse management

Traceability per batch via the WMS Plus add-on module, available from release 2028.

Source [2]

Workshop_warehouse_2026-02-12.docx

Agenda item 3 · Traceability

Traceability down to the storage location is a mandatory requirement, because of recalls and quality evidence.

Source [3]

Steering_committee_2026-03-14.pdf

Decision E-07

Vendor C is eliminated: the mandatory requirement of traceability per batch is not in the standard product.

Group chat: all project members can read along.

Private and team

Private chat or group chat: you decide who reads along.

Drafts in private, decisions in the team.

Private chat or group chat: you decide who reads along.

Drafts in private, decisions in the team.

A private chat accesses all project documents, but only you can read it. What the team needs to know belongs in the group chat or in the project as a finished document.

Private chat

You draft the statement for the steering committee in peace, with the specification and proposals at hand.

Group chat

All members read along and ask follow-up questions, including the neuland.ai HUB's answers and their sources.

From draft to project

Once the statement is finished, you add it to the project. From then on, every chat in the project answers from it too.

FAQ

Who reads along and what remains after the project ends.

When do we use a project, and when a knowledge base?

A project belongs to an initiative with a team and an end date, such as an ERP replacement, a tender, or an audit. A knowledge base holds what applies permanently, such as policies and manuals, and serves many projects, agents, and chats. The project reads linked knowledge bases instead of copying them. More under Knowledge and context.

When do we use a project, and when a knowledge base?

Who sees a project's documents and chats?

The members you invite, individually or as a group. They see all project documents and group chats; a private chat is visible only to the person who runs it. Admins define via roles who may create projects, and the neuland.ai HUB takes groups from your existing identity provider.

Who sees a project's documents and chats?

Which documents and systems fit into a project?

You upload files such as PDF, Word, Excel, text, Markdown or emails directly; data sources and connected knowledge bases are added. Via the connectors, the chat in the project also reads in systems such as SharePoint, Jira, Confluence or Outlook. We connect systems such as ERP or your own specialist applications individually as an additional service.

Which documents and systems fit into a project?

What happens to the project after it is completed?

The project remains after go-live, with all documents and chats, for everyone who stays a member. That way, the team behind the next replacement can also find the reasoning behind E-07.

What happens to the project after it is completed?

The project remains after go-live, with all documents and chats, for everyone who stays a member. That way, the team behind the next replacement can also find the reasoning behind E-07.

How does someone new get up to speed quickly?

You invite the person as a member. They ask for the status in the chat instead of reading through old emails, and every answer names the place in the documents it comes from.

How does someone new get up to speed quickly?

You invite the person as a member. They ask for the status in the chat instead of reading through old emails, and every answer names the place in the documents it comes from.

Can agents work in the project?

Yes. With “/”, you bring agents into any chat in the project, including the group chat. You adapt an agent from the Agent Library once and share it with the team of the next initiative.

Can agents work in the project?

Yes. With “/”, you bring agents into any chat in the project, including the group chat. You adapt an agent from the Agent Library once and share it with the team of the next initiative.

How do we create a project?

The project lead creates the project and invites the departments involved as members, individually or as a group. From then on, the specification, schedule, and other documents are in one place; you link knowledge bases such as policies to the project instead of copying them.

How do we create a project?

What is the difference between a private chat and a group chat?

A private chat accesses all project documents, but only the person who runs it can read it. In the group chat, all members read along and ask follow-up questions, including the neuland.ai HUB's answers and their sources. You add a finished document to the project; from then on, every chat in the project answers from it too.

What is the difference between a private chat and a group chat?

Are our project documents used to train language models?

No. Your data is never used to train language models, and only project members see documents and group chats.

Are our project documents used to train language models?

No. Your data is never used to train language models, and only project members see documents and group chats.

Where does the neuland.ai HUB run, and what documentation is available?

In EU data centers or in your own infrastructure, depending on the protection requirements of the initiative. The Trust Center offers, among other things, an ISMS certified to ISO 27001, a data processing agreement under Art. 28 GDPR, and documented technical and organizational measures for download; for financial companies, also the DORA addendum.

Where does the neuland.ai HUB run, and what documentation is available?

Your next initiative.

As a project, not a mailing list.

Tell us which departments are working on it and which documents already exist. Afterward, you know how the project status stays with the team, even when people change.

Talk to us

After your request

You describe the initiative, departments, and existing documents

You see the project, group chat, and linked knowledge bases in the neuland.ai HUB

We discuss the onboarding plan for your first project