Skip to content
Data & IT: legacy data, formats, connectorsPumps & ValvesMachinery & Plant EngineeringConveying & IntralogisticsConstruction & Building Services+1

Rebuild the folder structure from content

You get a structure by customer, project and document type, derived from what your files contain, with a naming rule.

Today

Every department files by its own logic: sales by customer, project management by job, service by year, and some people by their own name. Everyone only finds what they filed themselves. New staff need months to learn where things are, and in the end everyone asks the same two colleagues.

An example

At Nortavo Gebäudetechnik, the documents for an ILZ 40 ventilation unit sit under customer, site, year or fitter, depending on the department. demi reads 410,000 files, recognizes site, document type and date and proposes the structure customer, site, document type with the naming rule date_site-number_document-type. After project management approves, demi moves the files in three stages and points 1,900 links in maintenance plans and the ERP to the new paths.
Fictional company, typical workflow.

Your data, wherever it lives

Today your project documents sit in folders on the drive and the NAS, in SharePoint libraries, as Word and spreadsheet files, PDFs and photos, and every department files by its own logic. demi reads, understands and links them with customers, projects and orders from the ERP and CRM, with your rights. In days, the AI proposes a structure for hundreds of thousands of files that would take a team months, and you approve it.

Where the data lives today

  • Folders & drives
  • NAS & hard disks
  • SharePoint
  • Office files
  • PDFs
  • ERP
  • CRM
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from drives, NAS, cloud storage, the ERP and the CRM. demi replaces nothing, recognizes customer, project, document type and date in every file and matches them with customer and order numbers. Files are moved and renamed only after approval.

  2. 2 · PermitPermission Layer

    Rights move with the files: whoever could see a file before can see it afterwards, and nobody else. Where the proposal would put files with different rights into one folder, demi shows this before approval. Personal folders stay untouched. The person you name approves structure and move, and every step is recorded and can be reversed.

  3. 3 · ActIntelligence Layer

    The agent reads content, not just file names, and recognizes customer, project and document type; it matches numbers exactly against the ERP and CRM. From the patterns in your data it derives structure and naming rule, moves files in stages and points links to the new location.

How it runs

  1. 1

    demi reads folders and files and recognizes customer, project, document type and date from the content.

  2. 2

    The agent proposes a structure and a naming rule that fit the way you work.

  3. 3

    The departments check the proposal against real examples and adjust it.

  4. 4

    After approval demi moves and renames in stages and keeps an old-to-new list.

  5. 5

    demi points links to old paths to the new place, and new files land in the right place from the start.

What changes

  • Every department finds what the others filed

  • Consistent names instead of final_new_v2

  • Links keep working after the move

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.

Assumption, editable

Your numbers

Result

+180 hfreed per year

Assumptions and calculation

demi orders the files by customer, project and document type; you approve and find things faster.

6 min → 4.2 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

500 file searches × 6 min × 30% × 1.0 (manual) × 12 months = 10,800 min = 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 package

Questions about this use case

How does demi know where a file belongs?

From the content, not just the file name: demi reads which customer, project and document type it concerns and matches numbers against the ERP and CRM. Every assignment shows what demi recognized it by. Uncertain cases go on a review list.

What happens to links pointing to the old paths?

demi keeps an old-to-new list for every file. With it, after approval, demi points links in documents, shortcut files and stored paths in the ERP to the new location. Whatever cannot be switched goes on a list for IT.

Do all departments have to use the same structure?

No. There is a shared basic logic, such as customer, project and document type, and below it room for each department's needs. The person you name for this approves the structure.

How does the new structure stay in place?

demi proposes folder and name by the rule for every new file, including e-mail attachments. Deviations go to the owner of the area. So no new sprawl grows back.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases