Today
Projects repeat mistakes that were made before. The lessons sit in final reports nobody reads, or in the heads of people who have long moved to another team. The next similar project starts from scratch again.
An example
At Ebert & Lorenz Maschinenbau a project starts for a press line with two HP 400 presses. At kick-off the agent shows 7 lessons from two similar projects, among them late customs papers for the control cabinets and a commissioning that ran two weeks over plan. For each lesson it links the change order, the mail thread or the job costing.
Your data, wherever it lives
What went wrong in projects sits today in project folders on the drive, change orders in the DMS, actual job costs in the ERP, e-mail threads and final reports as Word files that nobody opens any more. demi reads, understands and links it all per project, plant type and assembly, with your rights. At kick-off the AI presents the lessons from similar projects in minutes instead of after half a day of digging through files, and the project manager decides what to adopt.
Where the data lives today
- Folders & drives
- DMS & archive
- ERP
- E-mails
- Office files
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the file share, ERP, DMS and mailbox. demi replaces nothing and links project files, change requests, change orders, complaints, actual job costs and final reports to the project, plant type and assemblies. demi writes back only after approval.
- 2 · PermitPermission Layer
The project manager reviews and approves the lessons at project close, and then they are open to every project team. Prices, contract terms and names stay with the people who could see the original project, and every step is recorded.
- 3 · ActIntelligence Layer
The agent pulls out of the project records what went wrong, what it led to and how it was solved, and adds nothing of its own. When a new project starts, it shows the relevant lessons by project type and assembly, each linked to its source.
How it runs
- 1
Connect project files, change orders and actual job costs
- 2
The agent extracts lessons and links them to project type and assembly
- 3
Project management reviews and adds to them at project close
- 4
At kick-off, the agent shows the lessons from similar projects
- 5
Project management adopts what fits into the project plan and checklists
What changes
Fewer repeated mistakes
Better prepared project starts
Project knowledge stays when teams change
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+58 hfreed per year
Assumptions and calculation
demi sums up problems and fixes and shows them on the next similar project; you learn from them.
4 h → 2.8 h per case
How we calculate
4 project reviews × 4 h × 30% × 1.0 (manual) × 12 months = 58 h
Value per year, before demi costs
Freed per year+58 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€3,770
gained per year
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Where do the lessons come from?
From records that exist anyway: change requests, change orders, complaints, acceptance reports, actual job costs and final reports. The agent sums up what happened and how it was solved. Nobody has to fill in an extra form.
How does the agent match lessons to a new project?
It compares the new project with earlier ones by plant type, assemblies, destination country and scope. It shows the lessons from similar projects, the most important first. Each one links to the records it comes from.
Are confidential customer details protected?
Yes. The lesson itself, such as “sort out customs papers for control cabinets early”, is visible to every project team. Customer names, prices and contract details stay with the people who could see the old project. Rights come from the org chart and the project roles.
Who maintains the lessons?
The agent proposes them; project management reviews and adds to them at project close. That keeps the collection current without anyone curating an archive. What proves itself can go into checklists and project templates.
