Use case
Quote preparation
From request to quote draft in the ERP: positions extracted and matched, availability and price rules checked, open points flagged. Sales releases.
01The problem
What the work looks like today
A request for quote arrives as an email with a PDF or a spreadsheet. Someone extracts positions, matches them to articles, checks availability and price rules, builds the quote in the ERP and sends it. For configured products or long position lists that takes hours, and the customer waits days.
02Failure modes
Where time and quality are lost
Three patterns we see in almost every operation of this kind.
- 01
Quotes go out days after the competitor's
- 02
Position-matching errors surface after the order
- 03
Price rules are applied from memory
03The agent
What the agent does, step by step
Extracts the positions from the incoming request, matches them to your article master and configuration rules, checks availability and applicable price lists, creates the draft quote in the ERP and summarises the open points: unclear positions, missing data, margin below the floor.
04Human checkpoint
Where a person decides
Sales releases every quote. The agent never sends. Discounts beyond the rule, special terms and strategic accounts are flagged to the account owner before the draft is complete.
05Control set
What is enforced and logged
Price rules and discount floors are enforced in the workflow, not suggested. Every quote draft shows which rule set and price list it used. Write access to the ERP is limited to draft status.
06Measurement
What the monthly report shows
Four numbers, against the baseline from the assessment.
- 01
Request-to-quote time
- 02
Share of positions matched automatically
- 03
Quote error rate after order
- 04
Hit rate on quotes sent within 24 hours