Today
Every week something worth telling happens in production and projects: a large system ships, a new product line is released, a colleague celebrates 25 years with the company. Marketing hears about it too late or not at all, because these occasions sit in the ERP, PLM and calendars. So the channels stay quiet, and before every trade fair the search for topics starts in a rush.
An example
On Monday at Conveyra Fördertechnik, the ERP reports the acceptance of four BK 10 t bridge cranes with an 18 m span in a gearbox maker's new assembly hall in Poland, the PLM the release of a new belt conveyor series, and the HR system three new mechatronics apprentices. The agent proposes nine posts for the next four weeks, including a countdown to the intralogistics fair in March. As the CRM holds no reference approval, it writes “a gearbox maker in Poland” and drafts the request to the customer. Marketing moves two dates and approves seven posts; two are still waiting for photos from the installation.
Your data, wherever it lives
Today these occasions are scattered across your systems: deliveries and acceptances in the ERP, new products in the PLM, certificates in the QM system, anniversaries in the HR system, trade fairs in calendars, customer approvals in the CRM, installation photos in the media library and the response to earlier posts in your social media accounts. demi reads, understands and links them, with your rights. The AI proposes finished posts with channel and date every week, and your marketing team decides what appears.
Where the data lives today
- ERP
- PLM
- QM system
- HR system
- Calendars
- CRM
- Photos, video & audio
- Social media
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, PLM, HR system, QM system, calendars, CRM, media library and your social media channels. demi replaces nothing and links deliveries, acceptances, product releases, certificates, anniversaries and dates with the photos, project data and customer approvals that belong to them. demi schedules approved posts into the channels.
- 2 · PermitPermission Layer
The agent never uses confidential orders, projects under NDA or export-controlled deliveries as material. Customer names appear only with a reference approval in the CRM, anniversaries only for people who have agreed; the agent never sees salaries or appraisals. The department checks every post and marketing approves it, and the approval is recorded.
- 3 · ActIntelligence Layer
The agent checks the systems daily against the rules marketing sets, rates each occasion by news value and places it in the editorial calendar. It proposes channel and date and writes the draft with facts from the system, such as load capacity, span or destination country. If a photo is missing, it asks the project manager for one; after publishing, it shows which topics land.
How it runs
- 1
Marketing defines once which occasions count: deliveries above a certain size, new products, certificates, anniversaries, trade fairs.
- 2
Every day the agent checks the ERP, PLM, HR system, QM system and calendars for new occasions.
- 3
For each occasion it proposes channel, date and draft, with facts from the system and matching photos.
- 4
The department checks the facts; marketing edits and approves.
- 5
Posts go out on schedule, and the agent shows which topics work best.
What changes
Material for every channel, every week
No project, product or anniversary goes unnoticed
Marketing hears about occasions before they are over
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
+108 hfreed per year
Assumptions and calculation
demi finds occasions in your systems and drafts dated posts; you check and approve.
90 min → 63 min per case
How we calculate
20 posts × 90 min × 30% × 1.0 (manual) × 12 months = 6,480 min = 108 h
Value per year, before demi costs
Freed per year+108 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
+€7,020
gained per year
108 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 packageQuestions about this use case
Which occasions does demi pick up?
Anything your systems record as an event: deliveries and acceptances, large orders, released products, new certificates, anniversaries, apprentice starts, trade fairs and talks. You set the rules, for example from which order size a delivery counts. You set up new kinds of occasions once.
What about confidential orders and customer names?
Orders under NDA and export-controlled deliveries are blocked as material. The agent names a customer only if the CRM holds a reference approval; otherwise it writes neutrally, such as “a gearbox maker in Poland”, and drafts the request to the customer. Marketing decides what goes out.
How does demi handle personal data, for example for anniversaries?
The agent sees only name, department and start date, and only for people who have agreed to be featured. Salaries, absences and appraisals stay locked in the HR system. Anyone who appears in a post sees the draft before it is approved.
What if there are no photos for an occasion?
Then the agent searches the media library for images of the system, the product line or the project. If it finds nothing approved, it asks the project manager or the fitter for photos and sends a shot list along. Until then, the post stays open in the calendar.
