Skip to content
Sales & quotingPumps & ValvesElectronics & SensorsMachinery & Plant EngineeringMetal & Machining+5

Plan a price increase and roll it out per customer

See in advance what a price increase brings per customer and where fixed prices and clauses apply. Every customer gets their own letter.

Today

The price increase goes out across the board: same rate, same letter for everyone. Then the calls come: customers with fixed prices until year end, frame agreements with material price clauses, key accounts whose notice period was missed. Where margins are thin the increase falls short, and good customers take the full hit for no reason.

An example

Tannried Möbelwerk has to raise prices because chipboard, HPL and fittings have become more expensive. Sales management has three scenarios calculated: a flat 6%, tiered rates by customer group, or a rate per product group by material share. The agent calculates the effect on revenue and contribution margin for 412 customers and 1,860 articles, finds 23 frame agreements with fixed prices until 31 March and nine with a material price clause where only the index counts, and reports that a hotel chain already received a material surcharge for table TI 1.800 × 900 in July. Sales management picks the rate per product group; the next morning 380 letters, each with the customer's own price list, are ready for approval.
Fictional company, typical workflow.

Your data, wherever it lives

Everything a price increase needs sits in many places today: prices, volumes and costs in the ERP, frame agreements and price clauses as PDFs in the DMS, special arrangements in e-mails and the CRM, the last price increase in a spreadsheet. demi reads, understands and links them per customer, with your rights. Effect, exceptions and letters are ready after a day instead of weeks of spreadsheets and mail merges, and sales management decides.

Where the data lives today

  • ERP
  • CRM
  • DMS & archive
  • Office files
  • E-mails
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, DMS, spreadsheets and e-mail. demi replaces nothing and joins sales volumes, prices and costs per customer and article with frame agreements, price clauses, special arrangements and the surcharges already charged this year.

  2. 2 · PermitPermission Layer

    Margins and price floors are visible only to sales management and controlling; each sales person sees their own customers. Letters go out only after sales management approves them, and new prices reach the ERP only after approval. Every approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent calculates each scenario exactly from the last twelve months' volumes, prices and costs and shows the effect on revenue and contribution margin per customer. It reads contracts and arrangements, flags fixed prices, index clauses and notice periods with the passage they come from, and writes each customer's letter and price list in their language.

How it runs

  1. 1

    Sales management sets the reason and the scenarios: across the board, per customer group or per product group by material share.

  2. 2

    The agent calculates the effect on revenue and contribution margin per customer and article.

  3. 3

    It flags fixed prices with their end date, index clauses, notice periods and surcharges already charged.

  4. 4

    Each customer gets a letter and a price list with their own articles, old and new price and effective date.

  5. 5

    Sales management approves: the letters go out, and the new prices reach the ERP on the effective date.

What changes

  • Increases where they stick, not across the board

  • Fixed prices and clauses caught before a letter goes out

  • Every customer gets their own letter with their own articles

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

+108 hfreed per year

Assumptions and calculation

demi calculates the effect per customer, checks contracts and writes letter and price list; you 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

30 customer price lists × 45 min × 40% × 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 package

Questions about this use case

How does demi know about fixed prices and price clauses?

From frame agreements, contract amendments and order confirmations in the DMS and from the conditions in the ERP. Each finding sits next to the customer with document and page. If a contract is missing or a clause is unclear, the agent flags the customer for review instead of guessing.

Can I compare several price increase scenarios?

Yes. Across the board, per customer group, per product group or with your own tiers: the scenarios sit side by side, with revenue and contribution margin per customer based on the last twelve months. How much volume the increase might cost you is an assumption you set, and the calculation follows.

Does demi write the new prices into the ERP by itself?

Only after approval. The agent prepares price lists and the change per customer and article, sales management approves, and the prices apply from the effective date. Every change is recorded and the old price stays traceable.

What happens when a customer objects to the increase?

Their reply is filed with the price increase and in the customer's record. The agent sums up the objection and puts volume, margin and contract next to it. Whether to make a concession is up to the responsible sales person, and the overview shows who has agreed and who is still open.

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