Today
In plant projects, changes are agreed by phone, by email or in site meetings and never invoiced. At the end nobody can prove what was agreed and when. The dispute comes at acceptance.
An example
In a conveyor project at Conveyra Fördertechnik, the agent finds 7 change requests in three months of project email, including extending the belt conveyor from 10 to 12 m and an extra vertical lift. 5 are outside the scope of supply, and change-order drafts are ready for them.
Your data, wherever it lives
Today change requests hide in the project mailbox, in minutes and call notes as documents or PDFs in the project folder and in drawing queries in the PLM; the agreed scope and your rates sit in the ERP. demi reads, understands and links them per project and change, with your rights. The AI spots change requests at once, checks them against the scope and drafts the change order with its source, instead of a dispute at acceptance, and project management and sales decide on the change order and its price.
Where the data lives today
- E-mails
- Office files
- PDFs
- Folders & drives
- PLM
- ERP
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 project mailbox, ERP, PLM and file share. demi replaces nothing and links drawing queries, meeting minutes, the agreed scope of supply and your rates. Every change request becomes its own record on the project.
- 2 · PermitPermission Layer
The project manager confirms whether a change order applies, and sales approves the price. Both steps are recorded with name and date.
- 3 · ActIntelligence Layer
The agent detects change requests, checks them against the agreed scope and derives the effort from similar past changes, priced with your rates. The change-order quote cites the e-mail or minutes it is based on.
How it runs
- 1
demi reads project emails, queries and minutes.
- 2
The agent detects change requests and assigns them to the project.
- 3
It checks whether the change is part of the scope of supply.
- 4
The project manager confirms the change order.
- 5
Sales approves the price and the quote goes to the customer.
What changes
Changes get billed
Proof for every agreement
Fewer disputes at acceptance
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
+108 hfreed per year
Assumptions and calculation
demi finds change requests in mails and minutes and drafts the change order; you negotiate it.
2 h → 1.4 h per case
How we calculate
15 change orders × 2 h × 30% × 1.0 (manual) × 12 months = 108 h
Value per year, before demi costs
Freed per year+108 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$7,020
gained per year
108 h ÷ 1,760 h per role = 0.1 full-time roles
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
How does it find change requests in emails?
It reads the project correspondence and recognizes wording that describes a departure from the agreed scope, such as different dimensions, extra parts or new dates. Every find links to the email or minutes.
How is the effort estimated?
From similar changes in past projects and your rates. The agent shows which past cases it used. The project manager can adjust the estimate before a price is set.
Who confirms a change order?
The project manager decides whether a change order applies, sales approves the price. Nothing goes to the customer without both steps.
What about changes agreed by phone?
The agent only knows about them if they are written down somewhere, such as a call note or a confirmation email. It can suggest confirming a verbal agreement by email.
