Today
The newsletter goes to everyone: dosing pumps to the customer with centrifugal pumps, training for product lines they never bought. Anyone who has found nothing for their equipment in three issues no longer opens the fourth. Yet the ERP and the service history record exactly which unit runs where, but nobody has the time to build a separate issue for every customer from it.
An example
Hartwig & Brunn Pumpenwerk plans its November issue with four blocks: a new mechanical seal kit for KP centrifugal pumps built up to 2015, a maintenance tip on bearing lubrication in hot-water service, a frequency inverter retrofit for part-load operation, and two dosing pump training dates in Schwarzenbach. The agent matches 1,340 recipients against orders, serial numbers and service tickets. A municipal utility running eight KP DN 100 in 1.4408 from 2014 in its district heating network gets the seal kit, the tip and the retrofit, a dairy that runs only dosing pumps gets only the training dates, and 210 recipients without matching equipment get nothing this time. Marketing checks 20 samples and approves in the morning.
Your data, wherever it lives
Which equipment a customer runs is recorded today in orders and serial numbers in the ERP and in tickets and service reports; contacts and consents sit in the CRM, maintenance intervals and retrofit kits in the PLM and in PDF manuals, follow-up questions in e-mails. demi reads, understands and links them, with your rights. The AI assembles a separate issue for every recipient within minutes, and your marketing team approves what is sent.
Where the data lives today
- ERP
- CRM
- Tickets
- PLM
- PDFs
- E-mails
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the ERP, CRM, ticket system, PLM, manuals and service bulletins as PDFs, and your newsletter system. demi replaces nothing and links orders, serial numbers, build years, materials and service cases into each customer's installed base. demi maps news, maintenance notes and retrofit kits from the PLM to the product lines they apply to.
- 2 · PermitPermission Layer
Only contacts with valid consent in the CRM are written to, and unsubscribes take effect at once. Each customer sees only their own equipment; prices, service cases and contacts of other customers never appear. The account manager can hold a customer back from an issue, and the issue goes out only after marketing approves it, which is recorded.
- 3 · ActIntelligence Layer
The agent works out each customer's installed base and checks which blocks of the issue fit it: a new accessory, a maintenance tip, a retrofit, a training date nearby. It assembles a separate issue for every recipient and writes the introduction around their equipment. Values and product lines come from master data; where the base is uncertain, it leaves the block out.
How it runs
- 1
Marketing plans the issue: news, maintenance tips, retrofits and training dates, each with the product lines it applies to.
- 2
The agent works out each customer's installed base: units, build years, materials and service history.
- 3
It assembles a separate issue for every recipient from the matching blocks, in their language.
- 4
Marketing checks samples and approves; account managers can hold individual customers back.
- 5
Replies and clicks land as a task with the responsible account manager, naming the unit concerned.
What changes
Newsletters that get read because they concern the reader's own equipment
Spare parts, retrofits and training reach the right customers
Plan once, send each customer what fits
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
+58 hfreed per year
Assumptions and calculation
demi assembles each issue to match every customer's equipment; you check and approve.
12 h → 7.2 h per case
How we calculate
1 newsletter issues × 12 h × 40% × 1.0 (manual) × 12 months = 58 h
Value per year, before demi costs
Freed per year+58 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
+$3,770
gained per year
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 which equipment a customer runs?
From orders and serial numbers in the ERP, commissioning and service reports, and spare part orders. If a ticket shows that a unit was decommissioned or replaced, the agent takes it out. When an account manager corrects the base, the correction applies from the next issue.
Are we allowed to contact our customers this way?
The agent writes only to contacts with valid consent, and unsubscribes take effect at once. Which data may be used for the selection, you decide with your data protection officer. Every issue can be traced in the log together with its selection rules.
What if a customer has an open complaint?
Then the agent sees the open complaint in the ticket system and puts the customer before the account manager for a decision, instead of sending them an ad for a retrofit. The account manager releases the customer or holds them back for this issue. That way the newsletter also fits the situation at the customer.
Do we keep our newsletter system?
Yes. demi assembles the issues and hands them to the system you use today; sending, unsubscribe link and statistics stay there. Opens, clicks and unsubscribes flow back, so the agent sees which blocks work for which customers.
