Skip to content
Sales & quotingFor every industry

Learn from lost quotes

Won and lost quotes analysed by price, delivery time, technical fit and customer, so the patterns show.

Today

Lost quotes are closed without a reason, or with the single word “price”. Nobody knows which product lines, delivery times or customer types lose most often. So the same mistake repeats in the next quote.

An example

At Talwerk Antriebstechnik the agent shows that 31 of 44 quotes for bevel gearboxes with delivery times above twelve weeks were lost. Price is rarely the recorded reason; in their e-mails, customers mostly mention an earlier delivery date.
Fictional company, typical workflow.

Your data, wherever it lives

Today quotes and loss reasons, often just the word “price”, sit in the CRM, orders and lead times in the ERP, the sales team's quote list in a spreadsheet, and the real reasons in e-mails and visit notes. demi reads, understands and links them per quote, customer and product, with your rights. The AI analyses a year of quotes in an hour instead of days, every reason with its source, and the head of sales decides what changes.

Where the data lives today

  • CRM
  • ERP
  • 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 CRM, ERP and e-mail. demi replaces nothing and links quotes, orders, loss reasons and visit notes to customer and product. Won and lost quotes sit in one view.

  2. 2 · PermitPermission Layer

    Sales sees its own region, management sees everything, and margins are visible only to those allowed to see them. Sales management decides whether prices, delivery times or messaging change, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads loss reasons from notes and e-mails and maps them to consistent categories, each with its source. It computes win rates per segment from quote and order records, not from estimates.

How it runs

  1. 1

    Quotes and orders from the ERP and CRM are brought together.

  2. 2

    The agent reads loss reasons from notes and e-mails and categorises them.

  3. 3

    Win rates are calculated by product line, delivery time, region and customer type.

  4. 4

    You discuss the patterns and adjust prices, delivery dates or approach.

What changes

  • Clear reasons behind lost business

  • Better decisions on price and delivery time

  • Sales learns from every quote

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 analyses won and lost quotes by price, lead time and technology; you draw the conclusions.

8 h → 4.8 h per case

How does it run today?

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

How we calculate

2 reviews × 8 h × 40% × 1.0 (manual) × 12 months = 77 h

Value per year, before demi costs

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

+€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

Where do the loss reasons come from?

From the CRM field where it is maintained, otherwise from e-mails, visit notes and call notes. Every reason shows the passage it came from. That way you can check the agent read it correctly.

Does every quote need a recorded loss reason?

No. Where no reason is recorded, the agent searches the e-mail thread and the notes. If it finds nothing, the quote stays marked “no reason” instead of getting an invented one.

Can I compare regions or product lines?

Yes, by product line, region, customer type, delivery time or quote value. Each sales rep sees only the regions they are authorised for.

How many quotes does a reliable pattern need?

Patterns appear once a group has enough closed quotes. If a group is too small, the agent says so instead of showing a rate that means little.

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