Today
NDAs are negotiated carefully and then filed away. After a few weeks, nobody knows which drawings, test reports or recipes went to the partner by e-mail, portal or share link. When the collaboration ends, nobody asks for return or deletion, and if documents turn up elsewhere later, there is no proof of what the partner had in the first place.
An example
Valbrecht ends its collaboration with an external engineering service provider on a new pump module. demi shows that 46 files went out under the 2023 NDA, including circuit diagrams of the syringe pump, the IEC 60601-2-24 test report and parts of the MDR technical documentation, 31 by e-mail and 15 via a share link that is still open. Under the NDA, return or deletion is due 30 days after the project ends. demi drafts the request with the list, the head of finance and administration approves it, and in the same step demi closes the share link.
Your data, wherever it lives
Signed NDAs sit as scans and PDFs in the DMS or in folders; shared drawings and test reports are in sent e-mails, SharePoint shares, the supplier portal and PLM exports. demi reads, understands and links them, with your rights. In minutes the AI shows what each partner received under which NDA and when return or deletion is due, and an authorised person decides what to request.
Where the data lives today
- DMS & archive
- E-mails
- PLM
- SharePoint
- PDFs
- Scans & paper
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
This case needs data from the DMS, e-mail, PLM, cloud storage, PDF files and scans. demi replaces nothing and reads every NDA with partner, purpose, term, confidentiality period and return obligation. Then it finds what was actually shared: attachments in sent e-mails, shares in cloud storage and in the supplier portal, exports from the PLM, each with date, revision and recipient.
- 2 · PermitPermission Layer
Management, legal and those responsible for each partner see the register; people working on a project see only its entries. A request for return or deletion goes out only after approval by an authorised person. Every approval and every partner confirmation is logged.
- 3 · ActIntelligence Layer
The agent matches each shared document to the right NDA and flags what went out without a valid NDA or outside the agreed purpose. demi calculates deadlines from term and project end by fixed rules. Before each deadline, the agent drafts the request with the list of documents and follows up on the partner's confirmation.
How it runs
- 1
demi reads all NDAs, old scans included, with partner, purpose, term and return obligation.
- 2
The agent finds in e-mails, cloud storage, the portal and the PLM what went to each partner.
- 3
Every document is matched to the right NDA, and gaps are flagged.
- 4
When a project or an NDA ends, demi drafts the request for return or deletion with the list.
- 5
An authorised person approves it, and demi follows up on the partner's confirmation.
What changes
A list per partner of what they actually received
Return and deletion are requested, not forgotten
Evidence with date and revision if documents turn up later
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 shows what was shared under each NDA and drafts the return request; an authorised person approves it.
90 min → 54 min per case
How we calculate
15 NDA cases × 90 min × 40% × 1.0 (manual) × 12 months = 6,480 min = 108 h
Value per year, before demi costs
Freed per year+108 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
+€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 demi know what was actually shared?
From the traces that sharing leaves: attachments in sent e-mails, share links from cloud storage, downloads from the supplier portal, exports from the PLM. demi assigns them to partner and NDA. Anything that went out another way, such as on a USB stick, you add by hand.
Can demi read old NDAs that exist only as scans?
Yes. demi reads scanned and signed NDAs including amendments and extracts partner, purpose, term, confidentiality period and return clause, each with a reference to the passage. Those responsible confirm the details once.
What happens if something went out without an NDA?
demi flags it in the register with date, sender and recipient. Whether an NDA is signed retroactively, the document is reclaimed or nothing is done, management or legal decides.
How does this relate to the NDA check before sending?
Both use the same register. The check before sending holds e-mails for which no valid NDA exists; the register shows what actually went out under each NDA and what has to come back or be deleted at the end.
