Skip to content
Sales & quotingPumps & ValvesElectronics & SensorsWater & EnvironmentMachinery & Plant Engineering+3

Route each requirement to the right department

A large requirements package becomes a responsibility list: which department answers, which proof is missing, what is must and what is can.

Today

A large requirements package has hundreds of lines, and they belong to different departments. The proposal team sorts them by hand into a responsibility matrix, often for a week. Meanwhile the departments wait and the deadline runs.

An example

Brandl Anlagenbau GmbH receives a requirements package of 1,480 lines for a combined heat and power plant. The agent assigns them to 9 departments: 212 go to electrical engineering, 164 to service and 38 to sales. 57 lines are unclear and are ready as questions for the customer.
Fictional company, typical workflow.

Your data, wherever it lives

The requirements package arrives as a PDF, Word file or table, the responsibilities sit in the organisation chart and in old matrices, and the answers of earlier proposals in the DMS. demi reads, understands and links them, with your rights. The AI assigns the requirements to departments, marks must and can and drafts first answers. The departments check their lines, and the head of proposals releases the whole package.

Where the data lives today

  • PDFs
  • Office files
  • DMS & archive
  • PLM
  • ERP
  • E-mails
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 requirements package comes as a PDF, Word file or table from the mailbox or DMS. demi replaces nothing and links it to your organisation, earlier proposal answers and the product data in the PLM and ERP. The requirements become single records, linked to the tender.

  2. 2 · PermitPermission Layer

    The proposal team and the departments see the list. The departments work on their own lines, and the head of proposals releases the whole.

  3. 3 · ActIntelligence Layer

    The agent assigns requirements to departments by subject, recognises must and can and which proof a requirement asks for. It proposes a draft from earlier answers and collects what is unclear.

How it runs

  1. 1

    File the requirements package; clarify the data sources: mailbox, DMS and organisation data.

  2. 2

    The agent splits the package into single requirements.

  3. 3

    It assigns them to the responsible departments and marks must, can and proof.

  4. 4

    The departments check their lines and correct the assignment.

  5. 5

    The proposal team merges the answers and releases the whole.

What changes

  • Less manual work sorting the requirements

  • Departments get only their own requirements

  • Open questions put to the customer early

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

+691 hfreed per year

Assumptions and calculation

demi assigns the requirements to departments and drafts answers; your departments check their lines.

16 h → 11.2 h per case

How does it run today?

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

How we calculate

12 requirements packages × 16 h × 30% × 1.0 (manual) × 12 months = 691 h

Value per year, before demi costs

Freed per year+691 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

+€44,915

gained per year

691 h ÷ 1,760 h per role = 0.4 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

Which departments does the agent know?

The ones you give it: from the organisation chart, from responsibility lists of earlier projects or from a table you upload. You add new departments in the assignment.

What if a requirement belongs to several departments?

The agent enters one lead department and names the others involved. You can change the assignment at any time, and the change stays visible in the list.

How does it tell whether something is must or can?

It reads the wording, such as "shall", "should" or "may", and the weighting in the document. Where the document says nothing, it marks the line for clarification.

Is this different from matching against the product range?

Yes. Matching asks whether your product meets a requirement. This is about who in your company answers it and with what.

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