Today
A customer specification easily runs to 200 pages, six annexes and references to company standards that are not attached. Under quoting pressure nobody reads it in full. Contradictions between text and annex, missing limits and words like “approx.” or “state of the art” slip into the quote and later turn into disputes, unpaid extra work and changes just before delivery.
An example
A customer sends Arnstein a 180-page specification for a housing in AlSi10Mg. The agent finds 41 requirements without a limit, among them a leak test with no test pressure. It also finds a contradiction in the salt spray test, 480 hours in chapter 4 against 720 hours in annex C, and seven customer standards that are not attached. When version 3 arrives, it shows 12 changed requirements, two of them affecting the casting die.
Your data, wherever it lives
Specifications arrive as PDFs by e-mail or from the customer portal; earlier versions and clarification lists sit in the DMS, project folders and spreadsheets, product data in the PLM. demi reads these documents, understands every requirement and links it to standards, annexes and your product data, with your rights. AI finds gaps and contradictions in minutes, and you decide which questions go to the customer.
Where the data lives today
- PDFs
- E-mails
- Office files
- Folders & drives
- DMS & archive
- PLM
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 DMS, PLM, e-mail and spreadsheets. demi replaces nothing and splits every specification into single requirements, linked to chapter, page, annex and the standards it cites. Earlier specifications from the same customer, clarification lists and your product data from the PLM sit alongside.
- 2 · PermitPermission Layer
Specifications and clarification lists are visible to sales, project and engineering on that project; customer documents under NDA stay within that group. What goes to the customer as a question is released by the project manager, and the release is recorded.
- 3 · ActIntelligence Layer
The agent checks each requirement against fixed rules: is there a value with unit and tolerance, does another passage contradict it, does it cite a missing standard or annex? It flags vague terms such as “approx.”, “where possible” or “by agreement”. Every finding gives page and wording, and values are quoted unchanged from the document.
How it runs
- 1
The specification arrives by e-mail or from the customer portal, with all annexes.
- 2
The agent splits it into single requirements, each with chapter and page.
- 3
It flags contradictions, missing values, vague wording and missing standards or annexes.
- 4
This becomes the clarification list, sorted by impact on cost, schedule and liability.
- 5
The project manager reviews, adds and sends the questions to the customer; whatever stays open goes into the quote as an assumption.
What changes
Gaps and contradictions settled before you quote
Clear assumptions in the quote instead of disputes after the order
New specification versions with every change in view
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
+180 hfreed per year
Assumptions and calculation
demi flags contradictions, missing values and vague terms with their page; you settle them with the customer.
2.5 h → 1.75 h per case
How we calculate
20 specifications × 2.5 h × 30% × 1.0 (manual) × 12 months = 180 h
Value per year, before demi costs
Freed per year+180 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
+$11,700
gained per year
180 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 gaps and contradictions does demi find?
Values without unit or tolerance, requirements that contradict each other across text, tables and annexes, references to standards or annexes that are missing or out of date, and vague terms such as “approx.”, “sufficient” or “state of the art”. You set the rules, for example a list of wording you never accept.
What happens when the customer sends a new version?
The agent compares the new version with the old one requirement by requirement, even when chapters have moved. It shows what is new, changed or dropped and which change touches design, cost or schedule. From that it drafts the basis for a change order, which you review.
Does demi also read annexes, tables and drawings in the specification?
Yes. Tables, annexes and embedded drawings are part of the specification and are read with it, scans included. If a value in a table contradicts the running text, both appear side by side with their page.
Who decides which questions go to the customer?
Your project manager. The agent proposes questions and assumptions; the project manager deletes, adds and releases them. Only then does the clarification list go to the customer, and the release is recorded.
