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

Match tenders to your products

Every line item gets your matching product, and deviations show up before you submit.

Today

Tenders list dozens or hundreds of items. Engineers match them to products by hand, under deadline pressure. A missed deviation from a required standard or value becomes expensive after the award.

An example

Hartwig & Brunn Pumpenwerk works on a municipal tender for pumping stations with 186 line items. The agent maps 171 of them to catalog variants, such as centrifugal pumps with Q 120 m³/h, H 80 m and PN 16. In 9 items the required efficiency class differs, and 6 need a special design in 1.4408.
Fictional company, typical workflow.

Your data, wherever it lives

Tender documents arrive from the portal as PDFs and bill-of-quantities files today, data sheets and the catalog sit in PDFs, technical data per variant in the PLM, prices in the ERP and earlier answers in Word files on the drive. demi reads, understands and links them item by item, with your rights. Every requirement sits next to your product value in minutes instead of after hours of manual work, and the bid team decides on deviations and the submission.

Where the data lives today

  • Web & portals
  • PDFs
  • PLM
  • ERP
  • Office files
  • Folders & drives
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

    Data sources in this case: the tender portal, DMS, PLM and ERP. demi replaces nothing and links the tender to the product catalog, technical data per variant, standards texts and earlier answers. Every item becomes its own record with its requirements.

  2. 2 · PermitPermission Layer

    The bid team sees the whole tender; price lists and margins are visible only to those who do the costing. The responsible bid manager approves the submission, and the approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent proposes a variant per item and sets requirement and product value side by side, with a page reference for every deviation. The data points come from your product data, not from the language model, and only approved answers are reused.

How it runs

  1. 1

    The documents from the tender portal land in the bid folder.

  2. 2

    The agent splits the bill of quantities and the specification into items with their requirements.

  3. 3

    For each item it proposes a variant from your catalog, with requirement and product value side by side.

  4. 4

    Deviations and special cases go on a separate list, each with its page reference.

  5. 5

    The bid team reviews, settles the open points and releases the submission.

What changes

  • More tenders answered with the same team

  • Deviations found before submission, not after award

  • Approved answers from earlier bids reused

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

+240 hfreed per year

Assumptions and calculation

demi maps every item to your product range and flags gaps and risks; you decide whether to bid.

4 h → 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

10 tenders × 4 h × 50% × 1.0 (manual) × 12 months = 240 h

Value per year, before demi costs

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

+$15,600

gained per year

240 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

Can it read tender documents in any format?

PDFs, spreadsheets, text documents and GAEB bills of quantities are read, scanned pages included. The documents come from the bid folder or from the e-mail they arrive in. Every item keeps a link to the document and page it comes from.

What happens to requirements our products do not meet?

They are never skipped silently. The agent lists every deviation with the requirement, your product value and the page reference. Your team decides whether to offer a special design, an alternative or nothing at all.

Does it learn from our earlier bids?

Approved answers from earlier tenders are proposed again for matching requirements, showing when and for which bid they were approved. New answers join that pool once you approve them. Answers you mark as outdated are no longer proposed.

Who can see prices and margins?

Only those the org chart allows to do costing. Technical staff see items, products and deviations, but no price lists. The whole team can work on the tender without commercial terms spreading.

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