Today
Every system has its own truth. In the PLM a product moved to revision C long ago, while the ERP still builds to the revision B bill of materials; the web shop still offers a variant that purchasing blocked weeks ago; the CRM has the customer's new delivery address, the ERP does not. It only comes to light at the customer: as a complaint, a wrong delivery or a query.
An example
In the first week, demi reports 63 contradictions at Tannried Möbelwerk. Among them: the TI 1,800 × 900 conference table is at revision C with a new frame connector in the PLM, but three production orders in the ERP still run on the revision B bill of materials. And the web shop offers a cabinet as FSC certified, although purchasing has listed the board supplier's certificate as expired for two weeks. Production planning switches the orders before anything is built, and sales removes the claim from the shop.
Your data, wherever it lives
The truth about an item or a customer is spread today across the ERP, PLM, CRM, web shop and warehouse system, plus spreadsheets that departments use to carry data from one system to another. demi reads, understands and links these records by item, customer and drawing number, with your rights. The AI finds contradictions on the same day instead of the customer finding them weeks later, and whoever maintains the field decides which value is right.
Where the data lives today
- ERP
- PLM
- CRM
- Web & portals
- Databases
- Office files
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: ERP, PLM, CRM, web shop, warehouse system and databases. demi replaces nothing and links the records for an item, customer or supplier across all systems, with field, value, time of last change and person. Corrections happen in the leading system, by the person who maintains it.
- 2 · PermitPermission Layer
Everyone sees only contradictions in data they may already see today; prices and terms stay with sales and purchasing. You define which system leads for which field. A correction is made by whoever maintains the field in the leading system, and every decision is recorded.
- 3 · ActIntelligence Layer
The agent compares continuously against rules you set: status, revision, price, stock, address, certificate. demi checks exactly from the records whether two values match. The agent explains since when the contradiction has existed, which orders, quotes or shop pages are affected and who may fix it.
How it runs
- 1
You define which system leads for which field: revision in the PLM, price in the ERP, address in the CRM.
- 2
demi compares the linked records continuously and finds every value that differs from the leading system.
- 3
For each contradiction the agent shows since when it has existed and which orders, quotes or shop pages it touches.
- 4
The alert goes straight to whoever maintains the field, urgent ones first, such as those with open orders.
- 5
They decide and correct; demi checks again and closes the alert.
What changes
Contradictions surface before the customer notices
Fewer wrong deliveries and complaints caused by wrong data
One clear leading system for every field
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
+216 hfreed per year
Assumptions and calculation
demi finds contradictions between systems and reports them to the owner, who decides.
30 min → 21 min per case
How we calculate
120 contradictions between systems × 30 min × 30% × 1.0 (manual) × 12 months = 12,960 min = 216 h
Value per year, before demi costs
Freed per year+216 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
+€14,040
gained per year
216 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
Which contradictions between systems does demi find?
All those you set a rule for: an item blocked in the ERP but orderable in the shop; a new revision in the PLM with an old bill of materials in the ERP; a price in a quote that does not match the price list; stock that differs between ERP and warehouse; addresses that differ between CRM and ERP. Every new rule widens what is checked.
How does demi know which value is the right one?
You define it: every field has a leading system. demi reports every value that differs from it and does not guess. If the leading system itself is wrong, the owner decides, and demi remembers the decision.
How often does demi compare the systems?
Continuously. Important fields such as block flags, revision or price are checked shortly after every change, everything else at least every night. How quickly a change arrives depends on how the systems are connected; we work that out with you.
Does this replace an interface between the systems?
No. Interfaces transfer data; demi checks whether everything fits together in the end, including where there is no interface and people move data by hand. Where a contradiction keeps arising at the same spot, demi shows it, so you can fix the cause.
