Skip to content
Marketing & campaignsPumps & ValvesElectronics & SensorsMachinery & Plant EngineeringPlastics & Packaging+2

Your website in every language, with local search terms

demi translates your website with your glossary and the terms buyers search for in each country, and keeps every language current.

Today

The German site is current, the English one a year old, and the French one does not even show the new product line. It was translated word for word, with terms nobody in the target country searches for and with units and standards that mean nothing there. Every change to the German page would have to be carried into five languages, and there is no time for that.

An example

Fibrana sells coated PA 6.6 fabrics to France, Italy and the USA, but the English website is 14 months old and the French one does not show the GW series at all. The agent translates 38 product pages with the 900-term glossary and proposes the terms searched for in each market, such as “toile enduite” instead of the literal “tissu revêtu” for France and “industrial fabrics” instead of “technical textiles” for the USA. For the US pages it converts 220 g/m² to 6.5 oz/yd² and the 160 cm width to 63 in, and cites the NFPA 701 flame test instead of DIN 4102, because the test report for it is in the QM system. The sales partner in Lyon changes three terms and approves the French version.
Fictional company, typical workflow.

Your data, wherever it lives

Your website lives today in the content management system, product values in the PLM, the glossary and earlier translations in Excel lists, Word files and SharePoint, test reports and approvals in the QM system and references per country in the CRM; what visitors search for shows in your website analytics. demi reads, understands and links them, with your rights. The AI brings every language version level with the German page within days, and your reviewers in each country decide what goes live.

Where the data lives today

  • Web & portals
  • PLM
  • QM system
  • CRM
  • Office files
  • SharePoint
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 the website and content management system, PLM, QM system, CRM, your glossary and earlier translations in spreadsheets and documents. demi replaces nothing and links every page with the master data, test reports, approvals and references it rests on. The search terms that bring visitors from each country today are added.

  2. 2 · PermitPermission Layer

    Only approved pages are translated, and values come unchanged from master data. A standard or approval appears in a market only if the evidence for it is in the QM system, references only with the customer's approval. A native speaker in-house or at the sales partner approves each language, the glossary owner approves new terms, and everything is recorded.

  3. 3 · ActIntelligence Layer

    The agent translates with your glossary and proposes, per market, the terms buyers there actually search for and write in enquiries. It converts units, for example to inches, PSI or Fahrenheit, inserts the standards and approvals valid there, picks references from the region and suggests slogans that work in the local language. When the German page changes, it brings every language up to date.

How it runs

  1. 1

    The agent reads the German website, your glossary and earlier translations and shows, per language, which pages are missing or outdated.

  2. 2

    For each target market it finds the terms buyers there search for and write in enquiries, and matches them against the glossary.

  3. 3

    It translates and adapts: units, the standards and approvals valid there, references from the region, slogans in the local language.

  4. 4

    Native-speaking reviewers in-house or at the sales partner check and approve their language.

  5. 5

    When the German page changes, the agent proposes the change in every language until all are level again.

What changes

  • Every language version as current as the German page

  • Terms that people in the target country actually search for

  • Only approvals that really exist for that country

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

+144 hfreed per year

Assumptions and calculation

demi translates and maintains each page with glossary and local search terms; your reviewers approve.

45 min → 27 min per case

How does it run today?

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

How we calculate

40 translated pages × 45 min × 40% × 1.0 (manual) × 12 months = 8,640 min = 144 h

Value per year, before demi costs

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

+€9,360

gained per year

144 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 what buyers in the target country search for?

From the search terms that bring visitors from that country to your website today, from enquiries and e-mails of customers there, and from public trade portals and websites in that market. The agent shows every suggestion with its source and frequency. You decide which terms go into the glossary.

How are units, standards and approvals adapted?

The agent converts units by fixed rules from master data and links every converted value to the original. It cites standards and approvals in a market only if the evidence for them is in the QM system; if it is missing, it leaves the statement out and flags it. So every converted value has its original, and every standard or approval its evidence.

What happens when the German page changes?

The agent detects the change, shows it per language side by side and translates only the changed passages. The reviewers see exactly what is new and approve it. An overview shows at any time which language version is lagging behind.

Who approves a language version?

A native speaker in your company or at the sales partner in that country, whom you appoint. They see the translation, glossary terms and sources side by side and edit directly in the draft. Their changes flow into the glossary and the next translation.

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