Skip to content
Sales & quotingFor every industry

Spot customers who are ordering less

Falling volumes, missing reorders and wear parts coming due, spotted early, with suggested calls for sales.

Today

Lost customers are often noticed at year end, when the revenue report turns red. Nobody watches reorder cycles or installed machines that will soon need parts. By the time sales calls, the customer has already ordered elsewhere.

An example

A Talwerk Antriebstechnik customer ordered shaft seals and gear oil for its 40 helical gearboxes every eight weeks, but nothing for five months. A complaint on order 45-1312 is still open. The agent suggests a call to the head of inside sales and attaches the complaint status.
Fictional company, typical workflow.

Your data, wherever it lives

Today order history and invoices sit in the ERP, quotes and visit reports in the CRM, service contacts and complaints in e-mails and the ticket system, and which machines run at the customer's site is often only in a service spreadsheet. demi reads, understands and links them per customer, with your rights. The AI flags falling volumes, missing reorders and wear parts that are due as soon as they show, not in the red year-end report, and the responsible sales rep decides whom to call.

Where the data lives today

  • ERP
  • CRM
  • E-mails
  • Tickets
  • Office files
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 ERP, CRM and e-mail. demi replaces nothing and joins order history, quotes, service contacts, installed machines and complaints into one record per customer. Next to every order you see what else is going on with that customer.

  2. 2 · PermitPermission Layer

    Each sales rep sees their own accounts; sales management sees the totals. The responsible rep decides what happens with a suggestion, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent calculates each customer's usual reorder rhythm per item from the order history and flags deviations, linked to complaints or lost quotes. Every alert shows the orders it was calculated from and suggests a next step.

How it runs

  1. 1

    demi evaluates the order history wherever it is available. We clarify in a conversation how the data from the ERP and CRM reaches demi.

  2. 2

    The agent works out the reorder rhythm per customer and item.

  3. 3

    Deviations and wear parts that are due are flagged.

  4. 4

    Each alert comes with possible reasons and a suggested talking point.

  5. 5

    Sales calls and records the outcome in the CRM.

What changes

  • Falling orders noticed early

  • More reorder and spare-parts revenue

  • Sales time spent where it counts

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

+77 hfreed per year

Assumptions and calculation

demi spots falling volumes and wear parts that are due; you call the right customers.

4 h → 2.4 h per case

How does it run today?

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

How we calculate

4 customer reviews × 4 h × 40% × 1.0 (manual) × 12 months = 77 h

Value per year, before demi costs

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

+$5,005

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 package

Questions about this use case

How does it learn reorder cycles?

From your actual order history per customer and item. It works out the usual intervals and quantities and flags when an order is clearly missing or smaller. You set the threshold.

Does it work for project business?

Partly. One-off plants have no reorder rhythm. There the agent looks at the installed base instead: service intervals, wear parts and machines reaching an age where a retrofit makes sense.

Can it combine service and sales data?

Yes, that is what makes the alert useful. Next to the missing order you see the customer's open tickets, complaints and lost quotes, as far as you are allowed to see them.

What if a customer simply orders seasonally?

The agent recognizes recurring patterns over several years and does not report a seasonal pause as churn. If the history is short, it says so.

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